diff --git a/.beads/interactions.jsonl b/.beads/interactions.jsonl index 4a39b0120..36f1ad8cb 100644 --- a/.beads/interactions.jsonl +++ b/.beads/interactions.jsonl @@ -46,3 +46,5 @@ {"id":"int-2fceaface0b1804f99343a043a446532","kind":"field_change","created_at":"2026-08-22T12:16:02.43722871Z","actor":"Sam Catlow","issue_id":"archie-core-azbo","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Removed the unwired BasePlatformAdapter, SendResult, ChatInfo, and their test-only stub. CapabilitiesOf is absent from the current checkout/history. Gateway and worktree tests pass. task check passes all packages except the pre-existing tracked agentworker architecture failure archie-core-hqst."}} {"id":"int-41f3180369b3e3d59287b8b661403433","kind":"field_change","created_at":"2026-08-22T15:03:38.692577153Z","actor":"Sam Catlow","issue_id":"archie-core-1786637493329-136-49b39c78","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Media portion delivered: gateway.MediaSender + telegramMediaSender + TurnStream.Media wiring in Telegram's liveReply. Typing/edit/delete indicators from this issue's original scope are NOT done -- splitting them out if still wanted, since they're unrelated to the video-gen work that drove this."}} {"id":"int-46b6d680396e11becb59162374a2ab2d","kind":"field_change","created_at":"2026-08-22T15:34:28.584715451Z","actor":"Sam Catlow","issue_id":"archie-core-3ghy","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Shipped and verified: task check equivalent (fmt/vet/build/test/lint) is clean across every touched package, red-then-green throughout. See the issue description for what's in scope and what's explicitly deferred."}} +{"id":"int-5acd1f65b747a819d5989f2cbd6555f9","kind":"field_change","created_at":"2026-08-22T18:14:27.709722923Z","actor":"Sam Catlow","issue_id":"archie-core-bia3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Release blockers fixed and pushed to main: ea76432 restored the media delivery result without reviving BasePlatformAdapter; ef2abd1 and bf72384 made the ClaimTurn regression isolate its intended race and yield between bounded SQLITE_BUSY retries. Full task check and fresh adversarial reviews passed."}} +{"id":"int-5dbcbfe3c8952f34e98764ab2cbd8385","kind":"field_change","created_at":"2026-08-22T18:14:27.90016743Z","actor":"Sam Catlow","issue_id":"archie-core-mzok","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Release blockers fixed and pushed to main: ea76432 restored the media delivery result without reviving BasePlatformAdapter; ef2abd1 and bf72384 made the ClaimTurn regression isolate its intended race and yield between bounded SQLITE_BUSY retries. Full task check and fresh adversarial reviews passed."}} diff --git a/.beads/issues.jsonl b/.beads/issues.jsonl index 65d68a106..3cbbfc3b4 100644 --- a/.beads/issues.jsonl +++ b/.beads/issues.jsonl @@ -1,3 +1,5 @@ +{"_type":"issue","id":"archie-core-mzok","title":"Make ClaimTurn insert-race regression deterministic under CI","description":"GitHub deploy run 32587841233 failed after the gateway compile fix because TestClaimTurnConcurrentInsertRaceNeverReturnsAnError launched 200 concurrent SQLite claims and exhausted its immediate retry loop with SQLITE_BUSY. The test's stated target is the two-connection same-turn insert race, not unrelated global write-lock saturation.","acceptance_criteria":"The regression still races two independent stores over the same turn ID; unrelated cross-trial SQLite contention cannot exhaust retries; repeated focused runs, task check, and diff-scoped lint pass; fresh adversarial review has zero surviving findings.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-22T17:34:07Z","created_by":"Sam Catlow","updated_at":"2026-08-22T18:14:28Z","started_at":"2026-08-22T17:34:11Z","closed_at":"2026-08-22T18:14:28Z","close_reason":"Release blockers fixed and pushed to main: ea76432 restored the media delivery result without reviving BasePlatformAdapter; ef2abd1 and bf72384 made the ClaimTurn regression isolate its intended race and yield between bounded SQLITE_BUSY retries. Full task check and fresh adversarial reviews passed.","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-bia3","title":"Fix merged gateway capability contract blocking GitHub deploy","description":"PR #560 removed the dead BasePlatformAdapter while PR #561 independently added adapter_capabilities.go and tests that still depend on it. Both branches passed alone, but merged main no longer compiles, so deploy.yml cannot publish the intended video-generation release.","acceptance_criteria":"internal/gateway compiles without BasePlatformAdapter; live Telegram media delivery and capability reporting remain covered; task check and lint pass; a fresh adversarial review has zero surviving findings.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-22T17:15:14Z","created_by":"Sam Catlow","updated_at":"2026-08-22T18:14:28Z","started_at":"2026-08-22T17:15:22Z","closed_at":"2026-08-22T18:14:28Z","close_reason":"Release blockers fixed and pushed to main: ea76432 restored the media delivery result without reviving BasePlatformAdapter; ef2abd1 and bf72384 made the ClaimTurn regression isolate its intended race and yield between bounded SQLITE_BUSY retries. Full task check and fresh adversarial reviews passed.","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-1ysw.1","title":"Bind worktree RPC operations to the dispatched task","description":"The sandboxed agent can currently choose owner, repo, issue, base, and branch on worktree RPC requests. The daemon then performs host deletion and credentialed forge operations without correlating the request to the dispatched task or enforcing WorkDir containment.","acceptance_criteria":"Reject traversal and unconfigured or task-mismatched coordinates before any filesystem or forge side effect; derive or validate the permitted branch; regression tests fail on the old behavior and pass on the fix.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:43Z","created_by":"Sam Catlow","updated_at":"2026-08-22T11:47:02Z","started_at":"2026-08-22T11:02:03Z","closed_at":"2026-08-22T11:47:02Z","close_reason":"Implemented per-dispatch publication grants, removed sandbox-selected prepare/path authority, made repository worktree keys collision-free, and added fail-closed legacy migration/cleanup coverage.","dependencies":[{"issue_id":"archie-core-1ysw.1","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:42Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-1ysw","title":"Repair internal/worktree correctness and trust-boundary defects","description":"Track the concrete worktree-package defects proven by the 2026-08-22 evidence-gated review. Child bugs cover RPC authority/path containment, repository-key isolation, retry/base/diff correctness, push lifecycle, terminal cleanup, cancellation, and branch naming. This epic groups implementation only; each child has its own observable acceptance criteria.","acceptance_criteria":"All child bugs are closed with red-green regression tests, scoped lint passes, and the repository quality gate is clean.","status":"open","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:18Z","created_by":"Sam Catlow","updated_at":"2026-08-22T11:01:18Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-t2db.5","title":"Security: an unauthenticated endpoint must not be able to run an agent","description":"P0 within this epic because the feature's own pitch is the threat model: a public intake surface whose output is an agent with tool access and a repo. Get this wrong and a webhook URL is remote code execution with extra steps.\n\nNon-negotiables to design:\n\n- Per-source authentication. A source registers with a secret (HMAC, as internal/channels/webhook already does per route) before its events can trigger anything. Capture-only for unknown senders is acceptable; triggering is not.\n- Human approval before a binding goes live. An operator authoring a binding is a deliberate act; an event arriving is not. Nothing should self-arm.\n- Rate and volume limits per source, so capture cannot be used to exhaust disk or drown the inspector.\n- Payload content is untrusted input flowing into an agent prompt. Treat prompt injection as expected, not exceptional -- the sender controls that text, and the agent has tools. Bound what a playbook-triggered workflow may do.\n- Captured payloads may contain secrets from the sending system. Decide retention, redaction and who can view them; internal/memory/scrubber may already have applicable prior art.\n\nArchie's own principle applies: environmental enforcement over prompt rules. 'The agent should ignore instructions in the payload' is not a control.","acceptance_criteria":"An event from an unauthenticated source can be captured but cannot trigger a workflow; a new binding requires explicit human approval before it arms; per-source rate limits exist; the blast radius of a playbook-triggered workflow is bounded by code rather than by prompt text; retention and visibility of captured payloads is decided and documented.","notes":"2026-08-22: security design decided and documented in docs/prds/webhook-intake-security.md, covering all five non-negotiables from this bead's description:\n1. Per-source auth reuses internal/channels/webhook's existing HMAC-SHA256 scheme; capture accepts unsigned events (visible, marked unauthenticated), only authenticated events can ever match a binding.\n2. Bindings gain a draft -\u003e pending_approval -\u003e armed state machine; any edit to an armed binding drops it back to pending_approval so approval can't be bypassed by editing. Modeled on telegram's existing dangerousAction/pendingApproval flow (dangerous.go/approval.go).\n3. Per-source token-bucket rate limiting (precedent: pairing/store.go's MaxPendingPerPlatform); limit-exceeded is an observable 429, not a silent drop.\n4. Blast radius bounded by the SAME code-level controls every task already gets -- gate, diff_cap_lines, sandboxed container, worktree isolation -- no new relaxation for playbook-triggered work, and payload text is ordinary untrusted prompt input, never a trusted instruction.\n5. 7-day configurable retention on captured payloads; best-effort redaction reusing gateway/stream.go's sensitiveParameterKey heuristic before persisting; visibility gated by the same dashboard auth as every other webui surface.\n\nThis bead's code-level acceptance criteria (capture-can't-trigger, rate limits exist, blast-radius bounded, approval gate) cannot be implemented yet: they constrain t2db.1 (capture), 7d5u.3 (intake family) and t2db.4 (binding), none of which have landed. This document is the contract those beads build against -- do not build any of them without satisfying it. Leaving this bead in_progress rather than closing it; it closes when t2db.1/7d5u.3/t2db.4 land and demonstrably satisfy points 1-5, not before.","status":"in_progress","priority":0,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:45:46Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:01Z","started_at":"2026-08-21T14:51:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/536","dependencies":[{"issue_id":"archie-core-t2db.5","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-08-21T23:45:45Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}