fix: the pilot close-out — the slug cap between words, keep-current re-arms, and the record carries what three pilots taught - #653
Merged
Conversation
Refs: iss-2609211735419853 Assisted-by: Claude:claude-opus-5
Three stores derived a slug the same way and capped it the same way, collapsed[:60] then a hyphen trim, so a slug that ended in a numbered token read as a different token: a capture naming criterion ac-10 landed as ...-ac-1, and one naming ac-13 the same. The cap now lives once, in the record-id package that owns record filenames: words are split on every non-alphanumeric run with a hyphen inside a word kept as part of it, and the cap takes as many whole words as fit, cutting inside a word only when the first word alone exceeds it. The capture ledger, the intent store and the decision store call it; below the cap the result is byte-identical to before, so no existing filename moves. Refs: iss-2609211735419853 Assisted-by: Claude:claude-opus-5
Resolves: iss-2609211735419853 Assisted-by: Claude:claude-opus-5
… a branch The forge's update-branch disarms auto-merge on the pull request it brings current, so the remedy for a BEHIND pull request left it CLEAN, green and unqueued with nothing saying so. The script re-arms after a successful update and prints what it did; the record carries the evidence and keeps its wider want. Refs: iss-2609211105011322 Assisted-by: Claude:claude-opus-5
…he pacing spec, and capture the specless planned intent The Dessau pilots' accounts (parts the script did that a verb should own; a pause that never fired) and this run's own recoveries go onto the implement verb's future-work seed and the pacing spec; the fourteen planned intents no verb can give a spec to are captured. Refs: iss-2609211105021406, iss-2609211738504433 Assisted-by: Claude:claude-opus-5
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
1 participant
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.
What
The pilot run's close-out, four changes in one branch:
ac-10filed as…-ac-1. The cap now lives once in the record-id package, keeps a hyphen inside a word as part of the word, and takes as many whole words as fit; below the cap the result is byte-identical, so no existing filename moves.scripts/pr-keep-current.shre-arms auto-merge after the forge's update-branch, which disarms it: a pull request brought current sat green and unqueued for a quarter of an hour with nothing saying so.Review
The slug change carries a table test watched red then green (boundary cut, a numbered token dropped whole, a first word over the cap hard-cut, punctuation runs); the capture, intent and decide packages pass unchanged. The script change is a shell edit with
bash -n. Full preflight and the format gate pass.Records
Resolves: iss-2609211735419853
Refs: iss-2609211105011322, iss-2609211105021406, iss-2609211738504433
Assisted-by: Claude:claude-opus-5