@cassiomc1/forgeloop 1.10.0 → 1.10.1

package/DOCS_INDEX.md

@@ -38,6 +38,7 @@ integration and guide context. Use this map before editing documentation.
 | Knowledge sources and provenance | [`docs/KNOWLEDGE_SOURCES.md`](./docs/KNOWLEDGE_SOURCES.md) | Snapshot, licensing observations, source roles, accepted/skipped concepts, and reuse boundaries |
 | Documentation guide | [`docs/DOCUMENTATION_GUIDE.md`](./docs/DOCUMENTATION_GUIDE.md) | Rules and checklist for modifying documentation |
 | Current release checklist | [`docs/RELEASE_CHECKLIST.md`](./docs/RELEASE_CHECKLIST.md) | Package, protocol, attestation, integration, and publication gates |
+| Core npm package contents | [`docs/PACKAGE_CONTENTS.md`](./docs/PACKAGE_CONTENTS.md) | Published consumer surface, intentional inclusions, exclusions, and clean-room verification |
 | ForgeLoop 1.6.1 release checklist (historical) | [`docs/RELEASE_CHECKLIST_1_6_1.md`](./docs/RELEASE_CHECKLIST_1_6_1.md) | Verification adapter boundary, isolation invariants, and publication gates |
 | ForgeLoop 1.5/MCP release checklist (historical) | [`docs/RELEASE_CHECKLIST_1_5_MCP.md`](./docs/RELEASE_CHECKLIST_1_5_MCP.md) | Integration API v1, MCP package, and publication gates |
 | ForgeLoop 1.4 release checklist | [`docs/RELEASE_CHECKLIST_1_4.md`](./docs/RELEASE_CHECKLIST_1_4.md) | Claim-recovery, compatibility, package, and publication gates |
