[Tracker] 2026-06-15 issue triage — 4 open

[jakebromberg]

End-of-day triage of all 4 open issues in this repo. Intended as the entry point for any contributor or agent picking up after 2026-06-15.

Website is the public station homepage (Next.js + TinaCMS + Tailwind, deployed to GitHub Pages). Mostly content-static; queue is dominated by editorial/UX tweaks plus one real build-safety guardrail.

P0 sequencing — recommended order

1. Validate TinaCMS content slugs to reject invalid URL characters #185 — Validate TinaCMS content slugs to reject invalid URL characters. Direct postmortem of the cli-2.x bump that broke the production build over content/blog/boy-harsher-at-cat's-cradle.md. The current slugify in tina/collections/blog.js strips non-word chars from the title path, but filename.readonly: true is set and editors can still ship bad slugs when the filename derivation lags behind a hand-edited title — the cli's tightened validator (issue chore(deps-dev): bump @tinacms/cli from 2.1.11 to 2.3.1 #177 bumped from 2.1.11 -> 2.3.1 in PR chore(deps): bump @tinacms/mdx from 2.0.7 to 2.1.4 #181, merged 2026-06-03) is what surfaced this. With dependabot now pushing to cli@2.5.0 (PR chore(deps-dev): bump @tinacms/cli from 2.4.3 to 2.5.0 #190), another silent regression on a different special-char filename is possible. Land schema + CI guardrail before pulling further cli majors.
2. Rename Older Blog Posts > label on homepage #92 — Rename Older Blog Posts > to More Blog Posts >. One-line copy edit.
3. Rename Archive > label on homepage #91 — Rename Archive > on homepage. Same as above; pick the wording first.
4. Reconfigure top site nav #93 — Reconfigure top site nav. Information-architecture refresh; pure tree edit, no engineering risk.

Critical / high severity

• HIGH: Validate TinaCMS content slugs to reject invalid URL characters #185 — build-safety regression class; recurrence is plausible on the next cli minor.
• LOW: Rename Archive > label on homepage #91, Rename Older Blog Posts > label on homepage #92, Reconfigure top site nav #93 — editorial polish.

Cross-cluster conflicts

None. The four open issues touch independent surfaces (build-time validation, homepage copy, nav IA).

Obsolete / needs-revision

None confirmed. Did NOT close anything.

PR #131 (Add Instagram feed to homepage, opened 2026-01-31) is mergeStateStatus: DIRTY with REVIEW_REQUIRED, untouched 4.5 months, 805 additions / 10 files — needs a decision (rebase + ship, or close). Not associated with an open issue.

Cross-repo dependencies

None. All four issues are self-contained within this repo.

Cross-repo runtime risks

None. Static site, no live integrations off the homepage. PostHog and TinaCMS Cloud are the only external dependencies and neither is referenced by an open issue.

Cluster map (4 open)

• Build safety / CMS guardrails (1): Validate TinaCMS content slugs to reject invalid URL characters #185
• Homepage copy / nav (3): Rename Archive > label on homepage #91, Rename Older Blog Posts > label on homepage #92, Reconfigure top site nav #93

Open PRs in flight

• chore(deps): bump tinacms from 3.9.0 to 3.9.2 #189 — dependabot bump tinacms 3.9.0 -> 3.9.2 (patch; edge-runtime cache hang fix, irrelevant for GH Pages but benign)
• chore(deps-dev): bump @tinacms/cli from 2.4.3 to 2.5.0 #190 — dependabot bump @tinacms/cli 2.4.3 -> 2.5.0 (minor; Astro init work, no behavior change for this repo). Worth verifying Validate TinaCMS content slugs to reject invalid URL characters #185's failure mode doesn't reappear before merging.
• Add Instagram feed to homepage #131 — Add Instagram feed to homepage (stale 4.5 months, DIRTY, REVIEW_REQUIRED)

How to find work

• All four open issues are unlabeled. The triage labels bug/enhancement could reasonably be applied (Validate TinaCMS content slugs to reject invalid URL characters #185 enhancement, Rename Archive > label on homepage #91-93 enhancement) but the label set here is intentionally minimal — only standard GitHub defaults — so labels were not added.
• Per-issue triage commentary is on each issue's page (look for "Triage finding" comments dated 2026-06-15).