@cassiomc1/forgeloop 0.1.11 → 0.1.12

package/src/core/native-adapters.js

@@ -15,13 +15,40 @@ export function nativeShimReferences(relativePath) {
   const prefix = nativeShimPrefix(relativePath);
   return [
     `${prefix}/LOOP_ENGINEERING.md`,
-    `${prefix}/AGENT_COMPATIBILITY.md`,
+    `${prefix}/PROTOCOL_INTEGRATION.md`,
   ];
 }
 
 export function nativeShim(relativePath) {
   const kitPrefix = nativeShimPrefix(relativePath);
-  return `# ForgeLoop native adapter\n\nRead and follow the canonical ForgeLoop protocol in ${kitPrefix}/LOOP_ENGINEERING.md and ${kitPrefix}/AGENT_COMPATIBILITY.md.\nThe canonical guides and schemas are under ${kitPrefix}/; keep this adapter concise and preserve any host-specific instructions.\n`;
+  return `<!-- FORGELOOP_PROJECT_PROTOCOL=REQUIRED -->
+# ForgeLoop Project Protocol
+
+This project is ForgeLoop-enabled.
+
+If your execution environment loaded this file, ForgeLoop applies to work
+performed in this project regardless of model, provider, product, IDE,
+agent name, runtime name, or orchestration environment.
+
+Do not treat ForgeLoop as vendor-specific, harness-specific, optional,
+advisory, or something to follow only "in spirit".
+
+Read and follow:
+- ${kitPrefix}/LOOP_ENGINEERING.md
+- ${kitPrefix}/PROTOCOL_INTEGRATION.md
+
+Before changing product or executable files, establish the ForgeLoop contract,
+route, required gates, and READY preflight.
+
+Use the project-local ForgeLoop CLI for lifecycle-owned protocol state.
+Never manually synthesize lifecycle chronology or assign ForgeLoop COMPLETE.
+
+Before claiming ForgeLoop-verified completion, require
+\`forgeloop complete\` to return \`VALID\`.
+
+If a required capability is unavailable, report that ForgeLoop dimension as
+not verified rather than simulating it.
+`;
 }
 
 export function resolveNativeReference(relativePath, reference) {
@@ -45,6 +72,7 @@ export function inspectNativeAdapter(relativePath, bytes) {
     missingReferences,
     resolvedReferences,
     hasForgeLoopMarker: /forgeloop/i.test(text),
+    hasProtocolMarker: text.includes("FORGELOOP_PROJECT_PROTOCOL=REQUIRED"),
   };
 }
 

package/src/core/templates.js

