rcf-lite 0.0.1 → 0.7.1

package/rcf/tacs/tac-006.json

@@ -0,0 +1,104 @@
+{
+  "tacId": "TAC-006",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "0.1.0",
+  "status": "draft",
+  "name": "MCP server",
+  "purpose": "Expose store, query, view and build operations as local stdio MCP tools so an AI harness can drive the whole feature set without shelling out to the CLI.",
+  "responsibilities": [
+    "Register tools with structured input and output for every CRUD, query, view and build operation",
+    "Route each tool to the same core operation the CLI uses",
+    "Communicate over local stdio only and open no network listener",
+    "Serialise structured errors so an AI tool can act on them"
+  ],
+  "internalStructure": "A thin MCP adapter registers each tool with a schema for its input and output and maps each tool to a core function. Errors are converted to structured objects via the error and reporting component.",
+  "interfaces": [
+    {
+      "name": "rcf.read",
+      "kind": "mcpTool",
+      "description": "Read any RCF document by id over MCP."
+    },
+    {
+      "name": "rcf.create",
+      "kind": "mcpTool",
+      "description": "Create a document with parent linkage over MCP."
+    },
+    {
+      "name": "rcf.update",
+      "kind": "mcpTool",
+      "description": "Update fields on a document over MCP."
+    },
+    {
+      "name": "rcf.delete",
+      "kind": "mcpTool",
+      "description": "Delete a document with reference safety over MCP."
+    },
+    {
+      "name": "rcf.coverage",
+      "kind": "mcpTool",
+      "description": "Report coverage gaps over MCP."
+    },
+    {
+      "name": "rcf.trace",
+      "kind": "mcpTool",
+      "description": "Trace forward or back over MCP."
+    },
+    {
+      "name": "rcf.impact",
+      "kind": "mcpTool",
+      "description": "Report impact over MCP."
+    },
+    {
+      "name": "rcf.view",
+      "kind": "mcpTool",
+      "description": "Generate the diagram and the static page over MCP."
+    },
+    {
+      "name": "rcf.build.assemble",
+      "kind": "mcpTool",
+      "description": "Assemble a build prompt over MCP."
+    },
+    {
+      "name": "rcf.build.markDone",
+      "kind": "mcpTool",
+      "description": "Mark a slice done over MCP."
+    }
+  ],
+  "dependencies": [
+    {
+      "name": "Document store",
+      "kind": "tac",
+      "tacId": "TAC-001",
+      "description": "CRUD tools route through the store."
+    },
+    {
+      "name": "View renderer",
+      "kind": "tac",
+      "tacId": "TAC-003",
+      "description": "The view tool routes to the renderer."
+    },
+    {
+      "name": "Query engine",
+      "kind": "tac",
+      "tacId": "TAC-004",
+      "description": "Coverage, trace and impact tools route to the query engine."
+    },
+    {
+      "name": "Build adapter",
+      "kind": "tac",
+      "tacId": "TAC-005",
+      "description": "Build tools route to the build adapter."
+    },
+    {
+      "name": "Error and reporting",
+      "kind": "tac",
+      "tacId": "TAC-007",
+      "description": "Structured errors are serialised for the MCP client."
+    }
+  ],
+  "tradeoffs": "Local stdio sacrifices the convenience of a hosted MCP but is the only transport that preserves filesystem access; the trade is locked by the differentiator.",
+  "notes": "The MCP surface mirrors the CLI verb set so behaviour is identical across surfaces.",
+  "createdAt": "2026-06-25T00:00:00Z",
+  "updatedAt": "2026-06-25T00:00:00Z"
+}

package/rcf/tacs/tac-007.json

