sdd-agent-platform 0.4.1 → 0.5.0

package/node_modules/@sdd-agent-platform/core/src/instructions.ts

@@ -2,7 +2,7 @@ import { SDD_VERSION } from './ai-tools.js';
 
 export const SDD_INSTRUCTIONS_CONTRACT = 'sdd-instructions-v1';
 
-export type InstructionAction = 'overview' | 'init' | 'doctor' | 'update' | 'spec' | 'plan' | 'tasks' | 'verifies' | 'test' | 'do' | 'verify' | 'sync-back' | 'ship' | 'run-task' | 'verify-task';
+export type InstructionAction = 'overview' | 'init' | 'doctor' | 'update' | 'spec' | 'plan' | 'tasks' | 'execute' | 'ship';
 
 export interface SddInstructionPayload {
   contract: typeof SDD_INSTRUCTIONS_CONTRACT;
@@ -17,26 +17,25 @@ export interface SddInstructionPayload {
 
 const INSTRUCTION_PAYLOADS: Record<InstructionAction, Omit<SddInstructionPayload, 'contract' | 'version' | 'action'>> = {
   overview: {
-    summary: 'Route natural-language SDD intent from branch/source status to task execution, agent evidence, strict verification-contract consumption, and release readiness while keeping CLI/core output as source of truth.',
-    requiredCommands: ['sdd status', 'sdd lifecycle decide --from-text <text>', 'sdd doctor', 'sdd tasks inspect <task_id>', 'sdd do task <task_id>', 'sdd test task <task_id> --branch <branch>', 'sdd test batch <batch_id> --branch <branch>', 'sdd test wave --branch <branch> --wave <n>', 'sdd ship --branch <branch> --dry-run', 'sdd instructions ship --json'],
+    summary: 'Route natural-language SDD intent through the fixed public lifecycle spec -> plan -> tasks -> execute -> ship while keeping runtime projection, accepted evidence, checkpoint, and release readiness as CLI/core-owned truth.',
+    requiredCommands: ['sdd status', 'sdd doctor', 'sdd instructions spec --json', 'sdd instructions plan --json', 'sdd instructions tasks --json', 'sdd instructions execute --json', 'sdd execute --branch <branch> --json', 'sdd ship close --branch <branch> --json'],
     allowedSideEffects: ['read .sdd state', 'read specs documents', 'read generated AI entries'],
-    forbiddenSideEffects: ['background write', 'worktree creation', 'auto commit', 'force push', 'unapproved sync-back apply', 'publish or push release artifacts without explicit human confirmation'],
+    forbiddenSideEffects: ['background write', 'worktree creation', 'auto commit', 'force push', 'publish or push release artifacts without explicit human confirmation'],
     nextSteps: [
       'Treat /sdd as a natural-language intent router, then run sdd status first to see branch/source context and the recommended next command; report only workflow state, blocker/current task, and next action unless the user asks for full detail.',
       'Dynamic routing comes from CLI/core output; follow the recommended next command and do not infer dynamic state from generated markdown.',
-      'If intent remains ambiguous after status, ask one clarifying question before spec/plan/tasks/do/test/ship work.',
-      'If status reports generated entry drift, missing config, compatibility drift, or legacy sync-back state, run sdd doctor and use diagnostic/recovery commands before normal do/test/ship.',
-      'If status recommends a pending task, run sdd tasks inspect <task_id> and execute only the approved task boundary; scout/implementer/reviewer/validator participation should be recorded as artifacts rather than hidden in the main chat.',
-      'For test, follow the task contract boundary: strict/task_end work uses sdd test task, batch_end work uses sdd test batch, and wave_end work uses sdd test wave; pass --run only for replay, CI, or old-run inspection.',
-      'After the selected test boundary returns PASS, proceed to a decision card if policy requires one, otherwise run `sdd ship --branch <branch> --dry-run`.',
-      'Use `sdd sync-back inspect|apply` only for explicit diagnostic, recovery, replay, or legacy compatibility work; do not add it as a normal happy-path step.'
+      'Use the fixed public lifecycle: /sdd:spec -> /sdd:plan -> /sdd:tasks -> /sdd:execute -> /sdd:ship.',
+      'Use /sdd:tasks to produce AI-ready implementation tickets with work-unit context, boundaries, rollback units, completion evidence, validation expected results, and failure routes; verification-design semantics belong in tasks, not a public verifies stage.',
+      'Use /sdd:execute for implementation, review, validation, debug, checkpoint, and evidence-judgment lanes; do not expose do/test/verify/goal-verify as public lifecycle stages.',
+      'If status reports generated entry drift, missing config, compatibility drift, or projection drift, run sdd doctor and follow its current-run repair or rebuild recommendation before normal execute/ship.',
+      'If status recommends a pending task, run sdd tasks inspect <task_id> and execute only the approved task boundary; scout/implementer/reviewer/validator participation should be recorded as stage evidence rather than hidden in the main chat.'
     ]
   },
   init: {
     summary: 'Initialize .sdd project configuration and managed AI tool entries for the current repository; workflow partition documents are entered through the spec stage, not init.',
     requiredCommands: ['sdd init --ai claude-code', 'sdd status', 'sdd instructions spec --json', 'sdd doctor'],
-    allowedSideEffects: ['write .sdd/project.yml', 'write .sdd/runs', 'write managed generated AI entries'],
-    forbiddenSideEffects: ['create workflow partition documents unless explicitly using the spec stage or legacy --scaffold-docs', 'overwrite foreign AI entry files', 'background write', 'auto commit'],
+    allowedSideEffects: ['write .sdd/project.yml', 'initialize runtime.sqlite state', 'write managed generated AI entries'],
+    forbiddenSideEffects: ['create workflow partition documents unless explicitly using the spec stage', 'overwrite foreign AI entry files', 'background write', 'auto commit'],
     nextSteps: ['Run sdd init --ai claude-code.', 'Run sdd status to inspect current Git branch partition state and the recommended next command.', 'Use the spec stage to create or refine specs/<partition>/spec.md; omitted --branch uses the current Git branch, explicit --branch uses the requested partition.', 'Run sdd doctor after initialization.']
   },
   doctor: {
@@ -54,82 +53,40 @@ const INSTRUCTION_PAYLOADS: Record<InstructionAction, Omit<SddInstructionPayload
     nextSteps: ['Run sdd update.', 'Run sdd doctor to verify drift is resolved.']
   },
   spec: {
-    summary: 'Create or refine specs/<partition>/spec.md as the workflow partition entry: omitted --branch uses the current Git branch, explicit --branch uses the requested branch partition.',
-    requiredCommands: ['sdd status', 'sdd lifecycle decide --from-text <text>', 'read specs/<partition>/spec.md', 'write specs/<partition>/spec.md'],
-    allowedSideEffects: ['read project context', 'create or read the resolved specs/<partition> directory', 'write proposed or approved requirement contract'],
-    forbiddenSideEffects: ['implement code', 'design technical solution in spec.md', 'silently advance to plan', 'auto commit'],
-    nextSteps: ['Resolve the workflow partition: omit --branch to use the current Git branch, or pass --branch <name> only when intentionally writing another partition.', 'Clarify user intent, objective/customer value, actors, scenarios, scope, and non-goals.', 'Run sdd lifecycle decide --from-text <text> when changes mention state-machine, concurrency, database, SQL, security, API/schema, CI/build, or external unknown risk.', 'Write acceptance criteria with stable IDs such as AC-1 and verification hints.', 'Record assumptions/dependencies, risks/hard gates, open questions, and lifecycle reference.', 'If this is a requirement change after plan/tasks/run work exists, update spec.md and let status expose stale downstream hashes before continuing.', 'Stop before technical design or implementation when requirement gaps remain.']
+    summary: 'Enter the spec stage through projection-backed SpecStageWorkOrderHandoff, then let spec-manager produce or refine specs/<partition>/spec.md V3 as the only runtime primary spec artifact for plan/tasks.',
+    requiredCommands: ['sdd status', 'sdd instructions spec --json', 'read specs/<partition>/spec.md', 'write specs/<partition>/spec.md', 'sdd spec close --branch <branch> --json'],
+    allowedSideEffects: ['read project context', 'read the resolved specs/<partition> directory', 'write final spec.md V3 after spec-manager synthesis', 'optionally write spec-stage side logs under .sdd/runs/<branch>/spec/'],
+    forbiddenSideEffects: ['implement code', 'design technical solution in spec.md', 'write spec-stage subagent output as runtime primary evidence', 'silently advance to plan', 'auto commit'],
+    nextSteps: ['Resolve the workflow partition: omit --branch to use the current Git branch, or pass --branch <name> only when intentionally writing another partition.', 'Run sdd instructions spec --json and read specStageWorkOrderHandoff; if it is missing, stop on the runtime authority repair reason instead of writing spec.md directly.', 'Hand off to spec-manager with the user request, current spec.md when present, the spec.md V3 artifact-depth template, and the projection-backed handoff.', 'Spec-manager uses the content chain surface request -> reframed problem -> real intent -> scope boundary -> acceptance criterion -> evidence target; it resolves knowable or researchable uncertainty through scout evidence when useful and asks the user only for blocking user decisions.', 'Spec-reviewer pressure should identify changelog-only specs, hidden user decisions, weak acceptance evidence, and plan/task leakage as repairable content findings, not runtime primary evidence.', 'Final spec.md V3 should contain Problem Reframing / Intent Discovery, Change Delta, Scope, Requirements with reasoning, Acceptance Criteria / Evidence Targets, Definitions / Rules, Planning Constraints / Signals, Open Questions / Ambiguity Ledger, and Close Quality Evidence.', 'Treat scout output, review output, and manager trace as internal or side-log material; runtime spec close accepts final spec.md ref/hash plus boundary facts only.', 'Do not include legacy lifecycle metadata, runtime gate metadata, candidate/analyzer handoff wording, implementation plan, task list, validation plan, or subagent trace in spec.md.', 'If blocking user decisions remain before plan, spec-manager must ask the user before producing a close-ready final spec.md.', 'Run sdd spec close --branch <branch> --json after final spec.md V3 is ready; plan/tasks must consume only the runtime accepted spec ref/hash.']
   },
   plan: {
-    summary: 'Refine specs/<partition>/plan.md as a deliverable technical solution document that bridges approved spec requirements into task-ready design and records based_on_spec_hash.',
-    requiredCommands: ['sdd status', 'read specs/<partition>/spec.md', 'read specs/<partition>/plan.md', 'write specs/<partition>/plan.md'],
-    allowedSideEffects: ['read project context', 'read spec document', 'write proposed or approved technical solution plan document'],
-    forbiddenSideEffects: ['implement code', 'silently advance to tasks', 'bypass unresolved spec gaps'],
-    nextSteps: ['Read the approved spec and acceptance criteria plus the current spec hash from sdd status.', 'Record based_on_spec_hash in plan.md so later spec-stage revisions can mark this plan stale.', 'Write plan.md as a technical solution document: background, goals/non-goals, current state, target design, architecture/component impact, interaction/sequence design, state/data design, API/schema design, concurrency/transaction/consistency design, key decisions, alternatives, risk control, rollout/rollback, validation matrix, and task breakdown rationale.', 'Use PlantUML diagrams when they clarify component impact, sequence/activity flow, state machines, or deployment/data relationships.', 'Apply risk-driven requirements: state-machine needs state design, concurrency needs sequence/activity and consistency design, database needs data/transaction/rollback design, api_schema needs interface/schema compatibility, security/sql needs risk control.', 'Stop with explicit plan gaps and tasks readiness.']
+    summary: 'Enter the plan stage through projection-backed PlanStageWorkOrderHandoff, then let plan-manager produce specs/<partition>/plan.md V3 as an AI-ready technical design artifact for tasks.',
+    requiredCommands: ['sdd status', 'sdd instructions plan --json', 'read planStageWorkOrderHandoff.acceptedSpecRef', 'read accepted specs/<partition>/spec.md by matching hash', 'write specs/<partition>/plan.md', 'sdd plan close --branch <branch> --json'],
+    allowedSideEffects: ['read project context', 'read runtime-accepted spec document by ref/hash', 'write final plan.md V3 after plan-manager synthesis', 'optionally write plan-stage side logs under .sdd/runs/<branch>/plan/'],
+    forbiddenSideEffects: ['runtime-authored Markdown artifacts', 'implement code', 'silently advance to tasks', 'bypass unresolved spec gaps', 'write plan-stage side logs as runtime primary evidence', 'put task topology or task decomposition in plan.md'],
+    nextSteps: ['Run sdd instructions plan --json and read planStageWorkOrderHandoff; if it is missing, stop on the runtime authority repair reason instead of planning from latest spec.md.', 'Verify the opened specs/<partition>/spec.md content hash matches planStageWorkOrderHandoff.acceptedSpecRef before planning.', 'Hand off to plan-manager with the accepted spec, current plan.md when present, the plan.md V3 technical design depth template, and the projection-backed handoff.', 'Plan-manager uses the content chain code/data fact -> design implication -> technical decision -> risk control -> validation scenario, grounded in concrete project files, APIs, SQL, UI, config, or tests.', 'Use plan-scout as bounded evidence-to-plan input when code/data/domain facts are missing, and use plan-review-agent to detect dense-but-shallow plans, vague mappings, missing risk controls, weak validation hooks, and task-list leakage.', 'Do not consume spec-stage side logs, subagent payload, warnings, or spec-manager internal trace as plan input; do not expose plan-stage side logs to tasks-stage as primary input.', 'Final plan.md V3 should contain Upstream Spec Trace, Planning Problem / Strategy Framing, Current Implementation Map, Target Design Overview, Change Topology / Responsibility Boundaries, Interface / API / Schema Design, State / Data / Concurrency Design, Key Design Decisions, Alternatives Considered, Risk Controls, Validation Strategy, Rollout / Rollback / Compatibility, Task-stage Constraints, Open Questions / User Decisions, and Plan Close Quality Evidence.', 'If blocking design decisions or open questions remain before tasks, plan-manager must ask the user before producing a close-ready final plan.md.', 'Plan side logs and professional agent findings may exist as optional/internal audit material, but runtime plan close accepts final plan.md ref/hash plus boundary facts only.', 'Do not include task graph, task units, task decomposition, code diff, validation results, runtime gate metadata, candidate/analyzer wording, or subagent trace in plan.md.', 'Run sdd plan close --branch <branch> --json after final plan.md V3 is ready; tasks must consume only the runtime accepted spec and plan refs/hashes.']
   },
   tasks: {
-    summary: 'Refine specs/<partition>/tasks.md and specs/<partition>/verify.md as frozen task and verification contracts with implementation waves, validation waves, and review gate declarations.',
-    requiredCommands: ['sdd status', 'read specs/<partition>/spec.md', 'read specs/<partition>/plan.md', 'sdd tasks format', 'write specs/<partition>/tasks.md', 'write specs/<partition>/verify.md', 'sdd tasks list', 'sdd tasks gaps', 'sdd verifies inspect --branch <branch>'],
-    allowedSideEffects: ['read spec and plan documents', 'write proposed or approved task execution/evidence contract', 'write task-derived verify contract'],
-    forbiddenSideEffects: ['implement code', 'execute dependency waves', 'run validation commands', 'silently advance to do', 'turn tasks.md into project-management backlog'],
-    nextSteps: ['Read approved spec acceptance IDs, approved plan design sections, and the current plan hash from sdd status.', 'Record based_on_plan_hash in tasks.md so later plan/spec revisions can mark these tasks stale.', 'Run sdd tasks format to get the canonical block format.', 'Map every task to acceptance_refs and plan_refs where applicable.', 'Declare change_surface, implementation_wave, validation_batch, validation_timing, requires_verify_before_next, required artifacts, and review gates before freezing tasks.', 'Use validation_timing task_end and requires_verify_before_next true for strict/high-risk tasks; use batch_end or wave_end with validation_batch only when sequential accumulation is safe.', 'Have the verification-designer produce verify.md from the frozen task contract, then inspect it with sdd verifies inspect --branch <branch>.', 'Keep #### Boundary, #### Acceptance, #### Definition of Done, #### Evidence Expectations, and #### Implementation Notes as companion sections outside the ```sdd-task fenced block; keep only metadata inside the fence.', 'Frontend-only tasks must not declare Maven/Gradle backend build validation.', 'For risky tasks, include allowed_agents, required_artifacts, verification_availability, and autonomy.', 'Run sdd tasks list and sdd tasks gaps.', 'Stop before do task when task boundary, acceptance refs, plan refs, evidence requirements, validation batches/waves, or verify expectations are unclear.']
+    summary: 'Enter the tasks stage through projection-backed TasksStageWorkOrderHandoff, then let tasks-manager produce specs/<partition>/tasks.md V2 as a readable execute playbook, not a runtime metadata form.',
+    requiredCommands: ['sdd status', 'sdd instructions tasks --json', 'read tasksStageWorkOrderHandoff.acceptedSpecRef', 'read tasksStageWorkOrderHandoff.acceptedPlanRef', 'read accepted specs/<partition>/spec.md and plan.md by matching hashes', 'sdd tasks format', 'write specs/<partition>/tasks.md', 'sdd tasks close --branch <branch> --json'],
+    allowedSideEffects: ['read runtime-accepted spec and plan documents by ref/hash', 'write final tasks.md V2 after tasks-manager synthesis', 'optionally write tasks-stage side logs under .sdd/runs/<branch>/tasks/'],
+    forbiddenSideEffects: ['runtime-authored Markdown artifacts', 'implement code', 'execute dependency waves', 'run validation commands', 'silently advance to execute', 'turn tasks.md into project-management backlog', 'write tasks-stage side logs as runtime primary evidence'],
+    nextSteps: ['Run sdd instructions tasks --json and read tasksStageWorkOrderHandoff; if it is missing, stop on the runtime authority repair reason instead of slicing from latest docs.', 'Verify opened specs/<partition>/spec.md and plan.md content hashes match tasksStageWorkOrderHandoff accepted upstream refs before task slicing.', 'Hand off to tasks-manager with accepted spec, accepted plan, current tasks.md when present, the tasks.md V2 execution playbook rubric, and the projection-backed handoff.', 'Tasks-manager builds coverage across requirements, acceptance criteria, plan decisions, risks, and non-goals, then writes task units using the chain: plan decision -> work-unit boundary -> dependency / rollback rationale -> internal execution sequence -> completion evidence -> one-to-one validation task -> failure route.', 'Do not mechanically split by file type: if backend Java, SQL, XML/Dubbo wiring, UI/config, or other surfaces are one rollback unit, keep them in one implementation task and write ordered internal steps for execute.', 'Every implementation task must hand off to exactly one validation task, and every validation task must validate exactly one implementation task; split broad validation scenarios into per-task checks instead of many-to-one mappings.', 'Prefer readable execute context over schema-first metadata: each task should explain why it exists, where execute should start, what to change, what not to change, what proves completion, which validation task proves it, and where failure routes.', 'Implementation tasks do code review and basic code sanity only; validation closure belongs to validation task units and execute validation lanes.', 'Use task-slicer when rollback unit, dependency unlock, validation closure, shared writable ownership, or parallelism safety is unclear.', 'Use task-review-agent to detect TOO_THIN_FOR_EXECUTE, CHECKLIST_TASKS, SCHEMA_FIRST_TASKS, BOUNDARY_CONFLICT, VALIDATION_INSUFFICIENT, oversized-without-sequence, many-to-one validation, scope expansion, missing expected results, and missing failure routes.', 'Keep only minimal structured anchors needed for routing and parsing; do not add obligation matrices, runtime projection payloads, or metadata fields just to force quality.', 'Tasks side logs and review notes may exist as optional/internal audit material, but runtime tasks close accepts final tasks.md ref/hash plus boundary facts only.', 'Do not include code diff, validation execution results, long-term backlog state, runtime gate metadata, candidate/analyzer wording, subagent trace, or obligation/projection payloads in tasks.md.', 'Run sdd tasks close --branch <branch> --json after final tasks.md V2 is ready; execute must consume only the runtime accepted tasks ref/hash plus minimal task routing/read model.']
   },
-  verifies: {
-    summary: 'Create or inspect specs/<partition>/verify.md as the task-derived verification contract before runtime evidence execution.',
-    requiredCommands: ['sdd status', 'sdd tasks list --branch <branch>', 'sdd verifies inspect --branch <branch>', 'sdd verifies write --branch <branch>'],
-    allowedSideEffects: ['read spec, plan, and tasks documents', 'write specs/<partition>/verify.md when explicitly using write'],
-    forbiddenSideEffects: ['run validation commands', 'update runtime.sqlite run state', 'create sync-back proposal', 'modify source files', 'auto commit'],
-    nextSteps: ['Run sdd status and confirm tasks.md is current.', 'Run sdd verifies inspect --branch <branch> to check whether verify.md exists and matches the current tasks hash.', 'Run sdd verifies write --branch <branch> to create verify.md, or add --force after reviewing task contract changes.', 'Use verify.md to guide validator evidence expectations; do not treat it as runtime evidence or as a replacement for `sdd test task|batch|wave`.']
-  },
-  test: {
-    summary: 'Execute validation commands from the frozen tasks.md + verify.md contract boundary, capture command output, evaluate acceptance evidence coverage, and return one unified task, batch, or wave judgment without authoring verify.md.',
-    requiredCommands: ['sdd status', 'sdd test task <task_id> --branch <branch>', 'sdd test batch <batch_id> --branch <branch>', 'sdd test wave --branch <branch> --wave <n>'],
-    allowedSideEffects: ['run declared validation commands', 'write branch-scoped test evidence artifacts', 'update runtime.sqlite test run and validation wave records', 'write validator evidence artifact'],
-    forbiddenSideEffects: ['modify source files outside the validation command effects', 'author or refresh verify.md', 'apply sync-back', 'auto commit', 'publish or push', 'treat command success alone as semantic PASS'],
-    nextSteps: ['Run sdd status and resolve the task, batch, or wave boundary plus branch.', 'Confirm verify.md exists and is current for the selected branch; if it is missing or stale, return to /sdd:tasks or use explicit sdd verifies write recovery before executing tests.', 'Use sdd test task <task_id> --branch <branch> for strict/task_end tasks or deliberate narrowed overrides with --run, --command, --command-json, --command-file, or passthrough argv.', 'Use sdd test batch <batch_id> --branch <branch> or sdd test wave --branch <branch> --wave <n> for batch_end or wave_end tasks so accumulated implementation evidence is judged together.', 'Inspect the generated command logs, test index, validator artifacts, acceptance maps, and workflow gate decision.', 'If the selected test boundary returns PASS, proceed to a decision card if policy requires one, otherwise run `sdd ship --branch <branch> --dry-run`; if it returns FAIL or BLOCKED, fix the reported command/evidence gaps and rerun the same boundary.']
-  },
-  do: {
-    summary: 'Execute one approved task boundary through the ingestion-aware SDD task workflow with explicit scout/implementer/reviewer/validator evidence handoff.',
-    requiredCommands: ['sdd status', 'sdd instructions do --json', 'sdd tasks inspect <task_id>', 'sdd artifact template artifacts/<agent>-<task_id>.md --task <task_id> --agent <agent> --run <run_id> --write', 'sdd artifact validate <run_id> <artifact> --task <task_id> --agent <agent>', 'sdd do task <task_id>'],
-    allowedSideEffects: ['write branch-scoped .sdd/runs evidence artifacts', 'update runtime.sqlite run state', 'modify files within selected task boundary'],
-    forbiddenSideEffects: ['background write', 'worktree creation', 'auto commit', 'expand beyond selected task boundary without checkpoint', 'mark missing evidence as PASS'],
-    nextSteps: ['Run sdd status and resolve exactly one task id from the user request or recommended next command.', 'Run sdd instructions do --json and sdd tasks inspect <task_id>.', 'Restate only the task Boundary, blocking gaps, and validation commands before implementation.', 'Use scout for bounded context only, implementer for selected-boundary edits, reviewer for review evidence, and validator for validation plus acceptance mapping.', 'Create or resolve the task run id, then write implement/review/validation result artifacts only with sdd artifact template artifacts/<agent>-<task_id>.md --task <task_id> --agent <agent> --run <run_id> --write; do not manually create copies under specs/<branch>/artifacts/ or specs/<branch>/evidence/artifacts/.', 'Pass run-relative artifacts/<file> paths to CLI flags, and keep source/test files in ## Evidence, not in sdd-result.artifacts.', 'Run sdd artifact validate before passing artifacts into sdd do task <task_id>.', 'Run or coordinate implementation only within the selected task boundary.', 'Run sdd do task <task_id> with explicit artifact paths when evidence is available.', 'Report run id, final status, blocking gaps, and next gate; if completed, follow sdd status recommended next command: continue sequential sdd do task, run sdd test task for strict/task_end work, or run sdd test batch / sdd test wave at the declared validation boundary.']
-  },
-  verify: {
-    summary: 'Run compatibility/diagnostic task acceptance coverage from reviewer/validator artifacts, resolving the latest eligible run from partition + task id unless --run is explicit; `sdd test task|batch|wave` is the primary runtime gate.',
-    requiredCommands: ['sdd status', 'sdd instructions verify --json', 'sdd artifact template artifacts/validation-<task_id>.md --task <task_id> --agent validator --run <run_id> --write', 'sdd artifact validate <run_id> <artifact> --task <task_id> --agent validator', 'sdd verify task <task_id> [--branch <branch>] [--run <run_id>]'],
-    allowedSideEffects: ['write acceptance coverage artifact', 'update runtime.sqlite diagnostic verification state'],
-    forbiddenSideEffects: ['auto commit', 'force push', 'auto-fix failures', 'create sync-back proposal as normal happy path', 'unapproved sync-back apply', 'mark completed with blocking validation gaps'],
-    nextSteps: ['Run sdd status and resolve exactly one task id plus workflow partition from the recommended command or user request.', 'Omit --run by default so CLI resolves the latest eligible run for partition + task id; pass --run only for explicit replay, CI, or old-run inspection.', 'Ensure the validator artifact includes exact Acceptance text, preferably under ## Acceptance Mapping from sdd artifact template.', 'When a validator artifact must be created manually for a run, write it only with sdd artifact template artifacts/validation-<task_id>.md --task <task_id> --agent validator --run <run_id> --write; do not manually create copies under specs/<branch>/artifacts/ or specs/<branch>/evidence/artifacts/.', 'Pass run-relative artifacts/<file> paths to validate/verify CLI flags.', 'Run sdd artifact validate before compatibility verify.', 'Run sdd instructions verify --json and sdd verify task <task_id> --branch <branch> only for explicit low-level diagnostics.', 'For the primary lifecycle path, use `sdd test task|batch|wave`; after PASS proceed to a decision card if policy requires one or `sdd ship --branch <branch> --dry-run`.', 'Report PASS/BLOCKED status and unresolved blockers; avoid pasting full acceptance coverage unless requested.']
-  },
-  'sync-back': {
-    summary: 'Inspect or replay verified task completion write-back state for diagnostic, recovery, replay, and legacy compatibility use.',
-    requiredCommands: ['sdd status', 'sdd instructions sync-back --json', 'sdd sync-back inspect [<run_id>] --branch <branch> --task <task_id>', 'sdd sync-back apply [<run_id>] --branch <branch> --task <task_id> [--approved]'],
-    allowedSideEffects: ['read runtime.sqlite run state', 'read sync-back proposal artifact', 'read specs/<partition>/tasks.md', 'write specs/<partition>/tasks.md during apply', 'write specs/<partition>/verify.md only when explicit --refresh-verify is supplied', 'update run sync_back state only during apply'],
-    forbiddenSideEffects: ['auto commit', 'force push', 'apply without inspect', 'apply confirm-required proposals without human approval', 'change source files outside tasks.md'],
-    nextSteps: ['Run sdd status and resolve exactly one task id plus workflow partition from an explicit diagnostic, recovery, replay, CI, or old-run inspection request.', 'Run sdd sync-back inspect --branch <branch> --task <task_id> first; pass an explicit run id only for replay, CI, or old-run inspection.', 'Report the inspect target update before asking for approval: target tasks file, task id, markdown status transition, proposal path, evidence artifacts, apply_policy, and policy reasons.', 'If apply_policy=direct and status=ready, run sdd sync-back apply --branch <branch> --task <task_id> only for explicit recovery/replay; if approval_required=true, ask for explicit confirmation and then add --approved.', 'Explain that default apply writes the task block status to completed, appends the sync-back implementation note from the proposal/evidence, marks the run sync_back state applied, and rebuilds the local run index; --refresh-verify is an explicit recovery option after reviewed task-contract changes.', 'After apply, report the updated task id, tasks.md path, applied flag, and sync_back state.']
+  execute: {
+    summary: 'Use /sdd:execute to consume accepted tasks.md ref/hash and the selected task brief, then implement or validate from readable task context without reinterpreting spec.md or plan.md.',
+    requiredCommands: ['sdd status', 'sdd instructions execute --json', 'sdd tasks inspect <bound_task_id>', 'sdd execute --branch <branch> --json', 'sdd execute close --branch <branch> --json'],
+    allowedSideEffects: ['modify files within selected task boundaries', 'run declared validation commands', 'write optional agent-authored execute side evidence under .sdd/runs/<branch>/execute/', 'update runtime.sqlite projections and run state through runtime commands'],
+    forbiddenSideEffects: ['runtime-authored Markdown artifacts', 'background write', 'worktree creation', 'auto commit', 'expand beyond selected task boundary without checkpoint', 'treat command success alone as semantic PASS', 'publish or push'],
+    nextSteps: ['Run sdd status and confirm the active public stage is execute or the recommended next command routes to execute.', 'Use the accepted tasks -> execute handoff and selected task brief as the primary input; read spec.md/plan.md only as shallow constraints for ambiguity, acceptance mapping, and goal validation.', 'If the current tasks.md hash differs from the accepted tasks ref/hash, stop and route back to tasks close/repair before implementation.', 'Use implementation board lanes for implementation/review/debug work and validation/checkpoint/evidence-judgment work; report them as execute lane state, not separate public stages.', 'Start from task context: why the task exists, where to start, allowed/forbidden boundary, completion evidence, validation handoff, and failure route. Do not repair tasks.md during execute unless runtime routes back to tasks.', 'Close the public stage through sdd execute close --branch <branch> --json; execute close validates accepted tasks ref/hash and projections, not fixed execute Markdown evidence files.', 'Stop and route back to tasks/plan/spec if the task brief still lacks boundary, validation, checkpoint, acceptance, or routing context after reading the accepted tasks artifact.']
   },
   ship: {
-    summary: 'Run local release readiness and optionally write specs/<branch>/release.md without publishing, pushing, tagging, or changing external release state.',
-    requiredCommands: ['sdd ship --branch <branch> --dry-run', 'sdd ship --branch <branch>', 'sdd statusline --branch <branch>', 'sdd doctor fast --branch <branch>', 'sdd update --check', 'npm run typecheck', 'npm test', 'npm run build', 'npm pack --dry-run --json', 'git status'],
-    allowedSideEffects: ['read project status', 'read SDD documents and run evidence', 'write specs/<branch>/release.md when not using --dry-run', 'run local validation commands'],
-    forbiddenSideEffects: ['npm publish', 'git push', 'git tag', 'create GitHub release', 'force push', 'auto commit', 'skip failed gates', 'treat historical doctor debt as a release blocker unless it affects current run evidence'],
-    nextSteps: ['Run sdd ship --branch <branch> --dry-run to inspect PASS/BLOCKED readiness without writing release docs.', 'If readiness output is acceptable, run sdd ship --branch <branch> to write specs/<branch>/release.md.', 'Use sdd statusline --branch <branch> for compact runtime/test/team/token/evidence health.', 'Run current-run health checks with sdd doctor fast --branch <branch>; use sdd doctor deep only for explicit historical audit.', 'Run npm run typecheck, npm test, npm run build, and npm pack --dry-run --json when preparing a real package release.', 'Report PASS/BLOCKED by readiness check, including exact failed commands and unresolved manual confirmations.', 'Stop before npm publish, git push, git tag, or external release creation unless the user explicitly approves that separate action.']
-  },
-  'run-task': {
-    summary: 'Run the ingestion-aware task workflow using CLI/core runtime state and artifacts.',
-    requiredCommands: ['sdd tasks inspect <task_id>', 'sdd do task <task_id>'],
-    allowedSideEffects: ['write branch-scoped .sdd/runs evidence artifacts', 'update runtime.sqlite run state'],
-    forbiddenSideEffects: ['background write', 'worktree creation', 'auto commit'],
-    nextSteps: ['Inspect the task.', 'Run the task loop with explicit artifacts and validation evidence.']
+    summary: 'Close ship readiness through agent-authored .sdd/runs/<branch>/ship/*.md evidence; optional release.md is ship-agent authored, not runtime-authored.',
+    requiredCommands: ['sdd status', 'sdd instructions ship --json', 'write .sdd/runs/<branch>/ship/ship-readiness-vN.md', 'write .sdd/runs/<branch>/ship/release-review-vN.md', 'write .sdd/runs/<branch>/ship/ship-manager-vN.md', 'write .sdd/runs/<branch>/ship/ship-collaboration-contract-vN.md', 'sdd ship close --branch <branch> --json', 'npm run build', 'npm pack --dry-run --json', 'git status'],
+    allowedSideEffects: ['read project status', 'read SDD documents and run evidence', 'write agent-authored .sdd/runs/<branch>/ship/*.md evidence', 'write optional agent-authored specs/<branch>/release.md', 'run local validation commands', 'record runtime ship projections in .sdd/runtime.sqlite'],
+    forbiddenSideEffects: ['runtime-authored Markdown artifacts', 'npm publish', 'git push', 'git tag', 'create GitHub release', 'force push', 'auto commit', 'skip failed gates', 'treat historical doctor debt as a release blocker unless it affects current run evidence'],
+    nextSteps: ['Run sdd status and confirm execute has accepted implementation, validation, checkpoint, and evidence-judgment evidence for the branch.', 'Have ship-manager/release agent author .sdd/runs/<branch>/ship/*.md evidence including a StageCollaborationContract; write specs/<branch>/release.md only as an explicit ship-agent artifact if needed.', 'Run sdd ship close --branch <branch> --json; runtime validates readiness refs/contracts/truthAlignment and writes only .sdd/runtime.sqlite.', 'Run package/build dry-run gates when preparing a real release.', 'Report PASS/BLOCKED by runtime ship readiness and local package checks.', 'Stop before npm publish, git push, git tag, or external release creation unless the user explicitly approves that separate action.']
   },
-  'verify-task': {
-    summary: 'Verify task acceptance coverage using CLI/core verifier artifacts and partition-aware run resolution.',
-    requiredCommands: ['sdd verify task <task_id> [--branch <branch>] [--run <run_id>]'],
-    allowedSideEffects: ['write acceptance coverage artifact', 'update .sdd run state'],
-    forbiddenSideEffects: ['auto commit', 'force push', 'unapproved sync-back apply'],
-    nextSteps: ['Run goal-level verify without --run for the latest eligible partition/task run, unless inspecting an explicit run.', 'Use sdd test task for primary lifecycle judgment; use sync-back only for explicit diagnostic/recovery/replay.']
-  }
   };
 
 
@@ -161,5 +118,5 @@ export function renderSddInstructions(payload: SddInstructionPayload): string {
 }
 
 function isInstructionAction(action: string): action is InstructionAction {
-  return action === 'overview' || action === 'init' || action === 'doctor' || action === 'update' || action === 'spec' || action === 'plan' || action === 'tasks' || action === 'verifies' || action === 'test' || action === 'do' || action === 'verify' || action === 'sync-back' || action === 'ship' || action === 'run-task' || action === 'verify-task';
+  return action === 'overview' || action === 'init' || action === 'doctor' || action === 'update' || action === 'spec' || action === 'plan' || action === 'tasks' || action === 'execute' || action === 'ship';
 }

package/node_modules/@sdd-agent-platform/core/src/lifecycle/decision-gate.test.ts

@@ -1,174 +1,174 @@
-import test from 'node:test';
-import assert from 'node:assert/strict';
-import { mkdtemp, rm } from 'node:fs/promises';
-import { tmpdir } from 'node:os';
-import path from 'node:path';
-
-import { initProject } from '../config/init-project.js';
-import { readRunEvents } from '../run-state/events.js';
-import { createRun, readRunState } from '../run-state/run-state.js';
-import { evaluateLifecycleDecisionGate, recordLifecycleDecision } from './decision-gate.js';
-import { renderLifecycleDecisionGate } from './rendering.js';
-import { extractLifecycleRiskSignalsFromText } from './risk-signals.js';
-
-test('lifecycle decision gate allows direct only through conservative whitelist', () => {
-  const result = evaluateLifecycleDecisionGate({
-    intent_clarity: 'high',
-    acceptance_clarity: 'high',
-    estimated_change_size: 'tiny',
-    task_count_estimate: 1,
-    file_count_estimate: 1,
-    impact_confidence: 'high',
-    risk_tags: [],
-    reversibility: 'reversible',
-    validation_clarity: 'clear',
-    validation_available: true,
-    validation_cost: 'cheap',
-    requires_agents: false,
-    handoff_count: 0,
-    artifact_dependency: false,
-    runtime_recovery_need: false,
-    orchestration_uncertainty: 'low'
-  }, new Date('2026-05-01T00:00:00.000Z'));
-
-  assert.equal(result.record.decision.profile, 'direct');
-  assert.equal(result.record.decision.confidence, 'high');
-  assert.equal(result.record.decision.hard_gate_hits.length, 0);
-  assert.equal(result.record.decision.human_checkpoint_required, false);
-  assert.equal(result.record.decision.skipped_stages.includes('full-spec'), true);
-});
-
-test('lifecycle hard gates force full profile for contract and state risks', () => {
-  const result = evaluateLifecycleDecisionGate({
-    intent_clarity: 'high',
-    acceptance_clarity: 'high',
-    impact_confidence: 'high',
-    validation_clarity: 'clear',
-    validation_available: true,
-    validation_cost: 'cheap',
-    reversibility: 'reversible',
-    affected_contracts: ['public-api'],
-    risk_tags: ['state-machine']
-  });
-
-  assert.equal(result.record.decision.profile, 'full');
-  assert.equal(result.record.decision.hard_gate_hits.includes('api_schema_contract'), true);
-  assert.equal(result.record.decision.hard_gate_hits.includes('state_machine_concurrency_liveness'), true);
-  assert.equal(result.record.decision.required_stages.includes('verify'), true);
-});
-
-test('lifecycle database risk forces full hard gate and human checkpoint', () => {
-  const result = evaluateLifecycleDecisionGate({
-    intent_clarity: 'high',
-    acceptance_clarity: 'high',
-    impact_confidence: 'high',
-    validation_clarity: 'clear',
-    validation_available: true,
-    validation_cost: 'cheap',
-    reversibility: 'reversible',
-    risk_tags: ['database']
-  });
-
-  assert.equal(result.record.decision.profile, 'full');
-  assert.equal(result.record.decision.hard_gate_hits.includes('database_or_data_loss'), true);
-  assert.equal(result.record.decision.human_checkpoint_required, true);
-  assert.equal(result.checkpointRequired, true);
-});
-
-test('Phase 5.1 lifecycle risk extraction maps Chinese hard-gate text', () => {
-  const extraction = extractLifecycleRiskSignalsFromText('三线程状态流转，并发更新，SQL 拼接，数据一致性风险');
-  const categories = extraction.evidence.map((item) => item.category);
-  const result = evaluateLifecycleDecisionGate(extraction.signals);
-  const rendered = renderLifecycleDecisionGate(result);
-
-  assert.equal(extraction.source, 'from_text');
-  assert.equal(extraction.riskTags.includes('state-machine'), true);
-  assert.equal(extraction.riskTags.includes('concurrency'), true);
-  assert.equal(extraction.riskTags.includes('database'), true);
-  assert.equal(categories.includes('state_machine'), true);
-  assert.equal(categories.includes('concurrency'), true);
-  assert.equal(categories.includes('sql'), true);
-  assert.equal(categories.includes('database_data_loss'), true);
-  assert.equal(result.record.decision.profile, 'full');
-  assert.equal(result.record.decision.hard_gate_hits.includes('state_machine_concurrency_liveness'), true);
-  assert.equal(result.record.decision.hard_gate_hits.includes('database_or_data_loss'), true);
-  assert.equal(result.autonomyCeiling, 'full_sdd_with_checkpoint');
-  assert.equal(rendered.includes('Lifecycle checkpoint is required.'), true);
-  assert.equal(rendered.includes('Why:'), true);
-  assert.equal(rendered.includes('Next:'), true);
-});
-
-test('lifecycle checkpoint triggers are recorded without executing workflow', () => {
-  const result = evaluateLifecycleDecisionGate({
-    intent_clarity: 'high',
-    acceptance_clarity: 'high',
-    impact_confidence: 'high',
-    validation_clarity: 'clear',
-    validation_available: true,
-    validation_cost: 'cheap',
-    reversibility: 'reversible',
-    policy_hits: ['git_commit'],
-    permission_required: ['dependency_install'],
-    human_checkpoint_required: true
-  });
-
-  assert.equal(result.record.decision.profile, 'compact');
-  assert.equal(result.record.decision.human_checkpoint_required, true);
-  assert.equal(result.record.decision.hard_gate_hits.includes('policy_or_permission_checkpoint'), true);
-  assert.match(result.boundaries.join('\n'), /must not execute Phase 1.8 task implementation loop/);
-});
-
-test('lifecycle research gate handles unscoutable unknown impact', () => {
-  const result = evaluateLifecycleDecisionGate({
-    impact_confidence: 'low',
-    can_scout_impact: false
-  });
-
-  assert.equal(result.record.decision.profile, 'research');
-  assert.equal(result.record.decision.confidence, 'low');
-  assert.equal(result.record.decision.hard_gate_hits.includes('low_impact_confidence_unscoutable'), true);
-  assert.equal(result.record.decision.required_stages[0], 'research');
-});
-
-test('lifecycle decision gate emits canonical Phase 1.3 contract id for new records', () => {
-  const result = evaluateLifecycleDecisionGate({
-    intent_clarity: 'high',
-    acceptance_clarity: 'high',
-    impact_confidence: 'high',
-    validation_clarity: 'clear',
-    validation_available: true,
-    validation_cost: 'cheap',
-    reversibility: 'reversible'
-  });
-
-  assert.equal(result.record.contract, 'sdd-lifecycle-decision-v1');
-  assert.equal(result.record.version, '1.3.0');
-});
-
-test('recordLifecycleDecision persists command gate output to run state and events', async () => {
-  const root = await mkdtemp(path.join(tmpdir(), 'sdd-lifecycle-'));
-  try {
-    await initProject(root);
-    const state = await createRun(root, { runId: 'run-1' });
-    const result = evaluateLifecycleDecisionGate({
-      intent_clarity: 'high',
-      acceptance_clarity: 'high',
-      impact_confidence: 'high',
-      validation_clarity: 'clear',
-      validation_available: true,
-      validation_cost: 'cheap',
-      reversibility: 'reversible',
-      risk_tags: ['database']
-    }, new Date('2026-05-01T00:00:00.000Z'));
-
-    await recordLifecycleDecision(root, state.runId, result.record);
-    const restored = await readRunState(root, state.runId);
-    const events = await readRunEvents(root, state.runId);
-    assert.equal(restored.lifecycleDecision?.decision.profile, 'full');
-    assert.equal(restored.lifecycleDecision?.decision.hard_gate_hits.includes('database_or_data_loss'), true);
-    assert.equal(restored.lifecycleDecision?.decision.human_checkpoint_required, true);
-    assert.equal(events.some((event) => /Lifecycle decision recorded by Phase 1.7 command gate/.test(event.summary ?? '')), true);
-  } finally {
-    await rm(root, { recursive: true, force: true });
-  }
-});
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import { mkdtemp, rm } from 'node:fs/promises';
+import { tmpdir } from 'node:os';
+import path from 'node:path';
+
+import { initProject } from '../config/init-project.js';
+import { readRunEvents } from '../run-state/events.js';
+import { createRun, readRunState } from '../run-state/run-state.js';
+import { evaluateLifecycleDecisionGate, recordLifecycleDecision } from './decision-gate.js';
+import { renderLifecycleDecisionGate } from './rendering.js';
+import { extractLifecycleRiskSignalsFromText } from './risk-signals.js';
+
+test('lifecycle decision gate allows direct only through conservative whitelist', () => {
+  const result = evaluateLifecycleDecisionGate({
+    intent_clarity: 'high',
+    acceptance_clarity: 'high',
+    estimated_change_size: 'tiny',
+    task_count_estimate: 1,
+    file_count_estimate: 1,
+    impact_confidence: 'high',
+    risk_tags: [],
+    reversibility: 'reversible',
+    validation_clarity: 'clear',
+    validation_available: true,
+    validation_cost: 'cheap',
+    requires_agents: false,
+    handoff_count: 0,
+    artifact_dependency: false,
+    runtime_recovery_need: false,
+    orchestration_uncertainty: 'low'
+  }, new Date('2026-05-01T00:00:00.000Z'));
+
+  assert.equal(result.record.decision.profile, 'direct');
+  assert.equal(result.record.decision.confidence, 'high');
+  assert.equal(result.record.decision.hard_gate_hits.length, 0);
+  assert.equal(result.record.decision.human_checkpoint_required, false);
+  assert.equal(result.record.decision.skipped_stages.includes('full-spec'), true);
+});
+
+test('lifecycle hard gates force full profile for contract and state risks', () => {
+  const result = evaluateLifecycleDecisionGate({
+    intent_clarity: 'high',
+    acceptance_clarity: 'high',
+    impact_confidence: 'high',
+    validation_clarity: 'clear',
+    validation_available: true,
+    validation_cost: 'cheap',
+    reversibility: 'reversible',
+    affected_contracts: ['public-api'],
+    risk_tags: ['state-machine']
+  });
+
+  assert.equal(result.record.decision.profile, 'full');
+  assert.equal(result.record.decision.hard_gate_hits.includes('api_schema_contract'), true);
+  assert.equal(result.record.decision.hard_gate_hits.includes('state_machine_concurrency_liveness'), true);
+  assert.equal(result.record.decision.required_stages.includes('verify'), true);
+});
+
+test('lifecycle database risk forces full hard gate and human checkpoint', () => {
+  const result = evaluateLifecycleDecisionGate({
+    intent_clarity: 'high',
+    acceptance_clarity: 'high',
+    impact_confidence: 'high',
+    validation_clarity: 'clear',
+    validation_available: true,
+    validation_cost: 'cheap',
+    reversibility: 'reversible',
+    risk_tags: ['database']
+  });
+
+  assert.equal(result.record.decision.profile, 'full');
+  assert.equal(result.record.decision.hard_gate_hits.includes('database_or_data_loss'), true);
+  assert.equal(result.record.decision.human_checkpoint_required, true);
+  assert.equal(result.checkpointRequired, true);
+});
+
+test('Phase 5.1 lifecycle risk extraction maps Chinese hard-gate text', () => {
+  const extraction = extractLifecycleRiskSignalsFromText('三线程状态流转，并发更新，SQL 拼接，数据一致性风险');
+  const categories = extraction.evidence.map((item) => item.category);
+  const result = evaluateLifecycleDecisionGate(extraction.signals);
+  const rendered = renderLifecycleDecisionGate(result);
+
+  assert.equal(extraction.source, 'from_text');
+  assert.equal(extraction.riskTags.includes('state-machine'), true);
+  assert.equal(extraction.riskTags.includes('concurrency'), true);
+  assert.equal(extraction.riskTags.includes('database'), true);
+  assert.equal(categories.includes('state_machine'), true);
+  assert.equal(categories.includes('concurrency'), true);
+  assert.equal(categories.includes('sql'), true);
+  assert.equal(categories.includes('database_data_loss'), true);
+  assert.equal(result.record.decision.profile, 'full');
+  assert.equal(result.record.decision.hard_gate_hits.includes('state_machine_concurrency_liveness'), true);
+  assert.equal(result.record.decision.hard_gate_hits.includes('database_or_data_loss'), true);
+  assert.equal(result.autonomyCeiling, 'full_sdd_with_checkpoint');
+  assert.equal(rendered.includes('Lifecycle checkpoint is required.'), true);
+  assert.equal(rendered.includes('Why:'), true);
+  assert.equal(rendered.includes('Next:'), true);
+});
+
+test('lifecycle checkpoint triggers are recorded without executing workflow', () => {
+  const result = evaluateLifecycleDecisionGate({
+    intent_clarity: 'high',
+    acceptance_clarity: 'high',
+    impact_confidence: 'high',
+    validation_clarity: 'clear',
+    validation_available: true,
+    validation_cost: 'cheap',
+    reversibility: 'reversible',
+    policy_hits: ['git_commit'],
+    permission_required: ['dependency_install'],
+    human_checkpoint_required: true
+  });
+
+  assert.equal(result.record.decision.profile, 'compact');
+  assert.equal(result.record.decision.human_checkpoint_required, true);
+  assert.equal(result.record.decision.hard_gate_hits.includes('policy_or_permission_checkpoint'), true);
+  assert.match(result.boundaries.join('\n'), /must not execute Phase 1.8 task implementation loop/);
+});
+
+test('lifecycle research gate handles unscoutable unknown impact', () => {
+  const result = evaluateLifecycleDecisionGate({
+    impact_confidence: 'low',
+    can_scout_impact: false
+  });
+
+  assert.equal(result.record.decision.profile, 'research');
+  assert.equal(result.record.decision.confidence, 'low');
+  assert.equal(result.record.decision.hard_gate_hits.includes('low_impact_confidence_unscoutable'), true);
+  assert.equal(result.record.decision.required_stages[0], 'research');
+});
+
+test('lifecycle decision gate emits canonical Phase 1.3 contract id for new records', () => {
+  const result = evaluateLifecycleDecisionGate({
+    intent_clarity: 'high',
+    acceptance_clarity: 'high',
+    impact_confidence: 'high',
+    validation_clarity: 'clear',
+    validation_available: true,
+    validation_cost: 'cheap',
+    reversibility: 'reversible'
+  });
+
+  assert.equal(result.record.contract, 'sdd-lifecycle-decision-v1');
+  assert.equal(result.record.version, '1.3.0');
+});
+
+test('recordLifecycleDecision persists command gate output to run state and events', async () => {
+  const root = await mkdtemp(path.join(tmpdir(), 'sdd-lifecycle-'));
+  try {
+    await initProject(root);
+    const state = await createRun(root, { runId: 'run-1' });
+    const result = evaluateLifecycleDecisionGate({
+      intent_clarity: 'high',
+      acceptance_clarity: 'high',
+      impact_confidence: 'high',
+      validation_clarity: 'clear',
+      validation_available: true,
+      validation_cost: 'cheap',
+      reversibility: 'reversible',
+      risk_tags: ['database']
+    }, new Date('2026-05-01T00:00:00.000Z'));
+
+    await recordLifecycleDecision(root, state.runId, result.record);
+    const restored = await readRunState(root, state.runId);
+    const events = await readRunEvents(root, state.runId);
+    assert.equal(restored.lifecycleDecision?.decision.profile, 'full');
+    assert.equal(restored.lifecycleDecision?.decision.hard_gate_hits.includes('database_or_data_loss'), true);
+    assert.equal(restored.lifecycleDecision?.decision.human_checkpoint_required, true);
+    assert.equal(events.some((event) => /Lifecycle decision recorded by Phase 1.7 command gate/.test(event.summary ?? '')), true);
+  } finally {
+    await rm(root, { recursive: true, force: true });
+  }
+});