@cassiomc1/forgeloop 0.1.6 → 0.1.9

package/README.md

@@ -16,6 +16,11 @@ ForgeLoop is the portable, evidence-first loop that connects deterministic
 routing, checkpointed state, observable evidence, conformance, and delegation
 for compatible agent harnesses.
 
+The npm package also ships the local `forgeloop` CLI. In a target project it
+installs canonical documents under `.forgeloop/kit/`, keeps only small native
+discovery shims at the root, and stores mutable protocol artifacts under
+`.forgeloop/`.
+
 ## Catalog
 
 | Topic | When to use it | Guide |
@@ -25,6 +30,7 @@ for compatible agent harnesses.
 | Testing | Risk-based testing strategy | [`test-code-eng.md`](./ENG/test-code-eng.md) |
 | Security | Web, mobile, desktop, APIs, and supply chain | [`sec-code-eng.md`](./ENG/sec-code-eng.md) |
 | Design | Visual direction, UX, motion, and perceived performance | [`design-code-eng.md`](./ENG/design-code-eng.md) |
+| Taste frontend | Contextual design-read, anti-slop, and visual pre-flight for premium frontend work | [`taste-frontend-eng.md`](./ENG/taste-frontend-eng.md) |
 | Performance | Measurement, diagnosis, budgets, and optimization | [`perf-code-eng.md`](./ENG/perf-code-eng.md) |
 | Accessibility | WCAG 2.2-oriented protocol for interfaces | [`accessibility-eng.md`](./ENG/accessibility-eng.md) |
 | Web games | Architecture, design, and operation of 2D, 3D, and procedural games | [`games-code-design-web-eng.md`](./ENG/games-code-design-web-eng.md) |
@@ -38,10 +44,12 @@ and catalog remain synchronized.
 The kit turns each request into a verifiable cycle: discover the project,
 define an execution contract, select applicable guides, execute, verify,
 diagnose, and correct until success or a genuine external blocker.
-[`LOOP_ENGINEERING.md`](./LOOP_ENGINEERING.md) is the operational source;
+[`LOOP_ENGINEERING.md`](./LOOP_ENGINEERING.md) is the operational source (and
+is installed under `.forgeloop/kit/` in a target);
 [`GUIDE_ROUTER.md`](./GUIDE_ROUTER.md) prevents irrelevant context from being
 loaded; and [`PROJECT_PROFILE.md`](./PROJECT_PROFILE.md) preserves only durable,
-proven project facts.
+proven project facts (installed as `.forgeloop/kit/PROJECT_PROFILE.md` in a
+target).
 
 The canonical system map, including the routing/state/evidence architecture, is
 in [`LOOP_SYSTEM_DESIGN.md`](./LOOP_SYSTEM_DESIGN.md).
@@ -50,60 +58,84 @@ in [`LOOP_SYSTEM_DESIGN.md`](./LOOP_SYSTEM_DESIGN.md).
 flowchart TB
   root["FORGELOOP"]
 
