Search-result snippets were cutting off mid-sentence across the journal: an audit of every published post found thirty-four descriptions longer than the display band, including the daily digests and the glossary cluster. The draft helper and the builder never checked description length, so each new post could repeat the mistake. This change adds the guard at both ends and rewrites the thirty-four offenders to fit, with this log entry shipping beside it in the same change.
Motivation
Snippet control compounds: the journal ships fresh pages almost daily, and every over-long description hands the search engine a truncated sentence on the highest-volume pages. A one-time rewrite without a guard just restarts the bleed, while a guard without the rewrite leaves thirty-four pages capped on click-through. Doing both together closes the loop permanently.
What changed
The draft helper now refuses a supplied description outside fifty to one hundred fifty-five characters, keeping empty drafts creatable for later completion. The builder prints a warning naming each published post outside the band while staying green on legacy content, by director decision. All thirty-four published descriptions now measure inside the band with keywords kept up front and no other copy touched, and a new regression test asserts the band for every published post plus both guards.
How it was done
After the hosting preflight and a fresh branch from the main line, development added the description validator to the draft helper with an optional command flag, added the warn-only listing to the builder beside the existing pack check, and rewrote each over-long description front-loading its keyword. The regression test mirrors the existing suite layout, and this log entry was drafted in the same change.
Verification evidence
The site build exits success with no description warnings remaining, the new regression test passes, and the full suite is green with the presence gate covered by this entry. A scan of all published descriptions reports zero outside the band, and the rebuilt hallucination page shows the shortened snippet in both the meta and the share-card tags. Sitemap, robots, and feed output are unchanged in shape, and security plus quality reviews attach to the exact pushed head after this pull request opens.
How this entry was built.
Built in the same change it describes; each step traces to a real branch and commit.
- Development verified the remote and login, then branched from the fresh main line.
- Development shipped the guards, the trimmed descriptions, and the regression test with this entry.
- Unit tests, presence gate and deterministic rebuild green; entry shipped in the same change.
Pipeline.
Each stage ran in order; blocked stages looped back through fix and re-review.
merge pending
- done — Hosting preflight and branchDEV · — Verified the remote and login, then branched from the fresh main line.
- done — Guard plus trim pass and testsDEV · — Shipped the draft and build guards, the trimmed descriptions, and the regression test with this entry.
- done — Pull requestDEV · — Opened the pull request with the guard, the trims, the test, and the log entry.
Verdict trail.
| Stage | Agent | Verdict | SHA | Why |
|---|---|---|---|---|
| Hosting preflight and branch | DEV | done | commit | Verified the remote and login, then branched from the fresh main line. |
| Guard plus trim pass and tests | DEV | done | commit | Shipped the draft and build guards, the trimmed descriptions, and the regression test with this entry. |
| Pull request | DEV | done | commit | Opened the pull request with the guard, the trims, the test, and the log entry. |
Why each step ran.
- DEV
- The snippet band is enforced where descriptions are born and where the site is assembled, so the next digest cannot silently repeat the old overflow. The thirty-four legacy descriptions were rewritten with keywords kept up front and no other copy touched. The deterministic build, the full test suite, and the presence gate pass on the change.
- SEC
- Not evidenced in the linked record. The security verdict for the reviewed head is recorded in the review child issue.
- QA
- Not evidenced in the linked record. The quality verdict for the reviewed head is recorded in the review child issue.
- Director
- This change touches draft tooling, build warnings, and published copy with no visual or structural change elsewhere. Security and quality reviews are pinned to the exact pull-request head in parallel child issues. Release approval fires only when both verdicts pass that exact head.
Receipts.
●●●