Repository navigation
docs(maintain): read reconcile's mechanical_count before a large drift report's findings - #550
Open
catincloudlabs wants to merge 1 commit into
Open
catincloudlabs wants to merge 1 commit into
catincloudlabs wants to merge 1 commit into
Conversation
…t report's findings exmergo#544. A `maintain check` against a week-old baseline returned hundreds of findings; the number that resolved the session came from `maintain reconcile`: zero mechanical proposals beside hundreds of advisory ones. Mechanical proposals exist only where dex can author the fix itself, so zero of them across hundreds of schema findings, with no dropped or retyped columns or tables among the codes, means the baseline is behind the project rather than the warehouse having moved. The result already returned both counts and the skill defined both terms; nothing told the reader to use them for triage. The *Reconcile proposals* section now opens with that heuristic, phrased against reconcile's current semantics (a type change is advisory on every format, so retypes are read from the codes), and points at the re-baseline discipline the skill already states. Outside the procedure block the three skills hold in common. Documentation only. Co-Authored-By: Claude Fable 5.1 <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.
What this changes
#544, as claimed on the issue. One bullet opens the maintain skill's Reconcile proposals section:
Phrased against reconcile's current semantics: the two mechanical cases are the ones the next bullet already names (a dex-scaffolded staging model re-scaffolded, or drifted columns edited into a declaration, the second being what #429 added), and the type-change sentence is there because the section already says a retype is advisory on every format, so a reader cannot infer "no retypes" from a zero mechanical count.
Where it sits, and where it does not
checkarrives there from step 4 of the procedure. The alternative placement, thecheckstep itself, would put a paragraph inside the procedure block the three skills hold in common (test_the_three_procedure_sections_are_one_text), which is not this change's to widen.Checks run
No em dash in the file (the
em-dashesjob), and the procedure block is untouched.Files
skills/maintain/SKILL.md: the bullet.CHANGELOG.md: one Changed entry under Unreleased.This touches the same file as #534 (the description, in the frontmatter) in a different region; whichever merges second rebases cleanly.
🤖 Generated with Claude Code