fix: cron commits trigger Pages; tighten diff-guard; scrollable card comments

[jeremymanning]

Five user-reported issues, all root-caused and fixed in a single bundle.

Issues

1. Personality cron (and all crons) aren't updating the website.
   Root cause: GitHub deliberately suppresses workflow triggers from
   GITHUB_TOKEN-authored pushes. Every cron correctly regenerated
   web/data/projects.json and committed, but pages.yml's push
   trigger silently no-opped — bot commits never fired Pages deploys.

2. Comments don't appear in cards / aren't scrollable.
   Root cause: JS rendering was correct (45 comments across 19 projects
   already feed the inline .comments-block) but had no max-height +
   overflow-y; "+N more" pushed card layout instead of scrolling.

3. Markdown renders literal '--- a/path' / '@@ -N,N' diff markers.
   Root cause: speckit diff-guard at tasks_cmd.py:161 only caught
   @@-prefixed leads; missed --- a/<path> headers AND the
   escalate-branch wrote patches verbatim without guarding.
   7 production .md files polluted (PROJ-001 spec/plan/tasks,
   PROJ-007 spec, PROJ-008 spec, PROJ-023 spec/plan).

4. Missing artifacts / dead links. Root cause: subsumed by issue 3
   — the user was seeing diff-polluted markdown bodies (links inside
   --- a/spec.md text are non-clickable). The artifact-link code in
   dialog.js already correctly suppresses null relpaths.

5. No cron triggers a Pages rebuild after touching dashboard files.
   Subsumed by fix 1.

Fixes

Fix 1: pages-deploy dispatch from every cron (10 workflows)

Each cron's commit step now sets pushed=true|false in $GITHUB_OUTPUT,
and a follow-up step runs gh workflow run pages.yml --ref main when
pushed == 'true'. workflow_dispatch invoked from a workflow DOES
fire regardless of token provenance — unlike push.

Workflows touched: pipeline-{personality,brainstorm,flesh-out,implement,paper-speckit,paper-write,research-speckit,review}.yml,
submission-intake.yml, paper-compile.yml. All YAML re-validated.

Fix 2: tighten + share diff-guard

• New module src/llmxive/speckit/_diff_guard.py (single source of
  truth, Constitution I) catches:
  • @@ -N,N +N,N @@ hunk-only leads (original case)
  • --- a/<path> lead (NEW — the case that polluted PROJ-001)
  • +++ b/<path> lead
  • any combination of 2+ unified-diff markers anywhere in the text
  • context-diff format (*** old\n--- new)
• Wired into all three speckit writers: tasks_cmd.py (main +
  escalate-branch patches), specify_cmd.py, plan_cmd.py.
• 7 polluted files purged; affected projects rolled back to
  flesh_out_complete via the same _walk_back_to_real_stage used by
  spec 010's speckit prune. Rollbacks recorded in
  state/projects/<id>.history.jsonl + state/run-log/.

Fix 3: scrollable comments block

web/css/site.css adds:

.card .comments-block.expanded {
  max-height: 320px;
  overflow-y: auto;
  scroll-behavior: smooth;
}

The existing JS toggle (+N more → .expanded class) already works;
this just constrains the height when expanded so the user scrolls instead
of pushing the card layout.

Tests

• 12 new unit tests for _diff_guard: hunk-only leads, --- a/ leads,
  +++ b/ leads, 2+-marker detection, context-diff format. Critically,
  also tests that markdown HR rules (---) and em-dashes don't false-fire.
• 78/78 spec-010 + librarian-gate tests pass.
• web/data/projects.json regenerated after cleanup.

🤖 Generated with Claude Code