Repository navigation
A new work log starts at the current format; format refusals say how to raise it - #485
Merged
Merged
Conversation
el-bri-ga
enabled auto-merge (squash)
November 20, 2026 01:26
|
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.



Closes #478
format_raisedtoFORMATas the first record when it starts on a log with no records (Settings.fresh_format, set from the constant, so a later bump follows). A log with records keeps its format; the raise stays person-only. No fold change, so no golden or replay-corpus change.Error::Format:refused: format: worker_started needs log format 21, this log is at 13; a person raises it with format_raised (see docs/upgrades.md#formats). HTTP still answers 409why: format; kbl-mcp tools pass the text through.supervise_status.paused_becausenow carries the last launch error.GET /v1/meaddslog_formatper team andcurrent_format;dev/quickstart.shprints them and the raise command when behind.Design calls: the docs section is docs/upgrades.md#formats (the issue named work-tracker.md, which has no formats section). The raise is written as a person record by the tracker, so the fold rule is unchanged.