Files
agentic-dev/docs/work/epics/ci-security-and-supply-chain/01-trace-schema-extensions/_story.md
Danijel Martinek 756e36c720 refactor(work): move epic folders into docs/work/epics/
The previous layout placed epic folders directly under docs/work/
alongside prds/ and _system/. Tightening: epics now live in their
own docs/work/epics/ subfolder, peer to prds/ and _system/. Same
shape as the existing prds/ bucket.

Final docs/work/ layout:
  README.md
  prds/<slug>.prd.md
  _system/_state.json
  epics/<slug>/_epic.md + <story-folder>/_story.md

Renames (git mv preserves history):
- docs/work/binder-wrap-helper/
    -> docs/work/epics/binder-wrap-helper/
- docs/work/library-evaluation-policy/
    -> docs/work/epics/library-evaluation-policy/
- docs/work/ci-security-and-supply-chain/
    -> docs/work/epics/ci-security-and-supply-chain/

Tooling updates:
- state-builder.mjs walks workRoot/epics/ directly; SKIP_FOLDERS
  obsoleted (no more sibling folders to filter out).
- dispatch.mjs's findNextTask, tickStoryBulletInEpic, and
  flipEpicDoneIfAllStoriesDone all join with "epics" segment.
- prd-ship.mjs's deriveShippingCommits walks workRoot/epics/ and
  git-logs docs/work/epics/<epic>/.
- decomposer.prompt.md emits epics under docs/work/epics/<epic-id>/.
- handoff + grill-with-docs glossary references updated.
- Glossary entry for Epic updated.

Reserved future shape: when a task-tracker integration (ClickUp,
Linear) ships, the epics/ subfolder hosts <task-id>-<slug>/
folders. Today it just hosts bare slugs.
2026-05-14 21:21:51 +02:00

3.1 KiB

id, epic, title, type, status, feature, depends-on, blocks, created, updated
id epic title type status feature depends-on blocks created updated
01-trace-schema-extensions ci-security-and-supply-chain Trace schema extensions (socketRisk + lastRevalidated) technical-story done scripts
02-socket-integration
04-major-bump-reevaluation
05-trace-revalidation-workflow
2026-05-14T18:59:12+02:00 2026-05-14T19:21:52.308Z

Goal

Extend scripts/library-decisions/schema.mjs with two new fields — socketRisk (the 9th filter result) and lastRevalidated (ISO-date or null) — and update docs/library-decisions/_template.md to reflect the expanded schema.

Why

Every downstream enforcement layer (the evaluate-library skill's 9th filter, the check.mjs major-bump mode, the revalidate.mjs weekly cron) depends on these two fields being present and validated at the schema layer first. Landing them here in one green commit before any consumer touches them prevents schema-drift between layers.

External dependency: library-evaluation epic story 01 (trace schema foundation) must be complete before this story — scripts/library-decisions/schema.mjs and docs/library-decisions/_template.md must exist. That epic is marked done.

Done when

  • scripts/library-decisions/schema.mjs exports an updated Zod schema where filter-results includes socketRisk: z.union([z.literal("clean"), z.literal("flagged"), z.string()]) and the trace frontmatter includes lastRevalidated: z.string().nullable() (ISO date or null).
  • docs/library-decisions/_template.md mirrors both new fields with inline documentation of their allowed values.
  • schema.test.mjs covers: socketRisk round-trips for all three variants (clean, flagged, arbitrary string); lastRevalidated accepts ISO date strings and null; a trace missing socketRisk in filter-results fails validation; lastRevalidated: null is valid (default for fresh adoptions).
  • pnpm typecheck && pnpm lint && pnpm test && pnpm conformance && pnpm fallow:audit && pnpm coverage:diff all pass.

In scope

  • scripts/library-decisions/schema.mjs — schema additions only (no new exports, no breaking changes to existing field shapes).
  • scripts/library-decisions/schema.test.mjs — new test cases for the two new fields.
  • docs/library-decisions/_template.md — field documentation additions.

Out of scope

  • socket-cli invocation or Socket CI step — Story 02.
  • check.mjs major-bump mode — Story 04.
  • revalidate.mjs script — Story 05.
  • Backfilling existing traces with the new fields — Story 05 (the revalidation cron handles this on its first run).

Tasks

  • Extend scripts/library-decisions/schema.mjs adding socketRisk (union: "clean" | "flagged" | string) to the filter-results Zod object and lastRevalidated (nullable ISO-date string) to the trace frontmatter schema; update docs/library-decisions/_template.md to document both fields with their enum values; add test cases to schema.test.mjs covering socketRisk round-trips (all three variants), lastRevalidated ISO + null acceptance, and missing-socketRisk rejection; all gates pass on this single commit.