-  subgraph surfaces["CONTROL SURFACES"]
-    direction LR
-    routing["ROUTING"] --> routingFacts["deterministic<br/>decisions"]
-    state["STATE"] --> checkpoint["checkpoint<br/>facts"]
-    evidence["EVIDENCE"] --> claims["observable<br/>claims"]
-
-    checkpoint --> repository["repository"]
-    checkpoint --> contract["contract"]
-    repository --> freshness["freshness"]
-    contract --> freshness
-  end
-
-  root --> routing
-  root --> state
-  root --> evidence
-
-  routingFacts --> conformance["CONFORMANCE"]
-  routingFacts --> delegation["DELEGATION"]
+  root --> entry["native adapters<br/>+ .forgeloop/kit/"]
+  entry --> migration{"target<br/>layout"}
+  migration -->|legacy v1| plan["validate paths<br/>+ build plan"]
+  plan --> hidden["write + verify<br/>hidden kit"]
+  hidden --> authority["atomic manifest<br/>authority switch"]
+  authority --> cleanup["hash-checked<br/>legacy cleanup"]
+  cleanup --> recovered["healthy or<br/>recoverable"]
+  migration -->|layout v2| retry["update + retry<br/>owned cleanup"]
+  entry --> discovery["discovery +<br/>project profile"]
+  discovery --> contract["current<br/>contract"]
+  contract --> routing["deterministic<br/>route"]
+
+  contract --> preflight["preflight"]
+  routing --> preflight
+  gates["required<br/>gates"] --> preflight
+  preflight -->|READY| ready["PREFLIGHT_READY"]
+  preflight -->|BLOCKED| blocker["repair /<br/>blocker"]
+
+  ready --> state["work-state<br/>checkpoint"]
+  ready --> events["append-only<br/>event ledger"]
+  state --> lifecycle["plan → execute<br/>→ verify → review"]
+  lifecycle --> prepare["prepare<br/>completion receipt"]
+  prepare --> checks["checks + structured<br/>evidence"]
+  checks --> receipt["updated execution<br/>receipt"]
+  checks --> audit["audit +<br/>complete"]
+  events --> audit
+
+  contract --> freshness["freshness<br/>fingerprints"]
+  routing --> freshness
+  state --> freshness
+  checks --> freshness
+  routing --> conformance["validate-protocol<br/>/ conformance"]
+  state --> conformance
+  receipt --> conformance
   freshness --> conformance
-  freshness --> delegation
-  claims --> conformance
-  claims --> delegation
+  conformance --> verdict["VALID / INCOMPLETE /<br/>STALE / INCONSISTENT / INVALID"]
+  audit --> verdict
 
-  conformance --> verdict["VALID / STALE / INVALID"]
-  delegation --> verdict
-  verdict --> harness["compatible harness"]
+  routing --> delegation["optional bundle /<br/>delegation"]
+  checks --> delegation
+  delegation --> handoff["handoff to<br/>compatible harness"]
+  verdict --> handoff
+  blocker --> handoff
 
   classDef root fill:#08090C,stroke:#6E6AF5,stroke-width:3px,color:#EDEEF0;
+  classDef entry fill:#101218,stroke:#3EDBB8,stroke-width:2px,color:#EDEEF0;
+  classDef migration fill:#0F766E,stroke:#5EEAD4,stroke-width:2px,color:#FFFFFF;
   classDef routing fill:#4F46E5,stroke:#A5B4FC,stroke-width:2px,color:#FFFFFF;
   classDef state fill:#373A46,stroke:#A1A1AA,stroke-width:2px,color:#FFFFFF;
   classDef evidence fill:#3EDBB8,stroke:#99F6E4,stroke-width:2px,color:#08090C;
   classDef fact fill:#181B24,stroke:#6E6AF5,stroke-width:1px,color:#EDEEF0;
-  classDef support fill:#181B24,stroke:#8A8F98,stroke-width:1px,color:#EDEEF0;
   classDef gate fill:#3730A3,stroke:#A5B4FC,stroke-width:2px,color:#FFFFFF;
   classDef result fill:#C9A876,stroke:#F5D9A6,stroke-width:2px,color:#08090C;
   classDef harness fill:#101218,stroke:#3EDBB8,stroke-width:2px,color:#EDEEF0;
 
   class root root;
-  class routing,routingFacts routing;
-  class state,checkpoint state;
-  class evidence,claims evidence;
-  class repository,contract,freshness fact;
-  class conformance,delegation gate;
+  class entry,discovery,delegation entry;
+  class migration,plan,hidden,authority,cleanup,recovered,retry migration;
+  class routing,preflight,ready routing;
+  class state,events,lifecycle state;
+  class checks,receipt,audit evidence;
+  class contract,freshness,conformance fact;
+  class gates,blocker gate;
   class verdict result;
