yaaw-se 0.3.7 → 0.3.8

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

@@ -1,26 +1,18 @@
 # Implement ticket
 
 ## Purpose
-Implement one admitted bounded ticket and produce reviewable evidence.
+Implement one admitted bounded ticket while making interruption recoverable from durable facts.
 
 ## Preconditions
-Repository status is `READY`. One ticket must be admitted as `READY`, dependencies pass, source revisions are current, and repository state is consistent. If no exact eligible ticket is available, return `PRECONDITION_UNSATISFIED:NO_READY_TICKET` to Orchestrator; never create the missing ticket.
+Reconciled state says the ticket is `READY`; source revisions are current; dependencies pass; repository identity is `READY`.
 
 ## Procedure
-1. If no exact ticket was supplied, execute `implementation.select-ticket`; on any typed prerequisite result, return it to Orchestrator while preserving desired intent `IMPLEMENT`.
-2. Load the ticket, referenced product/spec/decisions/research, `.yaaw-core/system/rules/changeability.md`, relevant .yaaw-core/system/rules/expertise, and relevant code only.
-2. Record `READY -> IN_PROGRESS` with transition provenance and repository identity.
-3. Establish the minimum authorized implementation surface before editing.
-4. Implement strictly within allowed scope while applying only the changeability principles relevant to the changed surface: visible main path, domain naming, external boundaries, valid-state modeling, decision/side-effect separation, useful failures, and focused change scope.
-5. Do not perform style-only rewrites, speculative abstractions, or unrelated cleanup. If a discovered maintainability issue is not necessary for safe ticket completion, leave it unchanged and surface it as a future planning candidate when materially valuable.
-6. If a material missing decision appears, transition to `REPLAN_REQUIRED` or `BLOCKED`; do not invent it.
-7. Execute `implementation.verify-ticket`, including targeted verification for materially affected changeability properties.
-8. Persist evidence tied to ticket/spec revisions and repository identity.
-9. Transition `IN_PROGRESS -> REVIEW_REQUIRED` only when required evidence exists.
+1. Read the exact handoff, state, ticket, source contracts, `.yaaw-core/system/rules/changeability.md`, applicable expertise, and minimal code.
+2. Before editing any application file, write immutable v3 `implementation_start` evidence with result `STARTED`, current ticket/spec revisions, workflow ID, and the exact pre-edit repository identity.
+3. Only after that durable start fact exists, implement strictly inside allowed scope.
+4. If a material contract gap appears, stop with `REPLAN_REQUIRED` or `BLOCKED`; do not invent it.
+5. Execute `implementation.verify-ticket`.
+6. Persist verification evidence. Do not mutate lifecycle state directly.
 
 ## Output
-Reviewable implementation plus evidence, or explicit replan/blocker state.
-
-## Evidence identity
-
-Use the canonical repository identity utility for implementation evidence. Do not implement a private worktree digest. Changeability requirements remain in force.
+Bounded implementation plus durable start/verification evidence or a typed stop. Orchestrator adopts `READY -> IN_PROGRESS` from start evidence and `IN_PROGRESS -> REVIEW_REQUIRED` only from current PASS verification.

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

@@ -4,19 +4,14 @@
 Correct implementation defects while keeping the accepted ticket/spec contract unchanged.
 
 ## Preconditions
-Ticket is `REPAIR_REQUIRED` and latest review result is `REPAIR` against the same current contract revisions.
+Reconciled state is `REPAIR_REQUIRED` and the latest review result is `REPAIR` against the current contract.
 
 ## Procedure
-1. Load the same ticket contract, `.yaaw-core/system/rules/changeability.md`, latest review findings, and relevant code/evidence.
-2. Repair only what is needed to satisfy the unchanged plan and the concrete review findings; do not broaden scope into adjacent cleanup.
-3. Apply the relevant changeability principles when they are part of the defect or needed for a safe repair.
-4. If repair requires product/architecture contract changes, transition to `REPLAN_REQUIRED` and stop.
-5. Rerun relevant verification, including any previously failed changeability check, and append a new evidence record.
-6. Transition `REPAIR_REQUIRED -> REVIEW_REQUIRED` with provenance.
+1. Load state, the unchanged ticket contract, `.yaaw-core/system/rules/changeability.md`, latest review findings, prior evidence, and relevant code.
+2. Repair only the bounded findings; do not broaden scope.
+3. If repair requires product/architecture contract changes, return `REPLAN_REQUIRED`.
+4. Rerun `implementation.verify-ticket` and write a new v3 verification record distinct from evidence referenced by the REPAIR review.
+5. Never edit state. Orchestrator moves `REPAIR_REQUIRED -> REVIEW_REQUIRED` only after fresh PASS verification.
 
 ## Output
-Repaired reviewable implementation or replan/blocker result.
-
-## Repair identity
-
-After bounded repair and verification, bind evidence to the canonical repository identity and return `REVIEW_REQUIRED`. Changeability requirements remain in force.
+Repaired reviewable implementation with fresh verification evidence, or a typed replan/blocker result.

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

@@ -4,17 +4,16 @@
 Produce reproducible implementation evidence without self-accepting the ticket.
 
 ## Inputs
-Ticket requirements/tests, changed surface, project tooling/rules, current repository identity.
+Exact handoff, reconciled state, ticket requirements/tests, changed surface, project rules/tooling, and current repository identity.
 
 ## Procedure
-1. Run every test/check required by the ticket.
-2. Add targeted regression checks justified by the changed surface.
-3. For each materially relevant changeability principle from `.yaaw-core/system/rules/changeability.md`, verify the concrete property rather than a style preference. Examples include boundary mapping behavior, invalid-state rejection, decision logic independent of side effects, stable error identity, and focused-diff inspection.
-4. Record commands, exit/result, relevant checks (including relevant changeability checks), ticket/spec revisions, and exact repository identity in `.yaaw-core/project/evidence/EVIDENCE-TASK-NNN-VK.json` using the evidence schema.
-5. Preserve failed evidence; do not rewrite it as success.
+1. Run every ticket-required test/check and justified targeted regressions.
+2. Verify materially relevant changeability properties as concrete behavior.
+3. After verification commands finish, capture the canonical repository identity.
+4. Write a new immutable `.yaaw-core/project/evidence/EVIDENCE-TASK-NNN-VK.json` using `yaaw.evidence/v3`.
+5. Set `kind: implementation_verification` and exactly one result: `PASS`, `FAIL`, or `BLOCKED`.
+6. Preserve failed records; fixes produce a later evidence record.
+7. If verification proves implementation materially incomplete, return `IMPLEMENTATION_INCOMPLETE` to Orchestrator rather than silently reimplementing in this verification workflow.
 
 ## Output
-Evidence record(s). Verification never transitions a ticket to PASS; only Reviewer can accept.
-
-## Verification identity
-After verification commands finish, invoke `.yaaw-core/system/tools/repository-identity.mjs` and record that exact output in `yaaw.evidence/v2`. Do not reserialize it through a second digest implementation. Replaceable `.yaaw-core/runtime/**` coordination files are excluded by canonical `yaaw-worktree-v2`; all semantic/project/application changes remain in the basis. Changeability requirements remain in force.
+One explicit verification result. Only a current PASS record can authorize review admission; evidence-file existence alone never does.

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

@@ -1,22 +1,19 @@
 # Reconcile state
 
 ## Purpose
-Repair only evidence-backed state inconsistencies before routing semantic work.
+Apply exactly one highest-priority evidence-backed state adoption or legal lifecycle transition.
 
 ## Inputs
-Current observed-state snapshot, state claims, artifact revisions, repository/evidence/review identity.
+Current observed-state snapshot and its `reconciliation` object from the production orchestration engine.
 
 ## Procedure
-- apply `core/recovery.md`, `core/transitions.md`, and `core/invalidation.md`;
-- examples: `IN_PROGRESS` + implementation + passing verification + no review -> `REVIEW_REQUIRED`; stale `PASS` -> `REPLAN_REQUIRED` or `REVIEW_REQUIRED` according to cause; `READY` + implementation already present -> recover/inspect rather than duplicate;
-- never change product/architecture meaning during reconciliation;
-- every repaired state records transition reason/evidence and increments transition sequence.
+1. Require framework integrity `HEALTHY`.
+2. Run `node .yaaw-core/system/tools/orchestration-runtime.mjs --workspace <WORKSPACE_ROOT> --reconcile-one`.
+3. Apply only the one reconciliation returned by the engine; do not batch multiple discovered facts.
+4. Increment `transition_sequence` exactly once and persist provenance.
+5. Return immediately to `orchestration.route` so reality is observed again.
 
-## Output
-Reconciled state or `BLOCKED` when the last trustworthy boundary cannot be proven.
-
-## Framework boundary
+Examples include ledger sync, accepted-spec adoption, ticket registration, implementation-start adoption, PASS-verification adoption, review-result adoption, acceptance invalidation, and project completion sync.
 
-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.
+## Output
+One reconciled mutation or a typed blocker. No semantic product/engineering/implementation/acceptance judgment is invented here.

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

@@ -4,18 +4,15 @@
 Resume safely after context/session failure without duplicating already-completed work.
 
 ## Inputs
-Active/recent artifact, state claims, runtime caches, repository identity/history/diff, verification/review evidence.
+Reconciled state, durable artifacts, implementation-start/verification evidence, reviews, and repository identity.
 
 ## Procedure
-1. Discard stale runtime handoffs/snapshots.
-2. Identify the last trustworthy completed boundary.
-3. If implementation exists, prefer verification/review over reimplementation when evidence supports it.
-4. Reconcile only via legal transitions with provenance.
-5. If the boundary cannot be proven, return `BLOCKED` with exact missing evidence.
-6. Return control to `orchestration.route` for normal next-action selection.
+1. Discard stale runtime caches/handoffs.
+2. Identify the last trustworthy durable boundary.
+3. For `IN_PROGRESS`: current PASS verification is reconciled to review; valid start evidence without PASS verification routes to `implementation.verify-ticket`; missing start evidence requires explicit recovery/blocking proof.
+4. Never rerun full implementation merely because a worker response disappeared.
+5. A source-current review artifact is adopted before another Reviewer dispatch.
+6. Use only legal transitions with provenance; if the boundary cannot be proven, return `BLOCKED`.
 
-Never repeat destructive work merely because a context ended.
-
-## Acceptance recovery
-
-A source-current stale `PASS` is recovered through `REVIEW_REQUIRED`. Do not dispatch Planner unless contract invalidation is independently proven.
+## Output
+A safe next boundary or exact blocker, then control returns to `orchestration.route`.

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

@@ -1,34 +1,27 @@
 # Orchestration main loop
 
 ## Purpose
-Continuously restore project reality and execute one safe canonical workflow at a time until a true stop condition.
+Continuously restore project reality and execute one safe canonical workflow at a time until the active intent is satisfied or a real stop occurs.
 
 ## Deterministic preparation
-Normal routing uses one command per basis:
-
+For normal continuation:
 ```text
 node .yaaw-core/system/tools/orchestration-runtime.mjs --workspace <WORKSPACE_ROOT>
 ```
 
-This command performs framework integrity, canonical repository identity, durable metadata inspection, route selection, and handoff construction together. Do not separately reconstruct those stages in shell/Python/model reasoning.
+For a public shortcut:
+```text
+node .yaaw-core/system/tools/orchestration-runtime.mjs --workspace <WORKSPACE_ROOT> --invoke-skill <skill-id>
+```
 
 ## Procedure
 Repeat:
 1. run deterministic preparation once;
-2. on `FRAMEWORK_STOP`, invalidate executable handoffs and stop with the typed framework failure;
-3. on `RECONCILE_REQUIRED`, execute `orchestration.reconcile-state` only, then return to step 1;
-4. on `ROOT_ACTION`, execute the returned Orchestrator workflow only, then return to step 1;
-5. on `TERMINAL` or `BLOCKED`, stop;
-6. on `DISPATCH_READY`, execute `orchestration.dispatch` for the 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, return to step 1 before another semantic workflow.
-
-`orchestration.inspect-state` and `orchestration.determine-next-action` remain canonical compatibility/debug workflows, but the normal loop does not execute them as separate model-driven reconstruction passes.
-
-There is no direct `worker A result -> worker B` authority chain. Reality reconstruction always sits between authority-role dispatches.
-
-## Loop safety
-If the same repository basis, lifecycle state, route, and expected output repeat without durable mutation/evidence change, stop as `BLOCKED` with `no_progress` rather than spinning.
-
-## Stop conditions
-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/profile fidelity; host requires approval for consequential action; or accepted scope is terminal `COMPLETE`.
+2. on `FRAMEWORK_STOP`, stop without lifecycle mutation;
+3. on `RECONCILE_REQUIRED`, apply exactly one reconciliation with `--reconcile-one`, then observe again;
+4. on `ROOT_ACTION`, execute only the returned Orchestrator recovery workflow, then observe again;
+5. on `DISPATCH_READY`, execute exactly the persisted handoff once;
+6. after any worker outcome or disappearance, discard worker text as authority and observe durable reality again;
+7. on `INTENT_COMPLETE`, `TERMINAL`, `BLOCKED`, or human input, stop.
+
+No worker-to-worker authority chain exists. Every semantic successor is selected after reality reconstruction.

package/dist/payload/yaaw-core/system/workflows/planning/create-spec.md

@@ -16,3 +16,6 @@ Current frontier readiness is `PASS`; its product/engineering revisions remain c
 
 ## Output
 One current accepted spec or an explicit planning gap.
+
+## Adoption
+Planner writes the accepted spec only. Orchestrator detects the unique current accepted spec and adopts it into state on the next observation. Planner never writes `state.json`.

package/dist/payload/yaaw-core/system/workflows/planning/create-tickets.md

@@ -18,3 +18,6 @@ Source spec is `ACCEPTED`, product/engineering revisions remain current, and rep
 
 ## Output
 Dependency-aware tickets requiring no planning-chat memory and preserving focused, reviewable change boundaries.
+
+## Registration
+Planner writes ticket artifacts only. Orchestrator registers current tickets into `state.json` one reconciliation at a time, preventing duplicate ticket creation when Planner output text is lost.

package/dist/payload/yaaw-core/system/workflows/planning/decision-frontier.md

@@ -28,3 +28,6 @@ Assign/update a stable frontier ID. Only current-frontier decisions/research/pro
 
 ## Output
 Durable bounded frontier plus zero or more admitted research artifacts. The next route is research, question-round, PRD, readiness, or READY as the persisted partition requires.
+
+## Scope completion signal
+Maintain `engineering.scope_status` on every meaningful frontier update. Use `UNKNOWN` when completion is not proven, `OPEN` when accepted product scope remains after this frontier, and `COMPLETE` only when durable product/planning evidence proves no accepted scope remains. Future ideas/non-goals do not keep accepted scope open.

package/dist/payload/yaaw-core/system/workflows/planning/replan.md

@@ -20,3 +20,5 @@ Current engineering contract plus updated downstream admission state.
 ## Admission guard
 
 Repository identity change alone is not sufficient reason to replan. Require stale source/contract revisions or Reviewer `REPLAN` evidence.
+
+Planner may revise engineering/spec/ticket artifacts but never writes lifecycle state directly. Orchestrator observes the durable revised contract and applies legal admission/invalidation transitions.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yaaw-se",
-  "version": "0.3.7",
+  "version": "0.3.8",
   "description": "Artifact-first autonomous software engineering workflow installer.",
   "type": "module",
   "bin": {
@@ -20,14 +20,15 @@
     "build:payload": "node scripts/build_npm_payload.mjs",
     "verify:payload": "node scripts/verify_npm_payload.mjs",
     "build": "npm run clean && npm run build:ts && npm run build:payload && npm run verify:payload",
-    "validate:core": "python scripts/validate_core.py && python scripts/validate_behavior.py && python scripts/behavior_oracle.py",
+    "validate:core": "npm run validate:schemas && python scripts/validate_core.py && python scripts/validate_behavior.py && node scripts/run_lifecycle_cases.mjs",
     "validate:distribution": "python scripts/validate_distribution.py",
     "test:python": "python -m unittest discover -s tests -v",
     "test:cli": "npm run build:payload && vitest run tests/cli",
     "test": "npm run validate:core && npm run validate:distribution && npm run test:python && npm run test:cli",
     "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"
+    "smoke:update": "npm run build && node scripts/smoke_npm_update.mjs",
+    "validate:schemas": "node scripts/validate_schemas.mjs"
   },
   "dependencies": {
     "@clack/prompts": "1.8.1",