@@ -57,6 +58,13 @@ integration and guide context. Use this map before editing documentation.
 | Code Attestation Chain | [`docs/CODE_ATTESTATION.md`](./docs/CODE_ATTESTATION.md#completion-flow) | Completion, exact-content manifest, in-toto statement, optional signing, and range coverage |
 | Real Execution Proof of Concept (PoC) | [`poc/README.md`](./poc/README.md) | Non-normative, reproducible public engineering workload, audit evidence, and technical audit. Normative behavior remains owned by [`LOOP_ENGINEERING.md`](./LOOP_ENGINEERING.md). |
 
+## Recent implementation review
+
+The repository-local [Astra implementation record](./docs/ASTRA_IMPLEMENTATION.md)
+maps the completed findings to code, tests, measurements, and remaining limits.
+Use the canonical guides below for operational instructions; the audit record
+is historical evidence and is not part of the published core package.
+
 ## Audience map
 
 | I am a... | Start here |
@@ -98,6 +106,7 @@ integration and guide context. Use this map before editing documentation.
 - **Integrate a new AI environment**: [`PROTOCOL_INTEGRATION.md`](./PROTOCOL_INTEGRATION.md)
 - **Map ForgeLoop state into an external runtime/orchestrator**: [`ORCHESTRATOR_INTEGRATION.md`](./ORCHESTRATOR_INTEGRATION.md)
 - **Edit documentation safely**: [`docs/DOCUMENTATION_GUIDE.md`](./docs/DOCUMENTATION_GUIDE.md)
+- **Audit the npm package boundary**: [`docs/PACKAGE_CONTENTS.md`](./docs/PACKAGE_CONTENTS.md)
 - **Verify source-content attestations**: [`docs/CODE_ATTESTATION.md`](./docs/CODE_ATTESTATION.md)
 - **Understand narrow verification and checker binding**: [`docs/REVISION_PROVIDERS.md`](./docs/REVISION_PROVIDERS.md#differential-verification-scope)
 - **Inspect the governed diagrams**: [`docs/diagrams/README.md`](./docs/diagrams/README.md)

package/LOOP_ENGINEERING.md

@@ -393,8 +393,8 @@ DESTRUCTIVE_ACTION_REQUIRED
 ```
 
 Multiple reasonable aesthetic or positioning choices do not justify a question.
-The deterministic support helper in `src/core/decision-classification.js`
-validates this boundary; it does not use an LLM or parse natural language.
+The executable test example in `tests/helpers/decision-classification.js`
+illustrates this boundary; runtime authority remains with this protocol and the task contract. The example does not use an LLM or parse natural language.
 
 ### Contract-before-clarification sequence
 
@@ -508,8 +508,8 @@ The compatibility distinction is explicit:
 "Installed" and "compatible" are different claims. A harness can have an
 external workflow installed and still be `INCOMPATIBLE WITH AUTONOMOUS MODE`.
 Use that wording instead of calling the workflow broken. The deterministic
-support helper in `src/core/workflow-compatibility.js` evaluates this boundary;
-it does not modify `src/core/decision-classification.js`, invoke an LLM, or
+test example in `tests/helpers/workflow-compatibility.js` exercises this boundary;
+it does not modify `tests/helpers/decision-classification.js`, invoke an LLM, or
 redesign a runtime, arbiter, supervisor, or approval broker.
 
 For the sixth blind conformance run, exclude mandatory-approval workflows at

package/LOOP_SYSTEM_DESIGN.md

@@ -561,3 +561,26 @@ canonical trace/reflection evidence. They preserve unknown usage values and
 only compare efficiency when a project-local reference scenario exists. The
 existing diagnostic and reflection model remains the authority for information
 gain, intervention effectiveness, failure signatures, and oscillation.
+
+## Transaction identity and diagnostic retention
+
+The transaction context binds the physical project root and task ID. Nested
+operations reject cross-project reuse, even when task IDs match. Filesystem
+aliases of the same physical project remain compatible. Reads and writes of
+transaction-aware artifacts enforce the same project boundary.
+
+Committed transactions, successful rollbacks, and failures aborted before
+publication are terminal. `doctor --fix` recovers eligible committing
+transactions under their task locks, then recomputes incomplete findings.
+This does not imply that an ambiguous external action was reconciled.
+
+Repository maintenance can preview or compact old terminal stage/backup
+payloads with `npm run transactions:compact`. Manifests and event ledgers
+remain intact; recent, ambiguous, invalid, locked, and unsafe records are
+preserved. See [maintenance usage](CONTRIBUTING.md#focused-verification-and-maintenance).
+
+Lifecycle selection keeps common identity, freshness, gates, and chronology
+checks ahead of phase-specific resolvers. Planning, verification, review,
+recovery, and pending-action modules organize decisions without changing that
+precedence. Executable protocol examples under `tests/helpers` are test
+fixtures, not runtime policy authorities.

package/QUALITY_SCORECARD.md

@@ -106,8 +106,8 @@ are both present:
 | Protocol activation resumability | `src/core/resumability.js`, READY consistency checks, event matrix, and `next` repair semantics | `tests/resumable-protocol.test.js` |
 | Hidden kit layout | `src/core/target-layout.js`, safe init/update migration, manifest layout version, native shims, and profile resolver | `tests/hidden-layout.test.js`, package and compatibility tests |
 | Contextual frontend taste | `ENG/taste-frontend-eng.md`, router metadata, attribution, and design/accessibility precedence | `tests/taste-guide.test.js`, route fixtures |
-| Pre-contract autonomy — structural | `LOOP_ENGINEERING.md`, `src/core/decision-classification.js`, `src/core/workflow-compatibility.js`, `CLAUDE.md`, `AGENTS.md`, `.github/copilot-instructions.md`, `.cursor/rules/project-loop.mdc` | `tests/decision-classification.test.js`, `tests/workflow-compatibility.test.js`, `tests/autonomy-policy.test.js`, `tests/preflight.test.js` |
-| External workflow compatibility — structural | `LOOP_ENGINEERING.md`, `PROTOCOL_INTEGRATION.md`, `src/core/workflow-compatibility.js`, and sixth-run harness metadata rule | `tests/workflow-compatibility.test.js`, `conformance/README.md` |
+| Pre-contract autonomy — structural | `LOOP_ENGINEERING.md`, `tests/helpers/decision-classification.js`, `tests/helpers/workflow-compatibility.js`, `CLAUDE.md`, `AGENTS.md`, `.github/copilot-instructions.md`, `.cursor/rules/project-loop.mdc` | `tests/decision-classification.test.js`, `tests/workflow-compatibility.test.js`, `tests/autonomy-policy.test.js`, `tests/preflight.test.js` |
+| External workflow compatibility — structural | `LOOP_ENGINEERING.md`, `PROTOCOL_INTEGRATION.md`, `tests/helpers/workflow-compatibility.js`, and sixth-run harness metadata rule | `tests/workflow-compatibility.test.js`, `conformance/README.md` |
 | Instruction-conflict handling — structural | Canonical source-attribution and `WORKFLOW_CONFLICT` policy in `LOOP_ENGINEERING.md` plus adapter references | `tests/autonomy-policy.test.js`, `tests/workflow-compatibility.test.js` |
 | Autonomous-mode precedence — structural | Autonomous/interactive mode contract and harness exclusion metadata | `tests/workflow-compatibility.test.js`, `tests/conformance-scenarios.test.js` |
 | Pre-contract autonomy — cross-agent live robustness | Prior third blind-run result, `conformance/runs/2026-08-13-codex-fourth-live.md`, preserved fifth-run report `conformance/runs/2026-08-13-codex-fifth-live.md`, and the exact blind request | `tests/conformance-scenarios.test.js`; sixth run is not started until mandatory approval is excluded |

package/README.md

@@ -462,6 +462,19 @@ validator-backed completion. Drift reopens verification, and migration keeps
 modified or unmanaged files for review. The terminal result is one of
 `VALID`, `INCOMPLETE`, `STALE`, `INCONSISTENT`, or `INVALID`.
 
+Before execution, profile selection reads structured obligations and explicit
+risks; exclusion constraints are not required actions. After a blocked
+preflight and contract revision, `next` may guide a checkpoint refresh through
+`clear-state` and a fresh preflight. This path requires a valid pre-execution
+ledger and routing bound to the revised contract. Execution transactions bind
+the physical project and task; a matching task ID in another project cannot
+reuse them. See [recovery guidance](./docs/TROUBLESHOOTING.md#revised-contract-after-a-blocked-preflight).
+
+CI audits each supplied task receipt explicitly. With no receipt it reports
+`NOT_VERIFIED`; green repository tests alone do not establish lifecycle
+completion or attestation. For contributor checks and safe payload retention,
+see [CONTRIBUTING.md](./CONTRIBUTING.md#focused-verification-and-maintenance).
+
 ## Protocol compatibility
 
 The npm package version is independent of protocol version. The current

package/docs/AGENT_PROTOCOL_SUMMARY.md

@@ -7,7 +7,7 @@
 ForgeLoop is a portable protocol and support CLI for verifiable engineering workflows. It records and validates task state, contracts, routing, checks, evidence, continuity, and optional code attestations. It does not become an agent scheduler, delegation service, source-control authority, or secret manager.
 
 Protocol version: 1
-Package version: 1.10.0
+Package version: 1.10.1
 
 ## Canonical loop
 

package/docs/ARTIFACT_REFERENCE.md

@@ -1217,3 +1217,18 @@ For `BASELINE` artifacts and `PASS`/`FAIL` evaluations, `sourceMaterialFingerpri
 and stable `sourceObservation` are conditionally required; their before and after
 fingerprints must equal the bound source fingerprint. `BLOCKED` and
 `NOT_OBSERVED` artifacts may omit these observed-source fields.
+
+## Transaction diagnostics and retention
+
+`.forgeloop/.txn/<transactionId>/manifest.json` records transaction identity,
+status, staged writes, and recovery diagnostics. `COMMITTED`, `ROLLED_BACK`,
+and `ABORTED` are terminal; an aborted staging callback did not publish its
+staged writes. A successful recovery is not reported as incomplete on the next
+doctor inspection. The transaction lock still protects recovery from live
+writers.
+
+The repository maintenance command described in
+[CONTRIBUTING.md](../CONTRIBUTING.md#focused-verification-and-maintenance)
+compacts eligible stage/backup payloads only. It retains manifests and ledgers,
+so historical manifest enumeration remains linear. These diagnostics are not
+substitutes for a valid execution receipt or external-action reconciliation.

package/docs/CODE_ATTESTATION.md

@@ -139,3 +139,12 @@ distinguished from invalid attestations by the stable exit-code contract:
 
 See [`REVISION_PROVIDERS.md`](./REVISION_PROVIDERS.md) and
 [`SIGNING_PROVIDERS.md`](./SIGNING_PROVIDERS.md) for extension boundaries.
+
+## Receipt availability in repository CI
+
+The repository audit workflow checks supplied task receipts individually with
+an explicit task ID. A checkout without a receipt reports `NOT_VERIFIED`.
+That is absence of lifecycle evidence, not an attestation trust level; it does
+not mean `PROCESSED`, `VERIFIED`, or `ATTESTED`. CI does not fabricate a receipt
+from successful repository tests. Transaction payload compaction preserves
+the manifests and ledgers needed to inspect the original history.

package/docs/DOCUMENTATION_GUIDE.md

@@ -24,12 +24,12 @@ ForgeLoop strictly separates normative protocol definitions from operational doc
 When updating documentation, always derive content from its authoritative source:
 
 ```text
-CLI syntax truth        -> CLI registry / parser (src/cli.js, src/core/cli-command-definitions.js, src/core/cli-metadata.js)
+CLI syntax truth        -> CLI registry / parser (src/cli.js, src/core/cli-command-definitions.js)
 Artifact shape truth    -> JSON schemas (schemas/*.schema.json, src/core/artifact-registry.js)
 Lifecycle truth         -> protocol / state machine (src/core/protocol.js)
 Reason-code truth       -> exported protocol constants (src/core/error-codes.js, src/core/protocol.js)
 Guide registry truth    -> canonical guide registry (src/config/guides.json)
-Package contents truth  -> package.json + package tests (tests/package.test.js)
+Package contents truth  -> package.json + docs/PACKAGE_CONTENTS.md + package tests (tests/package.test.js)
 Documentation routing   -> DOCS_INDEX.md
 Integration API truth   -> src/integration.js (exports, envelope, limits, risk classes, resources)
 MCP behavior truth      -> integrations/mcp/src/* and integrations/mcp/package.json
@@ -119,7 +119,7 @@ conformance checks detect omissions.
 
 | Documentation Area | Canonical Machine Source | Conformance Validator |
 | --- | --- | --- |
-| **CLI commands & flags** | `CLI_COMMAND_METADATA` (`src/core/cli-metadata.js`) & `src/cli.js` | `scripts/validate_documentation_conformance.mjs` |
+| **CLI commands & flags** | `CLI_COMMAND_DEFINITIONS` (`src/core/cli-command-definitions.js`) & `src/cli.js` | `scripts/validate_documentation_conformance.mjs` |
 | **Artifact paths** | `ARTIFACT_REGISTRY` & `task-paths.js` | `scripts/validate_documentation_conformance.mjs` |
 | **Artifact fields & types** | `schemas/*.schema.json` | `scripts/validate_documentation_conformance.mjs` |
 | **Enums & consts** | `schemas/*.schema.json` | `scripts/validate_documentation_conformance.mjs` |
@@ -128,7 +128,7 @@ conformance checks detect omissions.
 | **Stable error codes** | `PUBLIC_ERROR_CODES` (`src/core/error-codes.js`) | `scripts/validate_documentation_conformance.mjs` |
 | **Discovery resume rules** | `DISCOVERY_SURFACES` & `nativeShim` | `scripts/validate_documentation_conformance.mjs` |
 | **Task-layout path freshness** | `TASK_LAYOUT_DOCUMENTS` & `task-paths.js` | `scripts/validate_documentation_conformance.mjs` |
-| **Package-shipped docs** | `package.json` (`files`) | `tests/package.test.js` |
+| **Package-shipped docs and runtime** | `package.json` (`files`) + `docs/PACKAGE_CONTENTS.md` | `tests/package.test.js` + `scripts/package_smoke.mjs` |
 | **Architecture and trust diagrams** | `docs/diagrams/manifest.json` plus each typed workflow source | `scripts/check-documentation-diagrams.mjs` and `scripts/documentation-diagram-inventory.mjs` |
 
 ---

package/docs/EXECUTION_PROFILE_BENCHMARKS.md

@@ -421,3 +421,13 @@ The source policy is intentionally narrow: provider or host observations are
 accepted for benchmark claims, while actor-reported or absent telemetry stays
 non-comparable. This is an efficiency observation boundary, not verification
 evidence and not an external publication result.
+
+## Contract signals and exclusions
+
+Profile selection reads string and structured success/verification
+requirements, including nested requirements and explicit publication or
+production-readiness types. Constraints and stop conditions describe
+boundaries and are excluded from obligation scanning. For example, a
+constraint saying “No publication” does not create a publication requirement.
+An explicit route risk remains authoritative and can still raise the safety
+floor. Profiles classify work; they do not grant execution authority.

package/docs/MCP.md

@@ -135,7 +135,7 @@ forgeloop-mcp-http --project /repo --mode safe          # 127.0.0.1:3333
 
 | Component | Current contract |
 | --- | --- |
-| ForgeLoop core package | `>=1.5.0 <2` dependency range; current release `1.10.0` |
+| ForgeLoop core package | `>=1.5.0 <2` dependency range; current release `1.10.1` |
 | ForgeLoop protocol | `1` |
 | Integration API | `1` |
 | MCP package | `0.1.x` initial package |
@@ -187,3 +187,15 @@ list in [TROUBLESHOOTING](./TROUBLESHOOTING.md):
 
 Canonical ForgeLoop errors (e.g. `E_TASK_SCOPE_CONFLICT`,
 `E_TASK_CLAIM_OWNERSHIP_INCONSISTENT`) are always preserved verbatim.
+
+## Reproducible adapter verification
+
+The adapter commits its own lockfile and declares both server and test-client
+SDK versions. `npm run mcp:setup` installs that lock with lifecycle scripts
+disabled, then substitutes the locally packed core offline. Packed smoke uses
+the same dependency graph and substitutes both local tarballs using the system
+`tar` command. This replacement does not resolve registry metadata or require a
+warm npm cache; `npm ci` still retrieves the locked dependencies. Both paths
+verify resolved dependency versions and print lock/tarball SHA-256 identities.
+The adapter remains a separate package; these dependencies are not added to
+the ForgeLoop core runtime.

package/docs/PACKAGE_CONTENTS.md

@@ -0,0 +1,83 @@
+# Core npm package contents
+
+This page describes the intentional boundary of the published
+`@cassiomc1/forgeloop` package. The [`files`](../package.json) list in
+`package.json` is the packaging source of truth, while the repository's
+`tests/package.test.js` and clean-room `scripts/package_smoke.mjs` checks keep
+the boundary executable. Those test files are repository tooling and are not
+part of the consumer tarball.
+
+## Consumer surface
+
+The package exposes the `forgeloop` executable from `src/cli.js` and the
+`@cassiomc1/forgeloop/integration` subpath from `src/integration.js`, with its
+declaration file. The package has no runtime dependencies and requires Node.js
+20 or newer.
+
+## Included files
+
+The published tarball includes the following consumer-facing groups:
+
+- **Runtime and protocol:** every maintained JavaScript module under `src/`,
+  the guide registry, protocol templates, JSON schemas, completions, and the
+  generic CI verifier. Four retired compatibility helpers remain in the
+  repository for historical context and are explicitly excluded:
+  `src/core/cli-metadata.js`, `src/core/decision-classification.js`,
+  `src/core/gates.js`, and `src/core/workflow-compatibility.js`.
+- **Initialization material:** the root protocol and integration documents,
+  legal notices, the target profile template, and every path listed by
+  `src/core/templates.js`. These files are read by `init` and `update`, so
+  they are part of the executable consumer contract even when a document is
+  marked deprecated in the documentation manifest.
+- **Benchmark inputs:** execution-profile scenario definitions and their
+  README. They make new measurements reproducible; historical measurements
+  and generated results are repository evidence and are excluded.
+- **User documentation:** the getting-started, integration, CLI, artifact,
+  troubleshooting, release, package-boundary, and related reference pages.
+  The typed diagram sources, generated HTML/SVG/receipt artifacts, and
+  source-bound review records under `docs/diagrams/` are included together so
+  the packaged documentation keeps its visual provenance.
+- **Release tooling:** the selected deterministic generators, validators,
+  benchmark helpers, and shell completions needed by maintainers who consume
+  the source kit.
+
+## Excluded files
+
+The tarball intentionally omits repository-only material:
+
+- tests, conformance fixtures, coverage output, and secret-scanning helpers;
+- local `.forgeloop` state, task ledgers, locks, transactions, and execution
+  receipts (the `.forgeloop/forgeloop.gitignore` template is the sole
+  exception);
+- raw or aggregate benchmark results, package archives, and release train
+  contracts;
+- historical release plans and retired MCP adapter sources; the MCP adapter
+  is published as its own package;
+- the repository README hero PNG, which is a GitHub-only asset. The packaged
+  README remains intentionally text-first around that relative repository
+  image reference.
+
+The package test checks both required paths and these exclusion classes. It
+also enumerates `src/**/*.js` and fails if a maintained runtime module is
+missing from the candidate tarball or if a retired helper is reintroduced.
+The repository index remains a catalog: links from `DOCS_INDEX.md` to tests,
+proof-of-concept evidence, historical plans, and source trees may intentionally
+resolve only in the full repository and are not package dependencies.
+
+## Verification and publication
+
+Run the following checks from a clean checkout before opening a release PR:
+
+```bash
+npm pack --dry-run --json
+npm run pack:check
+npm run pack:smoke
+```
+
+`pack:smoke` installs the candidate tarball into a temporary consumer and
+exercises the CLI, public Integration API, initialization, schemas, and
+packaged documentation references. The tag-triggered publication workflow
+runs the same smoke gate before `npm publish --provenance --access public`.
+Publication therefore remains owned by the trusted GitHub Actions OIDC
+workflow; local package inspection proves the candidate boundary but does not
+publish it.

package/docs/RELEASE_CHECKLIST.md

@@ -13,6 +13,12 @@ preparation and verification checklist; it does not authorize publication.
 - [ ] `npm pack --dry-run` contains the required scenario definitions but no
       raw or aggregate benchmark results, tests, local state, or repository
       metadata.
+- [ ] [`docs/PACKAGE_CONTENTS.md`](./PACKAGE_CONTENTS.md) matches the current
+      `package.json` file list and documents intentional inclusions and
+      exclusions.
+- [ ] Every maintained `src/**/*.js` module is present in the candidate
+      tarball; only the four explicitly retired compatibility helpers are
+      excluded.
 
 ## Protocol and attestation
 
@@ -62,6 +68,8 @@ preparation and verification checklist; it does not authorize publication.
 ## Integration and cross-platform evidence
 
 - [ ] `npm run pack:check` and `npm run pack:smoke` pass.
+- [ ] The npm publication workflow runs `npm run pack:smoke` before its
+      provenance-backed publish step.
 - [ ] `npm run mcp:test` either runs the configured MCP tests or reports the
       single actionable setup prerequisite.
 - [ ] `npm run mcp:pack:check` passes when MCP dependencies are available.

package/docs/REVISION_PROVIDERS.md

@@ -134,3 +134,12 @@ provider semantics fail closed.
 An implementation should be tested for deterministic identity, exact bytes,
 binary and empty files, Unicode and space-containing paths, symlinks,
 Gitlinks, deletions, renames, path traversal, and stable error mapping.
+
+### Focused test selection and evidence
+
+A test-runner filter chooses what a command executes. It does not establish a
+canonical differential verification scope. Use `run-check` to bind executed
+commands to evidence, and supply a fresh canonical scope reference when the
+checker requires one. A manual observation must declare `manual-review`;
+command metadata alone does not prove that a process ran. Packed TypeScript
+consumer checks and critical lifecycle coverage complement these boundaries.

package/docs/TROUBLESHOOTING.md

@@ -1299,3 +1299,15 @@ current-cycle validation.
 | `E_WORKSPACE_IDENTITY_UNAVAILABLE` | A ForgeLoop boundary, artifact, provider, or attestation validation condition was not satisfied. | Inspect the structured command result, correct the named boundary or artifact, then retry the canonical command. |
 
 <!-- END FORGELOOP GENERATED: public-error-codes -->
+
+## Revised contract after a blocked preflight
+
+Before execution starts, a revised contract and route can leave the old
+checkpoint stale. Run `forgeloop next --task <id> --json`. When the validated
+history ends in a blocked preflight and the new route binds the revised
+contract, it offers `clear-state` followed by `preflight`. Execute those in
+that order, satisfy any remaining gates, and require `READY` again.
+
+This recovery guidance is unavailable after execution has started, for an
+invalid ledger, or when the new route does not match the contract. Preserve
+those barriers and follow the task's canonical recovery guidance.

package/docs/assets/diagrams/forgeloop-code-attestation-flow.html

@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html lang="en" data-theme="dark" data-preset="signal-flow" data-present="true">
 <head>
-      <meta name="forgeloop-diagram-source-sha256" content="669966fba9e69df0525a3581baa4e90075923dbe3069f81f706761a40abf9073">
+      <meta name="forgeloop-diagram-source-sha256" content="33bb9c3c4f3fb4a793febeab34b2d07ca7bf2c058d4f5e7575dba3a6065eedeb">
     <meta name="forgeloop-diagram-renderer" content="archify@2.15.0 (e1ac748f19cf805e44bf74fb93c796662152e273)">
 <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -40,6 +40,15 @@
   <style>
       /* Keep boundary labels clear of the first node in each group. */
       [data-composition-frame-kind="group"] + text { transform: translateY(-18px); }
+      @media (max-width: 720px) {
+        html:not([data-present="true"]) .toolbar {
+          top: 0;
+          right: 0;
+          width: 100%;
+          flex-wrap: wrap;
+          justify-content: flex-start;
+        }
+      }
 
     /* ==========================================================
        THEME VARIABLES — switch by toggling [data-theme] on <html>
@@ -4868,7 +4877,7 @@
       <p class="subtitle">Exact content binding from valid completion to read-only trust results</p>
     </div>
 
-    <script id="archify-guided-views-data" type="application/json">[{"id":"completion-to-manifest","label":"Completion to manifest","focus":["complete","receipt","manifest","captured"],"note":"Follow the transactional binding between valid completion evidence and exact source content."},{"id":"manifest-to-statement","label":"Manifest to statement","focus":["manifest","captured","statement","signing","bundle"],"note":"See how the deterministic code manifest becomes an in-toto Statement v1 and optional signature bundle."},{"id":"revision-range-coverage","label":"Revision-range coverage","focus":["base","provider","changed","attestations","union","range"],"note":"Inspect the separate changed-path coverage question and its gap or conflict result."}]</script>
+    <script id="archify-guided-views-data" type="application/json">[{"id":"completion-to-manifest","label":"Completion to manifest","focus":["complete","receipt","manifest","captured"],"note":"Completion and exact-content evidence bind to the project and task. No supplied CI receipt means NOT_VERIFIED."},{"id":"manifest-to-statement","label":"Manifest to statement","focus":["manifest","captured","statement","signing","bundle"],"note":"See how the deterministic code manifest becomes an in-toto Statement v1 and optional signature bundle."},{"id":"revision-range-coverage","label":"Revision-range coverage","focus":["base","provider","changed","attestations","union","range"],"note":"Inspect the separate changed-path coverage question and its gap or conflict result."}]</script>
 
     <div class="guided-views no-print" id="guided-views" hidden aria-label="Guided diagram views">
       <button id="guided-view-prev" type="button" aria-label="Previous guided view" title="Previous guided view ([)">&#8592;</button>
@@ -5426,6 +5435,7 @@
           <li>&bull; PROCESSED means artifacts exist and parse</li>
           <li>&bull; VERIFIED means completion, evidence, manifest, and content bindings validate</li>
           <li>&bull; ATTESTED additionally requires a valid external signature policy</li>
+          <li>&bull; No supplied CI receipt means NOT_VERIFIED, not a trust level</li>
         </ul>
       </div>
 
@@ -5438,6 +5448,7 @@
           <li>&bull; The manifest records one SHA-256 digest per changed source entry</li>
           <li>&bull; The in-toto statement binds the manifest to completion evidence</li>
           <li>&bull; Read-only verification never rewrites task state or ledger events</li>
+          <li>&bull; Compaction preserves transaction manifests and event history</li>
         </ul>
       </div>
 

package/docs/assets/diagrams/forgeloop-code-attestation-flow.receipt.json

@@ -15,17 +15,17 @@
     "license": "MIT"
   },
   "input": {
-    "sha256": "669966fba9e69df0525a3581baa4e90075923dbe3069f81f706761a40abf9073",
-    "bytes": 7744
+    "sha256": "33bb9c3c4f3fb4a793febeab34b2d07ca7bf2c058d4f5e7575dba3a6065eedeb",
+    "bytes": 9857
   },
   "artifacts": {
     "html": {
-      "sha256": "62666342ec4efbc295ed65f4450008ca5a39072d8a11ff7b8b675ab258711286",
-      "bytes": 652836
+      "sha256": "85bb7abf910d3f6dd12037cfcd90c4b67f0aad4dca2b4cb21be1b0112cbdd92e",
+      "bytes": 653258
     },
     "svg": {
-      "sha256": "0af63dd51683d07981fc681042c437377a78ae8a7e6a7175c18a1def02e6280a",
-      "bytes": 216313
+      "sha256": "3a768148886ffdfcce75221c11e51ee77a3702510e90917bf6e8ba0581ebdb44",
+      "bytes": 216543
     }
   },
   "staticSvg": {

package/docs/assets/diagrams/forgeloop-code-attestation-flow.svg

@@ -1,8 +1,17 @@
-<svg data-archify-version="2.15.0" data-forgeloop-source-sha256="669966fba9e69df0525a3581baa4e90075923dbe3069f81f706761a40abf9073" data-theme="dark" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 720 1024" role="img" aria-labelledby="archify-diagram-title archify-diagram-description" data-animation="trace" data-preset="signal-flow" data-quality-profile="showcase">
+<svg data-archify-version="2.15.0" data-forgeloop-source-sha256="33bb9c3c4f3fb4a793febeab34b2d07ca7bf2c058d4f5e7575dba3a6065eedeb" data-theme="dark" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 720 1024" role="img" aria-labelledby="archify-diagram-title archify-diagram-description" data-animation="trace" data-preset="signal-flow" data-quality-profile="showcase">
     <style>
       .c-bg-rect { fill: var(--bg); }
 /* Keep boundary labels clear of the first node in each group. */
       [data-composition-frame-kind="group"] + text { transform: translateY(-18px); }
+      @media (max-width: 720px) {
+        html:not([data-present="true"]) .toolbar {
+          top: 0;
+          right: 0;
+          width: 100%;
+          flex-wrap: wrap;
+          justify-content: flex-start;
+        }
+      }
 
     /* ==========================================================
        THEME VARIABLES — switch by toggling [data-theme] on &lt;html>

package/docs/assets/diagrams/forgeloop-engineering-flow.html

@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html lang="en" data-theme="dark" data-preset="signal-flow" data-present="true">
 <head>
-      <meta name="forgeloop-diagram-source-sha256" content="a83128a8639db5db497ac552cfdbc318839e6451c718581fbfcd064e3e869981">
+      <meta name="forgeloop-diagram-source-sha256" content="0bfd5bbf8d6bbeaec23db543deb1e99844321c77b3c7feb21ee0cc877bbba9a9">
     <meta name="forgeloop-diagram-renderer" content="archify@2.15.0 (e1ac748f19cf805e44bf74fb93c796662152e273)">
 <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -40,6 +40,15 @@
   <style>
       /* Keep boundary labels clear of the first node in each group. */
       [data-composition-frame-kind="group"] + text { transform: translateY(-18px); }
+      @media (max-width: 720px) {
+        html:not([data-present="true"]) .toolbar {
+          top: 0;
+          right: 0;
+          width: 100%;
+          flex-wrap: wrap;
+          justify-content: flex-start;
+        }
+      }
 
     /* ==========================================================
        THEME VARIABLES — switch by toggling [data-theme] on <html>
@@ -4865,10 +4874,10 @@
         <div class="pulse-dot"></div>
         <h1>ForgeLoop Evidence-First Engineering Flow</h1>
       </div>
-      <p class="subtitle">Typed intent → scoped work → observed evidence → validator-backed closure</p>
+      <p class="subtitle">Structured intent → project-bound work → observed evidence → valid closure</p>
     </div>
 
-    <script id="archify-guided-views-data" type="application/json">[{"id":"contract-to-work","label":"Contract to work","focus":["request","profile","contract","route","gates","preflight","work"],"note":"Follow how a request becomes scoped, routed, and safe to execute."},{"id":"evidence-to-close","label":"Evidence to close","focus":["work","evidence","review","valid"],"note":"See the evidence and review boundary that makes completion trustworthy."},{"id":"recovery-loop","label":"Recovery loop","focus":["evidence","diagnose","correct","preflight","blocked"],"note":"Failures return to diagnosis and correction before another claim is made."}]</script>
+    <script id="archify-guided-views-data" type="application/json">[{"id":"contract-to-work","label":"Contract to work","focus":["request","profile","contract","route","gates","preflight","work"],"note":"Structured obligations and explicit risks set the profile; exclusions do not create required actions."},{"id":"evidence-to-close","label":"Evidence to close","focus":["work","evidence","review","valid"],"note":"See the evidence and review boundary that makes completion trustworthy."},{"id":"recovery-loop","label":"Recovery loop","focus":["evidence","diagnose","correct","preflight","blocked"],"note":"Before execution, blocked refresh needs a valid ledger and revised route. Later failures use diagnosis and correction."}]</script>
 
     <div class="guided-views no-print" id="guided-views" hidden aria-label="Guided diagram views">
       <button id="guided-view-prev" type="button" aria-label="Previous guided view" title="Previous guided view ([)">&#8592;</button>
@@ -4911,9 +4920,9 @@
 
     <!-- Main Diagram -->
     <div class="diagram-container" data-detail-level="read">
-      <svg viewBox="0 0 720 900" role="img" aria-labelledby="archify-diagram-title archify-diagram-description" data-animation="trace" data-preset="signal-flow" data-quality-profile="showcase">
+      <svg viewBox="0 0 850 900" role="img" aria-labelledby="archify-diagram-title archify-diagram-description" data-animation="trace" data-preset="signal-flow" data-quality-profile="showcase">
         <title id="archify-diagram-title">ForgeLoop Evidence-First Engineering Flow</title>
-        <desc id="archify-diagram-description">Typed intent → scoped work → observed evidence → validator-backed closure</desc>
+        <desc id="archify-diagram-description">Structured intent → project-bound work → observed evidence → valid closure</desc>
         <!-- Definitions -->
         <defs>
           <marker id="arrowhead" markerWidth="10" markerHeight="7" refX="9" refY="3.5" orient="auto">
@@ -5065,19 +5074,19 @@
         <text data-detail="fine" x="500" y="265" class="t-security" font-size="7" text-anchor="middle">Preflight</text>
         </g>
 
-        <g id="node-work" data-node-id="work" data-node-label="Execution" tabindex="0" role="button" aria-label="Focus Execution, checkpoint, Resumable Execution › Route + authorize" aria-pressed="false" data-node-kind="backend" data-node-sublabel="checkpoint" data-node-context="Resumable Execution › Route + authorize">
-          <title>Execution · checkpoint · Resumable Execution › Route + authorize</title>
+        <g id="node-work" data-node-id="work" data-node-label="Execution" tabindex="0" role="button" aria-label="Focus Execution, root + task, Resumable Execution › Route + authorize" aria-pressed="false" data-node-kind="backend" data-node-sublabel="root + task" data-node-context="Resumable Execution › Route + authorize">
+          <title>Execution · root + task · Resumable Execution › Route + authorize</title>
           <rect x="469" y="341" width="62" height="52" rx="6" class="c-mask"/>
           <rect x="469" y="341" width="62" height="52" rx="6" class="c-backend" data-animate="node" style="--step:6" stroke-width="1.5"/>
           <g aria-hidden="true" data-semantic-sigil="backend" class="semantic-sigil s-backend" transform="translate(475 347) scale(0.6875)">
             <path d="M6 3 3 8l3 5M10 3l3 5-3 5"/>
           </g>
           <text data-detail-anchor x="500" y="362" class="t-primary" font-size="10" font-weight="600" text-anchor="middle">Execution</text>
-          <text data-detail="context" x="500" y="379" class="t-muted" font-size="8" text-anchor="middle">checkpoint</text>
+          <text data-detail="context" x="500" y="379" class="t-muted" font-size="8" text-anchor="middle">root + task</text>
         </g>
 
-        <g id="node-evidence" data-node-id="evidence" data-node-label="Evidence" tabindex="0" role="button" aria-label="Focus Evidence, scope + checks, Evidence Ledger › Evidence boundary › Route + authorize" aria-pressed="false" data-node-kind="database" data-node-sublabel="scope + checks" data-node-tag="observed" data-node-context="Evidence Ledger › Evidence boundary › Route + authorize">
-          <title>Evidence · scope + checks · Evidence Ledger › Evidence boundary › Route + authorize · observed</title>
+        <g id="node-evidence" data-node-id="evidence" data-node-label="Evidence" tabindex="0" role="button" aria-label="Focus Evidence, run-check, Evidence Ledger › Evidence boundary › Route + authorize" aria-pressed="false" data-node-kind="database" data-node-sublabel="run-check" data-node-tag="observed" data-node-context="Evidence Ledger › Evidence boundary › Route + authorize">
+          <title>Evidence · run-check · Evidence Ledger › Evidence boundary › Route + authorize · observed</title>
           <rect x="465" y="457" width="70" height="68" rx="6" class="c-mask"/>
           <rect x="465" y="457" width="70" height="68" rx="6" class="c-database" data-animate="node" style="--step:7" stroke-width="1.5"/>
           <g aria-hidden="true" data-semantic-sigil="database" class="semantic-sigil s-database" transform="translate(471 463) scale(0.6875)">
@@ -5085,7 +5094,7 @@
             <path d="M3 4v8c0 1.1 2.2 2 5 2s5-.9 5-2V4M3 8c0 1.1 2.2 2 5 2s5-.9 5-2"/>
           </g>
           <text data-detail-anchor x="500" y="478" class="t-primary" font-size="11" font-weight="600" text-anchor="middle">Evidence</text>
-          <text data-detail="context" x="500" y="495" class="t-muted" font-size="7.3" text-anchor="middle">scope + checks</text>
+          <text data-detail="context" x="500" y="495" class="t-muted" font-size="8" text-anchor="middle">run-check</text>
         <text data-detail="fine" x="500" y="513" class="t-database" font-size="7" text-anchor="middle">observed</text>
         </g>
 
@@ -5383,6 +5392,7 @@
           <li>&bull; Workspace binding is optional but blocks mismatched execution</li>
           <li>&bull; Failures return to diagnosis before another claim</li>
           <li>&bull; Completion is validator-backed, not inferred from a screenshot</li>
+          <li>&bull; Blocked pre-execution refresh requires a valid ledger and revised route</li>
         </ul>
       </div>
 
@@ -5396,6 +5406,7 @@
           <li>&bull; run-check binds exact commands to an execution reference</li>
           <li>&bull; record-check covers manual observations</li>
           <li>&bull; Drift reopens verification instead of being hidden</li>
+          <li>&bull; Matching task IDs never authorize cross-project transaction reuse</li>
         </ul>
       </div>
 

package/docs/assets/diagrams/forgeloop-engineering-flow.receipt.json

@@ -15,17 +15,17 @@
     "license": "MIT"
   },
   "input": {
-    "sha256": "a83128a8639db5db497ac552cfdbc318839e6451c718581fbfcd064e3e869981",
-    "bytes": 7610
+    "sha256": "0bfd5bbf8d6bbeaec23db543deb1e99844321c77b3c7feb21ee0cc877bbba9a9",
+    "bytes": 9779
   },
   "artifacts": {
     "html": {
-      "sha256": "55d71098d15a46778454d53690110195e0e923d37f34cb6c57fcc5e6601ab7ec",
-      "bytes": 647796
+      "sha256": "251e09f3cc36d54c4b8567dd3e6dd8a890a2621cdd12667fb80cc61e7dbf4b7c",
+      "bytes": 648281
     },
     "svg": {
-      "sha256": "37244a07cc862e3fe4a7188f5236a509a4adf565d5b785ba3c0932057ac6f3a8",
-      "bytes": 211160
+      "sha256": "ef3effe7e756494c7dffef9ee315e970bbbdb9fddc0ee0a1e4bfccfbb0c05534",
+      "bytes": 211373
     }
   },
   "staticSvg": {