-  class harness harness;
-  style surfaces fill:#101218,stroke:#2D3340,stroke-width:1px,color:#EDEEF0;
+  class handoff harness;
   linkStyle default stroke:#8A8F98,stroke-width:1.5px;
 ```
 
-Equivalent reading for text-only environments: ForgeLoop turns routing into
-deterministic decisions, state into checkpoint facts, and evidence into
-observable claims. Repository and contract facts establish freshness; all
-three control surfaces feed conformance and delegation, which produce a
-`VALID`, `STALE`, or `INVALID` result for the compatible harness.
+Equivalent reading for text-only environments: adapters load the canonical kit;
+an older target follows validate paths → write and verify hidden files → switch
+manifest authority → hash-checked cleanup, while an interrupted migration is
+diagnosed and retried by `doctor`/`update`;
+discovery creates the contract and deterministic route; contract, route, and
+required gates must produce `PREFLIGHT_READY` before the resumable state and
+append-only event ledger authorize the lifecycle. Verification produces
+structured evidence and a receipt. `audit`/`complete` and `validate-protocol`
+then classify the result as `VALID`, `INCOMPLETE`, `STALE`, `INCONSISTENT`, or
+`INVALID`. Optional delegation creates a handoff; it is not an agent runtime.
 
 The operational request loop remains:
 
@@ -125,7 +157,12 @@ project without overwriting local instructions. When the package is available
 in the npm registry, use the commands below; otherwise use the repository
 checkout fallback.
 
+The current published release is `@cassiomc1/forgeloop@0.1.9`.
+Pin this version when a reproducible blind run or release-identity check is
+required:
+
 ```bash
+npx @cassiomc1/forgeloop@0.1.9 --version
 npx @cassiomc1/forgeloop init
 npx @cassiomc1/forgeloop doctor
 npx @cassiomc1/forgeloop update
@@ -133,16 +170,22 @@ npx @cassiomc1/forgeloop update
 
 Protocol-support commands are local and do not invoke an agent or model:
 
+The lifecycle example assumes that the harness has already written a
+schema-valid `.forgeloop/current-contract.json` and the required
+`.forgeloop/gates/*.json` files. `route` persists routing; `preflight` validates
+the contract, route, and gates before execution.
+
 ```bash
 npx @cassiomc1/forgeloop route --work complete-website --surface ui --risk untrusted-input
 npx @cassiomc1/forgeloop activate
 npx @cassiomc1/forgeloop preflight --json
 npx @cassiomc1/forgeloop next
 npx @cassiomc1/forgeloop next --json
+npx @cassiomc1/forgeloop advance --to PLANNED
 npx @cassiomc1/forgeloop advance --to EXECUTING
 npx @cassiomc1/forgeloop advance --to VERIFYING
 npx @cassiomc1/forgeloop prepare-completion --json
-npx @cassiomc1/forgeloop record-check --id tests --requirement tests --status passed --evidence-kind OBSERVED --command "npm test" --result "exit 0" --json
+npx @cassiomc1/forgeloop record-check --id tests --requirement tests --status passed --evidence-kind OBSERVED --command "npm test" --result "exit 0" --exit-code 0 --json
 npx @cassiomc1/forgeloop advance --to REVIEWING
 npx @cassiomc1/forgeloop audit --json
 npx @cassiomc1/forgeloop complete --json
@@ -153,10 +196,15 @@ npx @cassiomc1/forgeloop inspect --json
 npx @cassiomc1/forgeloop status --json
 npx @cassiomc1/forgeloop status --contract-file .forgeloop/current-contract.json --json
 npx @cassiomc1/forgeloop validate-state --json
-npx @cassiomc1/forgeloop validate-receipt --file ./execution-receipt.json --json
-npx @cassiomc1/forgeloop validate-protocol --route-file ./routing-result.json --state-file .forgeloop/work-state.json --receipt-file ./execution-receipt.json --contract-file .forgeloop/current-contract.json --json
+npx @cassiomc1/forgeloop validate-receipt --file .forgeloop/execution-receipt.json --json
+npx @cassiomc1/forgeloop validate-protocol --route-file .forgeloop/routing-result.json --state-file .forgeloop/work-state.json --receipt-file .forgeloop/execution-receipt.json --contract-file .forgeloop/current-contract.json --json
 ```
 
+For `complete-website`, record one structured check for each required success
+criterion before `complete`; the single `tests` entry above only illustrates the
+command shape. Route, receipt, state, and contract artifacts all live under
+`.forgeloop/` in the target.
+
 The query-driven post-implementation path is:
 
 ```text
@@ -176,6 +224,13 @@ implementation
 `forgeloop next` and `forgeloop next --json` read persisted state only. They do
 not run project checks or mutate protocol artifacts.
 
+A `READY` preflight is a resumable checkpoint, not only a status value. It must
+reconcile the contract, route, required gates, `.forgeloop/work-state.json`,
+`.forgeloop/events.ndjson`, and a matching `.forgeloop/preflight.json`. If
+`READY` remains while the work state is missing, `next` returns
+`RESOLVE_BLOCKER` with `E_STATE_MISSING_AFTER_PREFLIGHT_READY`; it does not
+silently fall back to discovery.
+
 `route` expands declared signals into deterministic guide IDs and reason codes.
 `activate` records a session marker without storing prompts or hidden reasoning.
 Before implementation, write the canonical contract, persist the route, create
@@ -202,6 +257,11 @@ cross-artifact relationships plus the same derived freshness classification
 used by `inspect` and `status`. Supply `--contract-file` to compare the saved
 contract fingerprint with the current contract; omitting it leaves contract
 freshness as `NOT_VERIFIED` and a complete artifact set requires revalidation.
+When delegation is in scope, also supply the matching repeated
+`--task-brief <path>` and `--delegated-result <path>` inputs. Without those
+inputs it reports `INCOMPLETE` with
+`task briefs and delegated results were not supplied`; that classification is
+separate from a local `complete --json` result of `VALID`.
 It returns `VALID`, `INCOMPLETE`, `STALE`, `INCONSISTENT`, or `INVALID` with
 exact invariant codes and derived stale reasons. The persisted
 `.forgeloop/work-state.json` schema is unchanged: `status`, `stale`, and `fresh`
@@ -224,7 +284,7 @@ forgeloop preflight
 ```
 
 Strict blind conformance is a separate profile. First verify the target
-`PROJECT_PROFILE.md`, then use `--strict` consistently with `preflight`,
+`.forgeloop/kit/PROJECT_PROFILE.md`, then use `--strict` consistently with `preflight`,
 `audit`, and `complete`. Do not evaluate a Standard run with Strict criteria
 unless that escalation is explicitly recorded.
 
@@ -260,7 +320,7 @@ target project. Its main threat boundaries are:
 | Untrusted state or profile data | JSON schemas, semantic checks, secret-like field checks, and non-execution rules apply before state or profile data is used. |
 | Command injection | Git inspection uses fixed arguments without a shell; the CLI never treats project text as a command. |
 | Data exposure | Receipts and checkpoints reject secret-like keys and values; examples use placeholders, and the repository secret scanner runs in CI. |
-| Unsafe update overwrite | `update` preserves locally modified files and `PROJECT_PROFILE.md`; adoption and writes remain bounded to the selected target. |
+| Unsafe update overwrite | `update` preserves locally modified files and the target's `.forgeloop/kit/PROJECT_PROFILE.md`; adoption and writes remain bounded to the selected target. |
 | Dependency supply chain | Runtime code uses Node built-ins only; the package does not install agents, providers, plugins, or remote services. |
 | Stale replay | Work state records contract and repository fingerprints; drift requires revalidation and never reruns destructive or publication actions automatically. |
 | Unverified publication | Receipts carry explicit publication booleans; local success never implies a push, pull request, merge, release, or deployment. |
