Fix roster-count mismatch and undocumented ops-registry setup step - #17
Merged
Merged
Conversation
… step README stated 'a team of 12' inside a sentence about this repo's own registry; the shipped example is sized for the 8 role archetypes, and 12 was production's headcount at measurement time. Clarified which is which. Separately, OPS_REGISTRY_PATH points at config/ops-registry.json, which isn't in the repo -- only the .example.json is. A live run (pull/poll/serve/board) hits ops-registry degraded mode with no doc explaining why. Added the copy step where live commands are first introduced. Verified: without the file, opsRegistryDegradedReason() returns 'nobody is in the roster'; with it copied from the example, null.
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
2 participants
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.
Two small README fixes found during a final coverage audit before launch:
"It runs for a team of 12, which is the roster size in the routing registry that governs it" sat inside a sentence about this repo's own numbers, but the repo ships an example registry sized for 8 role archetypes. 12 was production's headcount at the time the 711-item measurement was taken. Clarified which is which.
OPS_REGISTRY_PATH(.env.example) points atconfig/ops-registry.json, which isn't in the repo — onlyconfig/ops-registry.example.jsonis. The demo is unaffected (each fixture scenario carries its own registry), but the first live command (pull/poll/serve/board) hits ops-registry degraded mode with no doc explaining why. Added thecpstep where live commands are first introduced.Verified directly:
opsRegistryDegradedReason()returns "nobody is in the roster" without the file,nullonce copied from the example. Full test suite and demo still pass.