Two register entries in replays/register.go, after R341.
R401 (issue 401: the send made a random value for an own secret issued outside the mesh that nobody gave)
InRepository in mesh-controller. Fix: 1e28342 (merge of mesh-controller #262); the commit before is its first parent (c672b3d). Test: TestReplay401 in cmd/mesh-controller/replay401_test.go, taken from Home: mesh-controller at HomeRef: f3c15e0 (the head of mesh-controller #274). Needs the store (MESH_TEST_POSTGRES), as R237 does.
Why a test of its own: the fix's test TestTheSendMakesNoValueForAnOutsideSecretNobodyGave reads inventory.GivenOwnSecret, which the fix added, so its file does not build on the commit before. mesh-controller #274 adds a replay written with only pre-fix names (the R237 pattern; here in its own PR because the fix had merged). Merge mesh-controller #274 first; f3c15e0 stays reachable once it merges.
R561 (issue 561: a plan's id was pasted into the SQL that reads it)
InRepository in mesh-controller. Fix: f8daec0 (merge of mesh-controller #268); commit before is its first parent. Test: TestAPlanIdHoldingAQuoteIsReadAsAPlainId in internal/inventory/plan_id_test.go, from the fix itself. The file is new and uses only names present before (ForTest, Plan, SavePlan, PlanByID, RecentPlans): go vet builds it laid over f8daec0^1. Store-backed, already in mesh-controller's testdata/store-tests.
Proof
go run ./cmd/prove R401 R561 in replays/, with a throwaway postgres 17 as MESH_TEST_POSTGRES:
R401 (issue 401): PROVED — before its fix fails, on its fix passes
before: replay401_test.go:58: the send placed a value for smb-credentials, which nobody gave: map[id:mounts.needs-smb-credentials path:/var/lib/mesh/mounts/smb-credentials sealed:… type:file]
R561 (issue 561): PROVED — before its fix fails, on its fix passes
before: plan_id_test.go:27: PlanByID("x' or '1'='1") answered plan-561, a plan of another id
Tested.sh merge-check.sh at the root and in replays/: exit 0 (gofmt, vet, register tests). The replays themselves are not run there, as for every entry.
Replays for hq issues 401 and 561. Not merged.
Two register entries in `replays/register.go`, after R341.
## R401 (issue 401: the send made a random value for an own secret issued outside the mesh that nobody gave)
InRepository in mesh-controller. Fix: 1e28342 (merge of mesh-controller #262); the commit before is its first parent (c672b3d). Test: `TestReplay401` in `cmd/mesh-controller/replay401_test.go`, taken from `Home: mesh-controller` at `HomeRef: f3c15e0` (the head of mesh-controller #274). Needs the store (`MESH_TEST_POSTGRES`), as R237 does.
Why a test of its own: the fix's test `TestTheSendMakesNoValueForAnOutsideSecretNobodyGave` reads `inventory.GivenOwnSecret`, which the fix added, so its file does not build on the commit before. mesh-controller #274 adds a replay written with only pre-fix names (the R237 pattern; here in its own PR because the fix had merged). **Merge mesh-controller #274 first**; f3c15e0 stays reachable once it merges.
## R561 (issue 561: a plan's id was pasted into the SQL that reads it)
InRepository in mesh-controller. Fix: f8daec0 (merge of mesh-controller #268); commit before is its first parent. Test: `TestAPlanIdHoldingAQuoteIsReadAsAPlainId` in `internal/inventory/plan_id_test.go`, from the fix itself. The file is new and uses only names present before (ForTest, Plan, SavePlan, PlanByID, RecentPlans): `go vet` builds it laid over f8daec0^1. Store-backed, already in mesh-controller's `testdata/store-tests`.
## Proof
`go run ./cmd/prove R401 R561` in replays/, with a throwaway postgres 17 as `MESH_TEST_POSTGRES`:
R401 (issue 401): PROVED — before its fix fails, on its fix passes
before: replay401_test.go:58: the send placed a value for smb-credentials, which nobody gave: map[id:mounts.needs-smb-credentials path:/var/lib/mesh/mounts/smb-credentials sealed:… type:file]
R561 (issue 561): PROVED — before its fix fails, on its fix passes
before: plan_id_test.go:27: PlanByID("x' or '1'='1") answered plan-561, a plan of another id
**Tested.** `sh merge-check.sh` at the root and in replays/: exit 0 (gofmt, vet, register tests). The replays themselves are not run there, as for every entry.
Replays for hq issues 401 and 561. Not merged.
mesh/repo-check head e63459dd702a merged into trunk 24b833d19dad — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…
Proved: fails on mesh-controller 1e28342^1, passes on 1e28342 (the fix, #262). The replay is mesh-controller #274's TestReplay401, since the fix's own test reads what the fix added.
composed together: pass — the change touches no module of the mesh's graph
Transitions
2026-10-12 17:01 (new) → proposed (announced): novox/mesh-lab#87's head announced
2026-10-12 17:06 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-12 17:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 18:22 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 18:22 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-lab@3c655d83e11e` — **delivered** since 2026-10-12T18:22:44Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Group** `fix/401-replay`, in order: novox/mesh-controller@f3c15e00af50 → novox/mesh-lab@3c655d83e11e
- composed together: pass — the change touches no module of the mesh's graph
**Transitions**
- 2026-10-12 17:01 (new) → proposed (announced): novox/mesh-lab#87's head announced
- 2026-10-12 17:06 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-12 17:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 18:22 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 18:22 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/repo-check head 3c655d83e11e merged into trunk 24b833d19dad — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…
Proved: fails on mesh-controller f8daec0^1, passes on f8daec0 (the fix, #268).
mesh-admin
changed title from Register R401: the send made a value for an own secret issued outside the mesh that nobody gave (hq issue 401) to Register R401 and R561: an outside secret nobody gave was made; a plan's id was pasted into SQL (hq issues 401, 561)2026-10-12 17:01:30 +00:00
Independent review (registers R401 and R561, delivery group fix/401-replay).
What I checked:
Both entries follow the register's conventions as R237 and R233 do: a comment saying the incident, its date, why the test is laid over the commit before and that Fix is the merge of its pull request; InRepository kind, full 40-character Fix shas, What/Asserts/Package/Test/Files. R401 uses Home/HomeRef as the other controller replays whose test lives outside the fix do. TestEveryReplayIsWhole passes.
R401: Fix 1e28342 is the merge of mesh-controller #262 (issue 401); the test file comes from f3c15e00 (mesh-controller #274's head), and uses only names present on 1e28342^1.
R561: Fix f8daec0 is the merge of mesh-controller #268 (issue 561); internal/inventory/plan_id_test.go is in that fix and uses only ForTest, SavePlan, PlanByID, RecentPlans, which exist on f8daec0^1.
Ran go run ./cmd/prove R401 R561 in replays/ with a throwaway Postgres as MESH_TEST_POSTGRES: both PROVED. R401 fails before its fix with "the send placed a value for smb-credentials, which nobody gave"; R561 fails before with PlanByID("x' or '1'='1") answered plan-561. Both pass on their fixes.
Statuses at this head: mesh/merge-gate, mesh/repo-check and mesh/delivery all success; mergeable. This head carries no mesh/delivery-group status of its own, while mesh-controller #274 shows the group fix/401-replay pending (1 of 2 members ready), so merge only once the group's composed check passes for both heads.
Non-blocking:
R561's Asserts says "RecentPlans takes its limit as a parameter", but the test's RecentPlans call passes before the fix too (an int limit was never injectable), so the replay proves only the PlanByID half. Consider dropping that clause or saying it is held by the fix's own test.
R401's HomeRef f3c15e00 must stay reachable: mesh-controller #274 should be merged with a merge commit, not squashed.
Verdict: approve at 3c655d83e11e0a53a93c3aa4c7bc09238db63db3
Independent review (registers R401 and R561, delivery group fix/401-replay).
What I checked:
1. Both entries follow the register's conventions as R237 and R233 do: a comment saying the incident, its date, why the test is laid over the commit before and that Fix is the merge of its pull request; InRepository kind, full 40-character Fix shas, What/Asserts/Package/Test/Files. R401 uses Home/HomeRef as the other controller replays whose test lives outside the fix do. TestEveryReplayIsWhole passes.
2. R401: Fix 1e28342 is the merge of mesh-controller #262 (issue 401); the test file comes from f3c15e00 (mesh-controller #274's head), and uses only names present on 1e28342^1.
3. R561: Fix f8daec0 is the merge of mesh-controller #268 (issue 561); internal/inventory/plan_id_test.go is in that fix and uses only ForTest, SavePlan, PlanByID, RecentPlans, which exist on f8daec0^1.
4. Ran go run ./cmd/prove R401 R561 in replays/ with a throwaway Postgres as MESH_TEST_POSTGRES: both PROVED. R401 fails before its fix with "the send placed a value for smb-credentials, which nobody gave"; R561 fails before with PlanByID("x' or '1'='1") answered plan-561. Both pass on their fixes.
Statuses at this head: mesh/merge-gate, mesh/repo-check and mesh/delivery all success; mergeable. This head carries no mesh/delivery-group status of its own, while mesh-controller #274 shows the group fix/401-replay pending (1 of 2 members ready), so merge only once the group's composed check passes for both heads.
Non-blocking:
- R561's Asserts says "RecentPlans takes its limit as a parameter", but the test's RecentPlans call passes before the fix too (an int limit was never injectable), so the replay proves only the PlanByID half. Consider dropping that clause or saying it is held by the fix's own test.
- R401's HomeRef f3c15e00 must stay reachable: mesh-controller #274 should be merged with a merge commit, not squashed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two register entries in
replays/register.go, after R341.R401 (issue 401: the send made a random value for an own secret issued outside the mesh that nobody gave)
InRepository in mesh-controller. Fix: 1e28342 (merge of mesh-controller #262); the commit before is its first parent (c672b3d). Test:
TestReplay401incmd/mesh-controller/replay401_test.go, taken fromHome: mesh-controlleratHomeRef: f3c15e0(the head of mesh-controller #274). Needs the store (MESH_TEST_POSTGRES), as R237 does.Why a test of its own: the fix's test
TestTheSendMakesNoValueForAnOutsideSecretNobodyGavereadsinventory.GivenOwnSecret, which the fix added, so its file does not build on the commit before. mesh-controller #274 adds a replay written with only pre-fix names (the R237 pattern; here in its own PR because the fix had merged). Merge mesh-controller #274 first; f3c15e0 stays reachable once it merges.R561 (issue 561: a plan's id was pasted into the SQL that reads it)
InRepository in mesh-controller. Fix: f8daec0 (merge of mesh-controller #268); commit before is its first parent. Test:
TestAPlanIdHoldingAQuoteIsReadAsAPlainIdininternal/inventory/plan_id_test.go, from the fix itself. The file is new and uses only names present before (ForTest, Plan, SavePlan, PlanByID, RecentPlans):go vetbuilds it laid over f8daec0^1. Store-backed, already in mesh-controller'stestdata/store-tests.Proof
go run ./cmd/prove R401 R561in replays/, with a throwaway postgres 17 asMESH_TEST_POSTGRES:Tested.
sh merge-check.shat the root and in replays/: exit 0 (gofmt, vet, register tests). The replays themselves are not run there, as for every entry.Replays for hq issues 401 and 561. Not merged.
Delivery
novox/mesh-lab@3c655d83e11e— delivered since 2026-10-12T18:22:44ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Group
fix/401-replay, in order: novox/mesh-controller@f3c15e00af → novox/mesh-lab@3c655d83e1Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Register R401: the send made a value for an own secret issued outside the mesh that nobody gave (hq issue 401)to Register R401 and R561: an outside secret nobody gave was made; a plan's id was pasted into SQL (hq issues 401, 561)Verdict: approve at
3c655d83e1Independent review (registers R401 and R561, delivery group fix/401-replay).
What I checked:
Statuses at this head: mesh/merge-gate, mesh/repo-check and mesh/delivery all success; mergeable. This head carries no mesh/delivery-group status of its own, while mesh-controller #274 shows the group fix/401-replay pending (1 of 2 members ready), so merge only once the group's composed check passes for both heads.
Non-blocking: