Skip to content

local-llm-acp-record-is-put-right - #813

Merged
VeryComplexAndLongName merged 1 commit into
mainfrom
local-llm-acp-record-is-put-right
Oct 2, 2026
Merged

VeryComplexAndLongName merged 1 commit into
mainfrom
local-llm-acp-record-is-put-right

Conversation

@VeryComplexAndLongName

Copy link
Copy Markdown
Owner

local-llm-acp landed on 2026-10-01 in #803 with every box ticked, and
the sweep has refused to archive it ever since. Waiting longer would not
have helped.

owesNothing(describeTaskDebts(...)) — the one answer the sweep and the
merge gate both take — is false for it. Item 4.4 is
**Delegated to local-llm-acp**, and its record was written on the
checkbox line
with nothing indented beneath it. isUnrecordedTask reads
a delegated item as recording nothing when the lines under it are empty,
whatever is on the line, because nothing can mechanically tell evidence
appended to an item's sentence from the item's own instructions.

Measured at 513a5c96: describeTaskDebts reports 4.4 under
unrecorded, and validate --change local-llm-acp returns "ok": false.
After this change, both are clean.

Why it landed green. The gate resolves the change from
--change "$GITHUB_HEAD_REF", and #803's branch was fix-local-llm-acp,
not local-llm-acp. A name no active change has is skipped rather than
guessed at, so the debt check never ran. The title was the change id; the
branch was not, and the gate reads the branch.

What this does

  • Moves 4.4's record under its checkbox, verbatim —
    git diff --word-diff shows no word added or removed, only line breaks
    and indentation. Nothing re-verified, nothing reworded, no other item
    touched.
  • Adds the branch-name rule to openspec/README.md, next to "one change
    is one pull request", naming this as the measured case.
  • Modifies the openspec-workbench requirement so the rule is written
    down: a delegated or human-only item's evidence goes under the item.

No source changes, no behaviour changes, no changeset. After this lands,
the sweep archives local-llm-acp on its next pass.

Deliberately not done

Making the gate check every change whose tasks.md a pull request
touches would have caught this — and would also fail a pull request
carrying another change's freshly opened proposal. That rule has its own
blast radius and belongs in its own change, not smuggled into a record
correction.

Checks

typecheck 0 errors · lint 0 errors (3 pre-existing warnings already on
main) · lint:english passed · tests 287 files, all passed (cli 192,
core 2011 + 62, extension 499, server 118, webui 687) ·
openspec validate --changes --strict 2 passed, 0 failed · merge gate
"ok": true.

@VeryComplexAndLongName
VeryComplexAndLongName merged commit 737cdf4 into main Oct 2, 2026
10 checks passed
@VeryComplexAndLongName
VeryComplexAndLongName deleted the local-llm-acp-record-is-put-right branch October 2, 2026 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant