3 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Opus 4.8	ac086b65b9	fix(atlas): UX polish — stage-06 plain nodes + shorter arrow labels (#7) ... Stage 06 no longer renders bare in Plain: Build is now tolerant of a jobless/ absent workflow (keeps an authored plain placeholder instead of erroring), and generated CI job nodes carry a plain hint. Shortened the two overlong transition labels ("Order written, sealed, agent-ready" → "Sealed & agent-ready", "Agents produced a change" → "Change proposed") so they stop clipping. Build tolerance test-first. build/vet/lint(0)/test green; screenshot-verified. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-20 09:46:42 +02:00
mathiasandClaude Opus 4.8	5048450b79	feat(atlas): UX sprint — progressive disclosure (Plain default + transitions) ... Makes the atlas self-explanatory. Every stage/node gains a plain-language layer (plain_title + plain "what happens" + jargon-free node text); the previous technical copy demotes to a subtitle + on-demand detail. A Plain⇄Technical toggle (default Plain, persisted) flips the whole atlas. Biggest win: every transition arrow is now LABELLED with "what must be true to advance" (the gated- flow story that was invisible), gate hops (human @04, CI @06) styled distinctly. Spine repositioned into a uniform header band so labels never collide with copy. Copy grounded in a fresh-eyes UX review (docs/UX-REVIEW.md, reviewer≠implementer). Data model: plain_title/plain/trans_label/trans on Stage, plain on Node — guarded by a test (every stage has plain_title + a transition). Live overlays unchanged. Verified: build/vet/lint(0)/test green; Plain render screenshot-checked. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-20 08:22:21 +02:00
mathiasandClaude Opus 4.8	a9c72d6ca8	feat(atlas): Phase B — data-driven /api/atlas.json, CI stage generated from cd.yml ... The atlas no longer hand-maintains its content. Authored data lives in one place (internal/atlas/atlas.json); the Go layer overlays sourced facts and serves the result at /api/atlas.json; the frontend fetches + renders (inline arrays kept only as an offline fallback). First generated source: the CI/CD stage's nodes are parsed from the repo's own .gitea/workflows/cd.yml — so the viz shows the pipeline that actually runs (guard/check/build/deploy), dropping the aspirational var-go/oath-gate node that isn't wired yet. That's the point: it can't drift from the real pipeline. New internal/atlas package (JobsFromWorkflow, Build) built test-first. Adds gopkg.in/yaml.v3 (justified: parsing the workflow YAML; stdlib has no YAML). Verified: go build/vet/lint(0)/test green; /api/atlas.json → 9 stages, CI = real jobs; frontend renders from the fetch (screenshot). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-20 00:34:06 +02:00