ops(log): PMO activity log and turn/queue logs

This commit is contained in:
2026-08-29 05:22:43 -05:00
parent b2c4b74d76
commit 8009277c44
46 changed files with 425 additions and 0 deletions
+6
View File
@@ -0,0 +1,6 @@
Code matches the v0 spec. Now the build tooling and smoke:Working tree matches the v0 spec (file/env backends, bitwarden/vault 501 stubs, auth from file backend, redaction, no persistence/admin UI). Now re-verifying in the Docker builder:check green. Running the end-to-end smoke (uses a named container, torn down by exact name — no pkill):Smoke 10/10 PASS, log redacted. Checking for memory files, then committing:Push rejected — remote diverged. Inspecting what's on origin/main:Histories are unrelated (remote was re-seeded). Comparing remote content vs ours:Remote is a re-seeded spec README + LICENSE; ours is a superset. Checking whether remote README matches our local seed's README:Remote main content is byte-identical to our unpushed local seed (same README + LICENSE, different commit ids). Rebasing our 5 commits onto origin/main, dropping the redundant local seed:Rebase clean, tree identical to pre-rebase. Pushing:Pushed. Writing the PMO report:Done. keyproxy-v0 verified, committed (5 chunks), pushed to `origin/main` (`325a36c..47343d5`), report delivered.
- **Re-verification**: `./dev.sh check` green (build+vet+test in the digest-pinned golang:1.26 builder); `./dev.sh smoke` 10/10 PASS with redacted server log.
- **Push wrinkle**: first push was rejected — origin/main was re-seeded (`6c88e65`+`325a36c`) with byte-identical README/LICENSE to our unpushed local seed. Rebased the 5 implementation commits onto `325a36c` (tree verified identical), then pushed cleanly.
- **Commits**: `b43bc55` backends, `7bec2a1` config, `82861b6` server, `24a57c1` CLI, `47343d5` tooling/docs.
- **Report**: `~/.coordinate/inbox-pmo/REPORT-20260828-2130-keyproxy-v0.md`. No pkill used (smoke tears down by exact container name); nothing seeded; working tree clean.