@@ -284,8 +344,17 @@ node src/cli.js update
 The release workflow uses [npm trusted publishing](https://docs.npmjs.com/trusted-publishers)
 through GitHub Actions OIDC. Before the first release, register this repository
 and workflow as the package's trusted publisher in npm; each `vX.Y.Z` tag must
-match `package.json`. After publishing, verify the package version and its npm
-provenance record.
+match `package.json`. After publishing, verify the complete immutable release
+identity before a blind run:
+
+```bash
+RELEASE_COMMIT="$(git rev-list -n1 vX.Y.Z)"
+npm run release:identity -- --version X.Y.Z --release-commit "$RELEASE_COMMIT"
+```
+
+Only `RELEASE_IDENTITY_VALID` is sufficient. The read-only check compares the
+release commit and GitHub tag with npm's version, `gitHead`, tarball URL,
+SHA-1, and SHA-512 integrity; it never publishes or changes a tag.
 
 The commands above use the current directory. To install into another existing
 project directory, pass a relative or absolute `--path`:
@@ -306,11 +375,23 @@ The target must already exist and be a directory; the CLI will not create or
 replace an arbitrary path. Use `--dry-run` to preview writes before `init` or
 `update`. `--json`, `--strict`, and `--adopt <path>` are supported by `doctor`;
 adoption is limited to a supported adapter that has been reviewed locally. The
-CLI records managed files and their hashes in `.forgeloop/manifest.json`; `update`
-leaves locally modified files and `PROJECT_PROFILE.md` untouched. If a target
-already has a manifest, rerun `update` instead of `init`. Symlinked targets or
-template parents are rejected, and unadopted pre-existing adapters are reported
-for manual merge with the loop reference.
+CLI records managed files and their hashes in `.forgeloop/manifest.json`; a new
+target receives canonical documents under `.forgeloop/kit/` and only small
+native shims at the root. `update` leaves locally modified files and the
+project profile untouched. If a target already has a manifest, rerun `update`
+instead of `init`. Symlinked targets or template parents are rejected, and
+unadopted pre-existing adapters are reported for manual merge with the loop
+reference.
+
+Targets created by an older package layout are migrated by `update`: unchanged
+managed root files move into the hidden kit, while modified or unowned root
+files are preserved and reported as conflicts. The migration never follows a
+symlink or deletes a file whose managed hash no longer matches. The migration
+writes and verifies the complete hidden plan, atomically switches the manifest
+authority, and only then cleans owned legacy files. If a process stops between
+those stages, `doctor` reports `E_MIGRATION_INCOMPLETE` and the next `update`
+retries cleanup only when the recorded legacy hash still matches; modified or
+unowned files remain for manual review.
 
 ### Migrate an existing mdfiles installation
 
@@ -329,32 +410,40 @@ ForgeLoop does not automatically migrate, dual-write, or delete a legacy
 ### Install in a target project
 
 If npm is unavailable, download this public repository as a ZIP or clone it
-into a temporary directory. Copy this structure to the target project's root
-while preserving relative paths:
+into a temporary directory, then invoke the bundled CLI against the target:
+
+```bash
+node /path/to/forgeloop/src/cli.js init --path /path/to/my-project
+node /path/to/forgeloop/src/cli.js doctor --path /path/to/my-project
+```
+
+Copying source-root files directly is not equivalent to initialization: the
+canonical documents must be mapped into the hidden kit and the native adapters
+must remain thin. The resulting target layout is:
 
 ```text
 AGENTS.md
 CLAUDE.md
-AGENT_COMPATIBILITY.md
-LOOP_ENGINEERING.md
-GUIDE_ROUTER.md
-PROJECT_PROFILE.md
-LOOP_SYSTEM_DESIGN.md
-QUALITY_SCORECARD.md
-TERMINOLOGY.md
-EXECUTION_STATE.md
-DELEGATION_PROTOCOL.md
-ORCHESTRATOR_INTEGRATION.md
-THREAT_MODEL.md
-CONTRACT_COVERAGE.md
-THIRD_PARTY_NOTICES.md
-LICENSE
-LICENSE-DOCS.md
 .forgeloop/.gitignore
+.forgeloop/kit/AGENT_COMPATIBILITY.md
+.forgeloop/kit/LOOP_ENGINEERING.md
+.forgeloop/kit/GUIDE_ROUTER.md
+.forgeloop/kit/PROJECT_PROFILE.md
+.forgeloop/kit/LOOP_SYSTEM_DESIGN.md
+.forgeloop/kit/QUALITY_SCORECARD.md
+.forgeloop/kit/TERMINOLOGY.md
+.forgeloop/kit/EXECUTION_STATE.md
+.forgeloop/kit/DELEGATION_PROTOCOL.md
+.forgeloop/kit/ORCHESTRATOR_INTEGRATION.md
+.forgeloop/kit/THREAT_MODEL.md
+.forgeloop/kit/CONTRACT_COVERAGE.md
+.forgeloop/kit/THIRD_PARTY_NOTICES.md
+.forgeloop/kit/LICENSE
+.forgeloop/kit/LICENSE-DOCS.md
+.forgeloop/kit/ENG/
+.forgeloop/kit/schemas/
 .github/copilot-instructions.md
 .cursor/rules/project-loop.mdc
-ENG/
-schemas/
 ```
 
 If the target already has `AGENTS.md`, `CLAUDE.md`, Copilot instructions, or
@@ -366,8 +455,10 @@ maintain and validate this source repository.
 ### First run
 
 On the first task in a target project with code or manifests, change
-`profile-mode` from `template` to `project`, discover the stack, and record only
-confirmed facts in `PROJECT_PROFILE.md`. Keep `language: en`.
+`profile-mode` from `template` to `project` in
+`.forgeloop/kit/PROJECT_PROFILE.md`, discover the stack, and record only
+confirmed facts there. In this source checkout, the canonical profile is the
+root `PROJECT_PROFILE.md`. Keep `language: en`.
 
 The profile must not store tokens, passwords, keys, credentials, or task logs.
 Unknown commands remain unverified until a real source identifies them.
@@ -392,7 +483,7 @@ package installation or its automated tests.
 ### Update the kit
 
 When adopting a newer version, preserve target-specific facts from
-`PROJECT_PROFILE.md`. Compare adapters before replacing them, update the loop,
+`.forgeloop/kit/PROJECT_PROFILE.md`. Compare adapters before replacing them, update the loop,
 router, notices, and guides as one coherent set, and never erase local
 instructions. If validators were copied, run:
 
@@ -447,8 +538,9 @@ Optional provider-backed operations follow this boundary:
 
 Provide optional credentials through the process environment or the official
 Qwen configuration file at `~/.qwen-mm-plugins/config` (or its documented
-override). Never put keys in Git, `PROJECT_PROFILE.md`, or copied instruction
-files. The agent must leave an API-backed capability disabled when its key or
+override). Never put keys in Git, the target's
+`.forgeloop/kit/PROJECT_PROFILE.md`, or copied instruction files. The agent must
+leave an API-backed capability disabled when its key or
 service endpoint is absent, and report missing system dependencies instead of
 claiming that the feature is available.
 
