Skip to content

chore: preserve historical September 11 Beads audit events - #449

Merged
BunsDev merged 1 commit into
mainfrom
chore/preserve-beads-audit-history
Sep 13, 2026
Merged

BunsDev merged 1 commit into
mainfrom
chore/preserve-beads-audit-history

Conversation

@BunsDev

@BunsDev BunsDev commented Sep 13, 2026

Copy link
Copy Markdown
Member

Scope and authority

Preserve 18 already-generated September 11 audit events in .beads/interactions.jsonl, with explicit owner authorization to preserve the dirty journal in Git. Historical preservation only; DO NOT MERGE in this task. Parent independent R4 review, terminal exact-head required checks, normal protected merge, and subsequent root reconciliation remain pending.

These are chronological events, not current authority or new acceptance evidence. Repeated statuses, distinct event IDs, old completion claims, candidate-head claims, and their original wording remain intact. No deduplication by issue/status, correction, transition replay, or present-day closure is performed. No protocol, support, source, or mirror status changes are asserted.

The root journal was backed up privately before integration and remains unchanged and unstaged. Only the 18 appended records were integrated with apply_patch into a clean worktree branched from fetched origin/main; no wholesale overwrite of newer upstream was performed. No other worktree was modified or removed. No Beads CLI/database access, export, migration, Dolt operation, or synchronizer application occurred.

Exact artifact and preservation evidence

Base: ec28705ca2ac693bdfbd3ee959a0c9c6def23b07 (PR #448 merged). Commit: d42a3d3cb9a9d00f2c6c6b589efdf24a8ea1c0af.

Exact diff: .beads/interactions.jsonl only, 18 additions / 0 deletions, lines 97-114. Base contains 96, not 97, records. Root HEAD and fetched upstream journal were byte-identical; there were no overlapping appended IDs to reconcile.

Artifact Records Bytes SHA-256
Base journal 96 34004 c7951d345033684318934238e478165a1bfe8a6d22220382ecc0e9a405516a6f
Original dirty root / private backup / committed journal 114 44716 2ff0cf1f61630aa45482d0870302a80dacdfb10885d75c799d10872079e16a21
Exact appended suffix 18 10712 07215c3a9b32a96da7cfb8aa26cc02c24c9927ade7306ee9a28c70768504ba9e

Patch SHA-256: e5c314bc3585234508685fc93d57865dbfbdfde144cf8294af7a53bee3e0ae0e, reproducible with:

git diff --no-ext-diff --binary ec28705ca2ac693bdfbd3ee959a0c9c6def23b07 d42a3d3cb9a9d00f2c6c6b589efdf24a8ea1c0af -- .beads/interactions.jsonl | shasum -a 256
git show d42a3d3cb9a9d00f2c6c6b589efdf24a8ea1c0af:.beads/interactions.jsonl | shasum -a 256
git show d42a3d3cb9a9d00f2c6c6b589efdf24a8ea1c0af:.beads/interactions.jsonl | tail -n 18 | shasum -a 256
git diff --numstat ec28705ca2ac693bdfbd3ee959a0c9c6def23b07 d42a3d3cb9a9d00f2c6c6b589efdf24a8ea1c0af

Byte comparisons against the private backup passed before commit. JSON parsing, all 114 unique IDs, expected appended event shape, September 11 timestamp ordering, exact 34004-byte prefix, exact 10712-byte suffix, and final newline passed. Manual review of every added field plus bounded sensitive-pattern screening found no credentials, raw private paths, raw prompts, or private endpoints. Public historical actor attribution is unchanged. No raw database export or unrestricted logs are retained or published.

Bounded provenance

Read-only gh pr view NUMBER --json number,state,headRefOid,mergeCommit,mergedAt confirmed merged PR identities for #429, #436, #438, #439, #440, #441, #442, and #443. Their recorded merge references agree with GitHub metadata. This establishes reference identity only, not historical suite counts, review verdicts, current source state, or acceptance.

In particular, the earlier #440 candidate SHA is retained as an old candidate claim, not represented as the final merged head. The later event identifies head a9c0e2c8a75063198eba86120051f6a08617e0e4 and merge 3660351077eb4e9d5c68001ee9907a1ef1c21499. Repeated completion narratives are intentionally not reconciled. Physical-device, simulator, GPU, and lost-reply proof gaps are not adjudicated by this PR.

Validation

Executed on the exact tree committed as d42a3d3cb9a9d00f2c6c6b589efdf24a8ea1c0af:

pnpm exec vitest --run __tests__/agentRepositoryContract.test.ts __tests__/beadsProjectCli.test.ts __tests__/beadsProjectGithub.test.ts __tests__/beadsProjectGraphqlE2e.test.ts __tests__/beadsProjectModel.test.ts __tests__/beadsProjectOutcomes.test.ts __tests__/beadsProjectReconcile.test.ts __tests__/beadsProjectRecovery.test.ts __tests__/trackerDriftValidation.test.ts
pnpm exec vitest --run -c vitest.beads-render.config.ts
bash ./scripts/agent-check full
git diff --check

Results: focused governance/synchronizer tests 403 passed; isolated renderer tests 221 passed; full source gate passed, including tests, documentation, typecheck, smoke, packaging, deterministic bundles, Rust formatting/tests/check. No tracked/untracked drift from the gate. iOS opt-in simulator gate was not enabled; no new iOS/device/distribution acceptance is claimed. Existing Rust warnings were non-fatal. Hosted exact-head checks and parent independent R4 review are still separate merge gates.

Rollback and handoff

Before merge, leave the PR unmerged; the original root journal and private backup preserve all events. Any post-merge rollback must be a separately reviewed Git revert, not a database reversal or mirror mutation. The parent must compare the live root with the original digest and check for concurrent appended events before any cleanup; this task deliberately leaves the root dirty. No branch/worktree removal or root cleanup is authorized by this PR.

Retain 18 existing generated journal events byte-for-byte as historical records, not current acceptance or replayed source transitions. No database, mirror, protocol, or support status changes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings September 13, 2026 14:18
@vercel

vercel Bot commented Sep 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
psyche-build-docs Ready Ready Preview Sep 13, 2026 2:18pm UTC

Request Review

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

Hosted exact-head checks and the parent independent R4 review remain pending.

Pull request overview

Preserves 18 historical September 11 Beads audit events in .beads/interactions.jsonl without changing current authority or source state.

Changes:

  • Appends the original 18 JSONL audit records chronologically.
  • Retains IDs, timestamps, wording, repeated statuses, and historical claims.
  • Includes artifact integrity and validation evidence.
File summaries
File Description
.beads/interactions.jsonl Adds 18 preserved historical audit events.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@BunsDev

BunsDev commented Sep 13, 2026

Copy link
Copy Markdown
Member Author

Independent R4 review completed on exact head d42a3d3cb9a9d00f2c6c6b589efdf24a8ea1c0af: no findings. Confirmed byte-identical preservation of the pre-existing journal append: 18 events / 10,712 bytes, 96 to 114 records, unique IDs, both recorded digests matching. Historical repetitions/claims remain history, not new acceptance or source-state transitions. No database commands or publication are involved. Terminal exact-head checks passed; no unresolved threads. Proceeding through ordinary protected merge, followed by exact-byte local checkout reconciliation.

@BunsDev
BunsDev merged commit d64593f into main Sep 13, 2026
13 checks passed
@BunsDev
BunsDev deleted the chore/preserve-beads-audit-history branch September 13, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants