Skip to content

chore(ledger): reconcile 24 inbox requests; queue #8Y9169/#WWTRM5 wording fixes and the #8CKX6F ruling - #3624

Closed
BigSimmo wants to merge 9 commits into
mainfrom
chore/issues-reconcile-20261018
Closed

BigSimmo wants to merge 9 commits into
mainfrom
chore/issues-reconcile-20261018

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Oct 17, 2026 •

Copy link
Copy Markdown
Owner

User description

Reconciles the 24 inbox requests pending on main, following the documented flow: a fresh branch from origin/main, then issues:reconcile -- --dry-run, then issues:reconcile. This includes #3618's #WFYDV6 reopen (now #Z12CBC), the #8Y9169 correction, and the P3 reopen-action task (now #GYR7Q3).

It also queues three new requests through the ledger tool, to be applied at the next reconcile:

  • update #8Y9169: the /mockups/development pages are reachable. /admin/developer-hub links to clinical-answer-failures, and the owner panel links to clinical-sign-off, so they are not dead code.
  • update #WWTRM5: drops two items the code contradicts. coding-workflow.md:21 is about continuing same-task work, not a worktree rule, and the renewals tests still assert "Not checked with issuers".
  • update #8CKX6F: owner ruling 18 Oct 2026 00:10 AWST. National youth crisis lines stay unpinned until the owner approves the list, and closed or unavailable services must be excluded.

The competing branch fix/wfydv6-reopen-20261017 (closed #3616) was deleted on the owner's go-ahead. Its tip b6afc6f is still reachable at refs/pull/3616/head.

Checks: ledger write discipline, outstanding-issues, organisation and the repo-awareness snapshot.


Summary by cubic

Reconciles the 24 pending inbox requests into the outstanding-issues ledger, moves the applied request files into applied/, and refreshes both snapshots. Also queues new requests for the next reconcile and adds a supersede subcommand to scripts/branch-review-ledger.mjs for sanctioned branch-record corrections.

Queued Requests

  • #8Y9169: marks the /mockups/development pages as reachable from /admin/developer-hub and the owner panel, so they are not dead code.
  • #WWTRM5: drops two doc-drift items that the code contradicts.
  • #8CKX6F: records the owner ruling that national youth crisis lines stay unpinned until approved, excluding closed or unavailable services.
  • #54N8ZN, #2X90V6, and a new P3 task: restore print-media verification, correct a branch-review record via the supersede workflow, and track the missing CRAFT citation locator.
  • #WWV98H, #YJXRS3, #BDFFYF: retire duplicates, consolidating their verified work into #WWTRM5, #8Y9169, and #Z12CBC.

Written for commit 834042b. Summary will update on new commits.

View guided diff Turn on auto-fix


CodeAnt-AI Description

Reconcile the issue ledger and record updated owner decisions

What Changed

  • Applied 24 pending issue requests, moving completed work out of the active list and updating open issue details.
  • Reopened the WA MHA Form 6A/6B issue as a high-priority item; the form remains unwired until legal and clinical sign-off.
  • Corrected the record for reachable developer pages and queued clarifications, including the decision to keep national youth crisis lines unpinned until approved.
  • Refreshed the outstanding-issues and repository-awareness snapshots.

Impact

✅ Completed work removed from the active issue list
✅ WA MHA forms stay unwired pending sign-off
✅ National youth crisis lines remain unpinned pending approval

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.


Summary by Gitar

  • Ledger tooling:
    • Added supersede subcommand to scripts/branch-review-ledger.mjs to write corrected immutable records
  • Therapy sources:
    • Replaced CRAFT references in src/data/therapies-source.json with PMID-linked citation details

This will update automatically on new commits.

…CKX6F owner ruling

- #8Y9169: the /mockups/development pages are reachable from /admin/developer-hub
  and the owner panel, so they are not dead code
- #WWTRM5: drop items 2 and 5, which the code contradicts
- #8CKX6F: national youth crisis lines stay unpinned until the owner approves
  the list (ruling 18 Oct 2026 00:10 AWST); exclude closed or unavailable services
@supabase

supabase Bot commented Oct 17, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BigSimmo has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-17T16:14:34.624709Z f4bd0f7 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@codeant-ai

codeant-ai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR f4bd0f7 Oct 17, 2026 · 16:12 16:21

@codeant-ai

codeant-ai Bot commented Oct 17, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@BigSimmo
BigSimmo enabled auto-merge (squash) October 17, 2026 16:12
@coderabbitai

coderabbitai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Next included review available in 22 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available. Your 63 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Repository: BigSimmo/PsychSift/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Team
  • Run ID: 7d71b310-3628-46d2-b006-576ae9c2b39a
📥 Commits

Reviewing files that changed from the base of the PR and between 7ff341d and 1e98d59.

📒 Files selected for processing: 38
  • data/outstanding-issues-snapshot.json
  • data/repo-awareness-snapshot.json
  • docs/outstanding-issues-inbox/23456bfc-5a5e-4dcb-946d-c099165824bb.json
  • docs/outstanding-issues-inbox/3b76119a-afbd-47cc-b499-39213f31bb02.json
  • docs/outstanding-issues-inbox/3f1a7c9e-52d8-4b60-a843-6e9c2d5f7184.json
  • docs/outstanding-issues-inbox/5e8b3c17-2d94-46fa-a701-9c6f4b2d8e35.json
  • docs/outstanding-issues-inbox/6b2e9c4f-7a15-4d83-b061-5f8e2c1a9470.json
  • docs/outstanding-issues-inbox/7a4c2e19-83d6-4f50-b927-1e6a8c3d5f72.json
  • docs/outstanding-issues-inbox/8c4e1a7b-6d92-45f0-b3a8-2e7c9d1f5460.json
  • docs/outstanding-issues-inbox/9d2a1f4e-6b83-4c91-a5d8-2f7e9b1c4d60.json
  • docs/outstanding-issues-inbox/applied/15a11955-9ee3-4c86-ad8f-faa0af2a342c.json
  • docs/outstanding-issues-inbox/applied/177b7474-70f8-47a9-8299-8fdaf811c419.json
  • docs/outstanding-issues-inbox/applied/2ac34c8e-5b51-4a81-9126-1ec91ced63e5.json
  • docs/outstanding-issues-inbox/applied/34ed6c81-2113-45c6-8192-926f1add2c67.json
  • docs/outstanding-issues-inbox/applied/38224881-4405-4290-9248-12af6da757f6.json
  • docs/outstanding-issues-inbox/applied/3dcc07cc-77f4-41e6-bddc-52c16e8cb873.json
  • docs/outstanding-issues-inbox/applied/42088048-99df-45e5-8e16-5853c30a5850.json
  • docs/outstanding-issues-inbox/applied/45061e02-b8af-44d5-9279-1507db31931a.json
  • docs/outstanding-issues-inbox/applied/4fa31286-efac-46a9-8951-bc2dd5200a41.json
  • docs/outstanding-issues-inbox/applied/5b138aaf-016f-4fc3-8165-fd6b10f15a79.json
  • docs/outstanding-issues-inbox/applied/7c0377e7-899c-45d6-9f9f-94b54d8539ff.json
  • docs/outstanding-issues-inbox/applied/9288123e-b7af-460f-8374-5baef100481f.json
  • docs/outstanding-issues-inbox/applied/a5c25ca4-4fa3-421f-a944-35621169e55e.json
  • docs/outstanding-issues-inbox/applied/b1de924a-2e5b-4c0f-83d2-d9372a67aa15.json
  • docs/outstanding-issues-inbox/applied/b26640a5-b323-44ef-9a5c-9be3fc5ac3e0.json
  • docs/outstanding-issues-inbox/applied/c0471211-f9b1-44e4-bb54-8b1d5664c5f4.json
  • docs/outstanding-issues-inbox/applied/c455b372-522a-4894-b87c-4fd7827b61bb.json
  • docs/outstanding-issues-inbox/applied/c7323952-84fd-4a4b-b57b-99bdb81f394b.json
  • docs/outstanding-issues-inbox/applied/ca717f00-45fb-4610-8127-7e35b1597048.json
  • docs/outstanding-issues-inbox/applied/ec2c7d1d-0f7c-4f86-bf30-d2705a7b9431.json
  • docs/outstanding-issues-inbox/applied/ed0b610a-9920-4ffe-9e68-d451709e0c99.json
  • docs/outstanding-issues-inbox/applied/f25d2f0b-4522-42c8-9824-61100beb31c1.json
  • docs/outstanding-issues-inbox/applied/f8628e25-fe07-442f-9221-119b40e34213.json
  • docs/outstanding-issues-inbox/applied/fc8e9191-056d-4912-95ee-097581ed463d.json
  • docs/outstanding-issues-inbox/ba83e01e-38a3-4103-bec3-061f064824df.json
  • docs/outstanding-issues.md
  • scripts/branch-review-ledger.mjs
  • src/data/therapies-source.json
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@claude

claude Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Claude encountered an error after 2s —— View job


I'll analyze this and get back to you.

@qodo-code-review

Copy link
Copy Markdown
Contributor

PR Summary by Qodo

Reconcile 24 ledger requests and queue three corrections

📝 Documentation ⚙️ Configuration changes 🕐 40+ Minutes

Grey Divider

AI Description

• Reconciles 24 pending requests, updating open and resolved issues and archiving applied requests.
• Queues corrections to developer-page reachability, documentation drift, and youth crisis-line
 pinning.
• Refreshes issue and repo-awareness snapshots to reflect the reconciled ledger.
Diagram

graph TD
  Updates["Three updates"] --> Inbox["Request inbox"] --> Reconcile["Ledger reconciler"] --> Ledger["Issue ledger"] --> Snapshot["Issue snapshot"]
  Reconcile --> Applied["Applied archive"]
Loading
High-Level Assessment

Use the existing reconciler and inbox workflow. Directly editing the canonical ledger or applying the three later corrections prematurely would bypass request history and the distinction between applied and queued work.

Files changed (30) +151 / -104

Documentation (28) +60 / -13
23456bfc-5a5e-4dcb-946d-c099165824bb.jsonQueue owner ruling for #8CKX6F +12/-0

Queue owner ruling for #8CKX6F

• Queues an update keeping national youth crisis lines unpinned pending owner approval. It also specifies that future pinning exclude closed or unavailable services.

docs/outstanding-issues-inbox/23456bfc-5a5e-4dcb-946d-c099165824bb.json

3b76119a-afbd-47cc-b499-39213f31bb02.jsonQueue developer-page reachability correction +12/-0

Queue developer-page reachability correction

• Queues a correction to #8Y9169: developer pages have links from the developer hub and owner panel and should not be classified as dead code.

docs/outstanding-issues-inbox/3b76119a-afbd-47cc-b499-39213f31bb02.json

15a11955-9ee3-4c86-ad8f-faa0af2a342c.jsonArchive branch-record correction request +0/-0

Archive branch-record correction request

• Preserves the applied request to correct the recorded head branch for PR #3570 through sanctioned tooling.

docs/outstanding-issues-inbox/applied/15a11955-9ee3-4c86-ad8f-faa0af2a342c.json

177b7474-70f8-47a9-8299-8fdaf811c419.jsonArchive reopen-action task request +0/-0

Archive reopen-action task request

• Preserves the applied request for a ledger reopen action that would restore an archived issue's original ID and ULID.

docs/outstanding-issues-inbox/applied/177b7474-70f8-47a9-8299-8fdaf811c419.json

2ac34c8e-5b51-4a81-9126-1ec91ced63e5.jsonArchive MHA sign-off completion request +0/-0

Archive MHA sign-off completion request

• Preserves the applied closure of #6VPJ99 following sign-off of WA Mental Health Act forms, section summaries, and timeframes.

docs/outstanding-issues-inbox/applied/2ac34c8e-5b51-4a81-9126-1ec91ced63e5.json

34ed6c81-2113-45c6-8192-926f1add2c67.jsonArchive CME claim-pack closure request +0/-0

Archive CME claim-pack closure request

• Preserves the applied closure of #GR72PF after the claim-pack button became reachable from the CME annual summary.

docs/outstanding-issues-inbox/applied/34ed6c81-2113-45c6-8192-926f1add2c67.json

38224881-4405-4290-9248-12af6da757f6.jsonArchive PR #3538 leftover-work request +0/-0

Archive PR #3538 leftover-work request

• Preserves an applied follow-up for assessing remaining PR #3538 components after the dead-code review window.

docs/outstanding-issues-inbox/applied/38224881-4405-4290-9248-12af6da757f6.json

3dcc07cc-77f4-41e6-bddc-52c16e8cb873.jsonArchive chunking-regex closure request +0/-0

Archive chunking-regex closure request

• Preserves the applied closure of #BGDVPD after chunking regexes were precompiled and tested.

docs/outstanding-issues-inbox/applied/3dcc07cc-77f4-41e6-bddc-52c16e8cb873.json

42088048-99df-45e5-8e16-5853c30a5850.jsonArchive specifier sign-off status update +0/-0

Archive specifier sign-off status update

• Preserves the applied update recording signed-off written specifiers while retaining the outstanding unwritten placeholders.

docs/outstanding-issues-inbox/applied/42088048-99df-45e5-8e16-5853c30a5850.json

45061e02-b8af-44d5-9279-1507db31931a.jsonArchive registrar milestone closure request +0/-0

Archive registrar milestone closure request

• Preserves the applied closure of #XNAHY2 after owner-scoped milestone storage was connected to the Training page.

docs/outstanding-issues-inbox/applied/45061e02-b8af-44d5-9279-1507db31931a.json

4fa31286-efac-46a9-8951-bc2dd5200a41.jsonArchive corrected-source sign-off request +0/-0

Archive corrected-source sign-off request

• Preserves the applied closure of #4DFNHJ after six corrected sources received structured sign-off.

docs/outstanding-issues-inbox/applied/4fa31286-efac-46a9-8951-bc2dd5200a41.json

5b138aaf-016f-4fc3-8165-fd6b10f15a79.jsonArchive split leftover-work request +0/-0

Archive split leftover-work request

• Preserves the applied request that created #8Y9169 for work not covered by the archived calculator issue.

docs/outstanding-issues-inbox/applied/5b138aaf-016f-4fc3-8165-fd6b10f15a79.json

7c0377e7-899c-45d6-9f9f-94b54d8539ff.jsonArchive teaching authorization closure request +0/-0

Archive teaching authorization closure request

• Preserves the applied closure of #VDAXJX for the nullable-creator display-link revocation guard.

docs/outstanding-issues-inbox/applied/7c0377e7-899c-45d6-9f9f-94b54d8539ff.json

9288123e-b7af-460f-8374-5baef100481f.jsonArchive admin pilot follow-up update +0/-0

Archive admin pilot follow-up update

• Preserves the applied status update identifying the manual screen-reader check as the remaining admin-pilot work.

docs/outstanding-issues-inbox/applied/9288123e-b7af-460f-8374-5baef100481f.json

a5c25ca4-4fa3-421f-a944-35621169e55e.jsonArchive WA MHA form reopen request +0/-0

Archive WA MHA form reopen request

• Preserves the applied request creating the open P1 follow-up #Z12CBC because the unwired form lacks legal and clinical sign-off.

docs/outstanding-issues-inbox/applied/a5c25ca4-4fa3-421f-a944-35621169e55e.json

b1de924a-2e5b-4c0f-83d2-d9372a67aa15.jsonArchive Therapy Compass closure request +0/-0

Archive Therapy Compass closure request

• Preserves the applied closure of #NZ4X41 after references and clinician sign-off were recorded for the therapy profiles.

docs/outstanding-issues-inbox/applied/b1de924a-2e5b-4c0f-83d2-d9372a67aa15.json

b26640a5-b323-44ef-9a5c-9be3fc5ac3e0.jsonArchive documentation-drift follow-up request +0/-0

Archive documentation-drift follow-up request

• Preserves the applied request creating #WWTRM5 for residual ledger and decision-record drift.

docs/outstanding-issues-inbox/applied/b26640a5-b323-44ef-9a5c-9be3fc5ac3e0.json

c0471211-f9b1-44e4-bb54-8b1d5664c5f4.jsonArchive calculator-mockup audit request +0/-0

Archive calculator-mockup audit request

• Preserves the applied request to assess older calculator mockups before any deletion.

docs/outstanding-issues-inbox/applied/c0471211-f9b1-44e4-bb54-8b1d5664c5f4.json

c455b372-522a-4894-b87c-4fd7827b61bb.jsonArchive first #8Y9169 clarification +0/-0

Archive first #8Y9169 clarification

• Preserves the applied correction distinguishing wired components and covered tests from potential PR #3538 deletion candidates. A newer inbox request further corrects developer-page reachability.

docs/outstanding-issues-inbox/applied/c455b372-522a-4894-b87c-4fd7827b61bb.json

c7323952-84fd-4a4b-b57b-99bdb81f394b.jsonArchive durable assessment closure request +0/-0

Archive durable assessment closure request

• Preserves the applied closure of #AD9JC6 after durable dual-sign-off storage and supervisor booking endpoints were recorded.

docs/outstanding-issues-inbox/applied/c7323952-84fd-4a4b-b57b-99bdb81f394b.json

ca717f00-45fb-4610-8127-7e35b1597048.jsonArchive second WA MHA form follow-up +0/-0

Archive second WA MHA form follow-up

• Preserves the applied request for #BDFFYF, separately tracking legal and clinical sign-off or removal of the print component.

docs/outstanding-issues-inbox/applied/ca717f00-45fb-4610-8127-7e35b1597048.json

ec2c7d1d-0f7c-4f86-bf30-d2705a7b9431.jsonArchive timed mockup-removal request +0/-0

Archive timed mockup-removal request

• Preserves the applied follow-up to audit older calculator mockups after the dead-code candidate window.

docs/outstanding-issues-inbox/applied/ec2c7d1d-0f7c-4f86-bf30-d2705a7b9431.json

ed0b610a-9920-4ffe-9e68-d451709e0c99.jsonArchive remaining decision-drift request +0/-0

Archive remaining decision-drift request

• Preserves the applied request for a Caring Contacts decision update and other documentation follow-ups.

docs/outstanding-issues-inbox/applied/ed0b610a-9920-4ffe-9e68-d451709e0c99.json

f25d2f0b-4522-42c8-9824-61100beb31c1.jsonArchive retrieval-script closure request +0/-0

Archive retrieval-script closure request

• Preserves the applied closure of #YETFBJ after two protected retrieval scripts adopted the shared entrypoint guard.

docs/outstanding-issues-inbox/applied/f25d2f0b-4522-42c8-9824-61100beb31c1.json

f8628e25-fe07-442f-9221-119b40e34213.jsonArchive original WA MHA issue outcome amendment +0/-0

Archive original WA MHA issue outcome amendment

• Preserves the applied amendment explaining that archived #WFYDV6 remains unresolved and is tracked by a new open P1 row.

docs/outstanding-issues-inbox/applied/f8628e25-fe07-442f-9221-119b40e34213.json

fc8e9191-056d-4912-95ee-097581ed463d.jsonArchive production dual-sign-off closure request +0/-0

Archive production dual-sign-off closure request

• Preserves the applied closure of #AW8SRK after the assessment route was connected to durable storage with authorization protections.

docs/outstanding-issues-inbox/applied/fc8e9191-056d-4912-95ee-097581ed463d.json

ba83e01e-38a3-4103-bec3-061f064824df.jsonQueue documentation-drift correction +13/-0

Queue documentation-drift correction

• Queues an update removing two contradicted claims from #WWTRM5: the coding-workflow passage is not a worktree rule, and renewals tests still assert the stated wording.

docs/outstanding-issues-inbox/ba83e01e-38a3-4103-bec3-061f064824df.json

outstanding-issues.mdReconcile canonical open and resolved issue rows +23/-13

Reconcile canonical open and resolved issue rows

• Applies additions, closures, updates, and an archived-outcome amendment from the 24 pending requests. It records #WFYDV6's unresolved form risk under a new P1 identity and opens a task to support reopening with the original identity; the three newly queued corrections are not yet applied.

docs/outstanding-issues.md

Other (2) +91 / -91
outstanding-issues-snapshot.jsonRefresh structured issue counts and rows +90/-90

Refresh structured issue counts and rows

• Reflects the reconciled open and resolved issues, including the new P1 form-safety row and P3 reopen-tooling task. Counts now show 108 open and 806 resolved.

data/outstanding-issues-snapshot.json

repo-awareness-snapshot.jsonAdvance repo-awareness capture date +1/-1

Advance repo-awareness capture date

• Refreshes the snapshot's committed-at date to 18 October 2026 without changing its recorded route data.

data/repo-awareness-snapshot.json

Comment thread docs/outstanding-issues.md Resolved

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f4bd0f7f9b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/outstanding-issues.md Resolved
Comment thread docs/outstanding-issues.md Resolved
Comment thread docs/outstanding-issues.md Resolved
@codeant-ai codeant-ai Bot added the size:L This PR changes 100-499 lines, ignoring generated files label Oct 17, 2026
@codeant-ai

codeant-ai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

🏁 CodeAnt Quality Gate Results

Commit: 1e98d597
Scan Time: 2026-10-17 17:08:17 UTC

✅ Overall Status: PASSED

Quality Gate Details

Quality Gate Status Details
Secrets ✅ PASSED 0 secrets found
Duplicate Code ✅ PASSED 0.0% duplicated
SAST ✅ PASSED No security issues
Bugs ✅ PASSED Rating S: No bugs
IAC ✅ PASSED Rating S: No issues

View Full Results

@qodo-code-review

qodo-code-review Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

Grey Divider


Action required

No findings for this group


Remediation recommended

No findings for this group


Informational

No findings for this group

Grey Divider


Resolved findings

1. Form approval work is duplicated ✓ Resolved
Description
#BDFFYF creates a second open P1 issue for the Form 6A/6B component and the sign-off-or-removal
decision already tracked by #Z12CBC. Because both rows cover the same unresolved statutory details
and owner action, they can be worked or closed independently, splitting progress across two issue
identities.
Code

docs/outstanding-issues.md[187]

+| #BDFFYF <!-- issue-ulid:01M54ZYAB6BDFFYFA3ZA5MNPVB --> | P1 | issue | WA MHA Form 6A/6B print component: obtain legal/clinical sign-off or remove after 13 Nov 2026 (follow-up to #WFYDV6) | PR #3573 replaced official Department of Health branding with non-statutory study headers and corrected Form 6B report wording in src/components/forms/wa-mha-form-print.tsx, but the unverified statutory section lists, 7-day pre-expiry examination timing, and copy recipients still require either verified WA MHA 2014 legal/clinical sign-off or component removal after the 30-day dead-code window on 2026-11-13. | PR #3609 review; follow-up to #WFYDV6; src/components/forms/wa-mha-form-print.tsx | 2026-10-17 |
Relevance

●●● Strong

Both rows track the same Form 6A/6B component and identical sign-off-or-removal decision,
duplicating open governance work.

PR-#2329
PR-#3573

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The ledger skill requires open rows to be deduplicated by intent. Both rows name the same component,
unresolved statutory details, and legal or clinical sign-off or post-window removal action; the
separate reopen-tooling row also identifies split issue identities as a problem to repair.

docs/outstanding-issues.md[184-187]
docs/outstanding-issues.md[181-187]
src/components/forms/wa-mha-form-print.tsx[61-68]
Skill: ledger

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Two open P1 identities track the same Form 6A/6B sign-off or removal decision.

## Fix Focus Areas
- docs/outstanding-issues.md[184-187]

## Recommended Fix
Keep #Z12CBC as the surviving reopened issue, preserving the owner ruling and statutory-text concerns in its detail. Queue a sanctioned done request for #BDFFYF that references #Z12CBC, and apply it through the next serialized reconciliation rather than editing either canonical row directly.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


2. Live pages face deletion ✓ Resolved
Description
#YJXRS3 directs cleanup to delete development pages and labels wired features as unwired,
contradicting the queued correction to the overlapping #8Y9169 row. After the dead-code window,
following #YJXRS3 could remove pages linked from the developer hub and owner panel and overlook
the rendered note editor and teaching helpers.
Code

docs/outstanding-issues.md[182]

+| #YJXRS3 <!-- issue-ulid:01M54ZYA19YJXRS380P791XA0P --> | P3 | task | Remove remaining PR 3538 leftovers after 13 Nov 2026 (follow-up to #08216B) | After the 30-day dead-code candidate window (2026-11-13), delete or wire the remaining PR 3538 leftovers flagged in #08216B: /api/proxy route (remove or restrict to an explicit allowlist), scripts/recalculate-answer-support-labels.ts (replace regex chunk-tag stripping with shared parser or delete), src/app/mockups/development/* pages, and unwired safe-number editor / attendance roster / QR helper / note editor privacy review. | PR #3609 review; follow-up to #08216B | 2026-10-17 |
Relevance

●●● Strong

The sibling cleanup rows conflict, and recent ledger precedent supports splitting or correcting
residual work instead of leaving duplicates.

PR-#3573
PR-#2329

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The ledger skill calls for deduplication by intent and updates to an existing row rather than a
second open row. The two new rows address the same cleanup but give opposing instructions: the
queued correction to #8Y9169 reverses the development-page deletion instruction, links from the
developer hub and owner panel show those pages are reachable, and application components render the
note editor and teaching helpers.

docs/outstanding-issues.md[182-183]
docs/outstanding-issues-inbox/3b76119a-afbd-47cc-b499-39213f31bb02.json[7-10]
src/app/(admin)/admin/developer-hub/page.tsx[142-142]
src/components/developer-area/hub/owner-today-section.tsx[173-173]
src/components/developer-area/hub/owner-today-section.tsx[129-173]
src/components/on-call/handover/handover-page.tsx[1048-1069]
Skill: ledger

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`#YJXRS3` duplicates `#8Y9169`, directs deletion of reachable development pages, and mislabels wired features as unwired despite the queued correction to the adjacent row.

## Fix Focus Areas
- docs/outstanding-issues.md[182-183]
- docs/outstanding-issues-inbox/3b76119a-afbd-47cc-b499-39213f31bb02.json[7-10]

## Recommended Fix
Keep the queued correction to `#8Y9169` and use the sanctioned ledger workflow to queue a done request for `#YJXRS3` that references `#8Y9169` as the surviving task. Preserve the links and wired-feature findings in that row, assess any page consolidation separately from dead-code deletion, and apply the request in the next serialized reconciliation; do not hand-edit the canonical ledger or immutable requests.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


3. False documentation work stays open ✓ Resolved
Description
#WWV98H retains the cloud-profile worktree-rule change and admin-renewals wording decision that
the queued correction to #WWTRM5 explicitly drops after checking the instruction and tests.
Because both rows remain open, reconciling the correction to #WWTRM5 still leaves those rejected
tasks available for maintainers to pick up from #WWV98H.
Code

docs/outstanding-issues.md[189]

+| #WWV98H <!-- issue-ulid:01M54ZYADRWWV98H3N76EDCNCT --> | P3 | issue | Complete remaining doc/decision drift items from #WMGPSG | Follow-up to #WMGPSG for the remaining documentation and decision-record items: (1) add a superseding decision next to docs/decisions/2026-09-26-remove-ward-flow-and-caring-contacts.md covering live src/lib/caring-contacts/clock.ts, (2) record the admin renewals wording decision, (3) document the cloud-profile worktree rule, and (4) replace the mojibake arrow on docs/outstanding-issues.md:15 during a canonical ledger header maintenance pass. | PR #3609 review; follow-up to #WMGPSG | 2026-10-17 |
Relevance

●●● Strong

Queued correction drops two tasks, but sibling row still preserves them, leaving contradictory
duplicate instructions active.

PR-#3573
PR-#2509

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The ledger skill says to deduplicate by intent and put new information on the existing row.
#WWV98H repeats the original follow-up tasks, including the two that the queued correction to
#WWTRM5 rejects; updating only #WWTRM5 will therefore leave the sibling row unchanged.

docs/outstanding-issues.md[185-189]
docs/outstanding-issues-inbox/ba83e01e-38a3-4103-bec3-061f064824df.json[7-11]
docs/outstanding-issues-inbox/ba83e01e-38a3-4103-bec3-061f064824df.json[7-10]
Skill: ledger

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`#WWV98H` duplicates `#WWTRM5` and preserves two tasks rejected by the queued correction. Consolidate the follow-ups so the verified remaining work survives without the cloud-profile or renewals items.

## Fix Focus Areas
- docs/outstanding-issues.md[185-189]
- docs/outstanding-issues-inbox/ba83e01e-38a3-4103-bec3-061f064824df.json[7-11]

## Recommended Fix
Use the ledger tooling to queue a sanctioned done request for `#WWV98H` that points to `#WWTRM5` as the surviving, corrected issue. Apply it through a subsequent serialized reconciliation, ensuring the surviving row carries only the verified remaining work; do not edit the canonical ledger or existing inbox files by hand.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


View resolved (3)
4. The branch correction has no tool path ✓ Resolved
Description
#2X90V6 requires correcting an immutable branch-review record through sanctioned tooling and
forbids editing the record directly. The tool offers no correction operation and writes records with
exclusive-create semantics, so following the row's prescribed path cannot replace the incorrect
branch name.
Code

docs/outstanding-issues.md[180]

+| #2X90V6 <!-- issue-ulid:01M551BST62X90V6VK3DEP4C7S --> | P3 | task | Ledger correction: PR #3570 prlanded record names the wrong branch | docs/branch-review-records/a7be2760026da4bc040fa90bf847382bdcded2a8a7510ceaf7be4ac49c042211.record.md (added by PR #3609) records branch claude/reconcile-inbox-20261016 for PR #3570, but gh shows #3570's head branch was claude/reconcile-ledger-20261016 (merge fa526775c6, head d8eefbb91e). The SHAs and merge state are correct. Correct the branch name through the sanctioned branch-review-ledger tooling only; never hand-edit the record. | PR #3609 sweep proof verification, 17 Oct 2026 | 2026-10-17 |
Relevance

●●● Strong

Immutable-record precedents require a sanctioned superseding correction path rather than an
impossible direct edit.

PR-#2228
PR-#2250

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The tool documents lookup, append, migration, deduplication and rotation but no edit or correction
command. Its immutable-record write rejects differing content at an existing record path.

docs/outstanding-issues.md[180-180]
scripts/branch-review-ledger.mjs[12-29]
scripts/branch-review-ledger.mjs[191-210]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The new ledger task requires an immutable record correction that the named tooling cannot perform.
## Fix Focus Areas
- docs/outstanding-issues.md[180-180]
- scripts/branch-review-ledger.mjs[12-29]
## Recommended Fix
Specify an authorized correction workflow that can supersede or repair the incorrect branch field, implementing tooling if necessary. Then update the task to name that executable workflow.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


5. Print verification disappears from the queue ✓ Resolved
Description
The amended #54N8ZN detail says only a manual screen-reader check remains, dropping the previously
outstanding print check against the current pilot-client digest. Its cited accessibility tests cover
other display conditions but contain no print-media check, so that work is no longer tracked.
Code

docs/outstanding-issues.md[177]

+| #54N8ZN <!-- issue-ulid:01M520SQ7T54N8ZNCFC7KJ4HKC --> | P2 | task | Follow-up to PR 3546: CodeRabbit items held out of the merge | PR #3546 landed; tests/xlsx-sheet-dictionary-projection.test.ts (4/4) verifies per-worksheet shared-string and row/column style dictionary projection within provenance budgets, and tests/admin-pilot-client-accessibility.dom.test.tsx (7/7) verifies native form semantics under dark and forced-colors modes, 320px narrow-viewport stacking, and QR enrollment alt/warning copy. Remaining: manual VoiceOver / NVDA screen-reader announcement check on /admin/pilot. | PR 3546 CodeRabbit review 5545295336, owner decision 2026-10-16 | 2026-10-16 |
Relevance

●●● Strong

Recent precedent accepted preserving unverified screen-reader work; omitted print checks remain
materially untracked.

PR-#3586

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The preceding applied update explicitly retained the current-digest print check. The tests cited by
the replacement detail cover dark and forced colours, narrow layout and QR copy, but not print.

docs/outstanding-issues-inbox/applied/d72ccad1-e17d-4928-a9c4-70a53cb9e67c.json[8-8]
tests/admin-pilot-client-accessibility.dom.test.tsx[146-264]
docs/outstanding-issues.md[177-177]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The ledger amendment removes an outstanding current-digest print verification without evidence that it was completed.
## Fix Focus Areas
- docs/outstanding-issues.md[177-177]
- data/outstanding-issues-snapshot.json[944-944]
## Recommended Fix
Keep print verification in the row's remaining work until a check against the current pilot-client digest is recorded. Make the change through the sanctioned ledger workflow.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


6. Therapy citations remain hard to trace ✓ Resolved
Description
The #NZ4X41 outcome closes the unsourced-record work as populated with governed references,
although some of the newly added records contain only prose source descriptions without a specific
source locator. For example, the CRAFT record names authors and years but supplies no article title
or identifier, leaving its clinical-literature claim difficult to verify from the recorded
reference.
Code

docs/outstanding-issues.md[1006]

+| #NZ4X41 <!-- issue-ulid:01M488JH90NZ4X41FZT2339F40 --> | task | Therapy catalogue: 22 of 47 unsourced records now carry NICE references and await sign-off, 25 still have none | Populated governed guideline and clinical literature references for the remaining 26 Therapy Compass records and completed clinician sign-off across all 205 Therapy Compass profiles. | 2026-10-17 |
Relevance

●● Moderate

Citation traceability is a legitimate concern, but available history lacks a close precedent for
rejecting this specific clinical record format.

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The closure asserts governed guideline and literature references for the remaining records. The
CRAFT record's newly added citation text names publications only by authors and year and stores the
text inside the uploaded-source entry, rather than providing a specific article title or identifier.

docs/outstanding-issues.md[1006-1006]
src/data/therapies-source.json[3109-3117]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The closure describes the remaining therapy references as governed even where the newly supplied source text lacks a reproducible bibliographic locator.
## Fix Focus Areas
- docs/outstanding-issues.md[1006-1006]
- src/data/therapies-source.json[3109-3117]
## Recommended Fix
Check the newly referenced records for identifiable source titles and locators. Keep the citation-detail work open, or record a separate follow-up for missing locators, before describing that work as complete.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Context sources
❌ Tickets: failed to load — Ticket collection could not establish complete evidence
✅ Compliance rules (platform): 9 rules
✅ Skills: 5 invoked
  review
  data
  ledger
  gates
  issues
✅ Cross-repo context — repo relationships
✅ REVIEW.md
Review mode: Auto: ⚖️ Balanced: Ledger reconciliation spans many records with consistency and auditability risks.

Grey Divider

Tip of the day
💡 Did you know, you can see how risky a PR is at a glance with blast radius labels

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Comment thread docs/outstanding-issues.md Resolved
Comment thread docs/outstanding-issues.md Resolved
Comment thread docs/outstanding-issues.md Resolved
Comment thread docs/outstanding-issues.md Resolved
Comment thread docs/outstanding-issues.md Resolved
Comment thread docs/outstanding-issues.md Resolved
@qodo-code-review

Copy link
Copy Markdown
Contributor

Qodo Fixer

✅ Committed (6) · ☑ Fixed (6)

Grey Divider

Commits pushed directly to this PR — no separate fix PR opened.

Process — 6 fixed
  • ☑ Fixed: Form approval work is duplicated
  • ☑ Fixed: Live pages face deletion
  • ☑ Fixed: False documentation work stays open
  • ☑ Fixed: The branch correction has no tool path
  • ☑ Fixed: Print verification disappears from the queue
  • ☑ Fixed: Therapy citations remain hard to trace

Comment thread scripts/branch-review-ledger.mjs Resolved
@gitar-bot

gitar-bot Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor
CI failed: Both CI jobs fail on the same syntax error: a malformed regular expression at scripts/branch-review-ledger.mjs:544 breaks TypeScript checking and Node module loading. Whether this PR introduced that line is unclear from the supplied context.

Overview

Two unique error templates across 2 logs, both pointing to the same malformed regex at scripts/branch-review-ledger.mjs:544. The production build compiles, but type checking fails, and a separate Node module load fails during dependency install. Overall the failure is a single script syntax error, not an infrastructure problem.

Failures

Malformed regular expression in scripts/branch-review-ledger.mjs:544 (confidence: high)

  • Type: build
  • Affected jobs: 117443202040, 117443202045
  • Related to change: unclear
  • Root cause: Line 544 contains record.replace(/^\/+/, ""). TypeScript reports TS1161 (unterminated regex literal) in the build job, and Node reports SyntaxError: Invalid regular expression: missing / in the install job. The PR modifies this file, but the supplied context does not show whether this specific line was edited.
  • Suggested fix: Correct the regex so the slash is escaped properly, for example /^\/+/ should become /^\/+/ with the intended escaping verified, or simply /^\/+/ written as /^\/+/g if needed. Then run node --check scripts/branch-review-ledger.mjs and tsc locally to confirm.

Summary

  • Change-related failures: None confirmed. The failing file is touched by this PR, so the relationship is unclear rather than established.
  • Infrastructure/flaky failures: None. Both failures are deterministic syntax errors.
  • Recommended action: Fix the regex at line 544 of scripts/branch-review-ledger.mjs, confirm the file parses with node --check, then rerun CI. Check whether the line was changed in this PR to determine if it is a regression introduced here.
Code Review ✅ Approved 3 closed / 3 findings

🟡 Medium risk · The new supersede command writes immutable branch-review records, so an incorrect corrected ref could persist misleading audit history.

Reconciles 24 pending inbox requests into the outstanding-issues ledger and queues wording fixes for #8Y9169, #WWTRM5 and the #8CKX6F owner ruling; the PR is blocked. A critical SyntaxError in scripts/branch-review-ledger.mjs (over-escaped regex at line 544, plus \n in log messages at lines 581 and 587) prevents the module from loading, which breaks lookup, append, rotate, --self-test and the new supersede command.

The #8CKX6F national youth crisis line ruling exists only as an unapplied inbox JSON update, with no docs/decisions/ entry added in this PR, so it cannot be found through the decisions index. Add the decision entry, point the ledger row at it, and run npm run check:decisions.

✅ 3 closed
✅ Bug: Duplicate open rows still carry the corrections queued for #8Y9169/#WWTRM5

📄 docs/outstanding-issues.md:182-189 📄 data/outstanding-issues-snapshot.json:985-999 📄 docs/outstanding-issues-inbox/3b76119a-afbd-47cc-b499-39213f31bb02.json:8 📄 docs/outstanding-issues-inbox/ba83e01e-38a3-4103-bec3-061f064824df.json:9
The reconcile left paired rows open for the same work: #YJXRS3 duplicates #8Y9169, #WWV98H duplicates #WWTRM5, #BDFFYF duplicates #Z12CBC, and #GKAEZS duplicates #C4Q3T7. The new requests correct only one row of each pair. After the next reconcile, #YJXRS3 will still say to delete src/app/mockups/development/*, and #8Y9169 will say those pages are not dead code because /admin/developer-hub and the owner panel link to them. #WWV98H will also still list the cloud-profile worktree rule and the renewals wording, the two items this PR drops from #WWTRM5 as contradicted by the code. An agent working from #YJXRS3 or #WWV98H would act on the instructions this PR retracts, and could delete reachable pages. Queue done/cancel requests that fold #YJXRS3, #WWV98H, #BDFFYF and #GKAEZS into their twins, or apply the same corrections to them.

Closed: Bug: Over-escaped regex is a SyntaxError that breaks the whole ledger script

📄 scripts/branch-review-ledger.mjs:544 📄 scripts/branch-review-ledger.mjs:581 📄 scripts/branch-review-ledger.mjs:587
Line 544 reads record.replace(/^\/+/, ""). Because the backslash is doubled, the regex literal closes at /^\/ and the trailing +/, "") starts a regex that never closes. node --check scripts/branch-review-ledger.mjs fails with SyntaxError: Invalid regular expression: missing /. The module therefore can't load at all: lookup, append, rotate, --self-test and the new supersede command all fail, along with anything that imports this module. That includes the sanctioned workflow that inbox request #2X90V6 tells people to run. Lines 581 and 587 have the same over-escaping: \n in their template literals prints a literal where a newline should be. The fix is to use /^\/+/ on line 544 and in both log messages.