@@ -477,12 +569,12 @@ adoption. Local rendering requires Node.js 22+ and FFmpeg.
 ├── AGENT_COMPATIBILITY.md          # supported agents and official sources
 ├── LOOP_ENGINEERING.md             # canonical operating cycle
 ├── GUIDE_ROUTER.md                 # contextual guide selection
-├── PROJECT_PROFILE.md              # verified project facts
+├── PROJECT_PROFILE.md              # source profile (target copy is under .forgeloop/kit/)
 ├── LOOP_SYSTEM_DESIGN.md           # architecture and boundaries
 ├── THIRD_PARTY_NOTICES.md          # provenance and rights
 ├── LICENSE                         # CLI and validator code license
 ├── LICENSE-DOCS.md                 # original documentation license boundary
-├── ENG/                            # eight English guides
+├── ENG/                            # package-source English guides
 ├── .cursor/rules/                  # always-active Cursor rule
 ├── .github/copilot-instructions.md # GitHub Copilot entry point
 ├── .github/workflows/              # quality automation
@@ -495,6 +587,11 @@ adoption. Local rendering requires Node.js 22+ and FFmpeg.
 └── README.md
 ```
 
+The source repository keeps canonical documents at the root for package
+development and validation. A bootstrapped target uses the hidden-kit layout
+shown above; mutable contract, route, state, gate, event, preflight, and
+receipt artifacts remain directly under `.forgeloop/`.
+
 ## Maintenance
 
 - Preserve guide requirements, exceptions, numbers, examples, and references when editing.

package/THIRD_PARTY_NOTICES.md

@@ -127,3 +127,14 @@ collection. Do not host, redistribute, or infer rights for a font, image,
 template, prompt, audio asset, or other premium material from a citation or
 catalog listing. Verify the exact resource's author, license, attribution,
 hosting, and current terms before use.
+
+## Taste Skill
+
+The contextual frontend taste guide is informed by Taste Skill:
+
+- Taste Skill, Copyright (c) 2026 Leonxlnx, MIT License.
+- Source: <https://github.com/leonxlnx/taste-skill>
+
+ForgeLoop includes a short, adapted guide under `ENG/taste-frontend-eng.md`.
+It does not vendor upstream runtime code, depend on its repository at runtime,
+or make its prescriptive examples universal.

package/THREAT_MODEL.md

@@ -12,7 +12,7 @@ remaining trust boundaries and their executable evidence.
 | --- | --- | --- | --- | --- | --- |
 | Path traversal | Writes or reads outside the selected target | Target path and every managed relative path | `ensureWithin`, safe-path checks, realpath containment, Windows-drive rejection | A separately privileged process can change the filesystem after validation | `tests/core.test.js`, `tests/portability.test.js`, `tests/fixtures/protocol/invalid/path-traversal.json` |
 | Symlink escape | Redirects a managed path to another directory | Existing target parents and artifact paths | Reject symlinked targets, parents, and destinations before access | The check is not a filesystem lock | `tests/core.test.js`, `tests/portability.test.js`, `tests/fixtures/protocol/invalid/symlink-target.json` |
-| Malicious manifest | Causes unsafe update or false ownership claims | `.forgeloop/manifest.json` | Schema, hash, safe-path, and preserve-flag validation; conflicts remain visible | A trusted operator can still deliberately edit the manifest | `tests/cli.test.js`, `tests/core.test.js` |
+| Malicious manifest | Causes unsafe update or false ownership claims | `.forgeloop/manifest.json` | Schema, managed/legacy hash, safe-path, and preserve-flag validation; incomplete migration remains visible | A trusted operator can still deliberately edit the manifest | `tests/cli.test.js`, `tests/core.test.js`, `tests/hidden-layout.test.js` |
 | Malicious work-state | Resumes stale, secret-bearing, or invalid work | `.forgeloop/work-state.json` | Schema/semantic checks, version checks, transition checks, contract/HEAD/artifact freshness, secret scan, size/depth bounds | Freshness cannot prove that an external process did not alter a file immediately afterward | `tests/work-state.test.js`, `tests/checkpoint-freshness.test.js`, `tests/security-limits.test.js` |
 | Forged preparation | Makes an agent's prose claim look like a completed preflight | Contract, route, gate, and preflight artifacts | Canonical SHA-256 fingerprints, guide-declared gate requirements, stale-artifact checks, and `E_*` failures | The CLI cannot stop a separate process from writing project files before preflight | `tests/protocol-artifacts.test.js`, `tests/preflight.test.js` |
 | Chronology rewrite | Hides execution before route, gates, or verification | `.forgeloop/events.ndjson` | Append-only local ledger, sequence numbers, hash chaining, and chronology validation without prompts or hidden reasoning | A privileged process can still replace the ledger after validation | `tests/lifecycle.test.js` |

package/conformance/README.md

@@ -4,6 +4,10 @@ These scenarios are adapter-facing contracts. They describe requests and the
 artifacts a live agent must produce; they do not invoke a model runtime and are
 not part of the deterministic `npm test` execution path.
 
+The current published baseline for new runs is
+`@cassiomc1/forgeloop@0.1.9`. Pin that version when preparing a reproducible
+blind run; historical reports retain the exact package version they used.
+
 Run a scenario in a disposable target using the Standard profile first:
 
 ```bash
