id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8)

Gap found by the #1075 validation audit (Phase 2, P2.3/P2.8) — 2026-10-27

The plan of record (doc/2026-10-11T11-08-42Z_design_remaining_work/plan-phases.md) requires, for voiding (P2.3): "S2 scenarios; a planted bug must fail", and for P2.8: "Property tests over random operation orders, and planted-bug checks … mutation checks on demand".

The property half exists and is strong (pkgs/id/tests/membership_properties.rs, voiding_properties.rs, groups/tests.rs proptests, encryption/tests.rs roster property). But a fresh search of pkgs/id on main 452d69e6 (2026-10-27) finds no planted-bug / mutation check anywhere: no planted or mutation/mutant references in pkgs/id/src/membership, pkgs/id/src/groups, pkgs/id/tests, the justfile, or tests/README.md. Nothing demonstrates that a deliberately planted voiding/frontier bug is actually caught by the suite — the exact failure mode P2.3/P2.8 were written to prevent (a test suite that passes both the correct and the broken implementation).

Acceptance criteria

A documented, runnable planted-bug check exists for the membership/voiding layer (e.g. a script or just recipe that applies one or more named mutations to frontier/voiding logic and asserts the scenario/property suites fail for each).
The check is recorded in pkgs/id/tests/README.md with how to run it on demand.
At least the voiding-authority mutation and one frontier-mapping mutation are covered.

Found by: queue task 1256 (validation audit of #1075), slice 3 (Phases 2–4 walk). Parent audit: #1075. Path-to-Phase-12 queue: #1235.

CODE-487

Triage verdict: confirmed — gap is real on current main

Probed origin/main 0e26fa4b3 (2026-11-02) with case-insensitive greps for planted|mutation|mutant across pkgs/id/** plus fault-inject|byzantine|adversarial|negative-test|chaos|sabotage sweeps:

No planted-bug / mutation check exists for membership voiding + frontier. Every keyword hit is incidental:
- permutation(s) in pkgs/id/tests/membership_scenarios.rs:160,228, voiding_scenarios.rs:178,179,208, voiding_properties.rs:248, event_store/resolve.rs:562 (substring mutat inside permutation);
- mutation in the state-change sense (world/handle.rs, world/mod.rs, world/tests.rs:2806, protocol.rs, fileops.rs, benches, worker-poc/README.md, DOM ignoreMutation in image-node-view.ts);
- mutate() helper in pkgs/id/tests/relay_ops.rs:131 is about systemd unit rendering for relay ops, not voiding/frontier;
- evil* fixtures elsewhere are path-traversal/security test names, unrelated.
The property-test half cited in the issue is present (pkgs/id/tests/voiding_properties.rs has proptest content), so the gap is exactly as described: nothing demonstrates a deliberately planted voiding/frontier bug gets caught.

Route: enqueueing a scoped small_fix follow-up packet for issue #1395 (add a planted-bug check that fails the suite when a voiding/frontier invariant is deliberately broken). No hard-stop labels on this issue; triage claims no files changed.

Done: triaged, follow-up enqueued

Outcome: triaged — issue stays open, gap confirmed on origin/main 0e26fa4b3.
Follow-up: task 6582 (small_fix packet) queued to add the planted-bug check for voiding + frontier.
Queue labels cleared (work/assigned, queue/claimed, status/in-progress removed).

🤖 Agent note · handed off

Agent: fleet monitor
Session / ID: task 7238 (repo-fleet-monitor run 2026-11-03 22:12 CST)
Found via: monitor reconciliation
Task: Claim evaporated — the queue task is queued and unclaimed again (lease expired with no complete/park/block), so the issue labels are reset to the truth: queue/queued + status/needs-triage. Checkpoint stage at evaporation: handed_off.
Expectation: a queue lane re-claims task 7238 and resumes from the checkpoint.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-j
Session / ID: task 7238
Found via: queue claim
Task: triage for issue id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395 handed off to the opencode execution lane; claimant launches the bound opencode session
Expectation: s — triage verified at current main, blockers named, fix path enqueued or issue closed with evidence
Links: issue id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane c29174f1-48e0-4b13-b4ff-9b73ab67e9ab
Task: 7238 — triage the membership voiding/frontier planted-bug validation gap.
Revalidation: issue id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395 is OPEN with no hard-stop labels. Current origin/main 8331a77c0 has no planted-bug check in pkgs/id; test files include membership_scenarios.rs, voiding_scenarios.rs, and voiding_properties.rs. PR test(id): planted-bug check for membership voiding + frontier (#1395) #4754 is OPEN, authored and assigned to Drew, with only a neutral CodeRabbit check visible. It is the active fix path; I will not modify or duplicate that Drew-owned PR.
Next: record this triage verdict and leave test(id): planted-bug check for membership voiding + frontier (#1395) #4754's review/merge to its owner.
Links: id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395 · PR test(id): planted-bug check for membership voiding + frontier (#1395) #4754

🤖 Agent note · done (triaged)

Task: 7238 — triage id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395.
Verdict: confirmed at current origin/main 8331a77c0: the membership voiding/frontier planted-bug check is not on main. The issue stays OPEN.
Route: the existing follow-up is PR test(id): planted-bug check for membership voiding + frontier (#1395) #4754 (queue/6582-1395-planted-bug-check), which remains OPEN. It is authored and assigned to Drew; the only visible check is CodeRabbit NEUTRAL. Review/merge is the named blocker. I did not modify or duplicate that PR.
Outcome: triaged; the existing PR is the fix path, so no duplicate follow-up task was enqueued. id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395 remains open until that PR lands.
Links: id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395 · PR test(id): planted-bug check for membership voiding + frontier (#1395) #4754

Navigation Menu

Repository navigation

id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395

Gap found by the #1075 validation audit (Phase 2, P2.3/P2.8) — 2026-10-27

Acceptance criteria

Triage verdict: confirmed — gap is real on current main

Done: triaged, follow-up enqueued

42 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: validation gap — no planted-bug / mutation check exists for membership voiding + frontier (P2.3/P2.8) #1395

Description

Gap found by the #1075 validation audit (Phase 2, P2.3/P2.8) — 2026-10-27

Acceptance criteria

Activity

developing-today commented on Oct 27, 2026

dezren39 commented on Nov 2, 2026

Triage verdict: confirmed — gap is real on current main

dezren39 commented on Nov 2, 2026

Done: triaged, follow-up enqueued

42 remaining items

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions