project-loop-harness 0.5.2__tar.gz → 0.5.4__tar.gz

{project_loop_harness-0.5.2/src/project_loop_harness.egg-info → project_loop_harness-0.5.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: project-loop-harness
-Version: 0.5.2
+Version: 0.5.4
 Summary: Local control plane for agentic project development loops
 Author: Project Loop Harness Contributors
 License: MIT
@@ -189,8 +189,9 @@ exist, the project does not claim external adoption.
 - [Security](SECURITY.md) and [Contributing](CONTRIBUTING.md).
 
 Advanced contracts stay in `docs/`: completion packets, evidence sets,
-completion policy, context packs, code context, workflow execution, Council
-Profile, trace/resume, reports, migrations, and dashboard data.
+completion policy, [Harness Gap Reports](docs/gap-report-v1.md), context packs,
+code context, workflow execution, Council Profile, trace/resume, reports,
+migrations, and dashboard data.
 
 ## Local development
 

{project_loop_harness-0.5.2 → project_loop_harness-0.5.4}/README.md

@@ -154,8 +154,9 @@ exist, the project does not claim external adoption.
 - [Security](SECURITY.md) and [Contributing](CONTRIBUTING.md).
 
 Advanced contracts stay in `docs/`: completion packets, evidence sets,
-completion policy, context packs, code context, workflow execution, Council
-Profile, trace/resume, reports, migrations, and dashboard data.
+completion policy, [Harness Gap Reports](docs/gap-report-v1.md), context packs,
+code context, workflow execution, Council Profile, trace/resume, reports,
+migrations, and dashboard data.
 
 ## Local development
 

{project_loop_harness-0.5.2 → project_loop_harness-0.5.4}/agent-tasks/0199-v052-release-publication.md

@@ -1,6 +1,6 @@
 # 0199: v0.5.2 release preparation and publication
 
-- **Status:** Active; publication authorized
+- **Status:** Done; published and publicly verified
 - **Milestone:** v0.5.2 Reliability and Harness Minimization
 - **Priority:** P0
 - **Size:** M
@@ -44,4 +44,13 @@ uncollected external first-use cohort as adoption proof.
 
 ## Completion evidence
 
-- Pending publication and public-artifact verification.
+- Release commit: `bbe14cf5a8375e72eaa121c1b8a5a96362560d1d`
+- GitHub Release: `v0.5.2`
+- Green release-commit CI run: `29638815262`
+- Trusted Publishing run: `29639130354`, success
+- Public wheel SHA-256:
+  `d7f5dda21e721c3405e694991fa7bbc844f7a31daecb4572efd67c48ffc81048`
+- Public sdist SHA-256:
+  `529e2236628d70cef2efade82a4ff3017649658e960e6c5b3e8afc0e2f1f601b`
+- Clean public install, strict validation, render, and pipx update: passed
+- `docs/evidence/0199-v052-publication-closeout.md`

project_loop_harness-0.5.4/agent-tasks/0200-gap-report-contract.md

@@ -0,0 +1,83 @@
+# 0200: gap-report/v1 Harness Gap Evidence
+
+- **Status:** Complete
+- **Milestone:** Harness Engineering Feedback Loop
+- **Priority:** P0
+- **Size:** L
+- **Dependency:** 0146 Work Brief, 0197 Harness Ablation, strict Evidence resolvers
+- **Project Loop:** Goal `G-0058`, Task `T-0122`, Feature `F-0064`, Story `US-0062`, Test `TC-0135`
+- **DB schema:** remains 8
+
+## Goal
+
+Add the one missing layer identified while reviewing the Harness Engineering
+proposal: record the earliest failed handoff and a closed gap classification as
+immutable, target-bound Evidence. Candidate lessons stay isolated until a
+hash-bound human decision authorizes promotion; authorization must not claim
+that the lesson has already been applied to its durable owner.
+
+## Reviewed design corrections
+
+The inherited Cockpit plan is accepted with these corrections:
+
+1. Gap targets include observed execution boundaries (`workflow_run` and
+   `agent_job`) in addition to Goal, Task, Feature, and Defect targets.
+2. `pcl gap promote` records `gap_lesson_promotion_approved` with
+   `application_status=pending`; it never edits AGENTS.md, Skills, tests, or
+   other durable owners automatically.
+3. Read paths verify exactly one anchor event, one target link, canonical path
+   shape, regular-file identity, recorded bytes, and SHA-256 before returning a
+   healthy report or accepting promotion.
+4. Candidate lessons require cited Evidence before promotion so uncorroborated
+   producer self-report cannot become approved policy by implication.
+
+## Contract
+
+`gap-report/v1` is a producer-authored claim artifact with:
+
+- producer, timestamp, and a target;
+- optional related completion-packet / Evidence / Workflow Run references;
+- one `earliest_failed_handoff` with `stage` and `description`;
+- one closed `gap_class`:
+  `context`, `capability`, `domain_ownership`, `authority`, `proof`,
+  `feedback_delivery`, or `worker_limitation`;
+- zero or more candidate lessons in an object keyed by stable, structurally
+  unique `lesson_id` values, each with a proposed `durable_owner` and
+  supporting Evidence references.
+
+The diagnosis is a claim, not a fact. `worker_limitation` remains especially
+provisional; one report cannot establish a general model limitation.
+
+## CLI scope
+
+- `pcl contract validate --type gap-report/v1 FILE`
+- `pcl gap add FILE --summary ... [--dry-run]`
+- `pcl gap show --evidence E-XXXX`
+- `pcl gap list [--target TYPE:ID] [--gap-class CLASS]`
+- `pcl gap promote E-XXXX --lesson LESSON_ID --actor ... --reason ...`
+
+Human-mediated promotion records actor, recorder, Cockpit/conversation source,
+artifact hash, lesson digest, and pending durable-owner application. Non-human
+promotion and unhealthy or uncited lessons fail closed.
+
+## Acceptance
+
+1. Packaged JSON Schema and hand-written validator agree and reject unknown
+   fields, malformed IDs/real-date timestamps, invalid enums, duplicate raw
+   JSON lesson keys, and non-finite JSON.
+2. Add/dry-run/show/list are deterministic, target-bound, and zero-mutation on
+   failure; strict reads surface tampering instead of trusting the file path.
+3. Promotion is human-only, hash-bound, Evidence-corroborated, idempotent, and
+   explicitly pending application.
+4. Fresh `pcl init` installs a compact router contract once without adding a
+   parallel `.plh/`, HARNESS.md, or harness.yaml structure.
+5. No migration, dependency, completion-packet change, automatic durable-owner
+   write, hosted service, or `pcl harness review/improve` aggregator is added.
+6. Targeted tests, full pytest, Ruff, fresh-init/E2E smoke, strict validation,
+   audit check, render, and PCL completion proof pass.
+
+## Sources
+
+- Cockpit task `e22916a5` and reviewed plan
+- <https://github.com/lopopolo/harness-engineering>
+- Harness Engineering `Improve One Harnessed Job` playbook

project_loop_harness-0.5.4/agent-tasks/0201-gap-report-integrity-hardening.md

@@ -0,0 +1,43 @@
+# 0201: gap-report/v1 Integrity Hardening
+
+- **Status:** Complete
+- **Milestone:** Harness Engineering Feedback Loop
+- **Priority:** P1
+- **Size:** M
+- **Dependency:** 0200 Gap Report contract and Evidence flow
+- **Project Loop:** Goal `G-0059`, Task `T-0123`, Feature `F-0065`, Story `US-0063`, Test `TC-0136`
+- **DB schema:** remains 8
+
+## Goal
+
+Close the four integrity gaps found by the independent implementation review
+without expanding the Gap Report feature or changing completion semantics.
+
+## Corrections
+
+1. Create the artifact directory, temporary file, and final file through
+   canonical no-follow handles. Reject pre-existing directory, temporary-file,
+   or final-file symlinks without writing outside the project or mutating PLH
+   state.
+2. Make Schema and runtime validation agree on real UTC calendar timestamps.
+   Represent candidate lessons as an object keyed by `lesson_id`, and reject
+   duplicate raw JSON keys at load time so uniqueness is structural.
+3. Bind `artifact_sha256` to the exact stored bytes. Whitespace-only,
+   same-length changes must make the report unhealthy.
+4. Filter lists using the immutable class in the anchor event. Return both
+   `recorded_gap_class` and `artifact_gap_class`, and do not silently hide
+   records whose anchor class is invalid.
+
+## Acceptance
+
+1. Redirected artifact directory/temp/final paths fail with zero Evidence,
+   event, outbox, or link mutations and leave the external target unchanged.
+2. The packaged timestamp pattern and hand validator accept valid leap dates
+   and reject invalid dates and year zero; duplicate lesson keys fail loading.
+3. Same-size semantic-preserving byte drift produces
+   `artifact_hash_mismatch`.
+4. Artifact class tampering remains listed only under the recorded class and
+   exposes both recorded and artifact values.
+5. Targeted tests, full pytest, Ruff, source/wheel/sdist smoke, strict PLH
+   validation, audit check, and render complete with results recorded as
+   Evidence.

project_loop_harness-0.5.4/agent-tasks/0202-v053-local-release-preparation.md

@@ -0,0 +1,50 @@
+# 0202: v0.5.3 local release preparation
+
+- **Status:** Complete
+- **Milestone:** v0.5.3 Evidence Integrity and Harness Feedback
+- **Priority:** P0
+- **Size:** M
+- **Dependency:** 0200 Gap Report, 0201 Gap Report integrity hardening, event-anchored strict Evidence resolvers
+- **Project Loop:** Goal `G-0060`, Task `T-0124`, Feature `F-0066`, Story `US-0064`, Test `TC-0137`
+- **DB schema:** remains 8
+
+## Goal
+
+Prepare a reviewable local v0.5.3 release candidate containing the completed
+Evidence-integrity and Gap Report work. Keep publication as a separate,
+explicitly authorized operation.
+
+## Scope
+
+1. Align package, runtime, MCP fixture, task index, and release-note surfaces
+   on v0.5.3.
+2. Describe only commits actually included since public v0.5.2, preserving the
+   distinction between artifact integrity and factual validity.
+3. Run source QA, scratch-project validation/render, wheel and sdist contracts,
+   metadata checks, and a clean wheel-install smoke.
+4. Record artifact hashes and exact verification results as durable Evidence.
+5. Commit the complete local release candidate without tagging, pushing,
+   publishing, or changing pipx.
+
+## Invariants
+
+- No Git tag, push, GitHub Release, PyPI/TestPyPI upload, pipx mutation, or
+  external announcement.
+- No schema migration, dependency addition, hosted service, telemetry, or
+  unrelated repair.
+- Existing `.claude` session state and unrelated untracked files remain
+  untouched and outside the release commit.
+- Public v0.5.2 adoption documents remain historical v0.5.2 records; they are
+  not mechanically renamed to v0.5.3.
+
+## Acceptance
+
+1. `pyproject.toml`, `pcl.__version__`, CLI/MCP runtime output, wheel, and
+   sdist metadata agree on `0.5.3`.
+2. Ruff and the full pytest suite pass from the canonical source checkout.
+3. Fresh scratch init, strict doctor/validate, audit, and render pass using
+   the worktree source.
+4. Wheel and sdist build, `twine check`, extracted-sdist contract, and
+   clean-wheel init/strict-validate/render/Gap Report contract smoke pass.
+5. SHA-256 hashes, file sizes, commit boundary, known warnings, and publication
+   boundary are reviewable in a new write-once Evidence note.

project_loop_harness-0.5.4/agent-tasks/0203-v053-release-publication.md

@@ -0,0 +1,56 @@
+# 0203: v0.5.3 release publication
+
+- **Status:** Done; published and publicly verified
+- **Milestone:** v0.5.3 Evidence Integrity and Harness Feedback
+- **Priority:** P0
+- **Size:** S
+- **Dependency:** completed 0202 local release candidate; explicit owner publication instruction
+- **Project Loop:** Goal `G-0061`, Task `T-0125`, Feature `F-0067`, Story `US-0065`, Test `TC-0138`
+- **DB schema:** remains 8
+
+## Goal
+
+Publish the reviewed v0.5.3 release commit and verify the complete public
+artifact chain without converting artifact publication into an adoption claim.
+
+## Scope
+
+1. Push the reviewed release commit and require its GitHub CI matrix to pass.
+2. Create and push an annotated `v0.5.3` tag at that exact commit.
+3. Publish the GitHub Release and verify release-triggered Trusted Publishing.
+4. Verify PyPI metadata, exact artifact hashes, and a clean public install.
+5. Replace the editable pipx source with the released PyPI version and record
+   the immutable closeout evidence.
+
+## Invariants
+
+- No schema migration, dependency, telemetry, hosted state, provider execution,
+  launch post, or unrelated repair is added.
+- Publication is engineering evidence, not evidence of external adoption.
+- Existing `.claude` session state and unrelated worktree files are excluded
+  from release commits.
+
+## Acceptance
+
+1. `main`, annotated tag, GitHub Release target, package version, and public
+   PyPI artifacts all resolve to v0.5.3.
+2. Release-commit CI and Trusted Publishing succeed.
+3. Public wheel and sdist bytes match PyPI-reported SHA-256 digests.
+4. A clean PyPI install passes version, contract, init, strict validation,
+   audit, and render checks.
+5. Pipx runs the non-editable public v0.5.3 package.
+
+## Completion evidence
+
+- Release commit: `6e49ac43986e8b965f1777eef9a88f7c73236ef6`
+- Annotated tag object: `b5eb54666e8b537b17fd459bd1d9aa5cba94db89`
+- GitHub Release: `v0.5.3`, published `2026-07-20T06:30:42Z`
+- Green release-commit CI run: `29721069992`
+- Trusted Publishing run: `29721897474`, success
+- Public wheel SHA-256:
+  `0ce97a13c6deedf6525a8487aaba8080744e303c96845ee22028ad5bd623c54f`
+- Public sdist SHA-256:
+  `448166e9ed78c68ccba2c13dd4d9a20038c2e5e105b717ca97d5ebb02b07eb0a`
+- Clean public install, Gap Report contract, strict validation, audit, render,
+  and pipx replacement: passed
+- `docs/evidence/0203-v053-publication-closeout.md`

project_loop_harness-0.5.4/agent-tasks/0204-cli-stage3-entity-handlers.md

@@ -0,0 +1,28 @@
+# 0204: CLI Stage 3 entity lifecycle handlers
+
+- **Status:** Done; implemented and verified
+- **Milestone:** Post-v0.5.3 maintainability
+- **Priority:** P1
+- **Size:** M
+- **Dependency:** 0188 and the frozen split contract
+- **DB schema:** remains 8
+
+## Goal
+
+Extract Goal, Task, Feature, Story, Test, and Defect CLI orchestration from
+`cli.py` without changing observable behavior or mutation ownership.
+
+## Acceptance
+
+1. Parser definitions and service-layer transactions remain in their current
+   owners.
+2. Exact JSON/text output, errors, exit codes, events, and zero-trace
+   rejections are characterized and preserved.
+3. Targeted tests, Skill examples, distribution tests, Ruff, and full pytest
+   pass.
+
+## Completion evidence
+
+- `docs/evidence/0204-cli-stage3-entity-handlers.md`
+- Implementation commit: `d7d38ea`
+- Full regression: 1,164 passed, 1 skipped

project_loop_harness-0.5.4/agent-tasks/0205-cli-stage3-execution-evidence-handlers.md

@@ -0,0 +1,27 @@
+# 0205: CLI Stage 3 execution and Evidence handlers
+
+- **Status:** Done; implemented and verified
+- **Milestone:** Post-v0.5.3 maintainability
+- **Priority:** P1
+- **Size:** M
+- **Dependency:** 0204
+- **DB schema:** remains 8
+
+## Goal
+
+Extract Loop, Workflow, Jobs, Agent, Evidence, Verification, Decision,
+Escalation, and checkpoint CLI orchestration while preserving every mutation,
+event, outbox, artifact, and rejection contract.
+
+## Acceptance
+
+1. Services retain transaction and event ownership.
+2. Handler parity and failure zero-trace tests cover each moved family.
+3. Targeted tests, Skill examples, distribution tests, Ruff, and full pytest
+   pass.
+
+## Completion evidence
+
+- `docs/evidence/0205-cli-stage3-execution-evidence-handlers.md`
+- Implementation commit: `dd9a327`
+- Full regression: 1,169 passed, 1 skipped

project_loop_harness-0.5.4/agent-tasks/0206-cli-stage3-control-profile-handlers.md

@@ -0,0 +1,22 @@
+# 0206: CLI Stage 3 control and Profile handlers
+
+- **Status:** Complete
+- **Milestone:** Post-v0.5.3 maintainability
+- **Priority:** P1
+- **Size:** M
+- **Dependency:** 0205
+- **DB schema:** remains 8
+
+## Goal
+
+Extract Profile, contract, Evidence Set, completion, Work Brief, Gap Report,
+route/policy, initialization, audit/repair, context, index/eval, export/report,
+and remaining CLI orchestration from `cli.py`.
+
+## Acceptance
+
+1. Existing human gates, dry-run boundaries, artifacts, and update-check
+   behavior remain unchanged.
+2. Characterization tests pin moved JSON/text/error branches.
+3. Targeted tests, Skill examples, distribution tests, Ruff, and full pytest
+   pass.

project_loop_harness-0.5.4/agent-tasks/0207-command-service-responsibility-split.md

@@ -0,0 +1,21 @@
+# 0207: Command service responsibility split
+
+- **Status:** Complete
+- **Milestone:** Post-v0.5.3 maintainability
+- **Priority:** P1
+- **Size:** M
+- **Dependency:** 0206
+- **DB schema:** remains 8
+
+## Goal
+
+Turn `pcl.commands` into a compatibility facade over responsibility-specific
+domain, next-action routing, and finish-planning modules.
+
+## Acceptance
+
+1. Existing imports such as `pcl.commands.create_goal`, `loop_status`,
+   `build_next_action`, and `to_pretty_json` remain valid.
+2. Query ordering, transactions, event payloads, routing priority, and finish
+   plans remain byte-for-byte compatible where serialized.
+3. Direct service tests, next-action tests, Ruff, and full pytest pass.

project_loop_harness-0.5.4/agent-tasks/0208-cli-stage4-parser-construction.md

@@ -0,0 +1,20 @@
+# 0208: CLI Stage 4 parser construction split
+
+- **Status:** Complete
+- **Milestone:** Post-v0.5.3 maintainability
+- **Priority:** P1
+- **Size:** M
+- **Dependency:** 0207
+- **DB schema:** remains 8
+
+## Goal
+
+Split parser construction by command family while retaining one public
+`build_parser()` facade and the existing source/wheel/sdist entry points.
+
+## Acceptance
+
+1. Commands, flags, defaults, choices, help text, aliases, and parser errors
+   remain unchanged.
+2. Skill example parsing and complete help smoke checks pass.
+3. Distribution tests, Ruff, full pytest, and source/wheel/sdist smoke pass.

project_loop_harness-0.5.4/agent-tasks/0209-refactoring-integrated-verification.md

@@ -0,0 +1,23 @@
+# 0209: Refactoring integrated verification
+
+- **Status:** Complete
+- **Milestone:** Post-v0.5.3 maintainability
+- **Priority:** P1
+- **Size:** S
+- **Dependency:** 0208
+- **DB schema:** remains 8
+
+## Goal
+
+Verify the complete staged refactor as one integrated source and distribution
+surface, record durable Evidence, and close the refactoring Goal.
+
+## Acceptance
+
+1. Ruff, targeted tests, Skill examples, distribution tests, and full pytest
+   pass on the final revision.
+2. Doctor, strict validation, audit check, render, and diff check complete with
+   no new findings.
+3. Source, wheel, and sdist command/help smoke tests pass.
+4. PCL tasks are terminal, a completion packet is emitted, and the Goal is
+   closed with that packet Evidence.

project_loop_harness-0.5.4/agent-tasks/0210-v054-local-release-preparation.md

@@ -0,0 +1,52 @@
+# 0210: v0.5.4 local release preparation
+
+- **Status:** Complete
+- **Milestone:** v0.5.4 Maintainability
+- **Priority:** P0
+- **Size:** M
+- **Dependency:** 0209 Refactoring integrated verification
+- **Project Loop:** Goal `G-0063`, Task `T-0133`, Feature `F-0068`, Story `US-0066`, Test `TC-0139`
+- **DB schema:** remains 8
+
+## Goal
+
+Prepare a reviewable local v0.5.4 release candidate containing the completed
+post-v0.5.3 behavior-preserving CLI and command-service refactor. Keep remote
+CI and publication as separate, explicitly authorized operations.
+
+## Scope
+
+1. Align package, runtime, MCP fixture, baseline fixture, task index, and
+   release-note surfaces on v0.5.4.
+2. Describe only the behavior-preserving refactor included since public
+   v0.5.3; do not claim new command or runtime behavior.
+3. Run source QA, MCP conformance, advisory retrieval evaluation,
+   scratch-project validation/render, wheel and sdist contracts, metadata
+   checks, and a clean wheel-install smoke.
+4. Record artifact hashes, exact verification results, and known repository
+   audit findings as durable Evidence.
+5. Commit the complete local release candidate without pushing, tagging,
+   publishing, announcing, or changing pipx.
+
+## Invariants
+
+- No Git push or tag, GitHub Release, PyPI/TestPyPI upload, pipx mutation, or
+  external announcement.
+- No intentional command, flag, output, exit-code, transaction, event,
+  Evidence, human-gate, schema, dependency, or generated-artifact change.
+- Existing `.claude`, `.playwright-cli`, `.work`, and Project Loop lock files
+  remain outside the release commit.
+- Public v0.5.3 records remain historical v0.5.3 records; they are not renamed.
+
+## Acceptance
+
+1. `pyproject.toml`, `pcl.__version__`, CLI/MCP runtime output, wheel, and
+   sdist metadata agree on `0.5.4`.
+2. Ruff, the full pytest suite, optional MCP conformance, and the advisory
+   retrieval evaluation pass from the canonical source checkout.
+3. A fresh scratch project passes init, strict validation, clean audit, and
+   render using the source checkout.
+4. Wheel and sdist build, `twine check`, extracted-sdist contracts, and a
+   clean-wheel runtime/init/strict-validation/audit/render smoke pass.
+5. SHA-256 hashes, file sizes, candidate boundary, known warnings, and the
+   publication boundary are reviewable in a new write-once Evidence note.

{project_loop_harness-0.5.2 → project_loop_harness-0.5.4}/agent-tasks/README.md

@@ -116,7 +116,18 @@ implement from the spec file, not from prompt summaries.
 | 0197 | Layered harness minimization ablation | Harness Minimization | P0 | done (`modify`) |
 | 0197b | Layered ablation fixture materializer | Harness Minimization | P0 | done |
 | 0198 | Evidence-gated direct-flow reduction | Harness Minimization | P1 | done; not implemented after `modify` verdict |
-| 0199 | v0.5.2 release preparation and publication | v0.5.2 Reliability and Harness Minimization | P0 | active; publication authorized |
+| 0199 | v0.5.2 release preparation and publication | v0.5.2 Reliability and Harness Minimization | P0 | done; published and publicly verified |
+| 0200 | `gap-report/v1` Harness Gap Evidence | Harness Engineering Feedback Loop | P0 | done |
+| 0201 | `gap-report/v1` Integrity Hardening | Harness Engineering Feedback Loop | P1 | done |
+| 0202 | v0.5.3 local release preparation | v0.5.3 Evidence Integrity and Harness Feedback | P0 | done; local RC ready, not published |
+| 0203 | v0.5.3 release publication | v0.5.3 Evidence Integrity and Harness Feedback | P0 | done; published and publicly verified |
+| 0204 | CLI Stage 3 entity handler extraction | post-v0.5.3 maintainability | P1 | done |
+| 0205 | CLI Stage 3 execution/Evidence handler extraction | post-v0.5.3 maintainability | P1 | done |
+| 0206 | CLI Stage 3 control/Profile handler extraction | post-v0.5.3 maintainability | P1 | done |
+| 0207 | Command service responsibility split | post-v0.5.3 maintainability | P1 | done |
+| 0208 | CLI Stage 4 parser construction split | post-v0.5.3 maintainability | P1 | done |
+| 0209 | Refactoring integrated verification | post-v0.5.3 maintainability | P1 | done |
+| 0210 | v0.5.4 local release preparation | v0.5.4 Maintainability | P0 | done; local RC ready, not published |
 
 v0.3.0 dispatch order: **0113 + 0114 in parallel** (independent; different
 `evidence.py` surfaces) → **0108** (needs 0113 merged) → **0115** (freezes the
@@ -196,6 +207,22 @@ external first-use cohort remains open and no adoption claim is made. Task
 **0199** prepares, publishes, and verifies the reliability release under the
 owner's separate publication instruction.
 
+v0.5.3 packages event-anchored strict Evidence resolution and the bounded
+`gap-report/v1` feedback layer. Task **0202** prepared and verified the local
+release candidate; task **0203** published and independently verified the
+GitHub Release, Trusted Publishing run, PyPI artifacts, and clean public install.
+
+Post-v0.5.3 maintainability completes the frozen behavior-preserving split:
+**0204** entity lifecycle handlers -> **0205** execution/Evidence handlers ->
+**0206** control/Profile handlers -> **0207** `commands.py` responsibility
+split -> **0208** parser construction -> **0209** integrated verification.
+See `docs/plan-refactoring-completion.md`.
+
+v0.5.4 packages that completed behavior-preserving split as a patch release.
+Task **0210** aligns version and distribution surfaces, records local artifact
+Evidence, and keeps push, tag, GitHub Release, PyPI, and pipx changes behind a
+separate publication authorization.
+
 ## Planned next (see growth plan for scope)
 
 | Milestone | Theme |
@@ -211,6 +238,9 @@ owner's separate publication instruction.
 | v0.5.1 | Trace & Efficient Handoff: source-bound claims-not-facts handoff plus controlled cross-session/runtime resume evidence |
 | post-v0.5.1 | Behavior-preserving staged CLI split; 0184 presentation, then 0185 guide, 0186 loop status, 0187 doctor, and 0188 report-artifact handlers |
 | v0.5.2 | 0189 config-ready adoption and frozen cohort → 0190 participant kit and deterministic proof evaluator → five-user outcome cohort → observed-friction repair |
+| v0.5.3 | published and publicly verified; strict copied-Evidence resolution → 0200 Gap Report contract → 0201 integrity hardening → 0202 local RC → 0203 publication closeout |
+| post-v0.5.3 | complete frozen CLI/commands refactor: 0204 → 0205 → 0206 → 0207 → 0208 → 0209 |
+| v0.5.4 | behavior-preserving CLI/commands maintainability release → 0210 local RC → separately authorized publication |
 
 Everything with an ID below 0102 is completed design history; see `TASKS.md`
 for the one-line summary of each.

{project_loop_harness-0.5.2 → project_loop_harness-0.5.4}/docs/command-guide.md

@@ -28,3 +28,19 @@ The guide is available before `pcl init` and does not create `.project-loop`.
 It complements `pcl next --json`: use `guide` to learn a purpose-oriented route
 and `next` to read the authoritative recommendation for the current project
 state.
+
+## Record a repeated harness failure
+
+When a bounded trajectory exposes an environment problem rather than only a
+product defect, validate and record a `gap-report/v1`:
+
+```bash
+pcl contract validate --type gap-report/v1 gap-report.json --json
+pcl gap add gap-report.json --summary "Earliest failed handoff" --dry-run --json
+pcl gap add gap-report.json --summary "Earliest failed handoff" --json
+pcl gap list --target task:T-0001 --gap-class context --json
+```
+
+Candidate lessons remain claims. `pcl gap promote` requires hash-bound human
+provenance and records approval with durable-owner application still pending.
+See [Gap Report v1](gap-report-v1.md).

project_loop_harness-0.5.4/docs/evidence/0199-v052-publication-closeout.md

@@ -0,0 +1,60 @@
+# 0199 v0.5.2 publication closeout
+
+**Verified:** 2026-07-18
+
+**Outcome:** published and publicly verified
+
+## Immutable source chain
+
+- Release commit: `bbe14cf5a8375e72eaa121c1b8a5a96362560d1d`
+- Annotated tag object: `7643ce5ff982c79822dcef9dcf77396f55f9cc7a`
+- Tag target: `bbe14cf5a8375e72eaa121c1b8a5a96362560d1d`
+- GitHub Release:
+  `https://github.com/mocchalera/project-loop-harness/releases/tag/v0.5.2`
+- Release published at: `2026-07-18T09:25:20Z`
+- Release is neither draft nor prerelease.
+
+## CI and publication
+
+- The first candidate CI run `29638536535` failed because the newly frozen
+  ablation tests could not resolve historical commits from a shallow checkout.
+  `docs/evidence/0199-v052-ci-history-repair.md` records the bounded workflow
+  repair; no runtime or test expectation was weakened.
+- Release-commit CI run `29638815262`: success across Python 3.10, 3.11, 3.12,
+  and 3.13; Ubuntu/Windows MCP conformance; Windows CLI smoke; build; Twine;
+  installed CLI smoke; and sdist contracts.
+- Release-triggered Trusted Publishing run `29639130354`: success.
+- Build-distributions job `88066532078`: success.
+- Publish-to-PyPI job `88066563827`: success.
+
+## Public PyPI artifacts
+
+PyPI reports `project-loop-harness 0.5.2`, `Requires-Python >=3.10`, one wheel,
+and one sdist. Downloaded bytes matched PyPI JSON digests.
+
+| Artifact | Size | Uploaded | SHA-256 |
+| --- | ---: | --- | --- |
+| `project_loop_harness-0.5.2-py3-none-any.whl` | 487878 | `2026-07-18T09:26:10.519255Z` | `d7f5dda21e721c3405e694991fa7bbc844f7a31daecb4572efd67c48ffc81048` |
+| `project_loop_harness-0.5.2.tar.gz` | 1401906 | `2026-07-18T09:26:12.162754Z` | `529e2236628d70cef2efade82a4ff3017649658e960e6c5b3e8afc0e2f1f601b` |
+
+## Clean public install
+
+A new Python 3.13 venv installed
+`project-loop-harness==0.5.2` from PyPI with `--no-cache-dir` and no
+`PYTHONPATH`:
+
+- `pcl --version`: `pcl 0.5.2`;
+- `pcl init` on a fresh temporary project: passed;
+- `pcl validate --strict --json`: `ok: true`, no errors or warnings;
+- `pcl render --json`: generated dashboard HTML and JSON successfully.
+
+The existing pipx installation was upgraded from 0.5.1 to 0.5.2 and both
+`pcl` and `pcl-mcp` are registered. Pipx separately reported an invalid
+interpreter for unrelated package `haconiwa`; no repair was attempted because
+it is outside this release.
+
+## Claim boundary
+
+The external five-person first-use cohort is still unrun. This release proves
+artifact integrity and engineering verification only; it does not prove user
+adoption, activation thresholds, or seven-day reuse.