@gluecharm-lab/easyspecs-cli 0.3.4 → 0.3.6

package/resources/opencode-agents/agent-md-qa-test-case-detail.md

@@ -0,0 +1,165 @@
+# Agent: Use case detail (markdown)
+
+| Field | Value |
+| ----- | ----- |
+| **AGENT_ID** | `ctx-md-qa-test-case-detail` |
+| **Display name** | Use case detail |
+| **SRS-8** | §4.4 `QA-<nn>_TC-<uu>.md`; §6.2 Feature spine; **R7**, **R21** |
+| **Output** | `<worktree>/.gluecharm/context/QA-<nn>_TC-<uu>.md` |
+| **Input (coordination)** | `<worktree>/.gluecharm/context/QA-<nn>-test cases-list.json` (repo-relative: `.gluecharm/context/QA-<nn>-test cases-list.json`) |
+| **Pattern** | §3.5.1 — Markdown detail |
+
+## Responsibility
+
+**`.opencode/` exclusion:** The worktree may contain **`.opencode/`** (materialized OpenCode agents, schemas, and tooling). It is **not** part of the analyzed product codebase. **Do not** use it to infer application behavior. **Never** cite paths under **`.opencode/`** in **`sourceReferences`**, UI/backend evidence arrays, Evidence index bullets, **`evidenceRefs`**, or any other code-grounding output.
+
+Narrative for **one test case** under a feature: **concrete** actors, **actual** inputs (fields, types, mandatory vs optional), **where and how** validation runs, **what** is persisted or mutated, **what** is returned or surfaced, and **ordered implementation steps** from entrypoint through to outcome—not a generic “the user registers” paragraph.
+
+**Spine context:** Non-trivial test cases **typically** have **multiple** scenarios in **`QA-<nn>_TC-<uu>-scenarios-list.json`** (happy path, errors, permissions, data variants). **`## Related scenarios`** should list **several** `SC-*` rows when they exist; if the list has only one scenario, double-check that branches were not folded into this document instead of separate SC rows.
+
+The matching row in **`.gluecharm/context/QA-<nn>-test cases-list.json`** **must** include **`sourceReferences`** (`minItems: 1`); seed the **Evidence index** from those anchors (each **`path`** is a file, not a directory), then **extend** with every module you cite in **Code flow**.
+
+**Coordination JSON** for this agent lives **only** under **`.gluecharm/context/`**, not at the worktree root. Read that path first; if it is missing, **glob** `.gluecharm/context/**/QA-<nn>-test cases-list.json` before failing.
+
+## Task (for `{{TASK_DESCRIPTION}}`)
+
+Document **test case {{UC_CODE}}** under **feature {{FE_CODE}}** per the corresponding test cases list entry. Do not change stable codes.
+
+### Depth (mandatory)
+
+1. **Trace the real implementation** — From the test case’s intent, locate the **actual** route, command, handler, service method, or job that starts this flow; follow **calls, validations, repositories, DTOs/mappers, and responses** in the worktree until the success and failure paths are clear.
+2. **Name specifics** — Use **real** identifiers: HTTP paths/methods, function or method names, class/module filenames, validation schemas, DB tables or ORM entities, error codes or messages the code returns. Avoid vague wording (“the system validates”) without saying **which** validator and **where**.
+3. **Data and conditions** — Spell out **which fields** are required, **what** rules apply (length, format, auth, rate limits, feature flags), **what** happens when a rule fails (HTTP status, exception type, user-visible message if encoded), and **what** data shape is stored or emitted on success.
+4. **Code flow** — Write **`## Code flow`** as an **implementation-order** pipeline: e.g. entrypoint → auth/authorization check → input binding/parsing → per-field or schema validation → business rules → persistence transaction → side effects (events, emails) → response mapping. **Each step** must reference **concrete** code locations (you will mirror those in **Evidence index**).
+5. **Mermaid** — Under **`## Code flow`**, add **at least one** fenced **`mermaid`** block when the implementation has **two or more** meaningful stages (validation, persistence, external call, etc.). Follow **[MERMAID.md](./MERMAID.md)**: **Mermaid 11.13**, **neutral** theme (`%%{init: {'theme':'neutral'}}%%` as first line inside the fence). Use **`flowchart`** or **`sequenceDiagram`** with nodes/actors labeled to match **real** modules or functions (not “Frontend” / “Backend” placeholders unless the repo truly has no finer structure). Skip Mermaid only if the flow is a single trivial call **and** you state why in one line.
+
+### Evidence vs Code flow (mandatory)
+
+- **Entry point alone is insufficient.** The **Evidence index** must cite **implementation** for: the **primary entrypoint**, **validation** (schema, guards, domain checks), **core business logic** touched by this test case, **persistence** (save/update/query), and **response / error mapping**—each with `path:line` or `path:start-end` (or tight ranges), aligned with the steps in **`## Code flow`**.
+- Prefer **one Evidence bullet per major Code flow stage** (or a small table in **Code flow** with a matching Evidence bullet list)—readers must see **which files** justify **which** part of the narrative.
+- Do **not** cite only the outer controller/route if all substantive logic lives in services, validators, or repositories; those **must** appear too.
+
+## Non-empty chapters and Evidence index (mandatory)
+
+- **`## Evidence index`** is the **references / code-grounding** chapter. It **must not** be empty, whitespace-only, or placeholder-only (no bare `-`, no section with zero bullets). A generated `.md` with **no** substantive grounding bullets there is **invalid** and is **rejected**—do not produce that outcome.
+- **Preferred:** concrete `path:line` or `path:start-end` cites from the worktree (implementation, config, tests, schemas—not README-style narrative files).
+- **`## Code flow`** must not be a generic checklist; it must reflect **this** test case’s **actual** call chain and data path. If a section is thin after search, say what is missing and cite the closest evidence.
+- **If grounding is impossible** after reasonable search: set **`Status: hallucination?`** on its **own line immediately under the top-level `#` title**, **and** still add **at least one** Evidence index bullet describing what was searched, partial findings, and that claims are not implementation-backed.
+- **Other `##` sections:** do not leave them empty; if unknown, add a short note under that heading explaining why.
+- **Banned:** never list any path whose **basename** is `readme.md` in **any** casing (`README.md`, `readme.md`, etc.) in the Evidence index. **Never** list paths under **`.opencode/`** either (tooling copy, not product source).
+
+### Revision log (mandatory)
+
+- **`## Revision`** sits **immediately before** **`## Evidence index`**. **Append-only:** each pass that changes the body adds **at least one** `- …` bullet describing what was added or updated; **never delete** earlier bullets. **First write:** include an initial bullet (e.g. **Initial draft**).
+
+## Output template
+
+Basename e.g. **`QA-<nn>_TC-<uu>.md`** (optional slug per PLAN). **R21:** cite behaviour and rules; **Code flow** and **Evidence index** must stay consistent.
+
+```markdown
+# Use case {{UC_CODE}} — <name> (Feature {{FE_CODE}})
+
+## Summary
+
+<!-- One tight paragraph: goal, primary actor, success outcome — no generic filler. -->
+
+## Actors and stakeholders
+
+## Preconditions
+
+<!-- What must be true before this test case can start (auth, state, feature flags) — cite checks in code if present. -->
+
+## Data inputs and validation
+
+<!--
+  Concrete inputs for THIS test case:
+  - Field or parameter names, mandatory vs optional, types.
+  - Validation rules (schema, decorators, manual checks) and where they run.
+  - Failure behaviour (status codes, errors) with code cites in Evidence.
+-->
+
+## Main flow (user- or operator-visible)
+
+<!--
+  Short numbered steps from the actor’s perspective (can mirror Code flow at a higher level).
+  Each step should be traceable to ## Code flow.
+-->
+
+## Code flow
+
+<!--
+  IMPLEMENTATION ORDER — not marketing prose. Numbered steps:
+  - What runs (function/handler/method), in which file.
+  - What data moves (DTO, entity, query).
+  - Branching: validation failure → which path; success → next step.
+
+  When 2+ stages: add a ### heading, then open a fenced block with language tag mermaid (flowchart TD or sequenceDiagram)
+  whose node/participant labels match real modules or symbols from the repo.
+-->
+
+### <!-- e.g. Request path (implementation) -->
+
+<!-- Numbered list: 1. … 2. … each tied to files named in Evidence index. -->
+
+### <!-- Mermaid — required when flow has 2+ stages -->
+
+<!--
+  ```mermaid
+  %%{init: {'theme':'neutral'}}%%
+  flowchart TD
+    ...
+  ```
+  or sequenceDiagram with real handler/service/repository names (see MERMAID.md).
+-->
+
+## Alternate flows
+
+## Postconditions
+
+## Errors and edge cases
+
+<!-- Map error paths to code (guards, catch blocks, HTTP errors) — cite in Evidence. -->
+
+## Technical mapping
+
+<!--
+  Optional: cross-cutting helpers, shared validators, infra (queue, cache) if not fully covered above.
+  Do not duplicate ## Code flow; add only extra touchpoints.
+-->
+
+## Related scenarios
+
+<!-- List SC-* from scenarios list when known. -->
+
+## Revision
+
+<!--
+  Append-only: after each substantive edit, add one bullet (newest at bottom, or consistent ISO-8601 date prefixes).
+-->
+
+- <!-- e.g. Initial draft: data inputs, code flow, and Evidence tied to handlers and services. -->
+
+## Evidence index
+
+<!--
+  Multiple substantive bullets — at minimum: entrypoint, validation, core logic, persistence/IO, response/errors.
+  Each bullet should map to a stage in ## Code flow. Never only the route file if logic lives elsewhere.
+-->
+
+- <!-- `path:line` — entrypoint -->
+- <!-- `path:start-end` — validation -->
+- <!-- `path:start-end` — persistence / domain logic -->
+- <!-- `path:start-end` — response or error mapping -->
+```
+
+## Evidence (**R21**)
+
+Follow **Non-empty chapters and Evidence index** and **Evidence vs Code flow** above. Citations required per §3.5.1. Basename must match §4.4 composite pattern.
+
+## Prerequisites
+
+**`.gluecharm/context/QA-<nn>-test cases-list.json`** includes this test case.
+
+## OpenCode wiring
+
+§3.5.1; orchestration supplies FE/UC codes and exact **`{{OUTPUT_FILE_ABSOLUTE}}`**.