@@ -32,7 +36,7 @@ implementation
 Use the Strict profile only as a separate experiment:
 
 ```bash
-# PROJECT_PROFILE.md must be verified before this profile starts.
+# .forgeloop/kit/PROJECT_PROFILE.md must be verified before this profile starts.
 npx @cassiomc1/forgeloop preflight --strict --json
 npx @cassiomc1/forgeloop audit --strict --json
 npx @cassiomc1/forgeloop complete --strict --json
@@ -43,6 +47,34 @@ diagnostic records belong under [`conformance/runs/`](./runs/); they must not
 contain secrets, credentials, hidden reasoning, or unnecessary conversation
 history.
 
+## Release identity evidence
+
+Every live-run report records the exact published package used by the target.
+Include all of these fields before sending the blind prompt:
+
+```text
+package: @cassiomc1/forgeloop@X.Y.Z
+npm gitHead: <40-character commit SHA>
+release commit: <40-character commit SHA>
+GitHub tag: vX.Y.Z -> <40-character commit SHA>
+tarball URL: https://registry.npmjs.org/...
+tarball SHA-1: <40-character hex digest>
+npm SHA-512 integrity: sha512-<base64 digest>
+release identity: RELEASE_IDENTITY_VALID
+```
+
+Run the repository's read-only verifier against the exact release commit:
+
+```bash
+RELEASE_COMMIT="$(git rev-list -n1 vX.Y.Z)"
+npm run release:identity -- --version X.Y.Z --release-commit "$RELEASE_COMMIT"
+```
+
+Do not interpret a local package version, a green build, or a tarball URL by
+itself as publication proof. If the verifier cannot establish every identity
+field, record `RELEASE_IDENTITY_NOT_VERIFIED` or
+`RELEASE_IDENTITY_INVALID` and do not start the blind run.
+
 The complete-website scenario deliberately fails when implementation starts
 before the contract, route, and required gates exist.
 
@@ -73,3 +105,9 @@ cannot disable a mandatory approval workflow, record `TEST_NOT_STARTED` and do
 not interpret the run as a conformance failure or success. An installed
 workflow and a compatible workflow are separate claims; use
 `INCOMPATIBLE WITH AUTONOMOUS MODE`, not "broken", for the former.
+
+Every live-run report must classify how it ended with exactly one
+`terminationSource`: `AGENT`, `OPERATOR`, `HARNESS`, `TIMEOUT`, or `BLOCKER`.
+An operator-terminated run is recorded as `RUN_STATUS: OPERATOR_INTERRUPTED`,
+`CONFORMANCE: PARTIAL`, with post-termination capabilities marked
+`NOT_REACHED` and the smallest failure class `OPERATOR_INTERRUPTION`.

package/conformance/blind-premium-website/EXPECTED_ROUTE.json

@@ -3,5 +3,5 @@
   "surfaces": ["ui", "forms"],
   "risks": ["accessibility"],
   "platforms": ["web"],
-  "guides": ["premium", "design", "accessibility", "clean", "test", "security", "performance"]
+  "guides": ["premium", "design", "taste", "accessibility", "clean", "test", "security", "performance"]
 }

package/conformance/complete-website/EXPECTED_ROUTE.json

@@ -3,5 +3,5 @@
   "surfaces": ["ui", "forms"],
   "risks": ["accessibility"],
   "platforms": ["web"],
-  "guides": ["premium", "design", "accessibility", "clean", "test", "security", "performance"]
+  "guides": ["premium", "design", "taste", "accessibility", "clean", "test", "security", "performance"]
 }