Repository navigation
Conversation
This branch monitored the patient projection pipeline and was written against 2026-07-24 main, then sat unproposed for 44 commits. It now rebases cleanly, but its tests set hummingbird-patient.* config keys, which the rename (#101) moved to nightingale.*, so every assertion failed against the renamed PatientPathwaySourceReconciliationService. Renames those keys in the test, in SystemHealthService, and in the four .env.example lines this branch adds. No behavioural change. Verified in an isolated worktree: 7 tests pass with 41 assertions, and Pint is clean on both changed PHP files. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Revives a branch that was written on 2026-07-24, never proposed, and sat 44
commits behind main. Rebased and brought current.
What it adds
PatientProjectionPipelineHealthTest— 7 tests, 41 assertionsSystemHealthServiceprojection-pipeline checks andconfig/admin-health.phpdocs/operations/HUMMINGBIRD-PATIENT-PROJECTION-PIPELINE-RUNBOOK.md.env.exampleentriesWhy it is worth reviving now
There is currently no visibility into the projection pipeline, and that is
exactly where the product is stuck: 9,601 milestones and 6 encounter
projections sit in
draft,released_projectionsis 0, and nothing reports ondraft age, repeated draft failures, or freshness. When clinical review starts
releasing content, this is the monitoring that shows whether the pipeline is
actually moving.
What the rebase required
The tests set
hummingbird-patient.*config keys. The rename (#101) movedthose to
nightingale.*, so every assertion failed against the renamedPatientPathwaySourceReconciliationService. Renamed the keys in the test, inSystemHealthService, and in the four.env.examplelines this branch adds.No behavioural change.
Verification
Isolated worktree with its own
composer install— 7 tests pass, 41assertions; Pint clean on both changed PHP files.
Notes for review
.env.exampleis a single-writer file per.claude/rules/parallel-agents.md.Its 4 added lines are listed above; happy for them to be applied separately.
file. Merge Rename the remaining HUMMINGBIRD_PATIENT_ variables in .env.example #113 first or these two will conflict there.
docs/hummingbird/capability-ledger.v1.yamlgains one line; the ledgerverifier passes.