chore(work): decompose product-analytics-channel epic

Generated 1 epic + 9 stories under docs/work/epics/ from the approved
PRD docs/work/prds/product-analytics-channel.prd.md. Stories follow the
sequencing hints from the PRD (brand+wrapper → manifest+wireUseCase →
assertFeatureConformance → BindContext+ESLint → React provider → docs).
Ready for `pnpm work dispatch --execute` to begin implementation.
This commit is contained in:
2026-05-18 12:46:25 +02:00
parent 1595c9198e
commit b8d4cfe907
11 changed files with 618 additions and 3 deletions

View File

@@ -0,0 +1,51 @@
---
id: 09-documentation
epic: product-analytics-channel
title: Documentation — analytics.md, conformance-quickref, CLAUDE.md, template-tiers
type: technical-story
status: todo
feature: docs
depends-on:
[
06-analytics-protocol-bind-context,
07-eslint-rule-no-undeclared-analytics-event,
08-react-provider,
]
blocks: []
created: 2026-05-18T12:08:00Z
updated: 2026-05-18T10:46:27.080Z
---
## Goal
Write `docs/guides/analytics.md` and update `docs/guides/conformance-quickref.md`, `CLAUDE.md`, and `docs/architecture/template-tiers.md` to reflect the completed channel. All docs reference the final shipped shape.
## Why
Docs land last (per PRD sequencing) so they can reference the real API rather than draft shapes. The conformance-quickref and CLAUDE.md rule-count bump are load-bearing for agents that use those files as context pointers.
## Done when
- `docs/guides/analytics.md` exists and documents: server-side wiring path (`BindContext.analytics` → feature binder), client-side wiring path (`<AnalyticsProvider>` + `useAnalytics()`), consumer vendor evaluation step (ADR-022 `/evaluate-library` gate), and PII boundary deferral (ADR-024 §"PII boundary").
- `docs/guides/conformance-quickref.md` rule table shows 7 ESLint rules (adds `no-undeclared-analytics-event`) and drift patterns include analytics-event sprawl.
- `CLAUDE.md` rule count updated from 6 to 7 in the conformance ESLint rules list.
- `docs/architecture/template-tiers.md` lists `core-analytics` in the optional-cores table.
- All gates pass on each commit independently.
## In scope
- `docs/guides/analytics.md` — new guide.
- `docs/guides/conformance-quickref.md` — rule table + drift patterns update.
- `CLAUDE.md` — conformance rule count line update.
- `docs/architecture/template-tiers.md` — optional-cores list update.
## Out of scope
- Glossary update (already done in the ADR-024 commit per PRD).
- ADR-024 itself (already exists).
- Storybook component or demo app (deferred per PRD).
## Tasks
- [ ] Write `docs/guides/analytics.md` covering server-side wiring (`BindContext.analytics`), client-side wiring (`<AnalyticsProvider>` + `useAnalytics()`), vendor evaluation step (ADR-022), and PII boundary note — all gates pass on this commit.
- [ ] Update `docs/guides/conformance-quickref.md` (seventh rule + analytics-event drift pattern), `CLAUDE.md` (6 → 7 conformance ESLint rules), and `docs/architecture/template-tiers.md` (add `core-analytics` to optional-cores list) — all gates pass on this commit.