yaaw-se 0.2.0 → 0.2.1

package/dist/payload/yaaw-core/system/workflows/orchestration/dispatch.md

@@ -7,17 +7,22 @@ Execute exactly one already-selected canonical workflow. This file is not the or
 `.yaaw-core/runtime/handoff.json` created by `orchestration.determine-next-action`.
 
 ## Procedure
-1. Validate handoff schema, workflow registry entry, execution policy, role I/O, source artifact revisions, transition-sequence basis, and repository basis.
-2. Enforce repository requirement: `NONE` needs no Git prerequisite; `INSPECT` may proceed with a represented `UNVERSIONED` workspace; `IDENTITY` requires repository status `READY`.
-3. If any basis is stale or unsatisfied, discard the handoff and return a typed stale/prerequisite result to `orchestration.route`; do not execute it.
-4. Resolve the handoff's execution-context policy from `execution-policy.json` and `.yaaw-core/system/core/dispatch-execution.md`.
-5. If the target is an Orchestrator workflow or policy is `ROOT_ONLY`, execute in the current root context.
-6. Otherwise request the active host adapter's isolated-worker mechanism. When isolation is available, execute this one handoff in a fresh worker with minimal bootstrap context and without relying on inherited parent conversation.
-7. If isolation is unavailable or a named worker cannot be selected before child creation, follow the configured host fallback policy. If a child was already created and then failed, do **not** blindly retry; return to reality inspection first.
-8. The executing context loads only the target role contract, selected workflow contract, exact handoff reads, selected expertise, and minimal relevant repository context.
-9. Execute the target workflow once. A worker may not route or spawn another YAAW authority role.
-10. Require the expected durable output/state/evidence or an explicit legal typed stop/prerequisite result.
-11. Treat any child response only as an execution signal; do not accept it as project truth without re-inspection.
-12. Mark/remove the consumed runtime handoff and return control to `orchestration.route`.
+1. Re-run the framework integrity gate and require `HEALTHY`; compare its manifest basis with the handoff framework basis. If package integrity changed, discard the handoff and return the typed framework stop before loading target semantics.
+2. Validate handoff schema, workflow registry entry, execution policy, role I/O, source artifact revisions, transition-sequence basis, and repository basis.
+3. Enforce repository requirement: `NONE` needs no Git prerequisite; `INSPECT` may proceed with a represented `UNVERSIONED` workspace; `IDENTITY` requires repository status `READY`.
+4. If any basis is stale or unsatisfied, discard the handoff and return a typed stale/prerequisite result to `orchestration.route`; do not execute it.
+5. Resolve the handoff's execution-context policy from `execution-policy.json` and `.yaaw-core/system/core/dispatch-execution.md`.
+6. If the target is an Orchestrator workflow or policy is `ROOT_ONLY`, execute in the current root context.
+7. Otherwise request the active host adapter's isolated-worker mechanism. When isolation is available, execute this one handoff in a fresh worker with minimal bootstrap context and without relying on inherited parent conversation.
+8. If isolation is unavailable or a named worker cannot be selected before child creation, follow the configured host fallback policy. If a child was already created and then failed, do **not** blindly retry; return to reality inspection first.
+9. The executing context loads only the target role contract, selected workflow contract, exact handoff reads, selected expertise, and minimal relevant repository context.
+10. Execute the target workflow once. A worker may not route or spawn another YAAW authority role.
+11. Require the expected durable output/state/evidence or an explicit legal typed stop/prerequisite result.
+12. Treat any child response only as an execution signal; do not accept it as project truth without re-inspection.
+13. Mark/remove the consumed runtime handoff and return control to `orchestration.route`.
 
 Never recursively dispatch `orchestration.dispatch` as its own target. A target role never dispatches a peer.
+
+## Package boundary
+
+Dispatch rejects any handoff whose writes include installer-managed artifacts or `.yaaw-core/system/**`. An admitted application-file write never authorizes package framework mutation.

package/dist/payload/yaaw-core/system/workflows/orchestration/inspect-state.md

@@ -4,17 +4,18 @@
 Create a non-mutating observed-reality snapshot that separates claims from evidence and classifies repository capability safely.
 
 ## Inputs
