Files
specs/openspec/changes/archive/2026-08-26-harden-openspec-sdd-agent-resilience/tasks.md
T

6.2 KiB

1. Specs workflow delivery

  • 1.1 [specs] Restructure project schema instructions as compact Critical Rules and bump the schema contract to v3
    • Covers: openspec-authority-and-lifecycle — Project schema сохраняет заметные самодостаточные правила; openspec-authority-and-lifecycle — Изменение upstream artifact требует каскадной проверки
    • Verification: Inspect every generated artifact instruction for rule ownership and run openspec schema validate wealth-ledger-sdd --verbose.
  • 1.2 [specs] Replace the ADDED-first Delta Spec scaffold with the approved operation-neutral commented shape
    • Covers: openspec-authority-and-lifecycle — Delta Spec template не предрешает операцию
    • Verification: Generate or inspect the Specs instruction/template output and validate controlled ADDED, MODIFIED, REMOVED and RENAMED deltas without empty operation sections.
  • 1.3 [specs] Implement distinct artifact-validation, invocation and environment failure results in planning verification
    • Covers: openspec-authority-and-lifecycle — Planning artifact проверяется до запроса approval
    • Verification: Run controlled planning-verifier cases and observe the specified result category and exit status for each failure class.
  • 1.4 [specs] Reject unresolved N/A placeholders while keeping substantive rationale review semantic
    • Covers: multi-repository-delivery — Tasks трассируются к утверждённым требованиям
    • Verification: Run one compliant N/A fixture and controlled failures for empty, separator-only and unresolved-placeholder rationales.
  • 1.5 [specs] Route Apply through CLI-resolved contextFiles and affected-area local instructions
    • Covers: openspec-authority-and-lifecycle — Apply читает только разрешённый planning context
    • Verification: Inspect native Apply instructions for the active change and confirm they require every CLI-resolved context path without a second context map.
  • 1.6 [specs] Extend controlled fixtures to preserve every changed lifecycle invariant
    • Covers: openspec-authority-and-lifecycle — Project schema сохраняет заметные самодостаточные правила; openspec-authority-and-lifecycle — Delta Spec template не предрешает операцию; openspec-authority-and-lifecycle — Apply читает только разрешённый planning context; openspec-authority-and-lifecycle — Изменение upstream artifact требует каскадной проверки; openspec-authority-and-lifecycle — Planning artifact проверяется до запроса approval; multi-repository-delivery — Tasks трассируются к утверждённым требованиям
    • Verification: Run the planning and authority fixture suites and confirm compliant cases pass while each representative violation fails for the intended reason.
  • 1.7 [specs] Run the canonical specs validation set against schema v3 and the active change
    • Covers: N/A — repository gate verification confirms the approved workflow but introduces no independent spec-level behavior.
    • Verification: Run strict change validation with openspec validate harden-openspec-sdd-agent-resilience --type change --strict --store wealth-ledger-specs, strict main-spec validation, schema validation, planning fixtures and authority verification.

2. Durable audit and process documentation

  • 2.1 [docs] Move the six second-round reports into one immutable audit snapshot with a concise source index
    • Covers: N/A — evidence preservation applies the existing audit-remediation contract and introduces no new delta behavior.
    • Verification: Confirm the snapshot index links all six reports and records the known provenance limitations without checksum or byte-count gates.
  • 2.2 [docs] Triage the second-round claims and align as-built SDD lifecycle documentation with the delivered v3 contract
    • Covers: openspec-authority-and-lifecycle — Project schema сохраняет заметные самодостаточные правила; openspec-authority-and-lifecycle — Delta Spec template не предрешает операцию; openspec-authority-and-lifecycle — Apply читает только разрешённый planning context; openspec-authority-and-lifecycle — Изменение upstream artifact требует каскадной проверки; openspec-authority-and-lifecycle — Planning artifact проверяется до запроса approval; multi-repository-delivery — Tasks трассируются к утверждённым требованиям
    • Verification: Review every normalized claim against its source and existing Audit IDs, then check affected local links and current-state wording.
  • 2.3 [docs] Run the docs canonical gate after snapshot and lifecycle updates
    • Covers: N/A — repository gate verification checks delivered documentation and does not define separate observable workflow behavior.
    • Verification: Run npm run verify in docs under Node 22 and inspect the observed Markdown and diff-check result.

3. Cross-area verification

  • 3.1 [workspace] Run the affected-area workspace dispatcher
    • Covers: N/A — orchestration only; specs and docs retain ownership of their implementation and canonical gates.
    • Verification: Run bash specs/scripts/verify-workspace-change.sh harden-openspec-sdd-agent-resilience from the workspace root under Node 22 and observe both affected-area results.
  • 3.2 [workspace] Perform semantic verification and independent read-only review
    • Covers: N/A — terminal verification compares delivery with approved artifacts and introduces no independent behavior.
    • Verification: Compare implementation with every Proposal outcome, all six Requirements, all twenty Scenarios, Design decisions and completed tasks; require an independent review with no Critical or Important findings.