Skip to content

LATEST.md: the latest verdict under a fixed name - #33

Merged
markb-1 merged 2 commits into
mainfrom
feat/latest-verdict-file
Nov 17, 2026
Merged

markb-1 merged 2 commits into
mainfrom
feat/latest-verdict-file

Conversation

@markb-1

@markb-1 markb-1 commented Nov 17, 2026

Copy link
Copy Markdown
Owner

Why

The repo's homepage URL should point at the latest verdict, but GW{n}.md moves every week, so any link to it goes stale.

What

  • _write_report writes LATEST.md beside GW{n}.md: same report, same moment, so the reminder (which never touches the root verdict) leaves it alone too.
  • scripts/run-tick.sh and .github/workflows/gaffer.yml stage LATEST.md, guarded like the GW*.md glob.
  • LATEST.md seeded from GW11.md.
  • Test: test_latest_md_carries_the_same_report.

After merge the homepage URL moves to blob/main/LATEST.md.

Testing

pytest: 2105 passed, 2 skipped.

🤖 Generated with Claude Code

markb-1 and others added 2 commits November 17, 2026 18:59
The repo's homepage URL needs one address that stays current, and
GW{n}.md changes every week. Each saved report now also writes LATEST.md
beside it, and both the VM tick and the workflow stage it. Seeded from
GW11.md so the link works before the next run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…leaves it

Principal review changes on #33.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@markb-1

markb-1 commented Nov 17, 2026

Copy link
Copy Markdown
Owner Author

Principal review: approve with changes. All four applied: docstring notes the review is appended to GW{n}.md only; README lists LATEST.md; reminder test pins LATEST.md untouched; seed re-checked against main (still identical to GW11.md). Suite: 2105 passed, 2 skipped.

@markb-1
markb-1 merged commit 25ca71b into main Nov 17, 2026
1 check passed
@markb-1
markb-1 deleted the feat/latest-verdict-file branch November 17, 2026 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant