fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
3fc5c0f1ca821297ba15cf738777e4b55671f3e2
agentic-dev/docs/work/2026-05-14-library-evaluation-policy/_epic.md
Danijel Martinek 3fc5c0f1ca feat(work): auto-tick epic story bullets when a story finishes 
- Add tickStoryBulletInEpic(workRoot, epic, story) helper that finds
  the bullet in the parent epic's `## Stories` section linking to the
  given story folder and flips `- [ ]` to `- [x]`. Idempotent.
- applyApprovedState now ticks the parent epic bullet whenever a
  story flips to status: done (alongside the existing per-task tick
  and epic-status flip). Epic file gets staged on either ticked-or-
  flipped, not just flipped.
- Backfill all 3 existing epics: 21 bullets ticked to match their
  already-done story statuses (binder-wrap-helper x3, library-
  evaluation-policy x9, ci-security-and-supply-chain x9).
2026-05-14 21:05:06 +02:00

1.8 KiB
Raw Blame History

id, prd, title, type, status, features, created
id prd title type status features created
2026-05-14-library-evaluation-policy docs/work/prds/2026-05-14-library-evaluation-policy.prd.md Library evaluation policy — skill, traces, enforcement stack epic done
scripts
tooling
docs
2026-05-14

Goal

Implement a four-layer enforcement stack — Claude hook, skill, pre-commit hook, sandcastle reviewer prompt — that makes every new runtime dependency in a feature- or core-tier package produce a permanent library trace at docs/library-decisions/<YYYY-MM-DD>-<package-name>.md. Rejection traces are first-class records. Codifies ADR-022.

Why

The repo's narrow third-party surface is uncodified. New dependencies enter via pnpm add with no checkpoint. Three signals exposed the gap: a near-miss adding a build-time-only library, post-hoc ADR records (002/014/017), and a silent EU-data-residency risk from US-only SaaS defaults. The enforcement stack mirrors the 5-gate conformance pattern — same vocabulary, same agent feedback loop.

Stories