|
294 | 294 | Absent fields MUST be omitted from the JSON entry (not written as null). |
295 | 295 | source: ARCHITECTURE.md §YAML-Native Governance Layer |
296 | 296 | status: implemented |
| 297 | +- id: REQ-351 |
| 298 | + title: specsmith checkpoint Governance Anchor Command |
| 299 | + description: >- |
| 300 | + specsmith MUST provide a checkpoint CLI command that emits a compact GOVERNANCE ANCHOR |
| 301 | + summarising the current project state: project name (from scaffold.yml), AEE phase with |
| 302 | + readiness percentage, audit health and failed check count, REQ count, TEST count, |
| 303 | + ESDB record count with chain validity, up to 3 recent WI- identifiers from LEDGER.md, |
| 304 | + and the last preflight acceptance line. With --json it MUST emit a JSON payload containing |
| 305 | + ts, project, phase, phase_label, phase_pct, health, audit_failed, req_count, test_count, |
| 306 | + esdb_records, esdb_chain_valid, recent_wis, last_preflight, and anchor fields. |
| 307 | + Without --json it MUST emit a human-readable bordered GOVERNANCE ANCHOR block with a |
| 308 | + footer instructing agents to include it verbatim in any context summary. All data |
| 309 | + gathering MUST be best-effort (exceptions silently swallowed) so the command never |
| 310 | + fails even on projects with no ESDB or LEDGER. |
| 311 | + source: ARCHITECTURE.md §Session Governance Protocol |
| 312 | + status: implemented |
| 313 | +- id: REQ-352 |
| 314 | + title: M006 Session Governance Migration Auto-injects Protocol into AGENTS.md |
| 315 | + description: >- |
| 316 | + specsmith MUST include migration M006 (version=6) that detects whether AGENTS.md |
| 317 | + contains any of the sentinel strings 'specsmith checkpoint', 'Session Governance Protocol', |
| 318 | + 'GOVERNANCE ANCHOR', or 'governance heartbeat'. When none are present, M006 MUST |
| 319 | + back up AGENTS.md to .specsmith/agents.md.m006.bak and inject the full Session Governance |
| 320 | + Protocol section (heartbeat every 8-10 turns, preflight gate, drift detection checklist, |
| 321 | + checkpoint-in-summary rule, session end). M006 MUST be idempotent (re-running when section |
| 322 | + is present is a no-op), non-destructive (original always backed up), and registered in |
| 323 | + MigrationRegistry so it runs automatically via specsmith migrate-project and |
| 324 | + specsmith upgrade --full. |
| 325 | + source: ARCHITECTURE.md §Session Governance Protocol |
| 326 | + status: implemented |
| 327 | +- id: REQ-353 |
| 328 | + title: Modern Web Framework Project Types |
| 329 | + description: >- |
| 330 | + specsmith MUST support the following modern web framework project types in addition to |
| 331 | + the existing web-frontend and fullstack-js types: nextjs-app (Next.js / React with |
| 332 | + SSR/SSG, next lint, jest/playwright), nuxt-app (Nuxt.js / Vue, vitest, playwright), |
| 333 | + sveltekit-app (SvelteKit, vitest, playwright), remix-app (Remix React, vitest, |
| 334 | + playwright), astro-site (Astro static/SSR, vitest, playwright). Each MUST have a |
| 335 | + corresponding ToolSet entry in the tool registry with appropriate lint, typecheck, |
| 336 | + test, security, build, and format tools. Each MUST appear in _TYPE_LABELS with a |
| 337 | + human-readable label. |
| 338 | + source: ARCHITECTURE.md §Implemented Specsmith System |
| 339 | + status: implemented |
0 commit comments