docs(site): docs-site + workshop + gallery pages for the six CLM-era patterns - #168
Conversation
…patterns [regen-baselines] Combined docs-site batch for form-wizard, timeline, diff, work-queue, versions, and lineage (rounds 4b-4g), following the picker/uploader/ sidebar recipe: - registry: nine new pattern entries (form-wizard, timeline, diff-viewer, work-queue, workload-board, version-list, version-graph, lineage-graph, provenance-strip). - examples: live demos for each, driven by a shared deterministic docs-site/clm-demo-data.ts module (pinned REFERENCE_TIME so previews and screenshots never drift): intake wizard steps, contract activity events, the clause 4.2 before/after texts, an in-memory work-queue transport whose mutations actually update the list, the branch/merge version history, and the clause lineage DAG. - workshop: nine story modules with reference tables and usage variants; workshop.json re-extracted (126 stories). - gallery: new "CLM workflows" section rendering all nine elements with inline demo data; smoke-tested headless (all shadow roots populate, no page errors). - docs-site-shots: nine new capture routes. [regen-baselines] in the subject so the pinned container re-captures the gallery and docs-site baselines this PR shifts/adds. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JuNendvxv88rRhxQkoxTuH
|
Warning Review limit reached
Next review available in: 68 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (20)
📒 Files selected for processing (15)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JuNendvxv88rRhxQkoxTuH
What
The combined docs-site batch for the six patterns shipped in rounds 4b–4g — form-wizard, timeline, diff, work-queue, versions, lineage — following the recipe proven with picker/uploader/sidebar (#161). Until now these existed only in code and the catalog doc; this PR makes them discoverable and demoable.
form-wizard,timeline,diff-viewer,work-queue,workload-board,version-list,version-graph,lineage-graph,provenance-strip).docs-site/clm-demo-data.tsmodule — deterministic data pinned to a fixedREFERENCE_TIMEso previews and screenshots never drift: contract-intake wizard steps, contract activity events, the clause 4.2 before/after texts, an in-memory work-queue transport whose mutations really update the list (Claim/Complete/Escalate work in the preview), the branch/merge version history, and the clause-lineage DAG.workshop.jsonre-extracted — now 126 stories.Baselines
[regen-baselines]is in the commit subject, so the pinned container will re-capture the gallery and docs-site baselines this PR shifts (new gallery section) and adds (nine docs-site pages).Tests
Full suite green: 198 files, 1366 tests — the docs-site consistency tests validate the new registry/example/story identities.
🤖 Generated with Claude Code
https://claude.ai/code/session_01JuNendvxv88rRhxQkoxTuH
Generated by Claude Code