docs: post-adoption re-compaction — roadmap/triage/layout/readme match GitHub reality - #238
Merged
Merged
Conversation
WHAT: rewrites the v0.7-v0.12 back half to post-adoption reality: adds the 'Re-compaction — 2026-07-29' section; drops rows that scheduled the already- executed #52-#76 closes (dated 07-17/18 per GitHub); marks #37/#85 closed 2026-07-21 everywhere (headline table, renderer-epic prose, epics table); retitles v0.8 'Bindings (py)' (absorbs #79, which folded #80-#82) and v0.9 'Authoring' (#31 + #147); tombstones v0.10 (merged into v0.8); consolidates the SSIM/conformance tail (#77/#78/#83/#84) in v0.11; adds the adoption follow-through issues #235/#236/#237; corrects #84's licensing reality (resvg/usvg relicensed Apache-2.0/MIT — the MPL-2.0 surface is the desktop bundles' cssparser/selectors/dtoa-short/option-ext); notes #222 re-entry. WHY: the roadmap promised this re-compaction 'after #132' (adoption spike passed 2026-07-17) and it never happened — the back half still scheduled closes that were already done and milestones named for a dead from-scratch renderer plan. GitHub is the state; this makes the map match it. Co-Authored-By: Claude Fable 5 (gnuc agent) <[email protected]>
WHAT: the epic-table row now records what actually happened — #52-#76 + PR #99 closed (provided by the adopted mermaid-rs-renderer v0.3.1), #37/#85 closed 2026-07-21, remaining tail #77/#78/#83/#84 + #79 (absorbs #80-#82) — and the renderer-section banner gets a since-then note so the two summaries in this file agree. Fixes the nested-backtick <metadata> code span GitHub rendered incorrectly. WHY: the row still said '#52-#75 close on the #132 spike-Pass; #76-#85 kept', which disagrees with the applied disposition (off-by-one on both ranges) and with the closes that have since landed. 2026-07-29 backlog scrub. Co-Authored-By: Claude Fable 5 (gnuc agent) <[email protected]>
WHAT: adds the missing shipped-crate rows (scrybe-mermaid-render, scrybe-rpc, scrybe-ratatui, scrybe-tui) and the non-cargo members (scrybe-plugin-docx, scrybe-meta); moves scrybe-panels/scrybe-swarm rows to their real experimental/ paths with a 'not compiled' note; adds 'view' to the scrybe-cli subcommand list (#229). WHY: agents follow this table; it omitted four compiled workspace members and presented two parked experimental crates as shipped ones. 2026-07-29 scrub. Co-Authored-By: Claude Fable 5 (gnuc agent) <[email protected]>
WHAT: the Windows line no longer claims 'pending community moderation' (no push has occurred — the nupkg is staged, awaiting CHOCO_API_KEY; see #2), and the lock-step sentence now notes the brew tap / choco feed can lag a release until #1/#2 land their publish secrets. WHY: README claimed channel states that have not happened; the 2026-07-29 scrub verified the tap is at 0.6.2 vs released 0.6.3 and choco was never pushed. Co-Authored-By: Claude Fable 5 (gnuc agent) <[email protected]>
hartsock
added
the
risk:low
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Executes the post-adoption re-compaction that ROADMAP.md promised "after #132" — the from-scratch renderer plan died when
mermaid-rs-rendererv0.3.1 was adopted, but the roadmap's back half, TRIAGE, CLAUDE.md, and README still described the dead plan. Docs only; the GitHub side (milestone retitles/closes, issue re-scopes, #79 fold, new issues #235/#236/#237) already happened on 2026-07-29 and this PR makes the map match it.pngfeature #76 closes; feat: scrybe-mermaid-render — pure-Rust Mermaid renderer (sequence + flowchart) #37/mermaid-render: release: flip publish = true + bump version + tick gating checklist #85 marked closed 2026-07-21 everywhere; v0.8 → "Bindings (py)", v0.9 → "Authoring", v0.10 tombstoned); adds the adoption follow-through issues; corrects mermaid-render: licensing: add LICENSE-MPL-2.0 for resvg/usvg distribution #84's licensing reality — resvg/usvg relicensedApache-2.0 OR MIT; the true MPL-2.0 surface is the desktop bundles'cssparser/selectors/dtoa-short/option-ext(wheels/crates verified MPL-free).pngfeature #76 closed, tail mermaid-render: grader: SSIM via image-compare #77/mermaid-render: trace tests: enforce SSIM ≥ 0.92 for flowchart fixtures #78/mermaid-render: conformance: gen_oracle.sh --with-upstream + upstream fixtures Tier 1 #83/mermaid-render: licensing: add LICENSE-MPL-2.0 for resvg/usvg distribution #84 + feat(scrybe-py): expose Mermaid render (SVG + PNG, with provenance) from Python #79); fixes a broken nested-backtick code span.viewadded to the CLI row.CHOCO_API_KEY; brew tap may lag untilTAP_GITHUB_TOKENlands).Also landed with this push (same atomic ref update): the
archive/scrybe-mermaid-render-plantag preserving the from-scratch PLAN.md branch head, and deletion of the supersededfeat/scrybe-mermaid-render+ PR-#99centaur/*branches ("extract value, then delete").Test plan
just check+ feature-gated cargo checks) passed locally.gh(caught and fixed 10 defects, incl. wrong close dates and leftover present-tense feat: scrybe-mermaid-render — pure-Rust Mermaid renderer (sequence + flowchart) #37/mermaid-render: release: flip publish = true + bump version + tick gating checklist #85 prose); internal-consistency sweep of the full edited files; privacy/leak scan clean (no private IPs / internal DNS / secrets / PII).Fixes none — tracking issues remain open by design; the re-compaction itself was promised in ROADMAP.md ("Adoption dividend" note).
🤖 Generated with Claude Code