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

Merged
BI
1mo ago
+165-157

User description

Clean rebuild of closed #3624. Reconciles all 31 inbox requests pending on main (the 24 that #3624 covered plus 7 from #3617, including 2 cancellations), following the documented flow: a fresh branch from origin/main, then issues:reconcile -- --dry-run, then issues:reconcile, both with --preserved-source-pr 3624 --preserved-source-sha 1e98d5971a30f19fdf872f63d6c2781a2ff494c5. 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 b6afc6fb9 is still reachable at refs/pull/3616/head.

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

This leaves out all six qodo commits that were pushed to #3624 (owner decision): hand-written inbox requests, a branch-review tooling change, and the CRAFT citation edit. The duplicate closures will be re-queued through the ledger tool in a follow-up PR after this lands.

Summary by cubic

Reconciles all 31 pending inbox requests on main (24 from closed #3624 plus 7 from #3617, including 2 cancellations), then queues follow-up updates. Open issues drop from 108 to 105 and resolved rises to 809.

Queued updates

  • #8Y9169: the /mockups/development pages are reachable via /admin/developer-hub and the owner panel, so they are not dead code.
  • #WWTRM5: drops the worktree rule and renewals wording items, which the code contradicts.
  • #8CKX6F: national youth crisis lines stay unpinned until the owner approves the exact list; closed or unavailable services must be excluded.
  • #WFYDV6 stays open and unwired until legal and clinical sign-off.

Summary by CodeRabbit

  • Bug Fixes
    • Timeframe reviews now require sign-off by a named person; product names and role titles no longer count as reviewers.
    • Nine timeframes are marked as drafts, with prior review details cleared pending valid sign-off.
  • Documentation
    • Updated the outstanding-issues snapshot with current counts, statuses, and follow-up items.
    • Added and revised issue records to clarify remaining checks, decisions, and follow-up work.

Summary by Gitar

  • Reviewer validation:
    • Added isNamedReviewer in src/lib/mha-timeline.ts so product names and role labels no longer count as sign-off
    • Added tests/mha-timeline.test.ts cases rejecting PsychSift and role-label reviewers as unsigned

This will update automatically on new commits.

CodeAnt-AI Description

Reconcile the issue ledger and record corrected safety and wording decisions

What Changed

  • Reconciles 31 pending requests, records completed work, and refreshes the outstanding-issues list.
  • Reopens the WA MHA Form 6A/6B safety review as an active high-priority issue; the form remains unwired pending legal and clinical sign-off.
  • Queues corrections clarifying that developer mockup pages are reachable, disputed workflow and renewals claims were inaccurate, and national youth crisis lines must not be pinned without owner approval.

Impact

✅ Restored WA MHA sign-off tracking
✅ Crisis-line pins remain owner-approved
✅ Corrected dead-code and workflow assessments

💡 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.