chore: ascii-spec-diagrams#78
Draft
satyaborg wants to merge 1 commit into
Draft
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
devloop | 3a2684e | Commit Preview URL Branch Preview URL |
Jun 24 2026, 01:17 PM |
Owner
Author
Devloop Final Report
Acceptance Matrix Summary
Engineering Quality Summary
Implementation Summary
Commit References
Tests Run
Residual Risk
|
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
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.
ASCII spec diagrams, retire the HTML spec renderer
Problem
The devloop-spec skill makes Python and a browser part of the spec path. Specs are authored with
mermaidfences, and the skill shipsskills/devloop-spec/scripts/render.py(a ~20k Python file) and instructs runningpython3 scripts/render.py <spec>to produce an HTML companion (skills/devloop-spec/SKILL.md:19,:165,:168). That renderer is referenced inREADME.md:52and pinned by tests (scripts/devloop_test.sh:182,:194,:1129,:1133). Amermaidfence is only a diagram once that HTML is generated and opened in a browser. Withglowas the terminal reader (sibling spec) the HTML companion has no audience: specs are read in-terminal viaglowand on GitHub directly, and neither renders the Python HTML file. The moment it hurts: every spec carries amermaidblock that you can only see as a diagram by generating HTML and opening Chrome, the exact fragmentation being removed.Outcome
The devloop-spec skill instructs authoring diagrams as ASCII art inside plain
```code fences and nevermermaid; the spec template uses an ASCII schematic;render.pyis removed from the repo and is no longer installed, referenced, or tested;README.mdandscripts/devloop_test.shno longer mention it. A spec then renders identically as monospace inglow, on GitHub, and in any plain-text view, with no renderer and no browser.Acceptance Criteria
AC1:
skills/devloop-spec/SKILL.mdcontains nomermaidinstruction and norender.pyorpython3reference, and instructs authoring diagrams as ASCII inside plain code fences.AC2:
skills/devloop-spec/references/spec-template.md's schematic is an ASCII diagram inside a plain```fence, not a```mermaidblock.AC3:
skills/devloop-spec/scripts/render.pydoes not exist in the repo and is not installed byscripts/install.shinto either skills directory.AC4:
README.mdcontains norender.pyreference.AC5:
scripts/devloop_test.shinvokes norender.pyand asserts that neither installed skill directory containsrender.py.AC6:
bash scripts/devloop_test.shpasses.Review Trail
Review rounds and the final report are posted as PR comments below.
Spec: .devloop/specs/2026-06-19-ascii-specs-retire-html-renderer.md
Generated by devloop.sh