Closed: Quality: #8CKX6F owner ruling is only queued; no docs/decisions entry

📄 docs/outstanding-issues-inbox/23456bfc-5a5e-4dcb-946d-c099165824bb.json:8
The 18 Oct 00:10 AWST owner ruling (don't pin national youth crisis lines until the owner approves the list; exclude closed, planned, superseded or unavailable services; keep CAMHS Crisis Connect and MHERL first) exists only as a queued inbox update. docs/agents/native-startup/recording-decisions.md says a decision isn't recorded until it has a docs/decisions/ entry, added in the same PR. This PR adds none: there is no 2026-10-18-* file, and the related 2026-09-25-youth-crisis-wording-shows-both-lines.md is unchanged. Until the next reconcile runs, the ruling exists only in an unapplied JSON file, and no tool can find it through the decisions index. Add a decision entry citing the owner (in chat), point the ledger row at it, and run npm run check:decisions.

Verification

Rules No rules evaluated

Functional validation Not enabled

Set up

Auto-approval Approved

For more verification details, comment gitar display:verbose.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Important

Your trial ends in 4 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more.

Was this helpful? React with 👍 / 👎 | Gitar

@codeant-ai

codeant-ai Bot commented Oct 17, 2026

Copy link
Copy Markdown

CodeAnt Nitpicks

1 code suggestion

1. This adds a second P1 issue for the same Form 6A/6B sign-off-or-removal work already open as #Z12CBC, splitting one action across two IDs.

Code quality · data/outstanding-issues-snapshot.json:1033-1034

@codeant-ai

codeant-ai Bot commented Oct 17, 2026

Copy link
Copy Markdown

CodeAnt PR Risk: Medium Risk

  • The PR needs attention before merging because the ledger says to remove developer pages, while its accompanying update says they are linked and must not be deleted.
  • The specifier update names “Psych Sift” as the signer, but the retained governance rule requires a named clinician, leaving the approval record ambiguous.

Assessed commit: 1e98d5971a30

@BigSimmo

Copy link
Copy Markdown
Owner Author

Superseded by a clean rebuild on branch chore/issues-reconcile-20261018b, from current main without qodo's six commits (hand-written inbox requests, a branch-review tooling change and a CRAFT citation edit). Main had also gained 7 new pending requests (#3617), so this reconcile was stale. The replacement PR link follows. This branch is kept as the preserved source.

@BigSimmo

Copy link
Copy Markdown
Owner Author

Superseded by #3625, a clean branch from main without qodo's six commits.

BigSimmo added a commit that referenced this pull request Oct 17, 2026
…ding fixes and the #8CKX6F ruling (replaces #3624) (#3625)

* chore(ledger): reconcile 31 pending inbox requests (2 cancellations)

Rebuilds closed #3624 cleanly from current main: the 24 requests it reconciled
plus 7 from #3617. #3624's branch is the verified preserved source.

* chore(ledger): queue wording fixes for #8Y9169 and #WWTRM5 and the #8CKX6F owner ruling

- #8Y9169: the /mockups/development pages are reachable from /admin/developer-hub
  and the owner panel, so they are not dead code
- #WWTRM5: drop items 2 and 5, which the code contradicts
- #8CKX6F: national youth crisis lines stay unpinned until the owner approves
  the list (ruling 18 Oct 2026 00:10 AWST); exclude closed or unavailable services

* chore: refresh repo-awareness snapshot

* fix: Correct the clozapine completion outcome

* fix: Require named-person timeframe sign-off

* fix: Protect reachable developer pages

* fix: Clarify the youth crisis pin ruling

* fix: Retract disproved documentation work

* Revert "fix: Retract disproved documentation work"

This reverts commit d07f92c.

* Revert "fix: Clarify the youth crisis pin ruling"

This reverts commit 39b6f52.

* Revert "fix: Protect reachable developer pages"

This reverts commit df646ff.

* Revert "fix: Require named-person timeframe sign-off"

This reverts commit aece867.

* Revert "fix: Correct the clozapine completion outcome"

This reverts commit f1513eb.

---------

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: qodo-code-review[bot] <151058649+qodo-code-review[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🟠 Medium blast radius size:L This PR changes 100-499 lines, ignoring generated files 🕐 40+ Minutes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant