Danijel Martinek
90fc2853f2
- New scripts/work/bump-updated-timestamps.mjs stamps the `updated:`
frontmatter field to the current ISO 8601 UTC timestamp on every
staged docs/work/**/*.md file. Idempotent; adds the field after
`created:` if missing.
- .husky/pre-commit invokes the bump script as step 2 (before
rebuild-state) so _state.json sees the fresh timestamp.
- Backfill all existing work docs (4 PRDs + 3 epics + 21 stories):
* created: promoted from \`YYYY-MM-DD\` -> ISO timestamp using
git log --diff-filter=A on each file (first-commit date for
stories that had no \`created:\` line, midnight UTC for PRDs
and epics that had date-only created).
* updated: added from \`git log -1 --format=%aI\` on each file
(last-commit timestamp); will be re-stamped to "now" by the
pre-commit hook on this commit.
Stories that had no \`created:\` line now get one.
3.1 KiB
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 | |
|---|---|---|---|---|---|---|---|---|---|---|
| 07-generator-pre-shipped-traces | 2026-05-14-library-evaluation-policy | Generator templates — pre-shipped traces for optional core packages | technical-story | done | tooling |
|
2026-05-14T06:52:02+02:00 | 2026-05-14T19:10:35.370Z |
Goal
Update the five optional-core generator templates (events, realtime, audit, trpc, ui) so that when pnpm turbo gen core-package <name> runs, it copies pre-written decision: approved library traces into docs/library-decisions/ for every direct runtime dependency of that core package. Update the corresponding __snapshots__ files so the snapshot tests cover the new trace files.
Why
A developer who scaffolds an optional core via the generator should not immediately face a pre-commit failure for its bundled deps — the generator is the policy-compliant path, so the traces should land by construction. Without pre-shipped traces, the very act of using the generator would trigger the enforcement gate it's supposed to clear.
Done when
- Each of the five generator templates (
turbo/generators/templates/core-package/{events,realtime,audit,trpc,ui}/) contains adocs/library-decisions/subtree with one.mdtrace file per direct runtime dependency of that core, dated at generation time (use the template variable for date, or freeze to the scaffold date with a comment),decision: approved, and citing the relevant ADR (events→ ADR-015,realtime→ ADR-016,audit→ ADR-018;trpcanduicite their closest ADR ornullif none). - The generator copies these files into the workspace when run.
- The
turbo/generators/__snapshots__/core-package/<name>.snapshot.jsonfiles are updated to include the new trace files;pnpm turbo gen core-package events(or any other optional core) passes the existing snapshot test. pnpm lint && pnpm fallow:auditpass.
In scope
turbo/generators/templates/core-package/events/— pre-shipped trace(s).turbo/generators/templates/core-package/realtime/— pre-shipped trace(s).turbo/generators/templates/core-package/audit/— pre-shipped trace(s).turbo/generators/templates/core-package/trpc/— pre-shipped trace(s).turbo/generators/templates/core-package/ui/— pre-shipped trace(s).- Snapshot JSON updates for all five cores.
- Generator copy logic (if not already handled by the template mechanism).
Out of scope
- Backfill traces for already-installed optional cores in the live workspace — Story 08.
- Generator templates for non-core-package generators (feature, event, job, realtime, component) — no runtime deps are emitted by those generators.
Tasks
- Inventory the direct runtime deps of each of the five optional core generator templates (read each template's
package.json); write one approved trace file per dep in the correct generator template subtree with ADR citation; update the five snapshot JSON files to include the new trace file entries; verifypnpm turbo gen core-package events(or equivalent dry-run) matches the updated snapshot; all gates pass on this single commit.