From 723bf1038074408d824f7b56c693f128fc5b5922 Mon Sep 17 00:00:00 2001 From: Luis Rivera Date: Thu, 5 Nov 2026 02:55:36 +0000 Subject: [PATCH 1/3] =?UTF-8?q?v1.10.10:=20PR=20layout=20=E2=80=94=20autom?= =?UTF-8?q?ated=20checks=20vs=20manual=20QA,=20results=20as=20a=20table?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CLAUDE.md §0 gets a "PR layout" section. The status line reads "Automated checks" and covers only scripted sandbox checks; the hand-run script is a collapsed "Manual QA steps" section with a "Manual QA passed" box in "Please check before merging". Each automated run is one PR comment with a # · Check · Area · Result · Notes table and long logs collapsed below it. Earlier comments and CHANGELOG entries are untouched. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_013Z8iBUuvoYJaEX18vphJPz --- CHANGELOG.md | 10 ++++++++++ CLAUDE.md | 44 +++++++++++++++++++++++++++++++++++++++++--- README.md | 4 ++-- index.html | 2 +- js/views-settings.js | 2 +- 5 files changed, 55 insertions(+), 7 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a41488d..9089e7d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,16 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). --- +## [1.10.10] — 2026-11-04 + +### Technical (docs) +- **Automated checks and manual QA are told apart in PR descriptions.** CLAUDE.md §0 gets a "PR layout" section. The status line reads `**Automated checks:** 5/5 passed · …` and covers only the scripted checks run in a sandbox. The reviewer's hand-run script is a collapsed "Manual QA steps" section, recorded by a "Manual QA passed in Edge/Chrome with a real folder" box in "Please check before merging". +- **Automated check results are a table.** Each run is one PR comment headed `## Automated checks`, with the columns # · Check · Area · Result · Notes, and long logs in collapsed blocks below the table. Skipped rows don't count as passed. +- **Earlier "Test results" comments and CHANGELOG entries are left as they are.** +- Version: v1.10.6–v1.10.9 are already used by open PRs #22, #52, #61, #62 and #63, so this takes v1.10.10. Whichever merges later renumbers if needed (§0). + +--- + ## [1.10.5] — 2026-11-02 ### Fixed diff --git a/CLAUDE.md b/CLAUDE.md index d895c1b..48cb598 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -19,9 +19,47 @@ Nothing reaches `master` except through a reviewed pull request. This is the own ### What every PR includes - **CHANGELOG and version** bumped per §17. -- **A description** with a summary, the cause (for bugs), what changed, how it was tested, and a "please check before merging" list. +- **A description** with a summary, the cause (for bugs), what changed, what wasn't verified, manual QA steps and a "please check before merging" list, laid out as in "PR layout" below. - **Tests run** before opening the PR (headless browser checks against `samples/`). Report results honestly, including anything not verified. +### PR layout + +The description is for context: why the change exists, what caused it and what changed. Reproduction steps, manual QA steps and check results stay out of the way. + +**Two kinds of testing, kept apart:** + +| | Automated checks | Manual QA | +|---|---|---| +| **What** | Scripted checks run in a sandbox: syntax, version lines, product rules, headless Chromium against `samples/` | A step-by-step script followed by hand before merging | +| **Where it runs** | Headless browser, fake or no data folder | Real Edge/Chrome with a real data folder | +| **Where it lives** | A PR comment per run, summed up by the status line | The collapsed "Manual QA steps" section | +| **How it's recorded** | ✅ / ❌ / ⏭️ per row in the comment's table | The "Manual QA passed" box in "Please check before merging" | + +A passing status line means the automated checks passed. It never means manual QA was done. + +- **Order of the description:** summary; cause (bug fixes); what changed; any other context (finance notes, trade-offs, findings not fixed); `## Not verified` (what the automated checks couldn't cover, e.g. real Edge/Chrome with a real folder) and the status line; the collapsed sections; `## Please check before merging` last. +- **The status line** sits right after "Not verified" and links to the latest automated checks comment: + `` **Automated checks:** 5/5 passed · headless Chromium · `abc1234` · [results]() `` + - The count is ✅ rows out of all rows. Skipped rows are not counted as passed. + - Update it after every run. +- **Collapsed sections**, closed by default, in this order: + 1. **How to reproduce the bug** (bug fixes only) + 2. **Manual QA steps**: numbered, each one action plus what should be seen (exact screen, button, value or file), starting from a known state. + + Write each as `
Manual QA steps`, then a blank line, the steps, a blank line and `
`. Without the blank lines GitHub doesn't render the Markdown inside. When a new commit changes the steps, edit the section in place. +- **"Please check before merging"** always includes `- [ ] Manual QA passed in Edge/Chrome with a real folder`. +- **Automated check results go in a PR comment, never in the description.** One comment per run: + 1. Heading `## Automated checks`, then one line: the commit's short SHA · the environment · the date. + 2. A table with the columns **# · Check · Area · Result · Notes**: + - **Area** is one of Docs, Code, UI, Data, Finance, Rules, Security. + - **Result** is ✅ Pass, ❌ Fail or ⏭️ Skipped. A failed or skipped row says why in Notes, and every skipped row is also listed under "Not verified". + 3. Long logs go below the table, each in its own collapsed block named by its row: `
Log: 2 — JS syntax`, with the same blank lines as above. + + Don't edit an old comment to show a newer run. Post a new one and update the status line. +- **Opening a PR:** create it, post the automated checks comment, then add that comment's link to the status line. +- **Earlier comments stay as they are.** "Test results" comments posted before this rule are a record of past runs and are not rewritten into the table format. +- The `Generated by` footer stays last in the description. + ### Stacked PRs - **When a change depends on an unmerged PR,** branch from that PR's branch and set it as the new PR's base. Say so at the top of the description. @@ -59,7 +97,7 @@ Until then, this section is the rule. FinLens is a **single-origin, zero-build, vanilla JavaScript personal finance dashboard** that runs entirely in the browser. There is no server, no npm, no bundler, no framework, and no TypeScript. The entry point is `index.html`; everything else is a plain `.js` file in the `js/` folder. -**Current version:** v1.10.5 (updated in `index.html` footer, `README.md`, and `CHANGELOG.md` on every release). +**Current version:** v1.10.10 (updated in `index.html` footer, `README.md`, and `CHANGELOG.md` on every release). **What it does:** Imports CSV exports from Ally Bank (Checking + Savings) and Chase credit cards, parses and normalizes them into a unified transaction model, and renders a multi-tab financial dashboard with budgeting, debt tracking, savings forecasting, investment planning, and Claude-powered AI analysis. @@ -798,7 +836,7 @@ Multiple Chase card files can be loaded simultaneously. Each gets a unique `acco --- -*Last updated: v1.10.5 — 2026-11-02 (no section changes: Import Logs race fix; v1.10.4: §8, §13 single `~` is literal; §21 excerpts escape `~`; v1.10.3: §13 refusals; §21 declined runs; v1.10.2: §13 summary states its dates; §21 per-month derivations; v1.10.1: §13 `AI_MAX_TOKENS`, thinking and cut-off answers; v1.10.0: §21 AI Eval added; §13 `callClaude()` raw mode; v1.9.6: §14 folder access lasts until the last tab closes, not one page load; v1.9.5: §7 chart guard; v1.9.4: views-db.js changelog reads CRLF checkouts; v1.9.3: §14 folder permission: re-request on click, Reconnect banner, browser copy wins; v1.9.2: §0 branch, PR and approval workflow added; v1.9.1: §4.5 rehydrate transactions loaded from JSON; v1.9.0: §20 Data & Reset added; v1.8.1: §10 re-upload dedup rewritten for the occurrence-suffix fix; v1.8.0: AI Analysis restored with API-key and output hardening; `renderMarkdown()` added; `samples/` added; §1–3, §13, §14, §17 corrected to match the code)* +*Last updated: v1.10.10 — 2026-11-04 (§0 PR layout: automated checks vs manual QA; automated checks reported as a table in PR comments; v1.10.5: no section changes: Import Logs race fix; v1.10.4: §8, §13 single `~` is literal; §21 excerpts escape `~`; v1.10.3: §13 refusals; §21 declined runs; v1.10.2: §13 summary states its dates; §21 per-month derivations; v1.10.1: §13 `AI_MAX_TOKENS`, thinking and cut-off answers; v1.10.0: §21 AI Eval added; §13 `callClaude()` raw mode; v1.9.6: §14 folder access lasts until the last tab closes, not one page load; v1.9.5: §7 chart guard; v1.9.4: views-db.js changelog reads CRLF checkouts; v1.9.3: §14 folder permission: re-request on click, Reconnect banner, browser copy wins; v1.9.2: §0 branch, PR and approval workflow added; v1.9.1: §4.5 rehydrate transactions loaded from JSON; v1.9.0: §20 Data & Reset added; v1.8.1: §10 re-upload dedup rewritten for the occurrence-suffix fix; v1.8.0: AI Analysis restored with API-key and output hardening; `renderMarkdown()` added; `samples/` added; §1–3, §13, §14, §17 corrected to match the code)* --- diff --git a/README.md b/README.md index 1cd3fc5..bc17f65 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ > A zero-install, browser-native finance dashboard. Drop in your bank CSVs, get instant clarity on your money. -**Version:** v1.10.5  ·  **Stack:** Vanilla JS, HTML, CSS  ·  **Install:** None +**Version:** v1.10.10  ·  **Stack:** Vanilla JS, HTML, CSS  ·  **Install:** None --- @@ -260,4 +260,4 @@ See [CHANGELOG.md](CHANGELOG.md) for the full release history. --- -*FinLens v1.10.5 — Built for one person's finances, designed to be useful for anyone's.* +*FinLens v1.10.10 — Built for one person's finances, designed to be useful for anyone's.* diff --git a/index.html b/index.html index ee48405..4e7411b 100644 --- a/index.html +++ b/index.html @@ -326,7 +326,7 @@
⚙️ Settings
diff --git a/js/views-settings.js b/js/views-settings.js index 6f7d389..b9ced95 100644 --- a/js/views-settings.js +++ b/js/views-settings.js @@ -49,7 +49,7 @@ function _renderGeneralSettings(root) { -
FinLens v1.10.5 ·${State.transactions.length} transactions loaded${State.lastRefresh?' · Refreshed '+dayjs(State.lastRefresh).format('MMM D, YYYY h:mm A'):''}
`; +
FinLens v1.10.10 ·${State.transactions.length} transactions loaded${State.lastRefresh?' · Refreshed '+dayjs(State.lastRefresh).format('MMM D, YYYY h:mm A'):''}
`; root.appendChild(displayCard); /* ---- Anthropic API Key ---- */ From 1a0f893d4b583b4e66fbde09d4c87a1d28fa1de6 Mon Sep 17 00:00:00 2001 From: Luis Rivera Date: Thu, 5 Nov 2026 03:05:06 +0000 Subject: [PATCH 2/3] PR layout: automated checks collapsed in the description, not comments MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The "Automated checks" section moves from a PR comment into a collapsed section in the description; its title is the status line (count · environment · SHA · date). Each run replaces it in place. Adds when to re-run: full run for content commits, light run after a master merge or renumber. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_013Z8iBUuvoYJaEX18vphJPz --- CHANGELOG.md | 5 +++-- CLAUDE.md | 45 ++++++++++++++++++++++----------------------- 2 files changed, 25 insertions(+), 25 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9089e7d..9792fff 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,8 +8,9 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). ## [1.10.10] — 2026-11-04 ### Technical (docs) -- **Automated checks and manual QA are told apart in PR descriptions.** CLAUDE.md §0 gets a "PR layout" section. The status line reads `**Automated checks:** 5/5 passed · …` and covers only the scripted checks run in a sandbox. The reviewer's hand-run script is a collapsed "Manual QA steps" section, recorded by a "Manual QA passed in Edge/Chrome with a real folder" box in "Please check before merging". -- **Automated check results are a table.** Each run is one PR comment headed `## Automated checks`, with the columns # · Check · Area · Result · Notes, and long logs in collapsed blocks below the table. Skipped rows don't count as passed. +- **Automated checks and manual QA are told apart in PR descriptions.** CLAUDE.md §0 gets a "PR layout" section. Automated checks are the scripted checks run in a sandbox; manual QA is the hand-run script in a collapsed "Manual QA steps" section, recorded by a "Manual QA passed in Edge/Chrome with a real folder" box in "Please check before merging". +- **Automated check results are a collapsed table in the description.** The section's title is the status line (`Automated checks: 6/7 passed · environment · SHA · date`). Inside: a # · Check · Area · Result · Notes table, with long logs in nested collapsed blocks. Skipped rows don't count as passed. +- **When to re-run:** a full run for commits that change the PR's content, a light run (version lines, JS syntax, boot) after a `master` merge or renumber. Each run replaces the section in place, so the SHA in its title shows whether the checks match the latest commit. - **Earlier "Test results" comments and CHANGELOG entries are left as they are.** - Version: v1.10.6–v1.10.9 are already used by open PRs #22, #52, #61, #62 and #63, so this takes v1.10.10. Whichever merges later renumbers if needed (§0). diff --git a/CLAUDE.md b/CLAUDE.md index 48cb598..fa487af 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -24,7 +24,7 @@ Nothing reaches `master` except through a reviewed pull request. This is the own ### PR layout -The description is for context: why the change exists, what caused it and what changed. Reproduction steps, manual QA steps and check results stay out of the way. +The description is for context: why the change exists, what caused it and what changed. Reproduction steps, manual QA steps and check results are collapsed so they stay out of the way. **Two kinds of testing, kept apart:** @@ -32,32 +32,31 @@ The description is for context: why the change exists, what caused it and what c |---|---|---| | **What** | Scripted checks run in a sandbox: syntax, version lines, product rules, headless Chromium against `samples/` | A step-by-step script followed by hand before merging | | **Where it runs** | Headless browser, fake or no data folder | Real Edge/Chrome with a real data folder | -| **Where it lives** | A PR comment per run, summed up by the status line | The collapsed "Manual QA steps" section | -| **How it's recorded** | ✅ / ❌ / ⏭️ per row in the comment's table | The "Manual QA passed" box in "Please check before merging" | +| **Where it lives** | The collapsed "Automated checks" section, whose title is the status line | The collapsed "Manual QA steps" section | +| **How it's recorded** | ✅ / ❌ / ⏭️ per row in the section's table | The "Manual QA passed" box in "Please check before merging" | -A passing status line means the automated checks passed. It never means manual QA was done. +A passing "Automated checks" title means the automated checks passed. It never means manual QA was done. -- **Order of the description:** summary; cause (bug fixes); what changed; any other context (finance notes, trade-offs, findings not fixed); `## Not verified` (what the automated checks couldn't cover, e.g. real Edge/Chrome with a real folder) and the status line; the collapsed sections; `## Please check before merging` last. -- **The status line** sits right after "Not verified" and links to the latest automated checks comment: - `` **Automated checks:** 5/5 passed · headless Chromium · `abc1234` · [results]() `` - - The count is ✅ rows out of all rows. Skipped rows are not counted as passed. - - Update it after every run. +- **Order of the description:** summary; cause (bug fixes); what changed; any other context (finance notes, trade-offs, findings not fixed); `## Not verified` (what the automated checks couldn't cover, e.g. real Edge/Chrome with a real folder); the collapsed sections; `## Please check before merging` last. - **Collapsed sections**, closed by default, in this order: - 1. **How to reproduce the bug** (bug fixes only) - 2. **Manual QA steps**: numbered, each one action plus what should be seen (exact screen, button, value or file), starting from a known state. + 1. **Automated checks.** Its title is the status line: `Automated checks: 6/7 passed · headless Chromium · abc1234 · 2026-11-04`, i.e. ✅ rows out of all rows, the environment, the commit's short SHA and the date. Skipped rows are not counted as passed. Inside: + - a table with the columns **# · Check · Area · Result · Notes**. **Area** is one of Docs, Code, UI, Data, Finance, Rules, Security. **Result** is ✅ Pass, ❌ Fail or ⏭️ Skipped. A failed or skipped row says why in Notes, and every skipped row is also listed under "Not verified"; + - long logs below the table, each in its own nested collapsed block named by its row: `
Log: 2 — JS syntax`. + 2. **How to reproduce the bug** (bug fixes only). + 3. **Manual QA steps**: numbered, each one action plus what should be seen (exact screen, button, value or file), starting from a known state. - Write each as `
Manual QA steps`, then a blank line, the steps, a blank line and `
`. Without the blank lines GitHub doesn't render the Markdown inside. When a new commit changes the steps, edit the section in place. + Write each as `
Manual QA steps`, then a blank line, the content, a blank line and `
`. Without the blank lines GitHub doesn't render the Markdown inside. When a new commit changes the steps, edit the section in place. - **"Please check before merging"** always includes `- [ ] Manual QA passed in Edge/Chrome with a real folder`. -- **Automated check results go in a PR comment, never in the description.** One comment per run: - 1. Heading `## Automated checks`, then one line: the commit's short SHA · the environment · the date. - 2. A table with the columns **# · Check · Area · Result · Notes**: - - **Area** is one of Docs, Code, UI, Data, Finance, Rules, Security. - - **Result** is ✅ Pass, ❌ Fail or ⏭️ Skipped. A failed or skipped row says why in Notes, and every skipped row is also listed under "Not verified". - 3. Long logs go below the table, each in its own collapsed block named by its row: `
Log: 2 — JS syntax`, with the same blank lines as above. - - Don't edit an old comment to show a newer run. Post a new one and update the status line. -- **Opening a PR:** create it, post the automated checks comment, then add that comment's link to the status line. -- **Earlier comments stay as they are.** "Test results" comments posted before this rule are a record of past runs and are not rewritten into the table format. +- **When to re-run the automated checks.** Each run replaces the "Automated checks" section in place, title included. Past runs stay in the description's edit history. + + | Commit | Re-run | Checks | + |---|---|---| + | Changes the PR's own content (code, docs, review fixes) | Yes | Full run | + | Merge of `master`, or a version renumber | Yes | Light run: version lines, JS syntax, boot | + | No commit (description or comment edits only) | No | — | + + The SHA in the section's title should always match the branch's latest commit. If it doesn't, the PR hasn't been checked at its current state. +- **Earlier results stay as they are.** "Test results" comments and description sections written before this rule are a record of past runs and are not rewritten. A PR that gets a new run moves to this layout from that run on. - The `Generated by` footer stays last in the description. ### Stacked PRs @@ -836,7 +835,7 @@ Multiple Chase card files can be loaded simultaneously. Each gets a unique `acco --- -*Last updated: v1.10.10 — 2026-11-04 (§0 PR layout: automated checks vs manual QA; automated checks reported as a table in PR comments; v1.10.5: no section changes: Import Logs race fix; v1.10.4: §8, §13 single `~` is literal; §21 excerpts escape `~`; v1.10.3: §13 refusals; §21 declined runs; v1.10.2: §13 summary states its dates; §21 per-month derivations; v1.10.1: §13 `AI_MAX_TOKENS`, thinking and cut-off answers; v1.10.0: §21 AI Eval added; §13 `callClaude()` raw mode; v1.9.6: §14 folder access lasts until the last tab closes, not one page load; v1.9.5: §7 chart guard; v1.9.4: views-db.js changelog reads CRLF checkouts; v1.9.3: §14 folder permission: re-request on click, Reconnect banner, browser copy wins; v1.9.2: §0 branch, PR and approval workflow added; v1.9.1: §4.5 rehydrate transactions loaded from JSON; v1.9.0: §20 Data & Reset added; v1.8.1: §10 re-upload dedup rewritten for the occurrence-suffix fix; v1.8.0: AI Analysis restored with API-key and output hardening; `renderMarkdown()` added; `samples/` added; §1–3, §13, §14, §17 corrected to match the code)* +*Last updated: v1.10.10 — 2026-11-04 (§0 PR layout: automated checks vs manual QA; automated checks as a collapsed table in the description, re-run per commit; v1.10.5: no section changes: Import Logs race fix; v1.10.4: §8, §13 single `~` is literal; §21 excerpts escape `~`; v1.10.3: §13 refusals; §21 declined runs; v1.10.2: §13 summary states its dates; §21 per-month derivations; v1.10.1: §13 `AI_MAX_TOKENS`, thinking and cut-off answers; v1.10.0: §21 AI Eval added; §13 `callClaude()` raw mode; v1.9.6: §14 folder access lasts until the last tab closes, not one page load; v1.9.5: §7 chart guard; v1.9.4: views-db.js changelog reads CRLF checkouts; v1.9.3: §14 folder permission: re-request on click, Reconnect banner, browser copy wins; v1.9.2: §0 branch, PR and approval workflow added; v1.9.1: §4.5 rehydrate transactions loaded from JSON; v1.9.0: §20 Data & Reset added; v1.8.1: §10 re-upload dedup rewritten for the occurrence-suffix fix; v1.8.0: AI Analysis restored with API-key and output hardening; `renderMarkdown()` added; `samples/` added; §1–3, §13, §14, §17 corrected to match the code)* --- From bd682da3de9db916d699b980497ee52d5b294272 Mon Sep 17 00:00:00 2001 From: Luis Rivera Date: Thu, 5 Nov 2026 03:13:56 +0000 Subject: [PATCH 3/3] PR layout: record that open PRs' earlier results moved into the description Replaces "earlier results stay as they are" with how they were migrated: moved unchanged into "Automated checks: earlier run, not re-run", old "Test results" comments deleted, table format from the next run on. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_013Z8iBUuvoYJaEX18vphJPz --- CHANGELOG.md | 2 +- CLAUDE.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9792fff..a5d596d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,7 +11,7 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). - **Automated checks and manual QA are told apart in PR descriptions.** CLAUDE.md §0 gets a "PR layout" section. Automated checks are the scripted checks run in a sandbox; manual QA is the hand-run script in a collapsed "Manual QA steps" section, recorded by a "Manual QA passed in Edge/Chrome with a real folder" box in "Please check before merging". - **Automated check results are a collapsed table in the description.** The section's title is the status line (`Automated checks: 6/7 passed · environment · SHA · date`). Inside: a # · Check · Area · Result · Notes table, with long logs in nested collapsed blocks. Skipped rows don't count as passed. - **When to re-run:** a full run for commits that change the PR's content, a light run (version lines, JS syntax, boot) after a `master` merge or renumber. Each run replaces the section in place, so the SHA in its title shows whether the checks match the latest commit. -- **Earlier "Test results" comments and CHANGELOG entries are left as they are.** +- **Open PRs moved to the layout (2026-11-04):** each one's earlier results went, unchanged and not re-run, into a collapsed "Automated checks: earlier run, not re-run" section, and the old "Test results" comments were deleted. Earlier CHANGELOG entries are left as they are. - Version: v1.10.6–v1.10.9 are already used by open PRs #22, #52, #61, #62 and #63, so this takes v1.10.10. Whichever merges later renumbers if needed (§0). --- diff --git a/CLAUDE.md b/CLAUDE.md index fa487af..a4f199a 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -56,7 +56,7 @@ A passing "Automated checks" title means the automated checks passed. It never m | No commit (description or comment edits only) | No | — | The SHA in the section's title should always match the branch's latest commit. If it doesn't, the PR hasn't been checked at its current state. -- **Earlier results stay as they are.** "Test results" comments and description sections written before this rule are a record of past runs and are not rewritten. A PR that gets a new run moves to this layout from that run on. +- **Results from before this rule** were moved, unchanged and not re-run, into each open PR's "Automated checks" section on 2026-11-04, titled `Automated checks: earlier run, not re-run · ` (or `commit not recorded`), and the old "Test results" comments were deleted. They stay in their original free-form format until the PR's next run replaces them with the table. - The `Generated by` footer stays last in the description. ### Stacked PRs