-Resolved workspace root, `.yaaw-core/project/state.json`, product/engineering/research/spec/ticket/review/evidence/runtime files, project rules, and available repository/application reality.
+Resolved workspace root, installation manifest/framework-integrity result, `.yaaw-core/project/state.json`, product/engineering/research/spec/ticket/review/evidence/runtime files, project rules, and available repository/application reality.
 
 ## Procedure
 1. Resolve `WORKSPACE_ROOT` using `.yaaw-core/system/core/execution-context.md`; never trust ambient CWD.
-2. Probe Git only with root-anchored commands such as `git -C <WORKSPACE_ROOT> rev-parse --show-toplevel`.
-3. Classify repository status using `.yaaw-core/system/rules/repository-identity.md`. A failed `rev-parse` becomes `UNVERSIONED` or another explicit status; do not leak a raw Git fatal error as successful identity.
-4. When status is `READY`, compute workspace-scoped repository identity. If Git root is an ancestor, scope status/diff/untracked hashing to the workspace.
-5. Read machine-readable artifact metadata and active durable artifacts.
-6. Compare state claims with artifact/repository/review evidence without repairing yet.
-7. List inconsistencies, stale artifacts/handoffs, blockers, and candidate next states.
-8. Write replaceable `.yaaw-core/runtime/observed-state.json` conforming to observed-state v2.
+2. Execute `.yaaw-core/system/tools/framework-integrity.mjs --workspace <WORKSPACE_ROOT>` and record its status plus current manifest basis. If status is not `HEALTHY`, record the framework failure, invalidate any executable handoff candidate, write only the replaceable observation when safe, and stop inspection before semantic project reconciliation.
+3. Probe Git only with root-anchored commands such as `git -C <WORKSPACE_ROOT> rev-parse --show-toplevel`.
+4. Classify repository status using `.yaaw-core/system/rules/repository-identity.md`. A failed `rev-parse` becomes `UNVERSIONED` or another explicit status; do not leak a raw Git fatal error as successful identity.
+5. When status is `READY`, compute workspace-scoped repository identity. If Git root is an ancestor, scope status/diff/untracked hashing to the workspace.
+6. Read machine-readable artifact metadata and active durable artifacts.
+7. Compare state claims with artifact/repository/review evidence without repairing yet.
+8. List inconsistencies, stale artifacts/handoffs, blockers, and candidate next states.
+9. Write replaceable `.yaaw-core/runtime/observed-state.json` conforming to observed-state v2.
 
 ## Output
 Observed-state snapshot only; no semantic or ticket-state mutation.

package/dist/payload/yaaw-core/system/workflows/orchestration/reconcile-state.md

@@ -14,3 +14,9 @@ Current observed-state snapshot, state claims, artifact revisions, repository/ev
 
 ## Output
 Reconciled state or `BLOCKED` when the last trustworthy boundary cannot be proven.
+
+## Framework boundary
+
+Reconciliation is forbidden when the observed framework integrity status is not `HEALTHY`. Return the typed framework stop without changing ticket/project lifecycle state. A contradiction among canonical framework contracts is `FRAMEWORK_CONTRACT_INCONSISTENCY`; do not resolve it by editing the governing files.
+
+Reviewer-owned acceptance results are applied to `state.json` by Orchestrator only after the immutable review artifact is fresh and valid. Orchestrator records exactly the target implied by the review result and never invents an acceptance result.

package/dist/payload/yaaw-core/system/workflows/orchestration/route.md

@@ -9,12 +9,13 @@ Selection is metadata-first. Do not preload candidate target workflow bodies, te
 ## Procedure
 Repeat:
 1. execute `orchestration.inspect-state`;
-2. execute `orchestration.reconcile-state` when inconsistencies exist;
-3. execute `orchestration.determine-next-action`;
-4. if terminal/blocked/human-input stop condition is returned, stop;
-5. execute `orchestration.dispatch` for the one persisted handoff;
-6. require the dispatched execution to persist its artifact/state/evidence output or legal typed prerequisite/stop result;
-7. whether dispatch reports success, failure, interruption, or no response, discard/validate the consumed handoff as appropriate and return to step 1 before loading another target workflow.
+2. if framework integrity is not `HEALTHY`, invalidate executable handoffs and stop with the typed framework failure; do not reconcile project lifecycle state;
+3. execute `orchestration.reconcile-state` when project inconsistencies exist;
+4. execute `orchestration.determine-next-action`;
+5. if terminal/blocked/human-input/framework stop condition is returned, stop;
+6. execute `orchestration.dispatch` for the one persisted handoff;
+7. require the dispatched execution to persist its authorized durable output or legal typed prerequisite/stop result;
+8. whether dispatch reports success, failure, interruption, or no response, discard/validate the consumed handoff as appropriate and return to step 1 before loading another target workflow.
 
 There is no direct `worker A result -> worker B` authority chain. Reality reconstruction always sits between authority-role dispatches.
 
@@ -22,4 +23,4 @@ There is no direct `worker A result -> worker B` authority chain. Reality recons
 If the same repository capability/identity, state, handoff, and expected output repeat without any durable mutation/evidence change, stop as `BLOCKED` with `no_progress` rather than spinning.
 
 ## Stop conditions
-Human product/engineering answer required; evidence/permission unavailable; target workflow requires repository `IDENTITY` but status is not `READY`; active host/runtime policy blocks required isolation; host requires approval for consequential action; or accepted scope is terminal `COMPLETE`.
+Framework integrity unavailable/unhealthy; framework contract inconsistency; Human product/engineering answer required; evidence/permission unavailable; target workflow requires repository `IDENTITY` but status is not `READY`; active host/runtime policy blocks required isolation; host requires approval for consequential action; or accepted scope is terminal `COMPLETE`.

package/dist/payload/yaaw-core/system/workflows/review/record-review.md

@@ -1,18 +1,19 @@
 # Record review
 
 ## Purpose
-Persist immutable acceptance history and update current ticket state legally.
+Persist immutable Reviewer-owned acceptance history and return the authorized lifecycle outcome to Orchestrator without writing the state ledger directly.
 
 ## Procedure
 1. Create the next immutable `.yaaw-core/project/reviews/TASK-NNN-RK.md` from the review template.
 2. Frontmatter records ticket/review round, result, ticket/spec revisions, reviewed repository identity, and evidence references.
 3. Body records findings, verification, evidence interpretation, and next action.
 4. Never overwrite prior review rounds.
-5. Apply exactly one legal transition:
-   - `PASS` -> ticket `PASS`;
-   - `REPAIR` -> `REPAIR_REQUIRED`;
-   - `REPLAN` -> `REPLAN_REQUIRED`;
-   - `BLOCKED` -> `BLOCKED`.
-6. Write state-transition provenance.
+5. Select exactly one legal semantic outcome:
+   - `PASS` authorizes target ticket state `PASS`;
+   - `REPAIR` authorizes `REPAIR_REQUIRED`;
+   - `REPLAN` authorizes `REPLAN_REQUIRED`;
+   - `BLOCKED` authorizes `BLOCKED`.
+6. Reviewer writes only the immutable review artifact and returns the typed result. Reviewer does not edit `.yaaw-core/project/state.json`.
+7. Orchestrator re-inspects the new review, validates source/repository/evidence freshness, and records exactly the authorized transition plus provenance in `state.json`. Orchestrator may not substitute a different acceptance outcome.
 
 A prior PASS remains historical but becomes stale when repository/source revisions invalidate its basis.

package/dist/payload/yaaw-core/system/workflows/review/review-ticket.md

@@ -4,7 +4,11 @@
 Independently determine whether current implementation satisfies the current ticket contract.
 
 ## Preconditions
-Ticket is `REVIEW_REQUIRED`; source revisions and evidence are current enough to review.
+`.yaaw-core/project/state.json` is admitted read-only context. Its `tickets[TASK-NNN]` lifecycle value is authoritative for workflow admission and is `REVIEW_REQUIRED`, unless Orchestrator explicitly admitted a source-current stale-`PASS` acceptance revalidation.
+
+Ticket frontmatter `status` is artifact metadata/admission history and may still say `READY` or another earlier value after later lifecycle transitions. It does not override the reconciled state ledger. Source revisions and evidence must still be current enough to review.
+
+If state and stronger source/repository/evidence reality materially conflict, return `BLOCKED` with the exact conflict for Orchestrator reconciliation. Do not edit state.
 
 ## Procedure
 1. Use a fresh review context when practical.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yaaw-se",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Artifact-first autonomous software engineering workflow installer.",
   "type": "module",
   "bin": {