Multiple fixes: status vocabulary aligned, 065/026/070/007 resolved, 066/069/049/046 located, 064 diagnosed #64

Merged
jschoubben merged 10 commits from feat/multiple-fixes into main 2026-09-21 17:23:35 +00:00
Owner

Bookkeeping

  • The cycle check knew fixed and not wontfix; the playbook, README and status skill knew the reverse. The check now takes the playbook's five words. Eleven issues sitting in fixed with their fixes shipped are resolved. The check now asks a resolved issue for its owner, and twelve had none; filled from their fixed-by.

Resolved, with code in mesh-control (MR on the same branch name)

  • 065 — ADR 0090, a failure that repeats is said to be stuck; design 10 amended.
  • 026 — ADR 0091, a mount is declared three ways; design 18 amended. The field the report said would have to be invented already existed twice (accesses, capabilities).
  • 070 — ADR 0092, an operator delivers a pair credential; design 24 amended.

Resolved without code

  • 007 — the class question is answered in the mesh by capabilities, verify on an action (ADR 0005) and the lab's verdict (design 01); the old arrangement is replaced module by module.

Located, with the decision the fix needs named in a diagnosis

  • 066 — the mixed state is already visible (failed = some of it); duration was 065; the grouping primitive waits for a module that needs it.
  • 069 — read against the catalogue: seven of nine multi-secret modules hold genuinely independent values, so the fix is a way to require secret more than once under local names, and it moves the pair key. A feature of its own.
  • 049 — the controller is the way in (mesh-controller ask); a module-to-module call is a later grant.
  • 046 — a registry-to-registry copy never needs a platform; the builder's upstream step is the owner.
  • 064 — the package registry has proxied the public one since 09-03 and the builder scopes its npmrc, so the 404 must be re-run to be placed; the vendor-image half needs a decision on declaring build inputs.

Left as they are

  • 006 — the search consulting the agent is on the other side of the fence (hal).
  • 020 — needs a second ACME implementation to run against.
  • 074, 075 — blocked until #62/#41 (issue 073) merge; their changes would conflict with that branch's check list and rebuild test.

Checks: records, index, cycle pass. Branched off main; no file overlaps with #62 or #63 except the regenerated decision index, which is a mechanical regenerate after merge.

## Bookkeeping - The cycle check knew `fixed` and not `wontfix`; the playbook, README and status skill knew the reverse. The check now takes the playbook's five words. Eleven issues sitting in `fixed` with their fixes shipped are `resolved`. The check now asks a resolved issue for its owner, and twelve had none; filled from their `fixed-by`. ## Resolved, with code in mesh-control (MR on the same branch name) - **065** — ADR 0090, a failure that repeats is said to be stuck; design 10 amended. - **026** — ADR 0091, a mount is declared three ways; design 18 amended. The field the report said would have to be invented already existed twice (`accesses`, `capabilities`). - **070** — ADR 0092, an operator delivers a pair credential; design 24 amended. ## Resolved without code - **007** — the class question is answered in the mesh by `capabilities`, `verify` on an action (ADR 0005) and the lab's verdict (design 01); the old arrangement is replaced module by module. ## Located, with the decision the fix needs named in a diagnosis - **066** — the mixed state is already visible (`failed` = some of it); duration was 065; the grouping primitive waits for a module that needs it. - **069** — read against the catalogue: seven of nine multi-secret modules hold genuinely independent values, so the fix is a way to require `secret` more than once under local names, and it moves the pair key. A feature of its own. - **049** — the controller is the way in (`mesh-controller ask`); a module-to-module call is a later grant. - **046** — a registry-to-registry copy never needs a platform; the builder's upstream step is the owner. - **064** — the package registry has proxied the public one since 09-03 and the builder scopes its npmrc, so the 404 must be re-run to be placed; the vendor-image half needs a decision on declaring build inputs. ## Left as they are - **006** — the search consulting the agent is on the other side of the fence (hal). - **020** — needs a second ACME implementation to run against. - **074, 075** — blocked until #62/#41 (issue 073) merge; their changes would conflict with that branch's check list and rebuild test. Checks: records, index, cycle pass. Branched off main; no file overlaps with #62 or #63 except the regenerated decision index, which is a mechanical regenerate after merge.
jschoubben added 9 commits 2026-09-21 15:57:28 +00:00
The playbook, the README and the status skill knew five statuses; the cycle check
knew a sixth, 'fixed', and not 'wontfix'. Eleven issues sat in the sixth for weeks
with their fixes shipped, one step short of closed. They are resolved; the check
refuses the word from now on and accepts the one the playbook allows.
The cycle check now asks a resolved issue for its owner, and these had none.
The controller kept one report per machine, replaced, so a resource nothing can
ever apply looked like a failure that had just happened, every few minutes, for
ever. It now counts identical reports and status says stuck after three.
jschoubben added 1 commit 2026-09-21 17:23:05 +00:00
jschoubben merged commit 6a35e5a58c into main 2026-09-21 17:23:35 +00:00
jschoubben deleted branch feat/multiple-fixes 2026-09-21 17:23:35 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#64