Skip to content

docs: retire dependency-graph-legibility - #375

Merged
byronwall merged 1 commit into
mainfrom
retire/dependency-graph-legibility
Nov 13, 2026
Merged

byronwall merged 1 commit into
mainfrom
retire/dependency-graph-legibility

Conversation

@byronwall

@byronwall byronwall commented Nov 13, 2026 •

Copy link
Copy Markdown
Owner

Retire the dependency-graph-legibility initiative. All five milestones merged on 2026-10-15 (#50, #56, #58, #60, #61). The planning folder docs/intent/dependency-graph-legibility/ is removed, its lasting facts move into the docs, and docs/initiative-history.json gets its closure record.

What to do with it

Reference only. Merge to remove a finished plan that could mislead later planning.

Proof

  • The dependency graph now packs mid-level views to the viewport, draws two-line boxes with distinct, size-aware folders, groups neighbors by package then file, takes color and LOC from the treemap, and spreads edge bundles. Reconciled against origin/main 0bfb05b.
  • Every milestone maps to a merged PR, checked against gh pr list --state merged and the code on origin/main 0bfb05ba.
  • validate-sleuth.mjs docs/intent/dependency-graph-legibility --retirement: Validation passed before the folder was removed.
  • The docs site builds and its 5 Playwright tests pass on the stack top (cd site && pnpm build && pnpm test).
  • Docs only. No code changed, so app tests were not rerun.

Stack: retire shipped initiatives

What splits: Retiring every shipped software-design-sleuth initiative under docs/intent/, plus status fixes for the ones that only partly shipped.
Why it splits: Each retirement deletes one plan and moves its facts. One layer per initiative lets a reviewer check each closure record against its PRs on its own.
Why this split: One PR for all 13 would mix 13 unrelated deletions in one diff. Grouping by area (graph, compare, metrics, data flow) was rejected, because each closure record and its validator run belong to one initiative.

  1. docs: retire dependency-graph-legibility #375: retire dependency-graph-legibility.
  2. docs: retire compare-ref-picker #376: retire compare-ref-picker.
  3. docs: retire unified-navigation #377: retire unified-navigation.
  4. docs: retire dependency-and-treemap-quick-fixes #378: retire dependency-and-treemap-quick-fixes.
  5. docs: retire dependency-view #379: retire dependency-view.
  6. docs: retire pr-compare #380: retire pr-compare.
  7. docs: retire metric-system-overhaul #381: retire metric-system-overhaul.
  8. docs: retire metric-trust #382: retire metric-trust.
  9. docs: retire metric-portfolio #383: retire metric-portfolio.
  10. docs: retire git-activity #384: retire git-activity.
  11. docs: retire symbol-graph #385: retire symbol-graph.
  12. docs: retire python-dataflow #386: retire python-dataflow.
  13. docs: retire dataflow-logic-visibility #387: retire dataflow-logic-visibility.
  14. docs: set true statuses for partly shipped initiatives #388: set true statuses for the initiatives that only partly shipped.

Not retired, with status set in the last layer: agent-reporting, tsx-dataflow-integration, dataflow-robustness, imported-quality-evidence, dataflow-library-models, dataflow-js-react-solid.

🤖 Generated with Claude Code

All five milestones merged on 2026-10-15 (#50, #56, #58, #60, #61).
Move the layout rules into docs/CODE_MAP.md, add the closure record
to docs/initiative-history.json, and remove the planning folder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant