BlobStore trait + content-addressed fs backend (ADR-0006)

[filipeforattini]

What to build

Introduce a content-addressed BlobStore trait with an fs backend, addressing blobs by a cas content key. It ships alongside existing storage and is exercised by tests only (the expand step of ADR-0006); no production caller yet.

Acceptance criteria

• BlobStore trait with put/get by content-addressed key.
• fs backend stores/retrieves blobs content-addressed, zero-config default path.
• Round-trip and dedup-by-identical-bytes tests pass.

Current blocker

status: blocked
kind: main-red-untracked
summary: Refusing admin-merge onto red main because no open main-red repair issue exists. Restore the tracked-red visibility gate by letting syncMainRedRepairIssue auto-file "main-red repair: baseline probe failures on main" from the AFK feedback baseline probe before landing. The attempt branch afk/w8C4I/63-blobstore-trait-content-addressed-fs-bac is intact and validated, but landing is held until the tracked-red repair issue exists. The auto-file attempt for the main-red repair issue failed and must be inspected: gh: failed to create issue (code 1): could not add label: 'priority:urgent' not found. Requeue after the auto-file path recreates it.
next: Restore or create the auto-filed main-red repair issue, then requeue.

[filipeforattini]

🤖 AFK claim by worker 8cb3eafdcbd2:w8C4I (runner codex).

[filipeforattini]

🤖 /afk started at 2026-07-11T21:15:42.043Z on runner codex (worker w8C4I). branch: afk/w8C4I/63-blobstore-trait-content-addressed-fs-bac

[filipeforattini]

Decision card — BlobStore trait + content-addressed fs backend (ADR-0006) (#63)

Pending decision: Human guidance required.

Status

PR	CI	Mergeability	Head
—	—	⏳ UNKNOWN	—

Refreshed: 2026-07-11 21:42 UTC

Available actions

Post a comment with one of:

• /approve — merge the linked PR and close this issue
• /approve-ci — merge when all CI checks pass (waits if pending)
• /reject [reason] — close the PR without merging; reopen for rework
• /requeue <guidance> — send back to agent with guidance

Or reply in plain English — the bot maps your intent to an action.
Your instructions are processed securely; issue and PR content is treated as untrusted data.

[filipeforattini]

worker `w8C4I` · status: blocked · duration: 27m26s · diff: main-red-untracked · attempt: 1

notes

diff

live branch: afk/w8C4I/63-blobstore-trait-content-addressed-fs-bac
compare/main...afk-attempts/w8C4I/63-blobstore-trait-content-addressed-fs-bac

[filipeforattini]

🤖 /afk: Refusing admin-merge onto red main because no open main-red repair issue exists. Restore the tracked-red visibility gate by letting syncMainRedRepairIssue auto-file "main-red repair: baseline probe failures on main" from the AFK feedback baseline probe before landing. The attempt branch afk/w8C4I/63-blobstore-trait-content-addressed-fs-bac is intact and validated, but landing is held until the tracked-red repair issue exists. The auto-file attempt for the main-red repair issue failed and must be inspected: gh: failed to create issue (code 1): could not add label: 'priority:urgent' not found. Requeue after the auto-file path recreates it.