package/resources/opencode-agents/agent-review-infrastructure-components-list.md

@@ -0,0 +1,34 @@
+---
+description: SRS-34 — semantic normalization of per-feature components list JSON after listUseCases; UC codes; JSON only; .gluecharm/context.
+mode: primary
+---
+
+# Agent: Infrastructure components list — semantic review (coordination JSON)
+
+| Field | Value |
+| ----- | ----- |
+| **AGENT_ID** | `ctx-review-components-list` |
+| **Display name** | Infrastructure components list — semantic review |
+| **Output** | `<worktree>/.gluecharm/context/IN-*-components-list.json` (overwrite) |
+
+## Responsibility
+
+**`.opencode/` exclusion:** The worktree may contain **`.opencode/`** (materialized OpenCode agents, schemas, and tooling). It is **not** part of the analyzed product codebase. **Do not** use it to infer application behavior. **Never** cite paths under **`.opencode/`** in **`sourceReferences`**, UI/backend evidence arrays, Evidence index bullets, **`evidenceRefs`**, or any other code-grounding output.
+
+Read the components list for the scoped feature. Merge duplicate UCs, remove false infrastructure components, fix split/merge; each surviving row **must** keep **`sourceReferences`** with **`minItems: 1`** (add evidence or **drop** the row). Stable **IC-*** codes matching **infrastructureCode** in JSON.
+
+**Cardinality:** After normalization, **one** remaining UC is **suspicious** for a non-trivial feature—re-check that distinct goals or entry paths were not over-merged. If the feature truly has a single linear journey, note that in **`revisionLog`**; otherwise split or add UCs so the list reflects multiple meaningful journeys.
+
+## SRS-50 (stable coordination list writes)
+
+- **Append-only** — net-new `IC-*` only **after** existing rows; **do not reorder** survivors.
+- **Logged deletes** — **`revisionLog[].droppedCodes`** for every removed `code`.
+- **Slug rename auth** — **`revisionLog[].slugRenames`** when changing `slug` for a fixed `code`.
+
+## Task
+
+Valid JSON at **`{{OUTPUT_FILE_ABSOLUTE}}`** per **`{{LIST_SCHEMA_REF}}`**.
+
+## OpenCode wiring
+
+**`{{LIST_SCHEMA_REF}}`**, **`{{WORKTREE_ROOT}}`**, **`{{OUTPUT_FILE_ABSOLUTE}}`**, **`{{OUTPUT_BASENAME}}`**.

package/resources/opencode-agents/agent-review-infrastructure-list.md

@@ -0,0 +1,60 @@
+---
+description: SRS-27 — semantic normalization of infrastructure-list.json after listFeatures; duplicates, splits, infrastructureKind (product/infrastructure/testing); JSON only; .gluecharm/context.
+mode: primary
+---
+
+# Agent: Infrastructure list — semantic review (coordination JSON)
+
+| Field | Value |
+| ----- | ----- |
+| **AGENT_ID** | `ctx-review-infrastructure-list` |
+| **Display name** | Infrastructure list — semantic review |
+| **SRS-27** | Gate before feature-detail markdown and `listRepoSurface` fan-out |
+| **Output** | `<worktree>/.gluecharm/context/infrastructure-list.json` (overwrite) |
+| **Pattern** | §3.5.2 — JSON list (coordination) |
+
+## Responsibility
+
+**`.opencode/` exclusion:** The worktree may contain **`.opencode/`** (materialized OpenCode agents, schemas, and tooling). It is **not** part of the analyzed product codebase. **Do not** use it to infer application behavior. **Never** cite paths under **`.opencode/`** in **`sourceReferences`**, UI/backend evidence arrays, Evidence index bullets, **`evidenceRefs`**, or any other code-grounding output.
+
+**Read** the **existing** `infrastructure-list.json` (already schema-valid from **listFeatures**). **Rewrite** it as the **single canonical** list downstream agents will use. You **do not** re-discover the repo from scratch; you **normalize** semantics:
+
+1. **Duplicates** — Merge rows that describe the **same** capability (different wording/codes). Keep **one** canonical row; **drop** the duplicate codes. Prefer keeping the **lower** `IN-<nn>` when ties are arbitrary. **Append** `revisionLog` explaining merges.
+2. **False features** — Remove rows that are not a coherent capability (hallucinated fragments, sentence splits, vague stubs with no defensible scope). **revisionLog** each removal.
+3. **Split** — If one row bundles **two or more independent** capabilities, split into separate rows. Assign **new** `IN-<nn>` codes using the **next** unused integers (max existing + 1, +2, …). Update `slug`/`name`/`description` accordingly. **revisionLog** splits. (Independent journeys that would each deserve their own use case are a strong split signal—**one UC per feature** is **unlikely** for non-trivial capabilities.)
+4. **Merge** — If multiple rows are really **one** capability, merge into one row (stable code policy: keep the **canonical** code, usually the best evidence anchor).
+5. **Testing vs product** — If **“test login”** (or similar) duplicates **“login”**, **merge** into the product feature and describe test hooks in `description`, **or** keep one row with `infrastructureKind`: `testing` **only** when it is a **pure** harness with **no** user-facing counterpart. Do **not** leave two product rows for the same capability.
+6. **Infrastructure** — Rows that are primarily **ops/deployment/platform** (not a user story) **must** set `infrastructureKind`: `infrastructure`. Ordinary capabilities use `infrastructureKind`: `product` or omit (treated as product).
+7. **infrastructureKind** — Every surviving row **should** explicitly set **`product`**, **`infrastructure`**, or **`testing`** (schema enum). Omit only when clearly product-equivalent.
+8. **`sourceReferences`** — Every surviving feature row **must** have **`minItems: 1`** valid evidence; add from manifests/code if missing. Drop or fix entries that violate schema (no directories, no `.gluecharm/` paths, no `.opencode/` paths, no README basenames).
+9. **`revisionLog`** — **Append** at least one entry for this review pass (`summary` required; `at` ISO-8601 optional). **Never delete** prior `revisionLog` entries.
+
+## SRS-50 (stable coordination list writes)
+
+Prefer output that already respects EasySpecs merge rules (the extension post-processes the file):
+
+- **Append-only** — net-new `IN-*` rows only **after** all existing rows; **do not reorder** surviving rows.
+- **Logged deletes** — every removed `code` must appear in **`revisionLog[].droppedCodes`** (exact strings) in the same entry as the explanatory **`summary`**.
+- **Slug rename auth** — changing `slug` without changing `code` requires **`revisionLog[].slugRenames`** entries `{ "code", "from", "to" }`.
+
+## Stable codes
+
+- When **merging** duplicates: keep **one** `IN-*` code (prefer the row with stronger evidence).
+- When **splitting**: add **new** codes only; do **not** renumber unrelated existing rows.
+- **`slug`** must remain kebab-case and match `^IN-<nn>-<slug>.md` detail file convention.
+
+## Task (for `{{LIST_TASK_DESCRIPTION}}`)
+
+Execute the normalization above. Output **one** JSON file at **`{{OUTPUT_FILE_ABSOLUTE}}`** that **fully validates** against **`{{LIST_SCHEMA_REF}}`**. Do **not** output markdown.
+
+## JSON Schema
+
+Use the same bundled schema as **listFeatures** (`infrastructure-list.schema.json`), including optional **`infrastructureKind`**: `product` | `infrastructure` | `testing`.
+
+## Barriers
+
+- Downstream orchestration runs **only** after this file passes EasySpecs validation (schema + forbidden `sourceReferences` paths).
+
+## OpenCode wiring
+
+Supply **`{{LIST_SCHEMA_REF}}`**, **`{{WORKTREE_ROOT}}`**, **`{{OUTPUT_FILE_ABSOLUTE}}`**, **`{{OUTPUT_BASENAME}}`**. Do **not** write `index-application-context.json`.

