yaaw-se 0.3.11 → 0.3.13

package/dist/payload/yaaw-core/system/schemas/repository-identity.schema.json

@@ -4,44 +4,17 @@
   "type": "object",
   "required": ["schema","algorithm","status","workspace_scope","git_root_relation","head_commit","dirty","worktree_digest","components","changed_paths","error"],
   "properties": {
-    "schema": {"const": "yaaw.repository-identity/v2"},
-    "algorithm": {"type": ["string","null"], "enum": ["yaaw-worktree-v1","yaaw-worktree-v2",null]},
-    "status": {"enum": ["READY","UNVERSIONED","UNAVAILABLE","ROOT_MISMATCH","IDENTITY_FAILED"]},
-    "workspace_scope": {"type": "string", "minLength": 1},
-    "git_root_relation": {"enum": ["same","ancestor","none","unknown"]},
-    "head_commit": {"type": ["string","null"]},
-    "dirty": {"type": ["boolean","null"]},
-    "worktree_digest": {"type": ["string","null"]},
-    "components": {
-      "anyOf": [
-        {"type": "null"},
-        {
-          "type": "object",
-          "required": ["status_sha256","unstaged_diff_sha256","staged_diff_sha256","untracked_manifest_sha256"],
-          "properties": {
-            "status_sha256": {"type": "string"},
-            "unstaged_diff_sha256": {"type": "string"},
-            "staged_diff_sha256": {"type": "string"},
-            "untracked_manifest_sha256": {"type": "string"}
-          },
-          "additionalProperties": false
-        }
-      ]
-    },
-    "changed_paths": {
-      "type": "array",
-      "items": {
-        "type": "object",
-        "required": ["path","kind"],
-        "properties": {
-          "path": {"type": "string", "minLength": 1},
-          "kind": {"enum": ["tracked","untracked"]},
-          "sha256": {"type": "string"}
-        },
-        "additionalProperties": false
-      }
-    },
-    "error": {"type": ["string","null"]}
+    "schema":{"const":"yaaw.repository-identity/v2"},
+    "algorithm":{"type":["string","null"],"enum":["yaaw-worktree-v1","yaaw-worktree-v2","yaaw-worktree-v3",null]},
+    "status":{"enum":["READY","UNVERSIONED","UNAVAILABLE","ROOT_MISMATCH","IDENTITY_FAILED"]},
+    "workspace_scope":{"type":"string","minLength":1},
+    "git_root_relation":{"enum":["same","ancestor","none","unknown"]},
+    "head_commit":{"type":["string","null"]},
+    "dirty":{"type":["boolean","null"]},
+    "worktree_digest":{"type":["string","null"]},
+    "components":{"anyOf":[{"type":"null"},{"type":"object","required":["status_sha256","unstaged_diff_sha256","staged_diff_sha256","untracked_manifest_sha256"],"properties":{"status_sha256":{"type":"string"},"unstaged_diff_sha256":{"type":"string"},"staged_diff_sha256":{"type":"string"},"untracked_manifest_sha256":{"type":"string"}},"additionalProperties":false}]},
+    "changed_paths":{"type":"array","items":{"type":"object","required":["path","kind"],"properties":{"path":{"type":"string","minLength":1},"kind":{"enum":["tracked","untracked"]},"sha256":{"type":"string"}},"additionalProperties":false}},
+    "error":{"type":["string","null"]}
   },
-  "additionalProperties": false
+  "additionalProperties":false
 }

package/dist/payload/yaaw-core/system/templates/evidence.json

@@ -6,24 +6,7 @@
   "spec_revision": 1,
   "kind": "implementation_verification",
   "result": "PASS",
-  "repository": {
-    "schema": "yaaw.repository-identity/v2",
-    "algorithm": "yaaw-worktree-v2",
-    "status": "READY",
-    "workspace_scope": ".",
-    "git_root_relation": "same",
-    "head_commit": "COMMIT",
-    "dirty": false,
-    "worktree_digest": "sha256:DIGEST",
-    "components": {
-      "status_sha256": "HASH",
-      "unstaged_diff_sha256": "HASH",
-      "staged_diff_sha256": "HASH",
-      "untracked_manifest_sha256": "HASH"
-    },
-    "changed_paths": [],
-    "error": null
-  },
+  "repository": {"schema":"yaaw.repository-identity/v2","algorithm":"yaaw-worktree-v3","status":"READY","workspace_scope":".","git_root_relation":"same","head_commit":"COMMIT","dirty":false,"worktree_digest":"sha256:DIGEST","components":{"status_sha256":"HASH","unstaged_diff_sha256":"HASH","staged_diff_sha256":"HASH","untracked_manifest_sha256":"HASH"},"changed_paths":[],"error":null},
   "workflow": "implementation.verify-ticket",
   "commands": [],
   "checks": []

package/dist/payload/yaaw-core/system/templates/handoff.json

@@ -1,39 +1,23 @@
 {
-  "schema": "yaaw.handoff/v3",
-  "framework": {
-    "yaaw_version": "VERSION",
-    "system_schema": 3,
-    "installation_schema": 3,
-    "project_schema": 2,
-    "manifest_digest": "sha256:MANIFEST",
-    "integrity_status": "HEALTHY"
-  },
+  "schema": "yaaw.handoff/v4",
+  "framework": {},
   "role": "implementer",
   "workflow": "implementation.implement-ticket",
+  "operation": "implement-ticket",
+  "instruction": {"document":".yaaw-core/system/roles/implementer.md","operation":"implement-ticket"},
   "desired_intent": "IMPLEMENT",
-  "active_artifact": ".yaaw-core/project/tickets/TASK-000.md",
+  "active_artifact": "ticket",
+  "ticket": "TASK-000",
   "references": [],
   "reads": [],
   "writes": [],
   "forbidden_writes": [],
-  "revisions": {"product": 1, "engineering": 1, "spec": 1, "ticket": 1},
+  "revisions": {"product":1,"engineering":1,"spec":1,"ticket":1},
+  "basis": {"product_digest":null,"engineering_digest":null,"spec_digest":null,"ticket_digest":null,"ticket_status":"READY"},
   "expertise": [],
   "host_expertise": [],
-  "expected_output": "implementation evidence",
-  "result_vocabulary": ["VERIFICATION_PASS","VERIFICATION_FAIL","REPLAN_REQUIRED","BLOCKED"],
+  "expected_output": "bounded implementation and evidence",
+  "result_vocabulary": ["VERIFICATION_PASS","BLOCKED"],
   "repository_requirement": "IDENTITY",
-  "repository": {
-    "schema": "yaaw.repository-identity/v2",
-    "algorithm": "yaaw-worktree-v2",
-    "status": "READY",
-    "workspace_scope": ".",
-    "git_root_relation": "same",
-    "head_commit": "COMMIT",
-    "dirty": false,
-    "worktree_digest": "sha256:DIGEST",
-    "components": {"status_sha256": "HASH", "unstaged_diff_sha256": "HASH", "staged_diff_sha256": "HASH", "untracked_manifest_sha256": "HASH"},
-    "changed_paths": [],
-    "error": null
-  },
-  "transition_sequence": 0
+  "repository": {"schema":"yaaw.repository-identity/v2","algorithm":"yaaw-worktree-v3","status":"READY","workspace_scope":".","git_root_relation":"same","head_commit":"COMMIT","dirty":false,"worktree_digest":"sha256:DIGEST","components":{"status_sha256":"HASH","unstaged_diff_sha256":"HASH","staged_diff_sha256":"HASH","untracked_manifest_sha256":"HASH"},"changed_paths":[],"error":null}
 }

package/dist/payload/yaaw-core/system/templates/intent.json

@@ -1,9 +1,9 @@
 {
-  "schema": "yaaw.intent/v2",
+  "schema": "yaaw.intent/v3",
   "source_skill": "yaaw-orchestrator",
   "desired_outcome": "CONTINUE",
   "requested_workflow": "orchestration.route",
   "target_artifact": null,
   "completion_kind": "CONTINUE_UNTIL_STOP",
-  "created_from_transition_sequence": 0
+  "created_from": {}
 }

package/dist/payload/yaaw-core/system/templates/observed-state.json