@@ -0,0 +1,38 @@
+{
+  "tacId": "TAC-007",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "0.1.0",
+  "status": "draft",
+  "name": "Error and reporting",
+  "purpose": "The structured error type and the consistent rendering of errors across CLI and MCP surfaces.",
+  "responsibilities": [
+    "Define a structured error type carrying the offending field, the rule broken and the document id",
+    "Render errors as readable terminal output for the CLI",
+    "Serialise errors as structured objects for MCP clients",
+    "Aggregate multiple validation failures so all are reported together"
+  ],
+  "internalStructure": "A small error type and a pair of renderers (terminal and structured). The renderers are pure functions over the error type.",
+  "interfaces": [
+    {
+      "name": "RcfError",
+      "kind": "type",
+      "description": "The structured error type used throughout the tool."
+    },
+    {
+      "name": "renderForTerminal",
+      "kind": "function",
+      "description": "Render an RcfError as human-readable terminal output."
+    },
+    {
+      "name": "renderForMcp",
+      "kind": "function",
+      "description": "Serialise an RcfError as a structured object for an MCP client."
+    }
+  ],
+  "dependencies": [],
+  "tradeoffs": "A single error type across surfaces costs a small loss of surface-specific detail but guarantees that error reporting does not drift between CLI and MCP.",
+  "notes": "Validation failures aggregate; the renderers preserve the full list, not just the first.",
+  "createdAt": "2026-06-25T00:00:00Z",
+  "updatedAt": "2026-06-25T00:00:00Z"
+}

package/rcf/tacs/tac-008.json

@@ -0,0 +1,51 @@
+{
+  "createdAt": "2026-07-20T17:01:52.768Z",
+  "updatedAt": "2026-07-20T17:01:52.768Z",
+  "purpose": "Ship the agent-facing method layer - the elicitation and build-cycle playbooks, the reference docs and the harness fragment - that teaches an AI agent how to run the RCF method well, served over MCP as resources and prompts and readable in place under guidance/.",
+  "responsibilities": [
+    "Carry the elicitation method (question frames, AC-depth bar, deploy-target elicitation, hosting-choice guidance) the eliciting agent runs with a human",
+    "Carry the build-cycle method (five stages, local-preview default outcome, runtime-provenance discipline, interim self-review) the operating agent runs per FBS",
+    "Carry the harness fragment rcf init writes into CLAUDE.md and AGENTS.md, whose RULE blocks foreclose observed failure modes",
+    "Keep every shipped claim, verb and channel address mechanically agreed with the tool via the drift tests"
+  ],
+  "internalStructure": "Static markdown files under guidance/, indexed by guidance/manifest.json which maps each file to one canonical MCP address (resources for reference docs, prompts for the playbooks). The harness fragment is a fenced block in harness-template.md that src/setup extracts and writes into agent-instructions files. Drift tests (test/guidance) assert content-and-inventory invariants so the pack and the tool cannot silently diverge.",
+  "interfaces": [
+    {
+      "name": "rcf_elicit_requirements",
+      "kind": "prompt",
+      "description": "The elicitation playbook, served as an MCP prompt to the eliciting agent."
+    },
+    {
+      "name": "rcf_execute_build_cycle",
+      "kind": "prompt",
+      "description": "The build-cycle playbook, served as an MCP prompt to the operating agent."
+    },
+    {
+      "name": "harness fragment",
+      "kind": "artifact",
+      "description": "The RULE-bearing block rcf init writes into CLAUDE.md and AGENTS.md."
+    }
+  ],
+  "dependencies": [
+    {
+      "name": "MCP server",
+      "kind": "tac",
+      "tacId": "TAC-006",
+      "description": "Serves the pack's docs as resources and playbooks as prompts over local stdio."
+    },
+    {
+      "name": "Build adapter",
+      "kind": "tac",
+      "tacId": "TAC-005",
+      "description": "The build-cycle method the pack teaches is executed against the bundles the build adapter assembles."
+    }
+  ],
+  "tradeoffs": "The pack is prose served to a model, not enforced code: it can teach a property (local preview, provenance labelling) but cannot mechanically compel it the way a schema compels document shape. Drift tests hold the pack honest against the tool's verbs and inventory; the method's behavioural properties are held by the RULE blocks and the ACs that require them, not by a runtime gate. The productised independent gate is out of scope here (see ADR-009).",
+  "notes": "Modelled as a component for the first time by the Tier-1 hardening set; the pack existed and shipped before this TAC captured it.",
+  "tacId": "TAC-008",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "0.1.0",
+  "status": "draft",
+  "name": "Agent guidance pack"
+}

package/rcf/tad.json

@@ -0,0 +1,51 @@
+{
+  "tadId": "TAD-001",
+  "prdId": "PRD-001",
+  "version": "0.1.0",
+  "status": "draft",
+  "systemOverview": {
+    "executiveSummary": "Build Lite is a Node 24 ESM toolset whose core is a set of local filesystem operations over a project's RCF documents. CRUD, query, view, the build loop and the MCP surface are all thin layers over a shared document store that reads and writes the on-disk rcf tree and validates against the published schemas at every boundary.",
+    "systemPurpose": "Run the full RCF method over in-repository documents and surface it through deterministic, structured operations for a non-engineering owner and for AI tooling.",
+    "architecturalApproach": "Layered. A document-store core owns load, validate and persist. A CLI binary, a view renderer, a query engine, a build adapter and an MCP server are all consumers of that core. No layer reaches the filesystem except through the store.",
+    "keyCapabilities": [
+      "Filesystem-backed RCF document store with schema validation at boundaries",
+      "Deterministic CRUD verbs over every document type",
+      "Diagram and HTML rendering of the whole tree",
+      "Traceability and query over the chain",
+      "Build-specification to implementation-prompt assembly",
+      "Local stdio MCP surface over the whole feature set"
+    ]
+  },
+  "architecturePrinciples": [
+    {
+      "name": "Filesystem is the source of truth",
+      "description": "Every read and write goes to the local rcf tree; no other store mirrors it.",
+      "rationale": "Guarantees the in-repository differentiator and keeps the tool harness-agnostic."
+    },
+    {
+      "name": "Validate at every boundary",
+      "description": "Documents are validated against the published schemas on load and before persist.",
+      "rationale": "A non-coder cannot catch a malformed document by eye; the tool must refuse to write invalid state."
+    },
+    {
+      "name": "Adapters are thin",
+      "description": "CLI, MCP and the build loop carry no business logic the core does not already own.",
+      "rationale": "One behaviour, many surfaces; no drift between how a verb behaves on the CLI versus over MCP."
+    },
+    {
+      "name": "Harness-agnostic",
+      "description": "The tool runs the same against any AI harness because behaviour lives on the local filesystem and not in a hosted surface.",
+      "rationale": "Survives a change of AI harness without re-implementation or migration."
+    }
+  ],
+  "integrationArchitecture": {
+    "apiDesign": "The store exposes a typed-by-convention internal API of document operations. The CLI maps verbs to those operations and renders results for a terminal. The MCP server maps tools to the same operations and returns structured results. No HTTP API is exposed.",
+    "eventModel": "None. Operations are synchronous filesystem reads and writes."
+  },
+  "operationalConcerns": {
+    "healthChecks": "Not applicable for a local binary; a validate command reports project health by validating every document and listing broken references.",
+    "logging": "Human-readable terminal output by default; a quiet flag for scripting and a verbose flag for diagnostics."
+  },
+  "createdAt": "2026-06-25T00:00:00Z",
+  "updatedAt": "2026-07-02T10:22:43Z"
+}

package/rcf/test-suites/PENDING.md

@@ -0,0 +1,23 @@
+# Pending test cases
+
+Register of acceptance criteria with **no** Test Case. A TC binds an AC
+only when an existing test genuinely asserts the AC's *outcome* - a
+test that merely exercises the same module does not count. An AC that
+cannot yet be honestly bound is registered here as a row, never stubbed
+as a TC.
+
+The register is empty. The assertion-level audit of all 76 ACs
+(w-2026-07-28-005 step 4) opened it with 14 rows; 4 AC-drift rows were
+resolved by operator ruling (AC text revised to the deliberate design,
+then bound), 9 assertion gaps got their tests written and bound
+(w-2026-07-29-014 / w-2026-07-29-015), and the final row - AC-502-2,
+a genuine feature gap - was closed by porting the parallel-safe tier
+computation from the full RCF platform into the build queue and binding
+TC-014-independent-items-share-tier to it.
+
+Status: **76 bound / 0 pending** of 76 ACs. `rcf coverage --strict`
+exits 0, and CI runs `rcf validate` and `rcf coverage --strict` as
+required steps, so a new uncovered AC or a non-resolving testPointer
+fails the build. A future genuine gap gets a row here (AC id, US, kind,
+what a sufficient test must assert, nearest existing test) until its
+test lands.

package/rcf/test-suites/ts-001.json

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:17.054Z",
+  "updatedAt": "2026-07-29T12:57:17.346Z",
+  "purpose": "Verify initialisation creates the canonical rcf structure, refuses to overwrite an existing project, and yields a tree walkable from the manifest roots.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-101-1",
+    "AC-101-2",
+    "AC-101-3"
+  ],
+  "id": "TS-001",
+  "usId": "US-101",
+  "title": "Project initialisation on disk",
+  "testCases": [
+    {
+      "id": "TC-001-init-clean-tree-roots",
+      "acId": "AC-101-1",
+      "description": "initProject followed by walkTree yields a clean tree whose manifest declares the PRD, TAD and BS roots",
+      "status": "pending",
+      "testPointer": "test/core/store/init.test.js::initProject + walkTree yields a clean tree (AC-101-1, AC-101-3)"
+    },
+    {
+      "id": "TC-001-init-refuses-overwrite",
+      "acId": "AC-101-2",
+      "description": "a second initProject on the same directory refuses with a usage error reporting the project already exists",
+      "status": "pending",
+      "testPointer": "test/core/store/init.test.js::initProject refuses to overwrite an existing manifest (AC-101-2)"
+    },
+    {
+      "id": "TC-001-children-discoverable-from-roots",
+      "acId": "AC-101-3",
+      "description": "every scaffolded child document is resolved by walking parent id lists from the manifest roots",
+      "status": "pending",
+      "testPointer": "test/core/store/init.test.js::initProject + walkTree yields a clean tree (AC-101-1, AC-101-3)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-002.json

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:17.443Z",
+  "updatedAt": "2026-07-29T12:57:17.739Z",
+  "purpose": "Verify loading reads the manifest roots, resolves every child by walking parent id lists, and reports missing, unparseable or broken documents as structured errors without crashing.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-102-1",
+    "AC-102-2",
+    "AC-102-3"
+  ],
+  "id": "TS-002",
+  "usId": "US-102",
+  "title": "Tree load and walk",
+  "testCases": [
+    {
+      "id": "TC-002-walk-loads-every-document",
+      "acId": "AC-102-1",
+      "description": "walkTree reads the manifest roots and loads every document on the live tree with zero errors",
+      "status": "pending",
+      "testPointer": "test/store/walker.test.js::walkTree on the live tree loads every document and returns zero errors"
+    },
+    {
+      "id": "TC-002-parse-failure-structured-no-crash",
+      "acId": "AC-102-2",
+      "description": "an unparseable document surfaces as a structured parseFailure naming the document id while the walk continues",
+      "status": "pending",
+      "testPointer": "test/store/walker.test.js::walkTree reports parseFailure without crashing the walk"
+    },
+    {
+      "id": "TC-002-broken-reference-reported",
+      "acId": "AC-102-3",
+      "description": "a broken prdId reference surfaces as a brokenReference error naming document, field and file",
+      "status": "pending",
+      "testPointer": "test/store/walker.test.js::walkTree reports a REQ with a broken prdId as brokenReference (D7 step 5, D8)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-003.json

@@ -0,0 +1,43 @@
+{
+  "createdAt": "2026-07-29T12:57:17.843Z",
+  "updatedAt": "2026-07-29T13:35:26.351Z",
+  "purpose": "Verify the tree renders to mermaid diagram source. AC-201-1 and AC-201-2 are pending: no existing test asserts PRD plus architecture documents in the diagram, nor visible broken-link marking (see test-suites/PENDING.md).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-201-3"
+  ],
+  "id": "TS-003",
+  "usId": "US-201",
+  "title": "Mermaid diagram generation",
+  "testCases": [
+    {
+      "id": "TC-003-diagram-emitted-as-source",
+      "acId": "AC-201-3",
+      "description": "the requirement subdiagram is emitted as mermaid flowchart source",
+      "status": "pending",
+      "testPointer": "test/view/mermaid-diagram.test.js::requirementSubdiagram uses flowchart LR orientation"
+    },
+    {
+      "id": "TC-003-per-req-subdiagram-chain-edges",
+      "acId": "AC-201-1",
+      "description": "each REQ subdiagram carries chain edges REQ to US to AC plus FBS delivery back-links, scoped to that requirement only",
+      "status": "pending",
+      "testPointer": "test/view/mermaid-diagram.test.js::requirementSubdiagram carries chain edges and delivers back-links"
+    },
+    {
+      "id": "TC-003-one-subdiagram-per-req",
+      "acId": "AC-201-1",
+      "description": "every requirement is rendered as its own subdiagram (per-REQ design)",
+      "status": "pending",
+      "testPointer": "test/view/mermaid-diagram.test.js::allRequirementSubdiagrams returns one diagram per REQ"
+    },
+    {
+      "id": "TC-003-broken-node-marked-visibly",
+      "acId": "AC-201-2",
+      "description": "a broken node still renders in the subdiagram and carries the broken class rather than being omitted",
+      "status": "pending",
+      "testPointer": "test/view/mermaid-diagram.test.js::requirementSubdiagram marks a broken node visibly rather than omitting it (AC-201-2)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-004.json

@@ -0,0 +1,44 @@
+{
+  "createdAt": "2026-07-29T12:57:18.038Z",
+  "updatedAt": "2026-07-29T13:35:14.688Z",
+  "purpose": "Verify documents render as readable curated fields with working inter-document links. AC-202-1 is pending: its static-files-no-server clause predates the Phase 3.8 server-only view (see test-suites/PENDING.md).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-202-2",
+    "AC-202-3"
+  ],
+  "id": "TS-004",
+  "usId": "US-202",
+  "title": "Browsable page rendering",
+  "testCases": [
+    {
+      "id": "TC-004-curated-fields-not-raw-json",
+      "acId": "AC-202-2",
+      "description": "renderPage renders curated key fields as readable text rather than raw JSON",
+      "status": "pending",
+      "testPointer": "test/view/html-page.test.js::renderPage renders curated key fields, not raw JSON (AC-202-2)"
+    },
+    {
+      "id": "TC-004-doc-links-navigate-to-sections",
+      "acId": "AC-202-3",
+      "description": "document links render as anchors targeting the raw doc id section",
+      "status": "pending",
+      "testPointer": "test/view/doc-renderers/helpers.test.js::docLink renders an anchor to the raw id"
+    },
+    {
+      "id": "TC-004-valid-html5-page",
+      "acId": "AC-202-1",
+      "description": "the rendered page is a valid HTML5 document",
+      "status": "pending",
+      "testPointer": "test/view/html-page.test.js::renderPage emits a valid HTML5 document (AC-202-1)"
+    },
+    {
+      "id": "TC-004-served-live-no-files-written",
+      "acId": "AC-202-1",
+      "description": "the view serves from a local server process and never writes files to disk",
+      "status": "pending",
+      "testPointer": "test/view/cli.test.js::rcf view never writes any files to disk (regression against static mode)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-005.json

@@ -0,0 +1,30 @@
+{
+  "createdAt": "2026-07-29T12:57:18.331Z",
+  "updatedAt": "2026-07-29T12:57:18.527Z",
+  "purpose": "Verify the view is produced fresh from the on-disk tree on every regeneration and carries no cached prior state.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-203-1",
+    "AC-203-2"
+  ],
+  "id": "TS-005",
+  "usId": "US-203",
+  "title": "View freshness",
+  "testCases": [
+    {
+      "id": "TC-005-edit-present-after-regenerate",
+      "acId": "AC-203-1",
+      "description": "an on-disk edit is present in the regenerated view output",
+      "status": "pending",
+      "testPointer": "test/view/integration.test.js::renderModelToPage picks up manifest changes between calls (re-walk is fresh)"
+    },
+    {
+      "id": "TC-005-no-cached-prior-state",
+      "acId": "AC-203-2",
+      "description": "regeneration re-walks the tree fresh and drops all prior-state content",
+      "status": "pending",
+      "testPointer": "test/view/integration.test.js::renderModelToPage picks up manifest changes between calls (re-walk is fresh)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-006.json

@@ -0,0 +1,36 @@
+{
+  "createdAt": "2026-07-29T12:57:18.625Z",
+  "updatedAt": "2026-07-29T13:35:26.548Z",
+  "purpose": "Verify reading behaviour for unknown ids. AC-301-1 and AC-301-3 are pending: the read verb does not report per-document validity today (see test-suites/PENDING.md).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-301-2"
+  ],
+  "id": "TS-006",
+  "usId": "US-301",
+  "title": "Read verb",
+  "testCases": [
+    {
+      "id": "TC-006-read-unknown-id-not-found",
+      "acId": "AC-301-2",
+      "description": "reading an unknown id exits 2 with a structured not-found usage error",
+      "status": "pending",
+      "testPointer": "test/cli/read.test.js::rcf read UNKNOWN-999 exits 2 (usage, unknown id)"
+    },
+    {
+      "id": "TC-006-read-reports-valid",
+      "acId": "AC-301-1",
+      "description": "read returns the body on stdout and reports the document valid against its schema on stderr",
+      "status": "pending",
+      "testPointer": "test/cli/read.test.js::rcf read REQ-001 returns the body and reports it valid against its schema (AC-301-1)"
+    },
+    {
+      "id": "TC-006-read-invalid-content-plus-errors",
+      "acId": "AC-301-3",
+      "description": "read on an invalid-but-present document returns the content together with the validation errors",
+      "status": "pending",
+      "testPointer": "test/cli/read.test.js::rcf read on an invalid-but-present document returns the content together with the validation errors (AC-301-3)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-007.json

@@ -0,0 +1,43 @@
+{
+  "createdAt": "2026-07-29T12:57:18.823Z",
+  "updatedAt": "2026-07-29T13:35:48.640Z",
+  "purpose": "Verify create refuses conflicting ids. AC-302-1 (PRD requirementIds list, removed by D2) and AC-302-3 (create-invalid-body path untested) are pending (see test-suites/PENDING.md).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-302-2"
+  ],
+  "id": "TS-007",
+  "usId": "US-302",
+  "title": "Create verb safety",
+  "testCases": [
+    {
+      "id": "TC-007-create-id-collision-refused",
+      "acId": "AC-302-2",
+      "description": "create with a conflicting id returns a clear conflict error and writes nothing",
+      "status": "pending",
+      "testPointer": "test/core/store/writer.test.js::createDocument refuses on id collision (exit 2) and writes nothing (AC-302-2)"
+    },
+    {
+      "id": "TC-007-create-writes-validating-child",
+      "acId": "AC-302-1",
+      "description": "create writes the requirement file carrying its prdId parent edge and the reloaded tree validates clean",
+      "status": "pending",
+      "testPointer": "test/core/store/writer.test.js::createDocument req writes a schema-valid child file"
+    },
+    {
+      "id": "TC-007-create-leaves-prd-untouched",
+      "acId": "AC-302-1",
+      "description": "create leaves the parent PRD file byte-identical (child-owned parent edges)",
+      "status": "pending",
+      "testPointer": "test/core/store/writer.test.js::createDocument does NOT mutate the parent PRD file (Phase 3.7 §D2)"
+    },
+    {
+      "id": "TC-007-create-invalid-writes-nothing",
+      "acId": "AC-302-3",
+      "description": "create with a schema-invalid body returns the validation error and writes no file",
+      "status": "pending",
+      "testPointer": "test/core/store/writer.test.js::createDocument with a schema-invalid body writes nothing and returns the validation error (AC-302-3)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-008.json

@@ -0,0 +1,37 @@
+{
+  "createdAt": "2026-07-29T12:57:19.018Z",
+  "updatedAt": "2026-07-29T13:35:26.749Z",
+  "purpose": "Verify valid updates persist with updatedAt advanced and invalidating updates are refused. AC-303-3 (update on unknown id) is pending (see test-suites/PENDING.md).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-303-1",
+    "AC-303-2"
+  ],
+  "id": "TS-008",
+  "usId": "US-303",
+  "title": "Update verb safety",
+  "testCases": [
+    {
+      "id": "TC-008-valid-update-persists-updatedat",
+      "acId": "AC-303-1",
+      "description": "a valid update persists the change and advances updatedAt on disk",
+      "status": "pending",
+      "testPointer": "test/cli/update.test.js::rcf update REQ-001 --set title=X changes the title and bumps updatedAt"
+    },
+    {
+      "id": "TC-008-invalid-update-refused",
+      "acId": "AC-303-2",
+      "description": "a schema-invalidating update on a valid tree is refused with the validation error",
+      "status": "pending",
+      "testPointer": "test/core/store/writer-postwrite.test.js::(e) normal-path refusal intact: invalid doc into a VALID tree still refuses"
+    },
+    {
+      "id": "TC-008-update-unknown-id-not-found",
+      "acId": "AC-303-3",
+      "description": "update on a nonexistent id returns a structured not-found error naming the id and writes nothing",
+      "status": "pending",
+      "testPointer": "test/cli/update.test.js::rcf update REQ-999 returns a structured not-found error and writes nothing (AC-303-3)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-009.json

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:19.311Z",
+  "updatedAt": "2026-07-29T12:57:19.605Z",
+  "purpose": "Verify delete refuses while dependants exist, cascades cleanly, and removes unreferenced leaves leaving the tree valid.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-304-1",
+    "AC-304-2",
+    "AC-304-3"
+  ],
+  "id": "TS-009",
+  "usId": "US-304",
+  "title": "Delete with reference safety",
+  "testCases": [
+    {
+      "id": "TC-009-delete-refused-with-dependents",
+      "acId": "AC-304-1",
+      "description": "delete without cascade refuses with exit 4 naming dependents",
+      "status": "pending",
+      "testPointer": "test/cli/delete.test.js::rcf delete REQ-001 without --cascade refuses with exit 4"
+    },
+    {
+      "id": "TC-009-cascade-removes-subtree",
+      "acId": "AC-304-2",
+      "description": "cascade delete removes the sub-tree files leaving the tree valid",
+      "status": "pending",
+      "testPointer": "test/core/store/writer.test.js::deleteDocument REQ --cascade removes REQ + descendant USes + TSs"
+    },
+    {
+      "id": "TC-009-leaf-delete-removes-file",
+      "acId": "AC-304-3",
+      "description": "deleting an unreferenced leaf removes the file with exit 0 on a still-valid tree",
+      "status": "pending",
+      "testPointer": "test/cli/delete.test.js::rcf delete leaf ADR-001 removes the file (exit 0)"
+    }
+  ],
+  "status": "draft"
+}