Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Shorten the development transparency page
rcourtmancff4a88189b0
diff --git a/docs/AI_TRANSPARENCY.md b/docs/AI_TRANSPARENCY.mdindex c6597fa64e..f9a0bf21aa 100644--- a/docs/AI_TRANSPARENCY.md+++ b/docs/AI_TRANSPARENCY.md@@ -1,165 +1,67 @@# Development and Automation Transparency-Pulse is maintained by me and developed with extensive automation, including-coding agents. This page is the standing disclosure for that process, so the-same explanation does not need to be repeated across every commit, release,-or issue thread.--## The short version--Automation contributes to code, tests, documentation, release notes, issue-triage, and routine repository maintenance. Routine changes may be-investigated, implemented, tested, and merged to `main` without line-by-line-human review. The continuously running maintainer does this within boundaries-I define.--I set the product direction and remain responsible for everything that ships.-The automated maintainer owns day-to-day maintenance and public issue replies;-releases follow the fixed train described below. I do not claim to have-personally written every line.-Automated changes must pass the applicable project tests and audit gates, and-released builds still go through Pulse's release qualification process.--## How it is used--- **Code and tests.** Coding agents implement and test changes from product,- architectural, issue, and operational requirements.-- **Maintenance.** Automation monitors project signals, investigates defects,- prepares fixes, and performs bounded routine repository work continuously.-- **Documentation and releases.** The maintainer prepares documentation and- changelogs. The release train builds, checks and publishes releases. Release- claims must stay consistent with the actual published source and checks.-- **Issue triage.** Automated issue and discussion replies post- under the dedicated `pulse-triage` bot identity and link back to this page.- Automated issue state changes use that identity as well, except those made- by the repository's own GitHub Actions workflows, which appear as- `github-actions[bot]`: silent version and form labels, and the alert issues- that scheduled checks open, update and close. Mixed reports follow- the [topic-integrity triage contract](ISSUE_TRIAGE.md): automation can surface- declared secondary topics, but a maintainer or triage agent must give every- actionable topic a linked disposition. Private support email is handled by- Richard, not the automated maintainer: it does not read a support mailbox or- send email. Keep credentials and private diagnostics out of public threads.-- **Change provenance.** Commits made by the continuously running maintainer- carry a dedicated bot author and committer identity. Issue-driven changes- link back to the originating report where applicable.--The link on an automated reply is intentionally understated. It makes the-process discoverable without turning every technical exchange into a banner-about how the work was produced. Individual commits, fixes, and release notes-are not given tool-specific labels.+Pulse is maintained by me and built with heavy use of coding agents. This page+explains how, so it doesn't need repeating in every commit, release or issue.++## Who does what++- **Coding agents** write code, tests and documentation from requirements I set.+- **The automated maintainer** runs continuously. It investigates bugs, prepares+ fixes, triages issues and replies on GitHub as `pulse-triage[bot]`, and its+ commits carry that identity. Repository workflows appear as+ `github-actions[bot]`. Each problem in a mixed report gets its own answer+ under the [triage contract](ISSUE_TRIAGE.md).+- **I** set product direction, decide what the automation may do, and answer+ for everything that ships. I don't claim to have written every line.++I handle private support email myself. The automated maintainer does not read+a support mailbox or send email. Keep credentials and private diagnostics out+of public threads.## How changes land and ship-Every change reaches `main` through a pull request, whoever or whatever wrote-it. Maintainer changes receive independent review and must pass the-repository's required checks before merging.-The `main` branch ruleset requires that for every writer, with no bypass, so-a red check blocks the maintainer and me alike. The maintainer's pull-requests are opened by `pulse-triage[bot]` and state what changed, why it-was needed, which reports or demand-ledger entries it answers, and what-validation was used, so the record on GitHub is the record of the decision.--Minor stable publication is targeted seven days after the last minor stable release. The-next minor release candidate becomes eligible one day earlier, reserving its-full 24-hour soak; preparation and qualification can move publication later.-It is cut from the head of `main` and carries everything on `main` at that cut,-not a selected set of fixes. Repairs go on `main`, not onto an older release-line. A stable patch does not restart the weekly minor clock.--A limited stable-patch path is being added for regressions in the current-stable release, security vulnerabilities and data loss. **As of 27 October 2026,-stable patches are not yet available.** Until enabled, repairs reach stable users-in a containing minor release. Once available, a patch starts from the current-stable and adds only eligible repairs already merged to `main`, plus release-metadata and publication support, not every unrelated change on `main`. It does-not delay or replace the weekly minor cycle. The `stable-regression` label does-not guarantee a patch or establish availability; see-[limited stable patches](RELEASE_PROCESS.md#limited-stable-patches).--Between stable releases, daily betas carry new changes from `main`; no beta is-cut within a day of the candidate being due. An important fix ships in the next-beta, not through an early candidate or stable release. Work merged during a-candidate's soak waits for the next cycle unless a `release-blocker` requires-a fresh candidate. A beta is not promoted to stable.--The candidate soaks for 24 hours on the opt-in preview channel, then is promoted-unchanged to stable unless an open issue labelled `release-blocker` stops-promotion. A candidate regression from the previous stable release or a release-failure is repaired on `main`; once the blockers are closed, the train cuts a-fresh candidate that carries the repair. Product changes are not inserted into the frozen candidate.-The promotion resolver in the release pipeline enforces the soak and the-exact-content rule. [Releases and update channels](RELEASE_PROCESS.md) describes-the train for users.--A fix merged to `main` is not yet a published fix. A published beta or release-candidate is available to preview users, not proof that stable users have it.-Issue replies name the containing version only after checking its actual-released source, and ask for a retest when appropriate. See the-[published releases](https://github.com/rcourtman/Pulse/releases) for available-versions; a source commit or a passing test alone does not establish availability.+Every change reaches `main` through a pull request. Maintainer changes receive+independent review, and every change must pass the repository's required checks+before merging. Nobody can bypass this, me included.++Releases follow a fixed weekly train: daily betas, then a release candidate that+soaks for 24 hours and is promoted unchanged to stable unless a `release-blocker`+issue stops it. Stable patches are not yet available, so fixes reach stable in+the next minor release; see [limited stable patches](RELEASE_PROCESS.md#limited-stable-patches).+Full rules: [Releases and update channels](RELEASE_PROCESS.md).++A fix merged to `main` is not yet a published fix. Replies name a version only+after checking its released source.## Issue resolution and retesting-A bug is resolved when the reporter confirms recovery, or the maintainer-reproduces the correction with no reported symptom left unresolved. A working-workaround, one recovered screen or a merged fix does not settle every part of-a mixed report. Other dispositions, such as a duplicate, need their own-explanation; a feature request's demand-ledger entry is not an implemented feature.--After a fix for every reported symptom ships in a stable release, the maintainer-names that version and asks for a retest in the original issue. That reply says-the issue will be closed after 14 days without a reply and can be reopened.-Normally, the 14 days start with that stable-release retest reply. If an earlier-retest request named a beta or release candidate carrying the same fix, and the-limit on repeated unanswered contact prevents another reply, count from the-later of that request and the stable release's publication. A beta or release-candidate alone never starts the timeout, nor does a fix commit. Only retest-when it is safe; do not repeat an outage, update or backup just to answer.--Only after at least 14 days without any reply from the reporter, and with no-other person reporting the same problem since that retest request, may the-issue be closed with a note and the-`closed-needs-retest-timeout` label. This is a retest timeout, **not confirmed-resolution**. It does not apply to feature requests, issues labelled-`needs-human`, or reports with an unfixed or unexplained symptom.--If the problem persists, or a close missed part of the report, comment on the-original issue rather than filing it again. Say which symptom remains and give-the version already observed, with any relevant [locally reviewed, redacted-evidence](TROUBLESHOOTING.md#collect-diagnostics-safely); unknown details are-valid and credentials stay private. Credible continuing failures or a mistaken-close are grounds to reopen the issue, not evidence to dismiss because it was closed.+An issue is resolved when the reporter confirms the fix, or the maintainer+reproduces it with no reported symptom left unresolved. A merged fix or a+workaround alone is not enough.-## Authority and responsibility+Once the fix ships in a stable release, the maintainer names that version and+asks for a retest. After 14 days with no reply, and nobody else reporting the+same problem, the issue may be closed with the `closed-needs-retest-timeout`+label. That is **not confirmed resolution**, and it can be reopened. Feature+requests, `needs-human` issues and unexplained symptoms are never closed this way.-The automated maintainer owns ordinary maintenance and public Pulse issue-replies under standing authority. These actions do not require my approval for-each change or comment. The release train publishes prereleases and stable-releases without per-release approval; it follows the cycle above rather than-having a model choose release scope, maturity or timing.+Still broken? Comment on the original issue rather than filing it again. Say+which symptom remains and which version you're on; add+[redacted diagnostics](TROUBLESHOOTING.md#collect-diagnostics-safely) if you+have them. Don't repeat an outage, update or backup just to retest.-Standing authority does not waive independent review, release qualification,-exact-candidate promotion, required soak, or verification after publication.-Public replies must follow the conversation and verified implementation and-release evidence. The maintainer must avoid repetitive unsolicited follow-ups.-I retain project ownership, product direction and the ability to revoke authority.+## Authority and responsibility-My role is to direct the project, design and maintain those boundaries,-monitor outcomes, and answer for the result. If an automated change is wrong,-it is still my bug and my responsibility to correct it.+The automated maintainer handles routine maintenance and issue replies without+asking me each time. The release train publishes on schedule without+per-release approval; no model chooses what goes in a release or when. None of+this skips review, soak or release checks. I can revoke that authority at any+time, and if an automated change is wrong, it's my bug to fix.## How the work should be judged-The relevant standard is the resulting software: whether a change is-understandable, maintainable, secure, covered by appropriate tests, and borne-out by real behaviour. Pulse's issue history, source, test gates, release-process, and corrections remain visible so specific concerns can be evaluated-on their merits.--This document describes the current standing policy. Older repository and-issue activity may predate it and may not carry the same link or identity.+By the software: is it correct, secure, tested and maintainable? The source,+issues, tests and releases are all public.-For what Pulse itself does with AI as a product, including Pulse Patrol,-Assistant, and MCP, see [AI.md](AI.md). Those features are separate from the-development process described here.+Older activity may predate this policy. For Pulse's own AI features, such as+Patrol and MCP, see [AI.md](AI.md).diff --git a/frontend-modern/public/docs/AI_TRANSPARENCY.md b/frontend-modern/public/docs/AI_TRANSPARENCY.mdindex c6597fa64e..f9a0bf21aa 100644--- a/frontend-modern/public/docs/AI_TRANSPARENCY.md+++ b/frontend-modern/public/docs/AI_TRANSPARENCY.md@@ -1,165 +1,67 @@# Development and Automation Transparency-Pulse is maintained by me and developed with extensive automation, including-coding agents. This page is the standing disclosure for that process, so the-same explanation does not need to be repeated across every commit, release,-or issue thread.--## The short version--Automation contributes to code, tests, documentation, release notes, issue-triage, and routine repository maintenance. Routine changes may be-investigated, implemented, tested, and merged to `main` without line-by-line-human review. The continuously running maintainer does this within boundaries-I define.--I set the product direction and remain responsible for everything that ships.-The automated maintainer owns day-to-day maintenance and public issue replies;-releases follow the fixed train described below. I do not claim to have-personally written every line.-Automated changes must pass the applicable project tests and audit gates, and-released builds still go through Pulse's release qualification process.--## How it is used--- **Code and tests.** Coding agents implement and test changes from product,- architectural, issue, and operational requirements.-- **Maintenance.** Automation monitors project signals, investigates defects,- prepares fixes, and performs bounded routine repository work continuously.-- **Documentation and releases.** The maintainer prepares documentation and- changelogs. The release train builds, checks and publishes releases. Release- claims must stay consistent with the actual published source and checks.-- **Issue triage.** Automated issue and discussion replies post- under the dedicated `pulse-triage` bot identity and link back to this page.- Automated issue state changes use that identity as well, except those made- by the repository's own GitHub Actions workflows, which appear as- `github-actions[bot]`: silent version and form labels, and the alert issues- that scheduled checks open, update and close. Mixed reports follow- the [topic-integrity triage contract](ISSUE_TRIAGE.md): automation can surface- declared secondary topics, but a maintainer or triage agent must give every- actionable topic a linked disposition. Private support email is handled by- Richard, not the automated maintainer: it does not read a support mailbox or- send email. Keep credentials and private diagnostics out of public threads.-- **Change provenance.** Commits made by the continuously running maintainer- carry a dedicated bot author and committer identity. Issue-driven changes- link back to the originating report where applicable.--The link on an automated reply is intentionally understated. It makes the-process discoverable without turning every technical exchange into a banner-about how the work was produced. Individual commits, fixes, and release notes-are not given tool-specific labels.+Pulse is maintained by me and built with heavy use of coding agents. This page+explains how, so it doesn't need repeating in every commit, release or issue.++## Who does what++- **Coding agents** write code, tests and documentation from requirements I set.+- **The automated maintainer** runs continuously. It investigates bugs, prepares+ fixes, triages issues and replies on GitHub as `pulse-triage[bot]`, and its+ commits carry that identity. Repository workflows appear as+ `github-actions[bot]`. Each problem in a mixed report gets its own answer+ under the [triage contract](ISSUE_TRIAGE.md).+- **I** set product direction, decide what the automation may do, and answer+ for everything that ships. I don't claim to have written every line.++I handle private support email myself. The automated maintainer does not read+a support mailbox or send email. Keep credentials and private diagnostics out+of public threads.## How changes land and ship-Every change reaches `main` through a pull request, whoever or whatever wrote-it. Maintainer changes receive independent review and must pass the-repository's required checks before merging.-The `main` branch ruleset requires that for every writer, with no bypass, so-a red check blocks the maintainer and me alike. The maintainer's pull-requests are opened by `pulse-triage[bot]` and state what changed, why it-was needed, which reports or demand-ledger entries it answers, and what-validation was used, so the record on GitHub is the record of the decision.--Minor stable publication is targeted seven days after the last minor stable release. The-next minor release candidate becomes eligible one day earlier, reserving its-full 24-hour soak; preparation and qualification can move publication later.-It is cut from the head of `main` and carries everything on `main` at that cut,-not a selected set of fixes. Repairs go on `main`, not onto an older release-line. A stable patch does not restart the weekly minor clock.--A limited stable-patch path is being added for regressions in the current-stable release, security vulnerabilities and data loss. **As of 27 October 2026,-stable patches are not yet available.** Until enabled, repairs reach stable users-in a containing minor release. Once available, a patch starts from the current-stable and adds only eligible repairs already merged to `main`, plus release-metadata and publication support, not every unrelated change on `main`. It does-not delay or replace the weekly minor cycle. The `stable-regression` label does-not guarantee a patch or establish availability; see-[limited stable patches](RELEASE_PROCESS.md#limited-stable-patches).--Between stable releases, daily betas carry new changes from `main`; no beta is-cut within a day of the candidate being due. An important fix ships in the next-beta, not through an early candidate or stable release. Work merged during a-candidate's soak waits for the next cycle unless a `release-blocker` requires-a fresh candidate. A beta is not promoted to stable.--The candidate soaks for 24 hours on the opt-in preview channel, then is promoted-unchanged to stable unless an open issue labelled `release-blocker` stops-promotion. A candidate regression from the previous stable release or a release-failure is repaired on `main`; once the blockers are closed, the train cuts a-fresh candidate that carries the repair. Product changes are not inserted into the frozen candidate.-The promotion resolver in the release pipeline enforces the soak and the-exact-content rule. [Releases and update channels](RELEASE_PROCESS.md) describes-the train for users.--A fix merged to `main` is not yet a published fix. A published beta or release-candidate is available to preview users, not proof that stable users have it.-Issue replies name the containing version only after checking its actual-released source, and ask for a retest when appropriate. See the-[published releases](https://github.com/rcourtman/Pulse/releases) for available-versions; a source commit or a passing test alone does not establish availability.+Every change reaches `main` through a pull request. Maintainer changes receive+independent review, and every change must pass the repository's required checks+before merging. Nobody can bypass this, me included.++Releases follow a fixed weekly train: daily betas, then a release candidate that+soaks for 24 hours and is promoted unchanged to stable unless a `release-blocker`+issue stops it. Stable patches are not yet available, so fixes reach stable in+the next minor release; see [limited stable patches](RELEASE_PROCESS.md#limited-stable-patches).+Full rules: [Releases and update channels](RELEASE_PROCESS.md).++A fix merged to `main` is not yet a published fix. Replies name a version only+after checking its released source.## Issue resolution and retesting-A bug is resolved when the reporter confirms recovery, or the maintainer-reproduces the correction with no reported symptom left unresolved. A working-workaround, one recovered screen or a merged fix does not settle every part of-a mixed report. Other dispositions, such as a duplicate, need their own-explanation; a feature request's demand-ledger entry is not an implemented feature.--After a fix for every reported symptom ships in a stable release, the maintainer-names that version and asks for a retest in the original issue. That reply says-the issue will be closed after 14 days without a reply and can be reopened.-Normally, the 14 days start with that stable-release retest reply. If an earlier-retest request named a beta or release candidate carrying the same fix, and the-limit on repeated unanswered contact prevents another reply, count from the-later of that request and the stable release's publication. A beta or release-candidate alone never starts the timeout, nor does a fix commit. Only retest-when it is safe; do not repeat an outage, update or backup just to answer.--Only after at least 14 days without any reply from the reporter, and with no-other person reporting the same problem since that retest request, may the-issue be closed with a note and the-`closed-needs-retest-timeout` label. This is a retest timeout, **not confirmed-resolution**. It does not apply to feature requests, issues labelled-`needs-human`, or reports with an unfixed or unexplained symptom.--If the problem persists, or a close missed part of the report, comment on the-original issue rather than filing it again. Say which symptom remains and give-the version already observed, with any relevant [locally reviewed, redacted-evidence](TROUBLESHOOTING.md#collect-diagnostics-safely); unknown details are-valid and credentials stay private. Credible continuing failures or a mistaken-close are grounds to reopen the issue, not evidence to dismiss because it was closed.+An issue is resolved when the reporter confirms the fix, or the maintainer+reproduces it with no reported symptom left unresolved. A merged fix or a+workaround alone is not enough.-## Authority and responsibility+Once the fix ships in a stable release, the maintainer names that version and+asks for a retest. After 14 days with no reply, and nobody else reporting the+same problem, the issue may be closed with the `closed-needs-retest-timeout`+label. That is **not confirmed resolution**, and it can be reopened. Feature+requests, `needs-human` issues and unexplained symptoms are never closed this way.-The automated maintainer owns ordinary maintenance and public Pulse issue-replies under standing authority. These actions do not require my approval for-each change or comment. The release train publishes prereleases and stable-releases without per-release approval; it follows the cycle above rather than-having a model choose release scope, maturity or timing.+Still broken? Comment on the original issue rather than filing it again. Say+which symptom remains and which version you're on; add+[redacted diagnostics](TROUBLESHOOTING.md#collect-diagnostics-safely) if you+have them. Don't repeat an outage, update or backup just to retest.-Standing authority does not waive independent review, release qualification,-exact-candidate promotion, required soak, or verification after publication.-Public replies must follow the conversation and verified implementation and-release evidence. The maintainer must avoid repetitive unsolicited follow-ups.-I retain project ownership, product direction and the ability to revoke authority.+## Authority and responsibility-My role is to direct the project, design and maintain those boundaries,-monitor outcomes, and answer for the result. If an automated change is wrong,-it is still my bug and my responsibility to correct it.+The automated maintainer handles routine maintenance and issue replies without+asking me each time. The release train publishes on schedule without+per-release approval; no model chooses what goes in a release or when. None of+this skips review, soak or release checks. I can revoke that authority at any+time, and if an automated change is wrong, it's my bug to fix.## How the work should be judged-The relevant standard is the resulting software: whether a change is-understandable, maintainable, secure, covered by appropriate tests, and borne-out by real behaviour. Pulse's issue history, source, test gates, release-process, and corrections remain visible so specific concerns can be evaluated-on their merits.--This document describes the current standing policy. Older repository and-issue activity may predate it and may not carry the same link or identity.+By the software: is it correct, secure, tested and maintainable? The source,+issues, tests and releases are all public.-For what Pulse itself does with AI as a product, including Pulse Patrol,-Assistant, and MCP, see [AI.md](AI.md). Those features are separate from the-development process described here.+Older activity may predate this policy. For Pulse's own AI features, such as+Patrol and MCP, see [AI.md](AI.md).diff --git a/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts b/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.tsindex 095d5dded0..3804fdf05d 100644--- a/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts+++ b/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts@@ -36,34 +36,22 @@ const prose = (element: Element): string => (element.textContent ?? '').replace(describe('public issue follow-through guidance', () => {it('keeps resolution, stable-release retest and timeout distinct in rendered paragraphs', () => {const paragraphs = followThrough().querySelectorAll('p');- expect(paragraphs).toHaveLength(4);+ expect(paragraphs).toHaveLength(3);expect(prose(paragraphs[0])).toContain('no reported symptom left unresolved');- expect(prose(paragraphs[1])).toContain('start with that stable-release retest reply');- expect(prose(paragraphs[1])).toContain('carrying the same fix');- expect(prose(paragraphs[1])).toContain(- 'limit on repeated unanswered contact prevents another reply',- );- expect(prose(paragraphs[1])).toContain(- "later of that request and the stable release's publication",- );- expect(prose(paragraphs[1])).toContain(- 'A beta or release candidate alone never starts the timeout, nor does a fix commit',- );- const emphasis = paragraphs[2].querySelector('strong');+ expect(prose(paragraphs[0])).toContain('A merged fix or a workaround alone is not enough');+ expect(prose(paragraphs[1])).toContain('Once the fix ships in a stable release');+ expect(prose(paragraphs[1])).toContain('After 14 days with no reply');+ expect(prose(paragraphs[1])).toContain('nobody else reporting the same problem');+ const emphasis = paragraphs[1].querySelector('strong');expect(emphasis).not.toBeNull();expect(prose(emphasis!)).toBe('not confirmed resolution');- expect(prose(paragraphs[2])).toContain('at least 14 days without any reply from the reporter');- expect(prose(paragraphs[2])).toContain(- 'no other person reporting the same problem since that retest request',- );- expect(prose(paragraphs[2])).toContain('an unfixed or unexplained symptom');+ expect(prose(paragraphs[1])).toContain('unexplained symptoms are never closed this way');});it('keeps the existing issue and safe evidence route usable without new collection', () => {const section = followThrough();expect(prose(section)).toContain('original issue rather than filing it again');- expect(prose(section)).toContain('unknown details are valid and credentials stay private');- expect(prose(section)).toContain('do not repeat an outage, update or backup');+ expect(prose(section)).toContain("Don't repeat an outage, update or backup");expect(section.querySelector('pre, form, input, button')).toBeNull();const link = section.querySelector('a');expect(link?.getAttribute('href')).toBe('/docs/TROUBLESHOOTING#collect-diagnostics-safely');@@ -86,14 +74,9 @@ describe('public issue follow-through guidance', () => {it('keeps the disclosure and its linked release guide on the weekly, no-early-cut policy', () => {const article = renderGuide('AI_TRANSPARENCY', source);const text = prose(article);- expect(text).toContain(- 'Minor stable publication is targeted seven days after the last minor stable release',- );- expect(text).toContain('one day earlier, reserving its full 24-hour soak');- expect(text).toContain(- 'An important fix ships in the next beta, not through an early candidate or stable release',- );- expect(text).toContain('unless a release-blocker requires a fresh candidate');+ expect(text).toContain('Releases follow a fixed weekly train');+ expect(text).toContain('soaks for 24 hours and is promoted unchanged to stable');+ expect(text).toContain('unless a release-blocker issue stops it');expect(text).not.toContain('Every 14 days');expect(text).not.toContain('An early cut can bring');expect(@@ -110,17 +93,17 @@ describe('public issue follow-through guidance', () => {expect(prose(release)).not.toContain('can bring');});- it('makes the unavailable patch path and limited contents explicit in both consumed guides', () => {- for (const name of ['AI_TRANSPARENCY', 'RELEASE_PROCESS']) {- const article = renderGuide(name, readGuide(name));- const text = prose(article);- expect(text).toContain('As of 27 October 2026, stable patches are not yet available');- expect(text).toContain('containing minor release');- expect(text).toContain('eligible repairs already merged to main');- expect(text).toContain('release metadata and publication support');- expect(text).toContain('stable-regression');- expect(text).not.toContain('Patch releases are not scheduled');- }+ it('makes the unavailable patch path explicit in both consumed guides', () => {+ expect(prose(renderGuide('AI_TRANSPARENCY', source))).toContain(+ 'Stable patches are not yet available',+ );+ const text = prose(renderGuide('RELEASE_PROCESS', readGuide('RELEASE_PROCESS')));+ expect(text).toContain('As of 27 October 2026, stable patches are not yet available');+ expect(text).toContain('containing minor release');+ expect(text).toContain('eligible repairs already merged to main');+ expect(text).toContain('release metadata and publication support');+ expect(text).toContain('stable-regression');+ expect(text).not.toContain('Patch releases are not scheduled');});it('links the public triage disclosure to the actual scoped patch guidance', () => {diff --git a/scripts/tests/test_transparency_docs.py b/scripts/tests/test_transparency_docs.pyindex f66ec30938..994a6dc475 100644--- a/scripts/tests/test_transparency_docs.py+++ b/scripts/tests/test_transparency_docs.py@@ -20,19 +20,15 @@ class TransparencyDocsTest(unittest.TestCase):for path in DOCUMENTS:yield path, " ".join(path.read_text(encoding="utf-8").split())- def test_all_main_minor_cycle_not_selective_backports(self):+ def test_disclosure_summarises_the_train_and_links_the_full_rules(self):for path, text in self.documents():with self.subTest(document=path):- self.assertIn("Minor stable publication is targeted seven days after the last minor stable release", text)- self.assertIn("next minor release candidate becomes eligible one day earlier", text)- self.assertIn("reserving its full 24-hour soak", text)- self.assertIn("preparation and qualification can move publication later", text)- self.assertIn("cut from the head of `main`", text)- self.assertIn("everything on `main` at that cut", text)- self.assertIn("Repairs go on `main`, not onto an older release line", text)- self.assertIn("An important fix ships in the next beta, not through an early candidate or stable release", text)- self.assertIn("no beta is cut within a day of the candidate being due", text)- self.assertIn("A stable patch does not restart the weekly minor clock", text)+ self.assertIn("Releases follow a fixed weekly train", text)+ self.assertIn("soaks for 24 hours and is promoted unchanged to stable", text)+ self.assertIn("unless a `release-blocker` issue stops it", text)+ self.assertIn("Stable patches are not yet available", text)+ self.assertIn("[limited stable patches](RELEASE_PROCESS.md#limited-stable-patches)", text)+ self.assertIn("[Releases and update channels](RELEASE_PROCESS.md)", text)self.assertNotIn("Patch releases are not scheduled", text)self.assertNotIn("takes only backports", text)self.assertNotIn("Every 14 days", text)@@ -54,16 +50,15 @@ class TransparencyDocsTest(unittest.TestCase):def test_patch_policy_is_not_claimed_as_available_delivery(self):for directory in ("docs", "frontend-modern/public/docs"):- for name in ("AI_TRANSPARENCY", "RELEASE_PROCESS"):- path = ROOT / directory / f"{name}.md"- text = " ".join(path.read_text(encoding="utf-8").split()).replace("**", "")- with self.subTest(document=path):- self.assertIn("As of 27 October 2026, stable patches are not yet available", text)- self.assertIn("stable-regression", text)- self.assertIn("eligible repairs already merged to `main`", text)- self.assertIn("release metadata and publication support", text)- self.assertIn("containing minor release", text)- self.assertNotIn("Patch releases are not scheduled", text)+ path = ROOT / directory / "RELEASE_PROCESS.md"+ text = " ".join(path.read_text(encoding="utf-8").split()).replace("**", "")+ with self.subTest(document=path):+ self.assertIn("As of 27 October 2026, stable patches are not yet available", text)+ self.assertIn("stable-regression", text)+ self.assertIn("eligible repairs already merged to `main`", text)+ self.assertIn("release metadata and publication support", text)+ self.assertIn("containing minor release", text)+ self.assertNotIn("Patch releases are not scheduled", text)def test_patch_guide_distinguishes_eligibility_cadence_and_safe_reporting(self):for directory in ("docs", "frontend-modern/public/docs"):@@ -84,75 +79,50 @@ class TransparencyDocsTest(unittest.TestCase):):self.assertIn(claim, text)- def test_blockers_need_a_fresh_candidate_not_a_changed_soak(self):- for path, text in self.documents():- with self.subTest(document=path):- self.assertIn("soaks for 24 hours", text)- self.assertIn("promoted unchanged to stable", text)- self.assertIn("open issue labelled `release-blocker`", text)- self.assertIn("candidate regression from the previous stable release", text)- self.assertIn("train cuts a fresh candidate that carries the repair", text)- self.assertIn("not inserted into the frozen candidate", text)-- def test_source_preview_and_stable_availability_are_separate(self):++ def test_merged_fix_is_not_a_published_fix(self):for path, text in self.documents():with self.subTest(document=path):self.assertIn("A fix merged to `main` is not yet a published fix", text)- self.assertIn("not proof that stable users have it", text)- self.assertIn("checking its actual released source", text)- self.assertIn("https://github.com/rcourtman/Pulse/releases", text)- self.assertIn("[Releases and update channels](RELEASE_PROCESS.md)", text)- self.assertIn("passing test alone does not establish availability", text)+ self.assertIn("only after checking its released source", text)def test_private_support_is_not_automated_or_public_diagnostics(self):for path, text in self.documents():with self.subTest(document=path):- self.assertIn("Private support email is handled by Richard", text)+ self.assertIn("I handle private support email myself", text)self.assertIn("does not read a support mailbox or send email", text)self.assertIn("Keep credentials and private diagnostics out of public threads", text)self.assertNotIn("Automated support replies are sent", text)- self.assertIn("[topic-integrity triage contract](ISSUE_TRIAGE.md)", text)+ self.assertIn("[triage contract](ISSUE_TRIAGE.md)", text)def test_resolution_needs_every_reported_symptom_not_a_component_pass(self):for path, text in self.documents():with self.subTest(document=path):- self.assertIn("reporter confirms recovery", text)+ self.assertIn("reporter confirms the fix", text)self.assertIn("no reported symptom left unresolved", text)- self.assertIn("one recovered screen or a merged fix", text)- self.assertIn("duplicate, need their own explanation", text)- self.assertIn("demand-ledger entry is not an implemented feature", text)+ self.assertIn("A merged fix or a workaround alone is not enough", text)def test_timeout_starts_with_containing_stable_release_contact(self):for path, text in self.documents():with self.subTest(document=path):- self.assertIn("fix for every reported symptom ships in a stable release", text)- self.assertIn("closed after 14 days without a reply and can be reopened", text)- self.assertIn("start with that stable-release retest reply", text)- self.assertIn("earlier retest request named a beta or release candidate carrying the same fix", text)- self.assertIn("limit on repeated unanswered contact prevents another reply", text)- self.assertIn("later of that request and the stable release's publication", text)- self.assertIn("A beta or release candidate alone never starts the timeout, nor does a fix commit", text)- self.assertIn("at least 14 days without any reply from the reporter", text)- self.assertIn("no other person reporting the same problem since that retest request", text)+ self.assertIn("Once the fix ships in a stable release", text)+ self.assertIn("After 14 days with no reply", text)+ self.assertIn("nobody else reporting the same problem", text)def test_timeout_is_not_confirmed_resolution_and_has_explicit_exclusions(self):for path, text in self.documents():with self.subTest(document=path):self.assertIn("`closed-needs-retest-timeout` label", text)self.assertIn("**not confirmed resolution**", text)- self.assertIn("does not apply to feature requests", text)- self.assertIn("issues labelled `needs-human`", text)- self.assertIn("an unfixed or unexplained symptom", text)+ self.assertIn("it can be reopened", text)+ self.assertIn("Feature requests, `needs-human` issues and unexplained symptoms are never closed this way", text)def test_contesting_a_close_preserves_the_report_and_safe_existing_evidence(self):for path, text in self.documents():with self.subTest(document=path):self.assertIn("original issue rather than filing it again", text)self.assertIn("which symptom remains", text)- self.assertIn("version already observed", text)- self.assertIn("unknown details are valid and credentials stay private", text)- self.assertIn("do not repeat an outage, update or backup", text)- self.assertIn("grounds to reopen the issue", text)+ self.assertIn("Don't repeat an outage, update or backup just to retest", text)self.assertIn("TROUBLESHOOTING.md#collect-diagnostics-safely", text)def test_standing_authority_preserves_review_and_mechanical_releases(self):@@ -161,7 +131,7 @@ class TransparencyDocsTest(unittest.TestCase):self.assertIn("Maintainer changes receive independent review", text)self.assertIn("must pass the repository's required checks before merging", text)self.assertIn("without per-release approval", text)- self.assertIn("rather than having a model choose release scope", text)+ self.assertIn("no model chooses what goes in a release or when", text)self.assertNotIn("maintainer chooses release scope, maturity and timing", text)self.assertNotIn("b64709e7b7ad174e9c94ad2a0d3d841678690935", text)