Han publishing cleanup#131
Draft
mxriverlynn wants to merge 5 commits into
Draft
Conversation
Specifies the seven-step cleanup from the source plan artifact: publish han-linear to the Codex channel, close the work-items-to-issues silent hole, repair the release process, correct the frozen Codex versions, delete the two decorative han-core dependencies, correct every falsified document, and turn on the publishing check. All seven steps are retained. Execution order is 1, 2, 6, 3, 4, 5, 7: the release repair moves ahead of the version correction, because the release only writes the Claude Code channel until repaired, so any release cut between the two would re-freeze the correction and land the check red. Deleting the dependencies edits two plugin directories, which forces both to bump at the next release, so the plan's own work triggers it. Reviewed by junior-developer, devops-engineer, edge-case-explorer, and information-architect, then synthesized by project-manager. Every specialist claim was verified against the files; three were verified and rejected. Review changed the spec substantially: the ordering was a partial order asserting five couplings it did not have while missing the one it did; the release gate had no placement and the natural reading put it after the pushed tag; "the check and release share one answer" had no bearer; the document survey was incomplete by five locations; and the count of version records was wrong (three, not two).
Round 1 of iterative-plan-review, team mode, spec-aware. Five specialists: junior-developer, adversarial-validator, evidence-based-investigator, devops-engineer, edge-case-explorer. 16 findings (14 major, 2 minor). The load-bearing corrections: - The check cannot block a merge. main is unprotected, the sole ruleset is disabled, and it carries no required_status_checks rule even if enabled. Three agents converged on this from different angles. The guarantee is now stated per surface: the release refuses, a pull request reports. The real enforcement was always the release gate, not the check. - Steps 3 and 4 become one unit. The gate goes live at step 3, but nine version gaps stay open until step 4, so shipping 3 without 4 froze every release in between. - The repaired release could detect a missing target but not create one, so its headline promise never fired for the case that motivated the work. It now creates missing records (D31). - han-linear is a third untrue han-core declaration, not two. It was also the plugin D8 had chosen as the tutorial's example of a *real* dependency edge. - "Roughly twenty releases" is eleven, verified by tag ancestry. - The bundle publishes a version in two channel-one records, so exempting it from version agreement left the suite's most-exercised hand-sync unchecked. Adds review-findings.md and review-iteration-history.md. Adds D31-D35 and T2. Corrects D4, D6, D8, D13, D22, D25, D26, D29 against evidence that falsified their rationales. Round 1 was not stable; round 2 is in progress.
Round 2 of the iterative review found that R1's two headline resolutions contradicted each other: F30 gave the release the ability to repair, which means the gate never sees the version disagreements F29's steps-3+4 unit was created to survive. The unit is reverted to the ordering D18 always recorded. Also scopes creation to the two channel-two targets where the evidence lives, stops it at content that must be authored, commits every target the release writes, and extends the bundle's exception to the creation verb. Adds D36-D40; corrects D6, D18, D24, D31, D33, D34, D35, D8, D19.
Adds F44-F66 to the findings file and the R2 round entry to the iteration history, and brings the spec's Summary and Review History up to date. R2 raised 17 major and 4 minor findings and rejected 2. Nearly all trace to D31: the release's ability to repair was granted late in R1 and never carried into the six neighbouring decisions it changed. Two findings were rejected on evidence: D18's numeral list is stated in the source plan's numbering and is correct, and han-atlassian's han-communication declaration is real (README.md:84-85 documents it), so step 5 remains three.
All three R3 specialists independently found that D36 contradicted itself: it committed creation to two channel-two targets while establishing, in its own rationale, that one of them IS the authored presence the other half refuses to invent. A record that is the presence cannot be created. That is verbatim the mistake R2 caught R1 making, in the decision R2 wrote to fix it. Nine of R3's ten major findings are its blast radius. Creation now reaches channel two's listing entry alone. The Linear plugin is closed by a person at step 1, as step 1 always said and step 3 denied. Step 1 becomes a binding constraint, and a new plugin merged past the check stops the next release rather than costing lateness. Adds D41; corrects D24, D34, D36, D39, D40. Records F67-F81 and the R3 round. Review stops at its 3-round cap, not stable.
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.
No description provided.