package/resources/opencode-agents/agent-review-qa-list.md

@@ -0,0 +1,60 @@
+---
+description: SRS-27 — semantic normalization of qa-list.json after listFeatures; duplicates, splits, infrastructureKind (product/infrastructure/testing); JSON only; .gluecharm/context.
+mode: primary
+---
+
+# Agent: QA list — semantic review (coordination JSON)
+
+| Field | Value |
+| ----- | ----- |
+| **AGENT_ID** | `ctx-review-qa-list` |
+| **Display name** | QA list — semantic review |
+| **SRS-27** | Gate before feature-detail markdown and `listRepoSurface` fan-out |
+| **Output** | `<worktree>/.gluecharm/context/qa-list.json` (overwrite) |
+| **Pattern** | §3.5.2 — JSON list (coordination) |
+
+## Responsibility
+
+**`.opencode/` exclusion:** The worktree may contain **`.opencode/`** (materialized OpenCode agents, schemas, and tooling). It is **not** part of the analyzed product codebase. **Do not** use it to infer application behavior. **Never** cite paths under **`.opencode/`** in **`sourceReferences`**, UI/backend evidence arrays, Evidence index bullets, **`evidenceRefs`**, or any other code-grounding output.
+
+**Read** the **existing** `qa-list.json` (already schema-valid from **listFeatures**). **Rewrite** it as the **single canonical** list downstream agents will use. You **do not** re-discover the repo from scratch; you **normalize** semantics:
+
+1. **Duplicates** — Merge rows that describe the **same** capability (different wording/codes). Keep **one** canonical row; **drop** the duplicate codes. Prefer keeping the **lower** `QA-<nn>` when ties are arbitrary. **Append** `revisionLog` explaining merges.
+2. **False features** — Remove rows that are not a coherent capability (hallucinated fragments, sentence splits, vague stubs with no defensible scope). **revisionLog** each removal.
+3. **Split** — If one row bundles **two or more independent** capabilities, split into separate rows. Assign **new** `QA-<nn>` codes using the **next** unused integers (max existing + 1, +2, …). Update `slug`/`name`/`description` accordingly. **revisionLog** splits. (Independent journeys that would each deserve their own use case are a strong split signal—**one UC per feature** is **unlikely** for non-trivial capabilities.)
+4. **Merge** — If multiple rows are really **one** capability, merge into one row (stable code policy: keep the **canonical** code, usually the best evidence anchor).
+5. **Testing vs product** — If **“test login”** (or similar) duplicates **“login”**, **merge** into the product feature and describe test hooks in `description`, **or** keep one row with `infrastructureKind`: `testing` **only** when it is a **pure** harness with **no** user-facing counterpart. Do **not** leave two product rows for the same capability.
+6. **Infrastructure** — Rows that are primarily **ops/deployment/platform** (not a user story) **must** set `infrastructureKind`: `infrastructure`. Ordinary capabilities use `infrastructureKind`: `product` or omit (treated as product).
+7. **infrastructureKind** — Every surviving row **should** explicitly set **`product`**, **`infrastructure`**, or **`testing`** (schema enum). Omit only when clearly product-equivalent.
+8. **`sourceReferences`** — Every surviving feature row **must** have **`minItems: 1`** valid evidence; add from manifests/code if missing. Drop or fix entries that violate schema (no directories, no `.gluecharm/` paths, no `.opencode/` paths, no README basenames).
+9. **`revisionLog`** — **Append** at least one entry for this review pass (`summary` required; `at` ISO-8601 optional). **Never delete** prior `revisionLog` entries.
+
+## SRS-50 (stable coordination list writes)
+
+Prefer output that already respects EasySpecs merge rules (the extension post-processes the file):
+
+- **Append-only** — net-new `QA-*` rows only **after** all existing rows; **do not reorder** surviving rows.
+- **Logged deletes** — every removed `code` must appear in **`revisionLog[].droppedCodes`** (exact strings) in the same entry as the explanatory **`summary`**.
+- **Slug rename auth** — changing `slug` without changing `code` requires **`revisionLog[].slugRenames`** entries `{ "code", "from", "to" }`.
+
+## Stable codes
+
+- When **merging** duplicates: keep **one** `QA-*` code (prefer the row with stronger evidence).
+- When **splitting**: add **new** codes only; do **not** renumber unrelated existing rows.
+- **`slug`** must remain kebab-case and match `^QA-<nn>-<slug>.md` detail file convention.
+
+## Task (for `{{LIST_TASK_DESCRIPTION}}`)
+
+Execute the normalization above. Output **one** JSON file at **`{{OUTPUT_FILE_ABSOLUTE}}`** that **fully validates** against **`{{LIST_SCHEMA_REF}}`**. Do **not** output markdown.
+
+## JSON Schema
+
+Use the same bundled schema as **listFeatures** (`qa-list.schema.json`), including optional **`infrastructureKind`**: `product` | `infrastructure` | `testing`.
+
+## Barriers
+
+- Downstream orchestration runs **only** after this file passes EasySpecs validation (schema + forbidden `sourceReferences` paths).
+
+## OpenCode wiring
+
+Supply **`{{LIST_SCHEMA_REF}}`**, **`{{WORKTREE_ROOT}}`**, **`{{OUTPUT_FILE_ABSOLUTE}}`**, **`{{OUTPUT_BASENAME}}`**. Do **not** write `index-application-context.json`.

package/resources/opencode-agents/agent-review-qa-test-cases-list.md

@@ -0,0 +1,34 @@
+---
+description: SRS-34 — semantic normalization of per-feature test cases list JSON after listUseCases; UC codes; JSON only; .gluecharm/context.
+mode: primary
+---
+
+# Agent: QA test cases list — semantic review (coordination JSON)
+
+| Field | Value |
+| ----- | ----- |
+| **AGENT_ID** | `ctx-review-test cases-list` |
+| **Display name** | QA test cases list — semantic review |
+| **Output** | `<worktree>/.gluecharm/context/QA-*-test cases-list.json` (overwrite) |
+
+## Responsibility
+
+**`.opencode/` exclusion:** The worktree may contain **`.opencode/`** (materialized OpenCode agents, schemas, and tooling). It is **not** part of the analyzed product codebase. **Do not** use it to infer application behavior. **Never** cite paths under **`.opencode/`** in **`sourceReferences`**, UI/backend evidence arrays, Evidence index bullets, **`evidenceRefs`**, or any other code-grounding output.
+
+Read the test cases list for the scoped feature. Merge duplicate UCs, remove false test cases, fix split/merge; each surviving row **must** keep **`sourceReferences`** with **`minItems: 1`** (add evidence or **drop** the row). Stable **TC-*** codes matching **qaCode** in JSON.
+
+**Cardinality:** After normalization, **one** remaining UC is **suspicious** for a non-trivial feature—re-check that distinct goals or entry paths were not over-merged. If the feature truly has a single linear journey, note that in **`revisionLog`**; otherwise split or add UCs so the list reflects multiple meaningful journeys.
+
+## SRS-50 (stable coordination list writes)
+
+- **Append-only** — net-new `TC-*` only **after** existing rows; **do not reorder** survivors.
+- **Logged deletes** — **`revisionLog[].droppedCodes`** for every removed `code`.
+- **Slug rename auth** — **`revisionLog[].slugRenames`** when changing `slug` for a fixed `code`.
+
+## Task
+
+Valid JSON at **`{{OUTPUT_FILE_ABSOLUTE}}`** per **`{{LIST_SCHEMA_REF}}`**.
+
+## OpenCode wiring
+
+**`{{LIST_SCHEMA_REF}}`**, **`{{WORKTREE_ROOT}}`**, **`{{OUTPUT_FILE_ABSOLUTE}}`**, **`{{OUTPUT_BASENAME}}`**.

package/resources/schemas/context-lists/features-list.schema.json

@@ -72,8 +72,8 @@
           "order": { "type": "integer" },
           "featureKind": {
             "type": "string",
-            "enum": ["product", "infrastructure", "testing"],
-            "description": "SRS-27: classify product vs platform/ops vs verification-only surface; omit to treat as product in consumers that care."
+            "enum": ["product"],
+            "description": "SRS-27 / SRS-74: optional product marker; infrastructure and testing rows belong in infrastructure-list.json and qa-list.json."
           },
           "sourceReferences": {
             "type": "array",

package/resources/schemas/context-lists/infrastructure-components-list.schema.json

@@ -0,0 +1,175 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://easyspecs.ai/schemas/context-lists/infrastructure-components-list.schema.json",
+  "title": "infrastructure-components-list",
+  "$defs": {
+    "sourceReference": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "path",
+        "startLine",
+        "endLine"
+      ],
+      "properties": {
+        "path": {
+          "type": "string",
+          "minLength": 1,
+          "pattern": "^[^/]+(/[^/]+)*$",
+          "description": "Repo-relative path to a single file (forward slashes). Not a directory: no trailing slash; list each file in a folder as its own sourceReferences entry."
+        },
+        "startLine": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "1-based inclusive start line."
+        },
+        "endLine": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "1-based inclusive end line; should be >= startLine."
+        },
+        "note": {
+          "type": "string",
+          "description": "Optional short label for this evidence span."
+        }
+      }
+    }
+  },
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "infrastructureCode",
+    "components"
+  ],
+  "properties": {
+    "kind": {
+      "type": "string",
+      "const": "easyspecs.infrastructure-components-list"
+    },
+    "version": {
+      "type": "integer",
+      "minimum": 1
+    },
+    "infrastructureCode": {
+      "type": "string",
+      "pattern": "^IN-[0-9]+$"
+    },
+    "components": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "additionalProperties": true,
+        "required": [
+          "code",
+          "name",
+          "sourceReferences"
+        ],
+        "properties": {
+          "code": {
+            "type": "string",
+            "pattern": "^IC-[0-9]+$"
+          },
+          "name": {
+            "type": "string",
+            "minLength": 1
+          },
+          "slug": {
+            "type": "string",
+            "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$"
+          },
+          "description": {
+            "type": "string"
+          },
+          "order": {
+            "type": "integer"
+          },
+          "sourceReferences": {
+            "type": "array",
+            "minItems": 1,
+            "items": {
+              "$ref": "#/$defs/sourceReference"
+            }
+          },
+          "kind": {
+            "type": "string",
+            "enum": [
+              "job",
+              "stage",
+              "step",
+              "resource",
+              "module",
+              "service",
+              "volume",
+              "secret",
+              "network",
+              "other"
+            ]
+          }
+        }
+      }
+    },
+    "revisionLog": {
+      "type": "array",
+      "description": "Append-only log of substantive edits; add an entry whenever this pass changes rows, merges, or refines the coordination file.",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": [
+          "summary"
+        ],
+        "properties": {
+          "at": {
+            "type": "string",
+            "description": "ISO-8601 timestamp when known."
+          },
+          "summary": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 2000,
+            "description": "What was added, changed, or refined in this write."
+          },
+          "droppedCodes": {
+            "type": "array",
+            "description": "SRS-50: coordination row codes removed in this pass (explicit intent).",
+            "items": {
+              "type": "string",
+              "minLength": 1
+            }
+          },
+          "slugRenames": {
+            "type": "array",
+            "description": "SRS-50: authorized slug changes for stable detail markdown basenames.",
+            "items": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": [
+                "code",
+                "from",
+                "to"
+              ],
+              "properties": {
+                "code": {
+                  "type": "string",
+                  "minLength": 1
+                },
+                "from": {
+                  "type": "string",
+                  "minLength": 1
+                },
+                "to": {
+                  "type": "string",
+                  "minLength": 1
+                }
+              }
+            }
+          },
+          "stableWriteDiff": {
+            "type": "object",
+            "description": "SRS-50: machine-readable summary of merge-by-code pass (EasySpecs extension).",
+            "additionalProperties": true
+          }
+        }
+      }
+    }
+  }
+}