@@ -1,32 +1,9 @@
 {
-  "schema": "yaaw.observed-state/v3",
-  "framework": {
-    "yaaw_version": "VERSION",
-    "system_schema": 3,
-    "installation_schema": 3,
-    "project_schema": 2,
-    "manifest_digest": "sha256:MANIFEST",
-    "integrity_status": "HEALTHY",
-    "modified": [],
-    "missing": [],
-    "local_overrides": [],
-    "repair_required": false
-  },
-  "repository": {
-    "schema": "yaaw.repository-identity/v2",
-    "algorithm": null,
-    "status": "UNVERSIONED",
-    "workspace_scope": ".",
-    "git_root_relation": "none",
-    "head_commit": null,
-    "dirty": null,
-    "worktree_digest": null,
-    "components": null,
-    "changed_paths": [],
-    "error": "workspace is not versioned"
-  },
-  "transition_sequence": 0,
-  "claims": {},
+  "schema": "yaaw.observed-state/v4",
+  "framework": {},
+  "repository": {"schema":"yaaw.repository-identity/v2","algorithm":null,"status":"UNVERSIONED","workspace_scope":".","git_root_relation":"none","head_commit":null,"dirty":null,"worktree_digest":null,"components":null,"changed_paths":[],"error":"workspace is not versioned"},
+  "derived": {},
+  "reconstructable": true,
   "artifacts": {},
   "inconsistencies": [],
   "candidate_actions": [],

package/dist/payload/yaaw-core/system/templates/review.md

@@ -7,7 +7,7 @@ ticket_revision: 1
 spec_revision: 1
 repository:
   schema: yaaw.repository-identity/v2
-  algorithm: yaaw-worktree-v2
+  algorithm: yaaw-worktree-v3
   status: READY
   workspace_scope: .
   git_root_relation: same
@@ -28,7 +28,7 @@ evidence: []
 ## Findings
 
 ## Changeability assessment
-Record only materially relevant principles. Use PASS, FAIL, or NOT_APPLICABLE; do not use subjective scores. Blocking failures must cite concrete engineering impact rather than style preference.
+Record only materially relevant principles. Use PASS, FAIL, or NOT_APPLICABLE; blocking failures require concrete engineering impact.
 
 ## Verification
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yaaw-se",
-  "version": "0.3.11",
+  "version": "0.3.13",
   "description": "Artifact-first autonomous software engineering workflow installer.",
   "type": "module",
   "bin": {
@@ -28,7 +28,10 @@
     "prepack": "npm run test && npm run build",
     "smoke:tarball": "npm run build && node scripts/smoke_npm_tarball.mjs",
     "smoke:update": "npm run build && node scripts/smoke_npm_update.mjs",
-    "validate:schemas": "node scripts/validate_schemas.mjs"
+    "validate:schemas": "node scripts/validate_schemas.mjs",
+    "validate:contracts": "node scripts/validate_contracts.mjs .yaaw-core/system skills",
+    "smoke:dispatch-update": "npm run build && node scripts/smoke_dispatch_update.mjs",
+    "audit:workflows": "node scripts/audit_workflow_contracts.mjs .yaaw-core/system skills"
   },
   "dependencies": {
     "@clack/prompts": "1.8.1",

package/dist/payload/yaaw-core/system/core/artifact-model.md

@@ -1,43 +0,0 @@
-# Artifact model
-
-Canonical consumer workspace root is the directory containing the active YAAW installation. Canonical durable **project memory root** is `.yaaw-core/project/`.
-
-Ownership is separated under one YAAW root:
-
-- `.yaaw-core/system/core/`, `.yaaw-core/system/roles/`, `.yaaw-core/system/workflows/`, `.yaaw-core/system/expertise/`, `.yaaw-core/system/rules/`, `.yaaw-core/system/registries/`, `.yaaw-core/system/schemas/`, `.yaaw-core/system/templates/`, and `.yaaw-core/system/tools/`: package-managed framework content.
-- `.yaaw-core/project/`: durable project-owned semantic memory.
-- `.yaaw-core/runtime/`: replaceable coordination state.
-- `.yaaw-core/install/`: installer metadata only.
-
-Durable project artifacts:
-
-- `product.md`: human-approved product intent and unresolved product questions.
-- `engineering.md`: durable engineering understanding, `ENG-*` decisions, assumptions, risks, frontier, future fog, and readiness.
-- `research/RSH-*.md`: bounded external engineering research owned by Planner; research facts are not engineering decisions until promoted through normal planning.
-- `specs/SPEC-*.md`: coherent engineering contracts referencing product/decision revisions.
-- `tickets/TASK-*.md`: bounded implementation contracts.
-- `reviews/TASK-*-R*.md`: immutable review rounds tied to exact source and repository revisions.
-- `evidence/*.json`: machine-readable verification evidence tied to repository identity.
-- `.yaaw-core/project/rules/`: project-specific reusable invariants promoted from real evidence.
-- `state.json`: reconstructable routing cache and last transition provenance.
-
-Replaceable runtime artifacts:
-
-- `.yaaw-core/runtime/observed-state.json`: observed orchestration snapshot including repository capability.
-- `.yaaw-core/runtime/handoff.json`: exact dispatch contract.
-- `.yaaw-core/runtime/intent.json`: optional desired-outcome cache used while prerequisites are resolved.
-- `.yaaw-core/runtime/dispatch-failures.json`: replaceable per-handoff execution-failure ledger used only for bounded host capability escalation.
-
-Installer metadata:
-
-- `.yaaw-core/install/manifest.json`: package/integration ownership and version state. It is never semantic project truth.
-
-Markdown artifacts use YAML frontmatter for machine-readable identity/revision/status and a human-readable body for durable reasoning. Machine-readable ownership patterns live in `.yaaw-core/system/registries/artifacts.json`.
-
-Conversation is never an artifact of record. Package update logic must never treat `.yaaw-core/project/` as replaceable framework content.
-
-## Framework immutability
-
-Package-managed `.yaaw-core/system/**` content is not a semantic output surface. Normal PRD, Planner, Implementer, Reviewer, and Orchestrator workflows must not modify it. The installation manifest and `.yaaw-core/system/core/framework-integrity.md` define the runtime trust boundary.
-
-If package-managed framework bytes drift, semantic orchestration stops before project-state reconciliation. Installer repair may replace package content and runtime caches, but must preserve `.yaaw-core/project/**`.

package/dist/payload/yaaw-core/system/core/authority.md

@@ -1,21 +0,0 @@
-# Authority model
-
-Authority is semantic, not hierarchical.
-
-| Role | Owns | Must not own |
-|---|---|---|
-| Human / PRD | product goal, behavior, scope, non-goals | engineering architecture |
-| Planner | technical design, engineering decisions, specs, ticket contracts | product-intent changes |
-| Implementer | code within an admitted ticket | architecture changes outside admitted scope; acceptance |
-| Reviewer | independent acceptance, findings, repair-vs-replan classification | implementation authorship during review |
-| Orchestrator | routing, continuity, reconciliation, invalidation/recovery coordination | product, architecture, coding, self-approval |
-
-Expertise modules never grant authority. They may advise a role but cannot override the role contract.
-
-A downstream role may detect that an upstream contract is invalid, but it must return control to the owning role rather than silently rewriting that contract.
-
-## Framework authority
-
-Package-managed framework content is governed by `.yaaw-core/system/core/framework-integrity.md`. Semantic roles may report a framework defect but may not edit the framework to remove their own blocker. Installer authority is the only authority that may replace package-managed framework files in a consumer installation.
-
-Transition ownership is semantic decision ownership. Physical mutation of `.yaaw-core/project/state.json` is performed by Orchestrator after it verifies the durable output that authorized the transition.

package/dist/payload/yaaw-core/system/core/context-loading.md

@@ -1,56 +0,0 @@
-# Context loading
-
-Load the smallest authoritative context needed for the current judgment.
-
-## Progressive-disclosure invariant
-Workflow selection is metadata-first. Normal Orchestrator preparation is performed by `.yaaw-core/system/tools/orchestration-runtime.mjs`, which reads only durable metadata and the machine registries needed to produce one typed route/handoff. The Orchestrator consumes that result and **must not preload sibling or downstream workflow bodies**, templates, or expertise merely because they might be needed later.
-
-After exactly one workflow is selected:
-1. resolve that workflow through `.yaaw-core/system/registries/workflows.json`;
-2. load its body;
-3. load only handoff-declared/current artifact references and applicable rules;
-4. load selected expertise only after relevance is established;
-5. load a template only when the selected workflow will create that artifact.
-
-After durable output, return to routing before opening another workflow contract.
-
-## Fresh worker bootstrap
-When an Orchestrator dispatch runs in a fresh host worker, the worker should receive only enough parent context to locate and execute the handoff:
-- resolved workspace root;
-- target semantic role;
-- `.yaaw-core/runtime/handoff.json`;
-- instruction to load the canonical role contract and resolve the workflow through registries;
-- instruction to load only handoff-admitted artifacts/expertise/repository context;
-- instruction not to route another YAAW authority role.
-
-Do not copy the parent planning conversation, all project documents, all expertise, all workflows, review history, or a repository dump into a worker prompt. Those are either durable artifacts or discoverable only when admitted by the selected workflow.
-
-## Normal semantic context
-```text
-role contract
-+ selected workflow contract
-+ active artifact and revision
-+ directly referenced decisions/research
-+ relevant product constraints
-+ relevant project rules
-+ relevant repository files/diff
-+ selected expertise
-+ prior review finding when repairing
-+ current handoff/repository capability when dispatched
-```
-
-Do not automatically load every PRD revision, research artifact, ticket, review, expertise module, template, or the full repository.
-
-## Canonical artifact discovery
-Exact YAAW reads come from the deterministic handoff and registries. Roles do not grep for alternate YAAW artifact locations.
-
-## Handoff freshness
-A handoff binds exact artifact revisions, read/write sets, selected expertise, repository requirement, canonical repository identity, transition sequence, installed YAAW version, installation/project-state schema versions, and manifest digest.
-
-Immediately before dispatch, run:
-
-```text
-node .yaaw-core/system/tools/orchestration-runtime.mjs --workspace <WORKSPACE_ROOT> --check-handoff
-```
-
-Only `HANDOFF_FRESH` may execute. A stale result discards the handoff and returns to orchestration preparation. Runtime handoffs, intent, and observed-state snapshots are coordination caches, not semantic sources of truth.

package/dist/payload/yaaw-core/system/core/dispatch-execution.md

@@ -1,28 +0,0 @@
-# Dispatch execution contract
-
-Dispatch executes exactly one already-selected semantic handoff.
-
-## Canonical rules
-1. Public skills first become durable runtime intent.
-2. Orchestrator validates framework health, applies at most one reconciliation, validates source currency, and persists one exact handoff.
-3. A non-Orchestrator authority executes that handoff using the active host adapter's supported isolation/profile mechanism.
-4. The authority writes its durable semantic output and returns one allowed typed result.
-5. A worker message is an execution signal, not project truth. After success, failure, interruption, or lost response, Orchestrator observes reality again before routing.
-
-## Public invocation
-Direct public invocation does not bypass Orchestrator. For example, `yaaw-implement` means desired outcome `IMPLEMENT`; missing product/planning/spec/ticket prerequisites are resolved first, and the shortcut completes at `REVIEW_REQUIRED` rather than automatically reviewing.
-
-## Fresh-context invariant
-An orchestrated Implementer execution context must never become the Reviewer execution context for the same work. A dead worker is not retried blindly; durable progress is inspected first.
-
-## Authority execution profile fidelity invariant
-Provider/model execution selection belongs to the active host adapter, but changing execution mechanism may not silently change the configured effective authority profile.
-
-- `HOST_INHERIT` remains symbolic; unknown inherited model/reasoning values are never guessed.
-- If an execution mechanism exists but cannot guarantee the required profile, return `BLOCKED:HOST_EXECUTION_PROFILE_UNAVAILABLE`.
-- If strict isolation is required and no isolated mechanism exists, return `BLOCKED:HOST_ISOLATION_UNAVAILABLE`.
-- A profile/isolation stop before child creation means no authority worker ran and must not increment the execution-failure ledger.
-- Implementer/Reviewer capability fallback preserves the exact semantic role and handoff and is subject to the same profile-fidelity rule.
-
-## Provider boundary
-Provider/model mechanics remain adapter-owned. The canonical semantic path is provider-neutral and identical across supported host adapters.

package/dist/payload/yaaw-core/system/core/execution-context.md

@@ -1,61 +0,0 @@
-# Execution context
-
-## Purpose
-Define one runtime boundary for every YAAW workflow so ambient shell state and provider layout cannot silently change semantics.
-
-## Canonical workspace root
-The **workspace root** is the consumer directory that owns the active YAAW installation. Resolve it before repository or application inspection by walking from the provider's current location toward ancestors until `.yaaw-core/install/manifest.json` is found. During recovery of a damaged installation, `.yaaw-core/system/registries/paths.json` may be used as a fallback marker.
-
-The process CWD is never authoritative. `.yaaw-core/project/` is project memory, not the workspace root.
-
-## Framework integrity
-After resolving the workspace and before semantic project recovery, run only the canonical package-owned integrity gate:
-
-```text
-node .yaaw-core/system/tools/framework-integrity.mjs --workspace <WORKSPACE_ROOT>
-```
-
-Only `HEALTHY` permits semantic routing. Package drift, missing framework files, local framework overrides, or an invalid manifest produce a typed framework stop and invalidate executable handoffs. Orchestrator reports the condition; it never repairs package-managed files itself.
-
-There is no second framework-integrity implementation outside `.yaaw-core/system/tools/`.
-
-## Deterministic orchestration preparation
-Normal Orchestrator routing uses one deterministic preparation entrypoint:
-
-```text
-node .yaaw-core/system/tools/orchestration-runtime.mjs --workspace <WORKSPACE_ROOT>
-```
-
-That one invocation performs the framework gate, canonical repository identity, durable metadata inspection, routing, and handoff construction from one basis. The Orchestrator consumes its typed result; it must not reimplement repository hashing, routing precedence, artifact discovery, or handoff serialization in ad-hoc shell/Python code.
-
-Compatibility/debug inspection may use `--inspect-only`. Dispatch freshness uses `--check-handoff` immediately before execution.
-
-## Repository capability
-- `READY`: repository exists and exact identity is trustworthy.
-- `UNVERSIONED`: valid workspace, no Git repository.
-- `UNAVAILABLE`: Git or host permission unavailable.
-- `ROOT_MISMATCH`: repository/workspace ownership cannot be reconciled.
-- `IDENTITY_FAILED`: repository exists but exact identity failed.
-
-## Root-anchored command rule
-Every Git command is explicitly scoped:
-
-```text
-git -C <WORKSPACE_ROOT> ...
-```
-
-When Git top-level is an ancestor, inspection and identity remain workspace-scoped with `-- .`; unrelated sibling changes must not contaminate the active workspace identity.
-
-## Canonical identity execution
-For repository identity, every semantic workflow invokes or consumes output originating from:
-
-```text
-node .yaaw-core/system/tools/repository-identity.mjs --workspace <WORKSPACE_ROOT>
-```
-
-No role or workflow may independently compute or reserialize `worktree_digest`. Copy the returned repository identity into state, handoff, evidence, and review records.
-
-## Workflow requirements
-The machine policy in `.yaaw-core/system/registries/execution-policy.json` assigns one repository requirement to every workflow.
-
-Provider adapters point to this contract; Codex, Claude Code, Gemini CLI, and Cline do not fork repository semantics.

package/dist/payload/yaaw-core/system/core/framework-integrity.md

@@ -1,60 +0,0 @@
-# Framework integrity contract
-
-## Purpose
-Keep autonomous project execution inside an immutable package boundary. Package-managed YAAW framework semantics are inputs to consumer workflows, never workflow outputs.
-
-## Ownership classes
-Package-managed framework content is everything under `.yaaw-core/system/**`, including core contracts, roles, workflows, expertise, shared rules, registries, schemas, templates, and tools.
-
-The installer owns replacement of those files and records their package hashes in `.yaaw-core/install/manifest.json`.
-
-Project-owned durable semantics live under `.yaaw-core/project/**`. Replaceable coordination lives under `.yaaw-core/runtime/**`.
-
-## Runtime invariant
-PRD, Planner, Implementer, Reviewer, and Orchestrator must never intentionally create, edit, delete, rename, or weaken package-managed framework content during normal consumer execution.
-
-A role discovering a broken framework contract reports it. It does not repair the governing contract that constrained it.
-
-Temporary framework edits are forbidden. Restoring the bytes later does not make intermediate execution trustworthy.
-
-## Integrity gate
-Before semantic reconciliation or dispatch, Orchestrator runs:
-
-```text
-node .yaaw-core/system/tools/framework-integrity.mjs --workspace <WORKSPACE_ROOT>
-```
-
-Allowed runtime status is exactly `HEALTHY`.
-
-The following statuses stop semantic routing:
-
-- `MODIFIED`
-- `MISSING`
-- `LOCAL_OVERRIDE`
-- `MANIFEST_INVALID`
-- `UNKNOWN`
-
-A framework-integrity stop does not authorize a ticket lifecycle transition. It invalidates executable handoffs and requires installer repair/update before orchestration resumes.
-
-## Typed failures
-Use:
-
-- `FRAMEWORK_INTEGRITY_VIOLATION` when package-managed bytes differ from the installation manifest.
-- `FRAMEWORK_INTEGRITY_UNKNOWN` when integrity cannot be established safely.
-- `FRAMEWORK_CONTRACT_INCONSISTENCY` when intact canonical package contracts contradict one another.
-
-These are installation/runtime trust failures, not ticket states.
-
-## Repair authority
-Orchestrator may recommend installer repair, but only installer authority may replace package-managed files.
-
-The safe repair pattern is backup-and-replace. Package update/modify/repair invalidates replaceable runtime handoff/observation/intent caches so no dispatch survives a framework basis change:
-
-```text
-npx yaaw-se install --action repair --conflict-policy backup-replace --yes
-```
-
-Repair preserves `.yaaw-core/project/**`, restores package-managed framework content, and commits installer metadata only after verification.
-
-## No self-exemption
-No role, workflow, expertise module, project rule, handoff, or runtime observation may weaken or override this contract during consumer execution.

package/dist/payload/yaaw-core/system/core/invalidation.md

@@ -1,13 +0,0 @@
-# Invalidation propagation
-
-Prior reviews remain immutable historical evidence; current authority may become STALE without rewriting history.
-
-## Contract staleness
-For executable ticket states `READY`, `IN_PROGRESS`, `REVIEW_REQUIRED`, `REPAIR_REQUIRED`, and `PASS`, compare ticket product/engineering/spec revisions to current adopted sources before dispatch. Stable causes are `PRODUCT_SOURCE_STALE`, `ENGINEERING_SOURCE_STALE`, `SPEC_SOURCE_STALE`, `TICKET_SOURCE_STALE`, and `CONTRACT_INVALIDATED`. Their route is read from `routing-policy.json`; the current contract route is `REPLAN_REQUIRED`, and Orchestrator does not hard-code a second destination.
-
-## Acceptance staleness
-When source meaning remains current but current PASS verification/review repository identity is missing, stale, or legacy-unverifiable, preserve history and return current lifecycle authority to `REVIEW_REQUIRED`. Stable causes are `REVIEW_MISSING`, `REVIEW_REPOSITORY_STALE`, `VERIFICATION_MISSING`, `VERIFICATION_REPOSITORY_STALE`, and `LEGACY_IDENTITY_UNVERIFIABLE`.
-
-Repository identity mismatch alone never proves an architecture replan is required.
-
-Framework drift is neither contract nor acceptance invalidation. It stops orchestration fail-closed for installer repair.

package/dist/payload/yaaw-core/system/core/io-contract.md

@@ -1,23 +0,0 @@
-# Role I/O and communication contract
-
-YAAW roles communicate through durable artifacts, exact Orchestrator handoffs, and typed results. Roles never privately command peer roles.
-
-## Machine truth
-Registries define artifact ownership, role I/O, workflow mapping, execution policy, public intent, reconciliation policy, and exact handoff construction.
-
-## Public-entry invariant
-Every public skill is an intent entrypoint. It invokes `orchestration-runtime.mjs --invoke-skill <skill>`; it does not execute semantic role logic directly. Intent may prefer a destination, but it never bypasses framework health, reconciliation, source-current checks, repository policy, or handoff construction.
-
-## Communication topology
-```text
-public intent
-   -> Orchestrator observes/reconciles
-   -> one exact handoff
-   -> PRD / Planner / Implementer / Reviewer durable output
-   -> Orchestrator observes again
-```
-
-Worker text is an execution signal, not project truth. Filesystem access never grants semantic authority.
-
-## Host-execution typed stops
-`HOST_EXECUTION_PROFILE_UNAVAILABLE` means an execution mechanism existed, but it could not guarantee the configured authority profile. `HOST_ISOLATION_UNAVAILABLE` means strict isolation was required but unavailable. When either stop happens before child creation, no authority worker ran, so it is not an authority execution failure.

package/dist/payload/yaaw-core/system/core/lifecycle.md

@@ -1,23 +0,0 @@
-# Lifecycle contract
-
-YAAW advances only through durable facts adopted by Orchestrator.
-
-```text
-product missing/unready -> PRD
-product ready, planning unresolved -> Planner
-planning ready, spec missing -> create/adopt spec
-spec accepted, tickets missing -> create/register tickets
-registered DRAFT + dependencies PASS -> Planner re-evaluates admission
-Planner persists current DRAFT -> READY -> Orchestrator adopts TICKET_ADMISSION
-READY -> implementation_start fact -> IN_PROGRESS
-IN_PROGRESS -> PASS verification fact -> REVIEW_REQUIRED
-REVIEW_REQUIRED -> immutable Reviewer result -> PASS | REPAIR_REQUIRED | REPLAN_REQUIRED | BLOCKED
-REPAIR_REQUIRED -> fresh PASS verification -> REVIEW_REQUIRED
-PASS + scope_status OPEN/UNKNOWN -> Planner
-all current tickets PASS/CANCELLED + scope_status COMPLETE -> COMPLETE
-```
-
-One reconciliation is applied per observation cycle; recovery never jumps directly from `READY` to `REVIEW_REQUIRED`. Recovery is interruption-only and must not be used as the fallback for a current `DRAFT` ticket or missing planning admission.
-
-## Fresh-context invariant
-Conversation may disappear at any point. Durable artifacts and repository evidence must still identify the correct next boundary.

package/dist/payload/yaaw-core/system/core/recovery.md

@@ -1,17 +0,0 @@
-# Recovery contract
-
-Recovery reconstructs the last trustworthy durable boundary; conversation loss is never permission to repeat semantic work.
-
-- Accepted current spec not reflected in state -> adopt exactly that spec; multiple candidates block.
-- Current ticket file absent from state -> register one ticket per reconciliation cycle.
-- `READY` plus valid implementation-start evidence -> `IN_PROGRESS`.
-- `IN_PROGRESS` plus current PASS verification -> `REVIEW_REQUIRED`.
-- `IN_PROGRESS` plus start evidence but no PASS verification -> `implementation.verify-ticket`.
-- `REVIEW_REQUIRED` plus a valid current immutable review that references current PASS verification -> adopt its result before another Reviewer dispatch.
-- `REVIEW_REQUIRED` plus missing/stale/non-PASS implementation verification -> dispatch `implementation.verify-ticket` without rolling lifecycle state backward.
-- `REVIEW_REQUIRED` plus current PASS verification but missing/stale/non-referencing review -> dispatch `review.review-ticket` for a fresh immutable review round.
-- Source drift -> use routing-policy invalidation, normally `REPLAN_REQUIRED`.
-- Source-current acceptance/repository drift -> `REVIEW_REQUIRED`.
-- Missing proof is `BLOCKED` only when no authorized deterministic workflow can safely regenerate or refresh that proof; recoverable proof gaps route to their owning workflow.
-
-Each observation applies at most one legal reconciliation and increments transition provenance once.

package/dist/payload/yaaw-core/system/core/routing.md

@@ -1,21 +0,0 @@
-# Routing contract
-
-Routing chooses exactly one next canonical workflow from observed durable reality. Production semantics live in `.yaaw-core/system/tools/orchestration-engine.mjs`; `orchestration-runtime.mjs` is the filesystem/CLI shell.
-
-Before semantic routing:
-1. framework integrity must be `HEALTHY`;
-2. apply at most one highest-priority reconciliation, then observe again;
-3. validate ticket source currency;
-4. enforce repository requirement;
-5. consider public intent only as a destination preference.
-
-## Priority
-1. If a ticket is `REPLAN_REQUIRED`, route Planner.
-2. If a ticket is `REPAIR_REQUIRED`, route bounded repair.
-3. If a ticket is `REVIEW_REQUIRED`, route Reviewer unless a valid durable review result must first be adopted.
-4. If a ticket is `IN_PROGRESS`, current PASS verification is adopted; otherwise valid start evidence routes standalone verification, never blind reimplementation.
-5. If a dependency-satisfied ticket is `READY`, route Implementer.
-6. Missing current spec/tickets route Planner prerequisites.
-7. When all current tickets are `PASS`/`CANCELLED`, `scope_status COMPLETE` permits completion; `OPEN` or `UNKNOWN` routes Planner.
-
-Intent never skips these rules. `yaaw-implement` from an idea-only project can therefore route PRD -> planning -> spec -> tickets -> implementation while preserving desired outcome IMPLEMENT.

package/dist/payload/yaaw-core/system/core/state-model.md

@@ -1,14 +0,0 @@
-# State model
-
-Canonical project state is `.yaaw-core/project/state.json` using `yaaw.project-state/v2`.
-
-State is a routing/adoption ledger, not semantic authority. Ticket frontmatter is admission/history metadata and never directly overrides the reconciled ticket lifecycle value in state. A Planner-owned `DRAFT -> READY` artifact change is instead a candidate durable admission fact: Orchestrator validates current sources, planning readiness, dependency completion, repository identity, and the legal transition before adopting it as `TICKET_ADMISSION`.
-
-## State writer
-Orchestrator is the only physical writer of `state.json`. Semantic roles create durable facts: Planner creates engineering/spec/ticket facts, Implementer creates start/verification evidence, Reviewer creates immutable review results. Orchestrator validates and adopts those facts through legal transitions.
-
-## Planning completion
-`planning.scope_status` mirrors Planner-owned `engineering.md`: `UNKNOWN`, `OPEN`, or `COMPLETE`. Orchestrator never infers COMPLETE from absence of runnable tickets.
-
-## Provenance
-Every adopted mutation increments `transition_sequence` and records subject, from/to, workflow, reason, evidence, and observed commit.