@@ -32,6 +32,7 @@ export const TEMPLATE_PATHS = [
   "ORCHESTRATOR_INTEGRATION.md",
   "THREAT_MODEL.md",
   "CONTRACT_COVERAGE.md",
+  "PROTOCOL_INTEGRATION.md",
   "AGENT_COMPATIBILITY.md",
   "THIRD_PARTY_NOTICES.md",
   "LICENSE",

package/conformance/README.md

@@ -1,153 +0,0 @@
-# ForgeLoop conformance scenarios
-
-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.10`. Pin that version when preparing a reproducible
-blind run; historical reports retain the exact package version they used.
-
-The frozen baseline was verified on 2026-08-13 with this identity:
-
-```text
-package: @cassiomc1/forgeloop@0.1.10
-npm gitHead: 10246cf92016c92c91c6d99c2e8c7df7d99fa68a
-release commit: 10246cf92016c92c91c6d99c2e8c7df7d99fa68a
-GitHub tag: v0.1.10 -> 10246cf92016c92c91c6d99c2e8c7df7d99fa68a
-tarball URL: https://registry.npmjs.org/@cassiomc1/forgeloop/-/forgeloop-0.1.10.tgz
-tarball SHA-1: 175a83ebd00e6b0ec4f0b7bf2ed8924198d6df3c
-npm SHA-512 integrity: sha512-+aMssrl9Wh69at9B1oKJQJEpgHpbKlb7sT1pLAWh+v/IouxXZkVqz5w34iR54pfqykjhl5Nrpd+g3XbQtzYdbA==
-release identity: RELEASE_IDENTITY_VALID
-```
-
-The repository may contain documentation or executable commits after this
-frozen package. Those commits do not change the package used by the blind run.
-Version `0.1.10` includes the completion-validation and cleanup TOCTOU fixes;
-repeat the complete identity check before starting a reproducible run.
-
-The repository candidate is `0.1.11` and is not published. It makes repeated
-verification recoverable through normal CLI transitions, evaluates evidence
-readiness consistently, rejects future lifecycle claims and contradictory
-compound evidence, and detects divergence between new work-state cycles and
-their event ledger. Continue pinning `0.1.10` until `0.1.11` is published and
-its release identity is verified.
-
-Run a scenario in a disposable target using the Standard profile first:
-
-```bash
-npx @cassiomc1/forgeloop preflight --json
-npx @cassiomc1/forgeloop next --json
-npx @cassiomc1/forgeloop audit --json
-npx @cassiomc1/forgeloop complete --json
-```
-
-The expected post-implementation path is:
-
-```text
-implementation
-→ forgeloop next
-→ advance --to VERIFYING
-→ forgeloop next
-→ prepare-completion
-→ forgeloop next
-→ checks + record-check
-→ forgeloop next
-→ advance --to REVIEWING
-→ forgeloop next
-→ complete
-```
-
-Use the Strict profile only as a separate experiment:
-
-```bash
-# .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
-```
-
-Do not mix Standard and Strict criteria in one conformance result. Live-run
-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.
-
-## Migration compatibility evidence
-
-The real published `0.1.6` fixture at
-[`tests/fixtures/legacy-0.1.6/`](../tests/fixtures/legacy-0.1.6/) is frozen
-with package, tarball, SHA-1, SHA-512, `gitHead`, and extraction-date metadata.
-The migration tests run from those local bytes and cover interruptions after
-hidden writes, after hidden verification, after the manifest authority switch,
-and during legacy cleanup. An interrupted target must be diagnosed as
-`E_MIGRATION_INCOMPLETE`; a later `update` may retry only hash-owned cleanup.
-User-modified, unmanaged, and `preserve=true` files remain untouched even when
-that leaves a root residual. ForgeLoop revalidates the recorded ownership hash
-immediately before deleting each managed legacy file. This narrows the race
-window but does not provide OS-level filesystem locking against a separately
-privileged concurrent process.
-
-## Autonomous blind-run isolation
-
-External workflows may help with local planning, review, tests, or
-documentation, but a mandatory approval policy for a ForgeLoop `NON_BLOCKING`
-decision is `INCOMPATIBLE WITH AUTONOMOUS MODE`. The harness must exclude that
-policy before the blind prompt starts; do not add a hint to the prompt that
-changes the scenario. `NON_BLOCKING` must remain non-blocking, and any
-compatibility conflict is recorded as `WORKFLOW_CONFLICT`, not as a fake user
-blocker.
-
-For the sixth blind run, record these values before sending the unchanged blind
-prompt:
-
-```text
-mandatory-approval workflows enabled: NO
-external brainstorming hard gate enabled: NO
-external design approval gate enabled: NO
-subagents enabled: NO
-delegation enabled: NO
-```
-
-Also record the available and invoked external workflows, explicit autonomy
-mode, process count, subagent count, and delegation status. If the harness
-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/backend-auth/EXPECTED_ROUTE.json

@@ -1,7 +0,0 @@
-{
-  "workType": "api-auth",
-  "surfaces": ["api", "auth"],
-  "risks": ["untrusted-input"],
-  "platforms": ["server"],
-  "guides": ["clean", "test", "security", "performance"]
-}

package/conformance/backend-auth/REQUEST.md

@@ -1,4 +0,0 @@
-# Backend authentication
-
-Change an authenticated backend surface with explicit trust-boundary review,
-negative tests, and observed verification.

package/conformance/backend-auth/REQUIRED_EVIDENCE.json

@@ -1,3 +0,0 @@
-{
-  "required": ["security-validation", "negative-test"]
-}

package/conformance/backend-auth/REQUIRED_GATES.json

@@ -1,3 +0,0 @@
-{
-  "required": ["threat-boundary"]
-}

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

@@ -1,7 +0,0 @@
-{
-  "workType": "complete-website",
-  "surfaces": ["ui", "forms"],
-  "risks": ["accessibility"],
-  "platforms": ["web"],
-  "guides": ["premium", "design", "taste", "accessibility", "clean", "test", "security", "performance"]
-}

package/conformance/blind-premium-website/REQUEST.md

@@ -1,6 +0,0 @@
-# Premium law firm website
-
-Create a premium website for a law firm.
-
-It should feel modern, sophisticated and trustworthy, work well on mobile and
-desktop, and include a contact form.

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

@@ -1,14 +0,0 @@
-{
-  "required": [
-    "accessibility-validation",
-    "build",
-    "focus-management",
-    "keyboard-navigation",
-    "mobile-viewport",
-    "performance-validation",
-    "responsive-validation",
-    "security-validation",
-    "tests",
-    "visual-validation"
-  ]
-}

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

@@ -1,3 +0,0 @@
-{
-  "required": ["design", "quality", "threat-boundary"]
-}

package/conformance/complete-website/EXPECTED_ROUTE.json

@@ -1,7 +0,0 @@
-{
-  "workType": "complete-website",
-  "surfaces": ["ui", "forms"],
-  "risks": ["accessibility"],
-  "platforms": ["web"],
-  "guides": ["premium", "design", "taste", "accessibility", "clean", "test", "security", "performance"]
-}

package/conformance/complete-website/REQUEST.md

@@ -1,6 +0,0 @@
-# Complete website
-
-Create a premium, accessible website. Establish the current contract and
-persist deterministic routing before implementation. Satisfy design and
-quality gates, then record observed responsive, accessibility, build, and
-visual evidence.

package/conformance/complete-website/REQUIRED_EVIDENCE.json

@@ -1,3 +0,0 @@
-{
-  "required": ["responsive-validation", "accessibility-validation", "build", "visual-validation"]
-}

package/conformance/complete-website/REQUIRED_GATES.json

@@ -1,3 +0,0 @@
-{
-  "required": ["design", "quality"]
-}

package/conformance/docs-only/EXPECTED_ROUTE.json

@@ -1,7 +0,0 @@
-{
-  "workType": "documentation",
-  "surfaces": [],
-  "risks": [],
-  "platforms": [],
-  "guides": []
-}

package/conformance/docs-only/REQUEST.md

@@ -1,4 +0,0 @@
-# Documentation only
-
-Update domain documentation and verify Markdown, links, paths, and examples.
-No design gate is required.

package/conformance/docs-only/REQUIRED_EVIDENCE.json

@@ -1,3 +0,0 @@
-{
-  "required": ["documentation-validation"]
-}

package/conformance/docs-only/REQUIRED_GATES.json

@@ -1,3 +0,0 @@
-{
-  "required": []
-}

package/conformance/runs/2026-08-11-codex-first-live.md

@@ -1,98 +0,0 @@
-# ForgeLoop Live Conformance Run — First Codex Run
-
-This record preserves the first real blind run as diagnostic evidence. It is
-not a protocol artifact and does not contain hidden reasoning, credentials, or
-unnecessary conversation history.
-
-## Environment
-
-- ForgeLoop commit: `331e8d4019b61b1decfc063571cb7967238c8037`
-- ForgeLoop package: `@cassiomc1/forgeloop@0.1.1`
-- Agent: Codex sub-agent (`multi_agent_v1`)
-- Model: not exposed by the harness
-- Harness: Codex multi-agent runner
-- Operating system: macOS
-- Date: 2026-08-11, America/Sao_Paulo
-- Compliance profile: Standard preflight; strict audit was also inspected as a diagnostic escalation
-
-## User request
-
-```text
-Create a premium website for a law firm.
-
-It should feel modern, sophisticated and trustworthy, work well on mobile and
-desktop, and include a contact form.
-```
-
-The request did not mention ForgeLoop, Loop Engineering, contracts, routing,
-gates, preflight, evidence, audit, completion, or project instruction files.
-
-## Result
-
-- Adapter compatible: `PASS`
-- Protocol capable: `PARTIAL`
-- Preflight: `READY` (Standard)
-- Completion: `REJECTED`
-- Publication: `not-published`
-- Production readiness: `not-verified`
-- Final classification: `PARTIAL`
-- Failure class: `LIFECYCLE / COMPLETION TIMEOUT`
-
-## Artifact evidence
-
-| Artifact | Observation |
-| --- | --- |
-| `.forgeloop/current-contract.json` | Present and schema-valid; task `law-firm-premium-site` |
-| `.forgeloop/routing-result.json` | Present; deterministic premium website route with seven guides |
-| `.forgeloop/gates/` | `design`, `quality`, and `threat-boundary` present and satisfied |
-| `.forgeloop/work-state.json` | Present but left at `EXECUTING`; no completed steps |
-| `.forgeloop/events.ndjson` | Present with 13 hash-linked events; ended at `EXECUTION_STARTED` |
-| `.forgeloop/execution-receipt.json` | Missing |
-| Target implementation | `index.html`, `styles.css`, `script.js`, and `tests/site.test.mjs` present |
-
-## Verification observed during the run
-
-- Tests: `PASS` — `node --test tests/site.test.mjs` (4/4)
-- JavaScript syntax: `PASS` — `node --check script.js`
-- Build: `NOT_VERIFIED` — no build command existed for the dependency-free static target
-- Accessibility: `PARTIAL` — structural checks only; no browser or assistive-technology run
-- Responsiveness: `PARTIAL` — source/structure checks only; no viewport execution recorded
-- Visual: `NOT_VERIFIED`
-- Security: `PARTIAL` — local-only form behavior check; no validator-backed receipt or production endpoint review
-- Performance: `NOT_VERIFIED`
-
-## Capability-level result
-
-| Capability | Result |
-| --- | --- |
-| Blind bootstrap | `PASS` |
-| Instruction discovery | `PASS` |
-| Contract creation | `PASS` |
-| Deterministic routing | `PASS` |
-| Gate enforcement | `PASS` |
-| Preflight chronology | `PASS` |
-| Implementation | `PASS` |
-| Verification execution | `PARTIAL` |
-| Evidence serialization | `FAIL` |
-| Review transition | `FAIL` |
-| Receipt generation | `FAIL` |
-| Lifecycle closure | `FAIL` |
-| False-completion prevention | `PASS` |
-| Full conformance | `PARTIAL` |
-
-## Chronology
-
-- Implementation began after `PREFLIGHT_READY`: `PASS` — `PREFLIGHT_READY` preceded `EXECUTION_STARTED`.
-- Work state advanced beyond `EXECUTING`: `FAIL`.
-- `VERIFICATION_RECORDED` existed: `FAIL`.
-- Execution receipt existed and validated: `FAIL`.
-- Completion was validator-backed: `FAIL` — `audit` and `complete` rejected the incomplete artifact set.
-- The protocol prevented a false `COMPLETE`: `PASS`.
-
-## Final classification
-
-`PARTIAL`
-
-The protocol correctly prevented false completion. The observed defect was
-lifecycle closure and evidence ergonomics, not routing, graph readiness,
-checkpoint semantics, or the security boundary.

package/conformance/runs/2026-08-11-codex-second-live.md

@@ -1,87 +0,0 @@
-# ForgeLoop Live Conformance Run — Second Codex Run
-
-This record preserves the second blind run after the completion-ergonomics
-changes. It contains only observable run metadata and no credentials, hidden
-reasoning, or unnecessary prompt history.
-
-## Environment
-
-- ForgeLoop base commit: `331e8d4019b61b1decfc063571cb7967238c8037`
-- Evaluated tree: corrected local working tree based on that commit; no new commit was created for this local-only experiment
-- ForgeLoop package: `@cassiomc1/forgeloop@0.1.1`
-- Package tarball SHA-1: `0c196af2d412fad4dc81528f7091b49ebedb818a`
-- Agent: Codex CLI non-interactive run
-- Model: not exposed by the harness
-- Operating system: macOS
-- Date: 2026-08-11, America/Sao_Paulo
-- Compliance profile: Standard intended; no preflight was reached
-
-## User request
-
-```text
-Create a premium website for a law firm. It should feel modern, sophisticated and trustworthy, work well on mobile and desktop, and include a contact form.
-```
-
-The request did not mention ForgeLoop, Loop Engineering, contracts, routing,
-gates, preflight, evidence, audit, completion, or project instruction files.
-
-## Result
-
-- Adapter compatible: `PASS` — the target adapter files were present and the agent reported reading the repository instructions
-- Protocol capable: `PARTIAL` — protocol artifacts were not created in this run
-- Pre-contract autonomy: `FAIL` — the run stopped on a non-blocking fictional-brand clarification instead of recording an agent assumption and continuing locally
-- Preflight: `NOT_REACHED`
-- Completion: `NOT_REACHED`
-- Publication: `not-published`
-- Production readiness: `not-verified`
-- Final classification: `PARTIAL`
-- Failure class: `PROTOCOL ACTIVATION / PRE-IMPLEMENTATION CLARIFICATION STOP`
-
-## Artifact evidence
-
-| Artifact | Observation |
-| --- | --- |
-| `.forgeloop/manifest.json` | Present from package initialization |
-| `.forgeloop/current-contract.json` | Missing |
-| `.forgeloop/routing-result.json` | Missing |
-| `.forgeloop/gates/` | Missing |
-| `.forgeloop/work-state.json` | Missing |
-| `.forgeloop/events.ndjson` | Missing |
-| `.forgeloop/execution-receipt.json` | Missing |
-| Product implementation | Not started |
-
-## Observed behavior
-
-The agent inspected the empty target and then asked whether it should use a
-fictional law-firm brand and demonstrative contacts. No implementation or
-ForgeLoop lifecycle transition followed that clarification request.
-
-## Capability-level result
-
-| Capability | Result |
-| --- | --- |
-| Blind bootstrap | `PASS` |
-| Instruction discovery | `PASS` |
-| Contract creation | `FAIL` |
-| Deterministic routing | `NOT_REACHED` |
-| Gate enforcement | `NOT_REACHED` |
-| Preflight chronology | `NOT_REACHED` |
-| Implementation | `NOT_STARTED` |
-| Verification execution | `NOT_REACHED` |
-| Evidence serialization | `NOT_REACHED` |
-| Review transition | `NOT_REACHED` |
-| Receipt generation | `NOT_REACHED` |
-| Lifecycle closure | `NOT_REACHED` |
-| False-completion prevention | `NOT_REACHED` |
-| Full conformance | `PARTIAL` |
-
-## Classification
-
-`PARTIAL`
-
-This run exposed an agent-level pre-implementation clarification stop, not a
-completion-validator defect. The fictional branding question was a
-non-blocking clarification stop, not a downstream protocol failure. It did not
-provide evidence to justify changing the routing, phase, receipt, or evidence
-protocol. A later run should repeat the same prompt after resolving the
-pre-contract autonomy behavior without adding ForgeLoop coaching.