emdash/afraid-lamps-refuse-6jt16 - #451
Merged
Merged
Conversation
`<div class="mermaid">` renders its own source as article prose until mermaid.js swaps in the SVG. baseof.html defers mermaid.run() until document.fonts.ready, so on a slow font load the reader gets a wall of `flowchart TD R70["Rails 7.0 - ... "] ... classDef dead fill:#fff5f5,...` mid-paragraph; if Caveat never resolves it never goes away. Reported against the Rails 7 EOL post as "images have on it". The entity itself is fine - htmlLabels is on, so mermaid decodes it to a trailing space. The bug was only ever the flash. Site-wide and pre-existing: shipped with the first mermaid post in May 2026. The visual suite renders after fonts settle, so screenshots were always green and it went unreported for three months. Trade-off: if JS fails outright the diagram is absent rather than showing its source. Absent beats a wall of code. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CLAUDE.md's cognitive-load gate wants a hero visual over 800 words. Nothing enforced it: diagram_rendering_test.rb proves diagrams RENDER, not that posts HAVE them. 25 of the 31 long posts published since 2026-04 shipped with none; only 2 posts in all of 2026 carried an in-body visual. bin/check-post-visuals is a ratchet, not a clean gate - 81 legacy posts are over the line and nobody is backfilling them. It fails only when the count rises, so new work is blocked while the backlog burns down. Same shape as bin/check-svg-floor. Floor: 78. Diagrams added (all verified rendered at 1280x800 and 390x844, 0 console errors): - CVE-2026-66066: three-condition exposure funnel - Lovable->Rails: transplant-vs-rebuild fork - Kamal: the boot barrier where job hosts block on first healthy web Mermaid width comes from parallel COLUMNS, not label length - labels wrap at ~200px. A 3-siblings-into-1-gate fan-in renders 797px wide and measures 8.88px at 390px, under the 9px floor bin/check-svg-floor applies. Chained them vertically instead. Node shapes are rects per the house rule in .okf/design/mermaid-theme.md. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
… and CTA The post published 2026-08-08 said Rails 7.2 "reaches the end of its security support on August 9, 2026" in the future tense. That date has passed - 7.2 is now itself a dead branch. Corrected the two sentences carrying it, and the cover chip, which read "7.2 SUPPORT ENDS". Cover regenerated (status dot also moved green -> ruby; "UNSUPPORTED BRANCH" with a green dot was wrong). Added the version status ladder as the first-fold visual - three dead branches in red, 8.0 amber, 8.1 green - the post's thesis in one glance. Added one qualifier CTA after the "Which exit, which app" table, in the style the Lovable post already uses: the reader forks on whether anyone senior owns the fleet sequencing decision. Scoped to the decision, not the labor, because /services/fractional-cto/ sells technical leadership and not upgrade work - hence the closing caveat that the engagement "ranks the queue and owns the argument, it doesn't write your upgrade commits." Promotion is 3% of body words, one paragraph near the end, per the voice guide's 90/10 rule. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The cover-image sources under .stitch/designs/ are generated artifacts - each one is a copy of a reference cover HTML with six text slots swapped - and they are gitignored, so they never reach a reviewer anyway. The detector was flagging them against the site's DESIGN.md, but they are governed by .stitch/design.md, which documents every value it flagged: the Inter / Space Grotesk / JetBrains Mono stack (L93), the 22/26/30/34/56px cover type ramp (L77-L81), and the ruby/purple/cyan chip left-borders (L59-L62). Approved by Paul 2026-08-13 after the hook fired five times on one file. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Adds a pointer row so the task is visible from the board a cold session actually reads. Filed under 2607 because the split touches this project's 20-29-strategy/ files; the decision itself is Paul's, not a refactor an agent should take autonomously. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (12)
📝 WalkthroughWalkthroughThe pull request adds a visual backlog checker and publishing gate, documents Mermaid rendering and layout rules, hides unprocessed diagrams, adds diagrams to four blog posts, updates Rails support content, and records repository housekeeping changes. ChangesBlog visual quality
Repository housekeeping
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
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 by CodeRabbit