# BACKLOG — phase `dstamp`

## Build backlog (Builder-owned)

- [x] Read phase plan + plan.md §6.1/§7/§9 + Adversary prep notes + stamp-relevant harness code.
- [x] Establish abra's chaos-version mechanism from abra source @06a57de (= pinned binary).
- [x] Rule out abra-version drift (constant store path since nixos system-4, 2026-06-01).
- [x] Minimal reproductions of the git/abra chaos-version path (cp-a; go-git base; mirror-faithful)
      — all stamp the CORRECT head 7ae7b0f7, NO drift in current host state.
- [x] Timeline: run 184 (06-05, solo) green @7ae7b0f; clustered 06-10/06-11 runs drift @ same ref.
- [x] Identify shared-stack collision vector (`app_domain` = hash(recipe|pr|ref); upgrade
      chaos_redeploy bypasses app-domain flock).
- [ ] **IN FLIGHT:** single clean ISOLATED real run (install,upgrade @7ae7b0f, console-captured)
      → decide concurrency-artifact vs real drift.
- [ ] If concurrency artifact: pin the exact mechanism producing the `eb96de9+U` chaos label on
      the shared stack (deliberate 2-run concurrency repro if needed); decide the fix
      (app-lock the upgrade chaos_redeploy / serialize same-stack runs) WITHOUT weakening HC1.
- [ ] If real env drift: read the isolated-run console, attribute the exact 06-05→06-10 change.
- [ ] Blast-radius sweep: every enrolled recipe's latest upgrade-tier evidence for the same
      signature (prev-base tag commit stamped where a version was expected).
- [ ] Restore discourse to its true level in real CI via the drone `!testme` path (M2).
- [ ] Prove HC1 still has teeth (a deliberately wrong stamp still FAILs).
- [ ] Close the DEFERRED.md dstamp re-entry with pointers.

## Adversary findings
<!-- Adversary-owned. Do not edit above this line in this section. -->