diff --git a/.beads/interactions.jsonl b/.beads/interactions.jsonl index 0c52e3959..66de6d3c1 100644 --- a/.beads/interactions.jsonl +++ b/.beads/interactions.jsonl @@ -233,3 +233,14 @@ {"id":"int-7866a318104d743ab844af3f5f65b83b","kind":"field_change","created_at":"2026-08-03T13:03:16.844776253Z","actor":"Sam Catlow","issue_id":"archie-core-8u8.4","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"SQLite FTS lifecycle and literal-query guarantees are regression-protected; all focused/race/lint/format validation passes and independent review is clean."}} {"id":"int-b1f91a20f5ac5daa001747e80d8dd574","kind":"field_change","created_at":"2026-08-03T13:16:36.024444137Z","actor":"Sam Catlow","issue_id":"archie-core-8u8.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"SourceID parity and metadata-safe persistence are verified on NellDB and SQLite; all focused/race/lint/format validation passes and independent review has no blockers."}} {"id":"int-ee825a6b9c8e5d56d8d33f5a9a8a2a9c","kind":"field_change","created_at":"2026-08-03T15:17:17.214255978Z","actor":"Sam Catlow","issue_id":"archie-core-0y4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"File logging shipped: internal/logging with [log] file/level/max_size_mb/keep/quiet, size-based rotation with retention, no new dependency. A bad log path degrades to stderr with an error rather than killing the daemon. Verified end to end."}} +{"id":"int-8ebf0b3f2d74575081ee170b57704ffa","kind":"field_change","created_at":"2026-08-03T16:08:59.401228612Z","actor":"Sam Catlow","issue_id":"archie-core-3cf.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Completed responsive table containment across dashboard, tasks, settings, and workflows; added narrow-screen filter wrapping and grid shrink safeguards. Validated with ui npm test and npm run build; live daemon verification requires restarting the embedded UI bundle."}} +{"id":"int-7dfa3e120596080b39bc36a78c34c7ea","kind":"field_change","created_at":"2026-08-03T16:17:40.662105361Z","actor":"Sam Catlow","issue_id":"archie-core-3cf.7","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented layered project/shared/user-global skill discovery, deterministic precedence, global activation support, UI messaging, and tests."}} +{"id":"int-c21fcb5dcefe9c5d3c97c08a1b7e171d","kind":"field_change","created_at":"2026-08-03T16:27:58.198289341Z","actor":"Sam Catlow","issue_id":"archie-core-3cf.8","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented activity-to-task navigation, task source links using configured forge host, and Tasks KPI/table spacing. UI tests, build, and diff checks pass."}} +{"id":"int-c71ac05621a752929c58e232a8507c75","kind":"field_change","created_at":"2026-08-04T12:25:25.181652246Z","actor":"Sam Catlow","issue_id":"archie-core-cz8","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} +{"id":"int-3da01b667ab38bf334add7df8a18c0a8","kind":"field_change","created_at":"2026-08-04T12:25:25.937286678Z","actor":"Sam Catlow","issue_id":"archie-core-8k8","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} +{"id":"int-ce7aff318c5f03425427d6e0b7603702","kind":"field_change","created_at":"2026-08-04T12:25:26.342673397Z","actor":"Sam Catlow","issue_id":"archie-core-7s3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} +{"id":"int-cd41d327d95d5e9fb8d9915ae17930cc","kind":"field_change","created_at":"2026-08-04T12:25:26.715151228Z","actor":"Sam Catlow","issue_id":"archie-core-jex","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} +{"id":"int-f782b0c2638b0a12d16180ecb4701142","kind":"field_change","created_at":"2026-08-04T12:25:27.112314833Z","actor":"Sam Catlow","issue_id":"archie-core-x35","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} +{"id":"int-fdf0265456d2f378d6d26948e61e2aff","kind":"field_change","created_at":"2026-08-04T12:25:27.498290224Z","actor":"Sam Catlow","issue_id":"archie-core-6e0","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} +{"id":"int-28c9cc5292bd7ac7dc4b655b57edf8f0","kind":"field_change","created_at":"2026-08-04T12:25:27.885008748Z","actor":"Sam Catlow","issue_id":"archie-core-i6q","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} +{"id":"int-b47373a147adbb99b00f6eae652ebcff","kind":"field_change","created_at":"2026-08-04T12:25:28.265789043Z","actor":"Sam Catlow","issue_id":"archie-core-la1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} diff --git a/.beads/issues.jsonl b/.beads/issues.jsonl index 149eb3e3f..51f21c741 100644 --- a/.beads/issues.jsonl +++ b/.beads/issues.jsonl @@ -1,6 +1,6 @@ -{"_type":"issue","id":"archie-core-cz8","title":"fix(gateway): /compress destroys message identity, breaking dedup permanently","description":"applyCompress (session_commands.go:561-573) rebuilds retained head/tail turns as bare Message{From, Text}, dropping MessageID, SourceID and At. newMessageID with an empty SourceID returns a random UUID, so every protected message is deleted and re-inserted under a new identity with source_id NULL and _ts reset to now.\n\nCONFIRMED by two independent reviewers, executed on BOTH backends. Before compress, redelivering tg-59 is a correct no-op (60 stays 60). After compress the same redelivery duplicates (24 -\u003e 25). So archie-core-963's whole guarantee survives only until the first /compress -- after that, a Telegram 24h backlog replay on restart appends every surviving message a second time.\n\nAlso violates messaging-and-work-intake.md:88-90 (immutable application-generated MessageID) and 112-114 (immutable records), and dangles any branch-point correlation to the old IDs.\n\nBlocks archie-core-963 and archie-core-0ua.","status":"open","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:00:51Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:00:51Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-cz8","title":"fix(gateway): /compress destroys message identity, breaking dedup permanently","description":"applyCompress (session_commands.go:561-573) rebuilds retained head/tail turns as bare Message{From, Text}, dropping MessageID, SourceID and At. newMessageID with an empty SourceID returns a random UUID, so every protected message is deleted and re-inserted under a new identity with source_id NULL and _ts reset to now.\n\nCONFIRMED by two independent reviewers, executed on BOTH backends. Before compress, redelivering tg-59 is a correct no-op (60 stays 60). After compress the same redelivery duplicates (24 -\u003e 25). So archie-core-963's whole guarantee survives only until the first /compress -- after that, a Telegram 24h backlog replay on restart appends every surviving message a second time.\n\nAlso violates messaging-and-work-intake.md:88-90 (immutable application-generated MessageID) and 112-114 (immutable records), and dangles any branch-point correlation to the old IDs.\n\nBlocks archie-core-963 and archie-core-0ua.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:00:51Z","created_by":"Sam Catlow","updated_at":"2026-08-04T12:25:25Z","started_at":"2026-08-03T16:13:11Z","closed_at":"2026-08-04T12:25:25Z","close_reason":"Closed","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-8u8","title":"feat(gateway): migrate canonical session/message store to SQLite","description":"docs/architecture/messaging-and-work-intake.md:107 requires the canonical session and message implementation to supply durable SQLite round trips. The current store is NellDB-backed.\n\nScope is the SETTLED parts of the messaging architecture only:\n- SQLite persistence (modernc.org/sqlite; FTS5 verified available at 3.53.3, no CGo)\n- application-generated canonical MessageID, platform IDs as correlation only (doc 88-90)\n- immutable message records (doc 112-114)\n- append-only linear sequence per conversation (doc 128)\n- real transactions for ReplaceMessages and Delete\n\nExplicitly OUT of scope: the rich typed-content / tool-call / tool-result model and delivery-attempt semantics. docs/architecture/messaging-and-work-intake.md:273-284 lists the canonical inbound message model, source-correlation model, and outbound delivery/retry/dedup semantics as DECISIONS STILL REQUIRED, so they are not specified enough to implement. That work belongs to archie-core-abg.16.\n\nDecision by Sam 2026-08-03 after the third review surfaced that the NellDB-vs-SQLite question was already settled by the architecture docs.","notes":"SQLite SessionStore implemented and verified 2026-08-03. Not yet wired into production.\n\nAdded (no existing production file touched):\n- internal/gateway/session_store_sqlite.go -- SessionStore on modernc.org/sqlite. Real sql.Tx for ReplaceMessages and Delete, which is the actual reason for the migration: /compress gets genuine atomicity instead of the write-then-delete approximation the NellDB path needs. FTS5 external-content index (content='messages', content_rowid='id') kept in sync by AFTER INSERT/UPDATE/DELETE triggers, so sync is enforced by the schema and no Go code path can forget it.\n- internal/gateway/sessionstore_conformance_test.go -- runSessionStoreSuite(t, newStore), the backend-agnostic contract.\n- Conformance hooks for both backends.\n\nVERIFIED, not taken on trust:\n- 19 identical subtest groups pass against BOTH backends. The suite is the migration gate.\n- FTS index does not drift: search and count stay equal through delete (5-\u003e3), replace (-\u003e1) and session delete (-\u003e0); no cross-session leak.\n- FTS5 syntax injection neutralised: 'text:hello', '\"unbalanced', 'NEAR(a b)', '*', 'needle OR elsewhere' all return 0 hits with no error, confirming terms are escaped phrases AND'ed rather than operators.\n\nBehavioural differences from NellDB, both improvements:\n- MessagePage.Truncated is always false. SQLite gives an exact COUNT(*), so the MaxTextSearchLimit ceiling that field exists to describe does not apply.\n- SourceID is persisted and round-trips; the NellDB path derives the canonical ID from it but never stores it.\n\nCleanup: the two agents ran in parallel, so the SQLite implementation shipped 22 standalone tests written before the suite existed. 18 duplicated suite coverage and were removed (701 -\u003e 170 lines); the 4 kept are genuinely SQLite-specific (transaction atomicity, Truncated semantics, error paths, file creation).\n\ntask check clean, golangci-lint ./internal/gateway/... 0 issues, -race clean.\n\nREMAINING: wire cmd/archied over (config switch), decide the NellDB path's retirement, adversarial review of the combined diff.","status":"open","priority":0,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T10:03:05Z","created_by":"Sam Catlow","updated_at":"2026-08-03T11:54:41Z","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-0ua","title":"fix(gateway): make /compress failure-safe","description":"applyCompress swallows MessageCount and DeleteRecentMessages errors (allCount, _ := and _, _ =) then deletes all messages BEFORE saving the compressed replacement. A crash or error between the two loses the session's entire history unrecoverably. Add a store-level ReplaceMessages that saves first and deletes the previously-listed IDs after, so the failure mode is recoverable duplicates rather than total loss.","notes":"Fixed. Added SessionStore.ReplaceMessages, and applyCompress now calls it instead of MessageCount + DeleteRecentMessages + SaveMessages with both errors discarded.\n\nReplaceMessages snapshots the existing document IDs, writes the replacement, then deletes exactly the snapshotted IDs. Ordering matters: writing first means an interruption leaves both sets present (recoverable duplicates) rather than an empty session. The previous delete-then-save order lost the entire history if anything failed in between, and it discarded the errors that would have told you.\n\nDeleting by snapshotted ID also avoids the newest-n trap: DeleteRecentMessages(allCount) after a save would have deleted the replacement.","status":"open","priority":0,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T09:25:26Z","created_by":"Sam Catlow","updated_at":"2026-08-03T09:30:33Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-0ua","title":"fix(gateway): make /compress failure-safe","description":"applyCompress swallows MessageCount and DeleteRecentMessages errors (allCount, _ := and _, _ =) then deletes all messages BEFORE saving the compressed replacement. A crash or error between the two loses the session's entire history unrecoverably. Add a store-level ReplaceMessages that saves first and deletes the previously-listed IDs after, so the failure mode is recoverable duplicates rather than total loss.","notes":"ADVERSARIAL PASS 2026-08-04 (fresh reviewer). Does NOT close.\n\nCore claim HELD on both backends: ReplaceMessages writes before deleting, cannot delete a record it just wrote, and an injected failure leaves the full 60-message history intact with the error propagated. Two concurrent /compress runs end with exactly 24 messages and one summary. No error swallowing remains on this path.\n\nBLOCKED BY: archie-core-8k8 (bare /compress can NEVER apply -- the failure-safe path this bead added is unreachable via the documented command), archie-core-6e0 (mid-compress inbound message destroyed, unrecoverable, window is in the caller), archie-core-cz8 (compress re-mints identity), archie-core-7ve (applyCompress has zero test coverage; the NellDB failure-safety test never induces a failure).","status":"open","priority":0,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T09:25:26Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:02:25Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-b4i","title":"fix(gateway): chronological message ordering — _ts + per-session collections","description":"SaveMessages keys from i=0 and overwrites the first N messages of any non-empty session (verified: m0/m1 destroyed by a bulk save). SaveMessage derives seq from len(rows) so deletes cause key reuse. The 'at' timestamp is written and never read; ordering is by insertion counter, not time.\n\nFix: add Message.At, write nell.TimestampField (_ts), give each session its own NellDB collection (a room IS a collection), key messages by time-ordered unique IDs, and order/page via sdk.ScanSince. Clean break on existing data (carina is a testing ground).","notes":"ADVERSARIAL PASS 2026-08-04 (fresh reviewer, no knowledge of the implementation). Does NOT close.\n\nThe bead's own claims HELD under heavy probing: _ts is a bare JSON number on every write path (raw payload inspected; searching '2026' matches nothing), the clamp survives restart and a backwards clock, 32 concurrent saves to one session produce no duplicate _ts, paging over 2500 messages drops and duplicates nothing at boundaries and terminates on a short page, Truncated reflects the result set not the request, and per-session collection names need no sanitisation (nell.CompositeKey is byte-length-prefixed and provably injective; 5000-char, NUL-embedded and ../../ session IDs all round-trip).\n\nBLOCKED BY: archie-core-7s3 (List/GetByChannel are not newest-first, so the ordering this bead establishes inside a session is undone by picking the wrong session on restart), archie-core-cz8 (/compress re-mints identity and timestamps), archie-core-le6 items 4-6.\n\nAlso confirmed: /branch inherits parent MessageIDs so the session-scoped derivation never runs for branched history (see archie-core-la1).","status":"open","priority":0,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T02:27:48Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:02:25Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-ci3","title":"Telegram chat replies use stale and reordered session context","description":"Live Telegram conversation shows replies answering earlier user messages and replayed user history in non-chronological order. Trace ingestion, turn lanes, Nell persistence/history ordering, prompt construction, and response routing to identify the production cause.","acceptance_criteria":"Root cause is demonstrated with code path, live evidence, and a focused reproducer; affected ordering contract and correct fix seam are identified.","notes":"2026-08-03: Ordering half is FIXED by upgrading NellDB to v0.3.0 (go.mod v0.2.5 -\u003e v0.3.0). The ci3 17-message reproducer now passes: position 0 is seq 00 and all 17 are in order via the existing AllDocs path. No archie-core code change was required for the ordering defect — v0.3.0 gives List/AllDocs a deterministic (WallTime, Counter, collection, ID) order, which is exactly the unsorted-map root cause recorded above.\n\nStill open, tracked in archie-core-b4i (separate defect, not an ordering bug): SaveMessages keys from i=0 and destroys the first N messages of a non-empty session, and SaveMessage derives seq from len(rows) so deletes cause key reuse. Verified by reproducer.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-31T05:15:30Z","created_by":"Sam Catlow","updated_at":"2026-08-03T09:02:41Z","started_at":"2026-07-31T05:15:40Z","closed_at":"2026-08-03T09:02:41Z","close_reason":"Fixed by upgrading NellDB v0.2.5 -\u003e v0.3.0 (go.mod). Root cause as recorded: v0.2.5 sdk.DocDB.AllDocs consumed Store.List without sorting and LogStore.List iterated a map. v0.3.0 gives List/AllDocs a deterministic (WallTime, Counter, collection, ID) order.\n\nVerified with the 17-message reproducer from this issue: position 0 is now seq 00 and all 17 return in order. No archie-core code change was needed for the ordering defect itself.\n\nThe wider blast radius noted on this issue (prompt history, /undo, /retry, branch/resume copying, search ordering) is covered by the internal/gateway migration in archie-core-b4i, which moves message history onto _ts + per-session collections + ScanSince paging. Session list ordering is unchanged and still sorts newest-first in listAllLocked.","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-abg.16.33","title":"Telegram: allowlist senders, fail closed when unset","description":"telegram.New is called with a nil allowlist and isChatAllowed returns true when the allowlist is empty, so any Telegram user who finds the bot can talk to it. AllowedChatIDs is not plumbed into config at all. This gates exposing any real tools to the chat agent: with an MCP shell/filesystem server wired, allow-all becomes RCE for arbitrary senders.","acceptance_criteria":"Allowlist is configurable via config.toml. Unset means deny, not allow. Sender identity (user id) is checked, not just chat id, so a group chat cannot be used to bypass it. Rejections are logged with the sender id. Startup logs loudly when the chat gateway is enabled with an empty allowlist.","status":"closed","priority":0,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-26T19:11:40Z","created_by":"Sam Catlow","updated_at":"2026-07-26T19:15:22Z","closed_at":"2026-07-26T19:15:22Z","close_reason":"Shipped in cec0f3e. 16.33: chat.telegram.allowed_user_ids plumbed through config; empty list now DENIES (was: allowed everyone); matches sender from.id not chat id so groups cannot inherit access; rejections logged with sender id; startup warns on empty list. Old TestIsChatAllowed asserted the vulnerable fail-open behaviour and was replaced with fail-closed tests. Sam's id 1312197967 added to carina's config.toml before push. 16.34: SetMyCommands publishes the command list Router actually handles; non-fatal on failure.","dependencies":[{"issue_id":"archie-core-abg.16.33","depends_on_id":"archie-core-abg.16","type":"parent-child","created_at":"2026-07-27T05:11:40Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} @@ -58,12 +58,12 @@ {"_type":"issue","id":"archie-core-abg.18","title":"[EPIC] Memory: pluggable provider architecture with file-backed persistence","description":"Pluggable memory system to match Hermes parity:\\n\\n1. **MemoryProvider interface**: Abstract interface with methods for initialize(), get_tool_schemas(), prefetch(), sync_turn(), and optional lifecycle hooks (on_session_end, on_session_switch, on_pre_compress, on_memory_write).\\n\\n2. **Built-in file-backed memory**: MEMORY.md and USER.md stored per-session/profile. LLM-callable memory tool with add/replace/remove actions. Frozen snapshot at session start (preserves prefix cache), immediate disk write on updates. Section-sign delimited entries with substring matching.\\n\\n3. **MemoryManager**: Orchestrates built-in + at most one external provider. Background serialized write executor. Prefetch with timeout (8s). Streaming context scrubber that strips injected memory spans from model output.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 4","acceptance_criteria":"An external memory provider (e.g. Honcho, Mem0) can be plugged in via config. The built-in memory tool persists across sessions. Conversation context is recalled on session resume.","status":"closed","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-25T14:02:22Z","created_by":"Sam Catlow","updated_at":"2026-07-28T17:04:41Z","closed_at":"2026-07-28T17:04:41Z","close_reason":"Superseded by merged work: all 32 children complete (32/32, bd flags it 'eligible for close'). MemoryProvider interface, built-in file-backed memory, MemoryManager, scrubber, drain and threat scanning all landed in internal/memory. Nothing left in scope.","dependencies":[{"issue_id":"archie-core-abg.18","depends_on_id":"archie-core-abg","type":"parent-child","created_at":"2026-07-26T00:02:22Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-abg.16","title":"[EPIC] Gateway: rich message model, adapter lifecycle, session management","description":"Foundational gateway infrastructure to match Hermes parity. Three interdependent pieces:\\n\\n1. **Message model**: Replace the 3-field Message struct with a rich MessageEvent (MessageType enum: text/photo/video/audio/voice/document/sticker/command, media_urls, reply_to context, metadata dict, source). This is the wire type every adapter produces.\\n\\n2. **Adapter lifecycle**: Replace the 3-method Gateway interface with a BasePlatformAdapter interface: connect()/disconnect()/send() as required methods, plus optional overrides for typing indicators, edit/delete, image/voice/video/document send, interactive UX (clarify buttons, approval dialogs). Capability flags (supports_code_blocks, splits_long_messages, supports_async_delivery).\\n\\n3. **Session management**: SessionSource struct (platform, chat_id, chat_type, user_id, thread_id, guild_id, profile), AsyncSessionStore for persistent session storage, SessionContext for system prompt injection.\\n\\nAll three blocks together enable adding new platforms as plugins without touching core gateway code.\\n\\nRef: docs/prds/hermes-gap-analysis.md sections 1-2","acceptance_criteria":"New adapters can be added by implementing a Go interface with connect/disconnect/send + optional media methods. Messages carry full metadata through the pipeline. Sessions persist across gateway restarts.","status":"open","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-25T14:02:21Z","created_by":"Sam Catlow","updated_at":"2026-07-25T14:02:21Z","dependencies":[{"issue_id":"archie-core-abg.16","depends_on_id":"archie-core-abg","type":"parent-child","created_at":"2026-07-26T00:02:21Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-jfg","title":"Spawned archie-agent containers not on daemon's docker network — can't reach NATS","description":"Root cause of 'agent still failing on the server': archied's container.Pool.Acquire creates archie-agent containers via the Docker SDK with no NetworkMode set, so Docker attaches them to the default bridge network. archied and nats run on the compose-created 'archie-core_default' network instead, so the spawned container's hostname resolution for 'nats' (from NATS_URL=nats://nats:4222) fails and archie-agent can't connect. Confirmed on carina host logs: archied logs show repeating 'taskrun request failed err=\"nats: no responders available for request\"' for every task, containers created and destroyed within ~1.5s (consistent with archie-agent's NATS client failing fast). Fixed by detecting the daemon's own container's network in NewPool (selfNetwork, via ContainerInspect on os.Hostname()) and setting HostConfig.NetworkMode on spawned containers to match.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-24T03:10:26Z","created_by":"Sam Catlow","updated_at":"2026-07-25T13:04:34Z","closed_at":"2026-07-25T13:04:34Z","close_reason":"Fix already implemented and verified: selfNetwork() in internal/container/pool.go detects the daemon's own container network via ContainerInspect(os.Hostname()) and Acquire() sets HostConfig.NetworkMode to match, so spawned archie-agent containers join the same compose network as nats. Build and internal/container tests pass.","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-x35","title":"fix(gateway): resolve() orphans a session when it loses the double-check race","description":"CONFIRMED by execution with a blocking store decorator. sessionTracker.resolve calls sessions.Save BEFORE cacheActive, which may then discard the ID in favour of a racing caller's. The write is not rolled back.\n\nInterleaving: goroutine A misses the cache and GetByChannel returns empty; meanwhile /new saves a UUID session and setActives it; A resumes, saves the deterministic session 'chat-y', then cacheActive returns the UUID. Store holds 2 sessions; 'chat-y' is unreachable, shows up in /sessions and /topic listings as '(untitled)', and per the newest-first bug can be silently resurrected on restart.\n\nApplies equally to a racing /resume, /branch or /topic \u003cid\u003e -- the daemon genuinely runs commands on lane goroutines while submitTurn resolves on the bot worker.\n\nNote the synchronization itself is correct: all four accesses to sessionTracker.active are guarded, and stripping the locks produces 12 race-detector reports plus an assertion failure, so the test is load-bearing. This is a logic bug inside the guarded code, not a race.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:31Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:31Z","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-i6q","title":"fix(gateway): redelivery dedups the stored turn but still re-runs the model","description":"archie-core-963 made SaveMessage idempotent, but nothing upstream consults the result. cmd/archied/telegram_setup.go:158 respond() calls SaveMessage (now a no-op on redelivery) then unconditionally loads history, calls the model, and saves the reply -- which carries no SourceID, so it always gets a fresh random ID and always appends.\n\nCONFIRMED at store level on both backends: redelivering tg-1 leaves [ping, pong, pong], plus a second billed model turn with any tool side effects executed twice.\n\nThe bead's stated problem ('a re-delivered Telegram update appends a duplicate turn') is half fixed. SaveMessage returns no already-seen signal for the caller to act on.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:30Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:30Z","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-jex","title":"fix(gateway): /topic off poisons the tracker cache with an empty session ID","description":"CONFIRMED by execution. handleTopic (session_commands.go:200) 'off' does setActive(chan, \"\", getActive(chan, threadID)). With no session cached for (chan, threadID), getActive returns \"\" and that empty string is stored. resolve treats map presence as authoritative ('id, ok := t.active[key]; if ok { return id }'), and cacheActive also returns the empty existing value, so nothing can repair it.\n\nReachable when /topic off is the first message on the webhook (webhook.go:169) or email (email.go:207) channel -- both call router.Route directly and never call ResolveSessionKey first, unlike telegram's submitTurn.\n\nBlast radius: every later message in that chat persists under session ID \"\", history is shared with any other poisoned chat, and the turn-lane key becomes \"\" so /stop in one chat kills a turn in another.\n\nSame line is also non-atomic: setActive(...getActive(...)) is two critical sections, so a concurrent /resume or /branch is silently clobbered.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:18Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:18Z","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-7s3","title":"fix(gateway): session resolution is not newest-first, so restart resumes a stale session","description":"Found independently by two reviewers, CONFIRMED by execution.\n\nsessionTracker.resolve (session_commands.go:54-59) comments 'Find the most recent session matching this thread and bot' but returns the first element GetByChannel yields. The wired-up NellDB store returns document-ID order (listAllLocked reverses AllDocs, which sorts by document ID), i.e. UUID-lexicographic -- effectively random. LastActiveAt is populated on every record and never consulted.\n\nScenario: user runs /new 'old', chats, runs /new 'current'; daemon restarts (the tracker cache is in-memory only); the next message resolves to whichever session sorts first. Probed over 10 runs: 4 landed in the OLDER session, answering against pre-/new history. This is the user-visible lost-context class.\n\nAlso a silent backend divergence: SQLite's GetByChannel orders created_at DESC, NellDB does not, and the shared conformance suite does not pin it. Separately, SessionStore.List's doc comment (session_store.go:34-36) promises newest-first and does not deliver: saving zzz-oldest, aaa-middle, mmm-newest returns [zzz-oldest mmm-newest aaa-middle].\n\nBlocks archie-core-b4i and archie-core-gih.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:17Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:17Z","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-6e0","title":"fix(gateway): a message arriving mid-/compress is destroyed","description":"applyCompress reads MessageCount then RecentMessages, and ReplaceMessages later removes everything outside the replacement set. A chat turn that lands between the read and the replace is deleted, never summarised.\n\nCONFIRMED executed on both backends: 'nell: mid-compress inbound message destroyed (stored=24)', 'sqlite: ... (stored=24)'. NellDB deletes it via the AllDocs snapshot; SQLite via DELETE ... WHERE message_id NOT IN (survivors), a survivor-complement.\n\narchie-core-0ua's guarantee (worst case is recoverable duplicates) does not cover this: it is unrecoverable loss, and the store-level fix cannot address it because the window is in the caller. Nothing serialises /compress against an inbound turn.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:02Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:02Z","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-8k8","title":"fix(gateway): /compress argument dispatch is wrong in three ways","description":"session_commands.go:460-478, all CONFIRMED by execution:\n\n1. Bare /compress can never apply. isPreview is 'len(fields) == 0 || --preview || --dry-run', so /compress with no arguments takes the preview branch -- and compressPreview ends with 'Run /compress to apply'. The command tells the user to run a command that does nothing, forever. The failure-safe ReplaceMessages path added by archie-core-0ua is unreachable via the documented command; only '/compress here \u003cN\u003e' reaches it.\n\n2. /compress focus \u003ctopic\u003e silently ignores the topic. focus is validated for arity only; cfg is never modified, so it runs a full default compression and reports success. Irreversible history rewrite from a command the user believes does something narrower.\n\n3. /compress here (no N) and any unrecognised argument (/compress asdf) fall through to a full default compression rather than printing usage, unlike the sibling focus branch.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:02Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:02Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-x35","title":"fix(gateway): resolve() orphans a session when it loses the double-check race","description":"CONFIRMED by execution with a blocking store decorator. sessionTracker.resolve calls sessions.Save BEFORE cacheActive, which may then discard the ID in favour of a racing caller's. The write is not rolled back.\n\nInterleaving: goroutine A misses the cache and GetByChannel returns empty; meanwhile /new saves a UUID session and setActives it; A resumes, saves the deterministic session 'chat-y', then cacheActive returns the UUID. Store holds 2 sessions; 'chat-y' is unreachable, shows up in /sessions and /topic listings as '(untitled)', and per the newest-first bug can be silently resurrected on restart.\n\nApplies equally to a racing /resume, /branch or /topic \u003cid\u003e -- the daemon genuinely runs commands on lane goroutines while submitTurn resolves on the bot worker.\n\nNote the synchronization itself is correct: all four accesses to sessionTracker.active are guarded, and stripping the locks produces 12 race-detector reports plus an assertion failure, so the test is load-bearing. This is a logic bug inside the guarded code, not a race.","status":"in_progress","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:31Z","created_by":"Sam Catlow","updated_at":"2026-08-04T12:15:33Z","started_at":"2026-08-04T12:15:33Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-i6q","title":"fix(gateway): redelivery dedups the stored turn but still re-runs the model","description":"archie-core-963 made SaveMessage idempotent, but nothing upstream consults the result. cmd/archied/telegram_setup.go:158 respond() calls SaveMessage (now a no-op on redelivery) then unconditionally loads history, calls the model, and saves the reply -- which carries no SourceID, so it always gets a fresh random ID and always appends.\n\nCONFIRMED at store level on both backends: redelivering tg-1 leaves [ping, pong, pong], plus a second billed model turn with any tool side effects executed twice.\n\nThe bead's stated problem ('a re-delivered Telegram update appends a duplicate turn') is half fixed. SaveMessage returns no already-seen signal for the caller to act on.","status":"in_progress","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:30Z","created_by":"Sam Catlow","updated_at":"2026-08-04T12:21:24Z","started_at":"2026-08-04T12:21:24Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-jex","title":"fix(gateway): /topic off poisons the tracker cache with an empty session ID","description":"CONFIRMED by execution. handleTopic (session_commands.go:200) 'off' does setActive(chan, \"\", getActive(chan, threadID)). With no session cached for (chan, threadID), getActive returns \"\" and that empty string is stored. resolve treats map presence as authoritative ('id, ok := t.active[key]; if ok { return id }'), and cacheActive also returns the empty existing value, so nothing can repair it.\n\nReachable when /topic off is the first message on the webhook (webhook.go:169) or email (email.go:207) channel -- both call router.Route directly and never call ResolveSessionKey first, unlike telegram's submitTurn.\n\nBlast radius: every later message in that chat persists under session ID \"\", history is shared with any other poisoned chat, and the turn-lane key becomes \"\" so /stop in one chat kills a turn in another.\n\nSame line is also non-atomic: setActive(...getActive(...)) is two critical sections, so a concurrent /resume or /branch is silently clobbered.","status":"in_progress","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:18Z","created_by":"Sam Catlow","updated_at":"2026-08-04T12:14:00Z","started_at":"2026-08-04T12:14:00Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-7s3","title":"fix(gateway): session resolution is not newest-first, so restart resumes a stale session","description":"Found independently by two reviewers, CONFIRMED by execution.\n\nsessionTracker.resolve (session_commands.go:54-59) comments 'Find the most recent session matching this thread and bot' but returns the first element GetByChannel yields. The wired-up NellDB store returns document-ID order (listAllLocked reverses AllDocs, which sorts by document ID), i.e. UUID-lexicographic -- effectively random. LastActiveAt is populated on every record and never consulted.\n\nScenario: user runs /new 'old', chats, runs /new 'current'; daemon restarts (the tracker cache is in-memory only); the next message resolves to whichever session sorts first. Probed over 10 runs: 4 landed in the OLDER session, answering against pre-/new history. This is the user-visible lost-context class.\n\nAlso a silent backend divergence: SQLite's GetByChannel orders created_at DESC, NellDB does not, and the shared conformance suite does not pin it. Separately, SessionStore.List's doc comment (session_store.go:34-36) promises newest-first and does not deliver: saving zzz-oldest, aaa-middle, mmm-newest returns [zzz-oldest mmm-newest aaa-middle].\n\nBlocks archie-core-b4i and archie-core-gih.","status":"in_progress","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:17Z","created_by":"Sam Catlow","updated_at":"2026-08-04T12:12:02Z","started_at":"2026-08-04T12:12:02Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-6e0","title":"fix(gateway): a message arriving mid-/compress is destroyed","description":"applyCompress reads MessageCount then RecentMessages, and ReplaceMessages later removes everything outside the replacement set. A chat turn that lands between the read and the replace is deleted, never summarised.\n\nCONFIRMED executed on both backends: 'nell: mid-compress inbound message destroyed (stored=24)', 'sqlite: ... (stored=24)'. NellDB deletes it via the AllDocs snapshot; SQLite via DELETE ... WHERE message_id NOT IN (survivors), a survivor-complement.\n\narchie-core-0ua's guarantee (worst case is recoverable duplicates) does not cover this: it is unrecoverable loss, and the store-level fix cannot address it because the window is in the caller. Nothing serialises /compress against an inbound turn.","status":"in_progress","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:02Z","created_by":"Sam Catlow","updated_at":"2026-08-04T12:17:57Z","started_at":"2026-08-04T12:17:57Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-8k8","title":"fix(gateway): /compress argument dispatch is wrong in three ways","description":"session_commands.go:460-478, all CONFIRMED by execution:\n\n1. Bare /compress can never apply. isPreview is 'len(fields) == 0 || --preview || --dry-run', so /compress with no arguments takes the preview branch -- and compressPreview ends with 'Run /compress to apply'. The command tells the user to run a command that does nothing, forever. The failure-safe ReplaceMessages path added by archie-core-0ua is unreachable via the documented command; only '/compress here \u003cN\u003e' reaches it.\n\n2. /compress focus \u003ctopic\u003e silently ignores the topic. focus is validated for arity only; cfg is never modified, so it runs a full default compression and reports success. Irreversible history rewrite from a command the user believes does something narrower.\n\n3. /compress here (no N) and any unrecognised argument (/compress asdf) fall through to a full default compression rather than printing usage, unlike the sibling focus branch.","status":"in_progress","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:02Z","created_by":"Sam Catlow","updated_at":"2026-08-04T12:08:49Z","started_at":"2026-08-04T12:08:49Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-rml","title":"fix(memory): startup accepted an unusable memory directory","description":"cmd/archied/main.go builds the builtin memory provider at filepath.Join(cfg.WorkDir, \"memory\") and logs 'memory manager started' regardless of whether that path exists or is writable. builtin.NewStore treats ENOENT as an empty document and Reload does the same, so a missing directory is indistinguishable from a memory with nothing in it yet.\n\nFound live: carina's config was copied to the laptop with work_dir = /var/lib/archie/work, a container path that does not exist here. archied logged 'memory manager started dir=/var/lib/archie/work/memory' and ran with no memory at all. The failure would only have surfaced at the agent's first memory write, when writeFileAtomic's MkdirAll hit EACCES on /var/lib -- mid-conversation, as a tool error, after startup said it was fine.\n\nFixed: builtin.New now does MkdirAll(cfg.Dir) and returns an error the operator can act on, so an unusable path fails at startup where the existing error path already exits non-zero. New's doc claimed 'the provider is ready for use as soon as New returns'; it now is.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:00:07Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:00:07Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-3cf.6","title":"Restore compliance with the approved Archie visual design","description":"The current dashboard does not follow the supplied reference design. Rework the shell and page composition around the reference: a framed rounded workspace, compact top navigation, prominent welcome/header area, adjacent primary actions, getting-started panel, prominent status/compliance visualization, compact KPI strip with trend marks, forecast/projection panel, and live-runs table. Match the reference visual treatment: layered rounded surfaces, soft translucent panels, luminous abstract background treatment, compact information-dense cards, restrained status colours, and consistent icon/action placement. Do not reinterpret this as a generic dark admin console or as a light editorial marketing page. Capture desktop and narrow-viewport visual evidence before closing.","status":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-03T15:18:32Z","created_by":"Sam Catlow","updated_at":"2026-08-03T15:20:01Z","dependencies":[{"issue_id":"archie-core-3cf.6","depends_on_id":"archie-core-3cf","type":"parent-child","created_at":"2026-08-04T01:18:32Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-3cf.1","title":"Fix dashboard KPI tiles rendering blank values","description":"Authenticated runtime inspection of the supplied dashboard URL showed the first three dashboard stat tiles visually rendered with empty headline values while their comparison text was present; the Tokens used tile rendered 0. Trace the stat tile/render/update path and make every KPI display a stable value during initial load, loading, zero-data, and API-error states. Add focused regression coverage and verify against the live dashboard.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T15:17:39Z","created_by":"Sam Catlow","updated_at":"2026-08-03T15:17:58Z","dependencies":[{"issue_id":"archie-core-3cf.1","depends_on_id":"archie-core-3cf","type":"parent-child","created_at":"2026-08-04T01:17:38Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} @@ -76,8 +76,8 @@ {"_type":"issue","id":"archie-core-8u8.4","title":"test(gateway): pin SQLite FTS lifecycle and literal-query semantics","description":"Trigger-driven FTS synchronization and hostile-query escaping were manually verified but are not retained by the trimmed SQLite-specific test suite. Preserve these SQLite-specific guarantees without duplicating the shared SessionStore contract.","acceptance_criteria":"Table-driven tests show FTS search/count remains correct after message deletion, ReplaceMessages, and session deletion with no cross-session leak; hostile inputs including column syntax, unmatched quotes, NEAR, wildcard, and boolean operators return literal-match behavior without syntax errors; multi-term queries pin AND semantics; tests stay SQLite-specific and focused.","notes":"Implemented and independently reviewed 2026-08-03. Added SQLite-specific FTS lifecycle tests for delete/replacement/session deletion, cross-session isolation, exact counts, hostile literal queries, multi-term AND semantics, exact MATCH escaping, and FTS5 rank=1 integrity checks. Sensitivity test proves the integrity check catches orphaned index entries when the delete trigger is absent. Focused tests, full gateway suite, gateway race, scoped lint, and format check pass. Fresh DeepSeek V4 Flash review reports zero surviving findings.","status":"closed","priority":1,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T12:34:38Z","created_by":"Sam Catlow","updated_at":"2026-08-03T13:03:17Z","started_at":"2026-08-03T12:43:49Z","closed_at":"2026-08-03T13:03:17Z","close_reason":"SQLite FTS lifecycle and literal-query guarantees are regression-protected; all focused/race/lint/format validation passes and independent review is clean.","dependencies":[{"issue_id":"archie-core-8u8.4","depends_on_id":"archie-core-8u8","type":"parent-child","created_at":"2026-08-03T22:34:38Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-8u8.2","title":"fix(gateway): align newest-session ordering across SessionStore backends","description":"SQLite List/GetByChannel order by created_at, while NellDB orders by latest document write/HLC. Touching or re-saving a session can therefore select a different active session after a backend cutover even though both pass the shared suite. Pin one observable newest-session contract and make both adapters satisfy it.","acceptance_criteria":"The shared conformance suite covers multiple sessions with distinct CreatedAt and LastActiveAt values plus Touch/re-save; List and GetByChannel return the same deterministic order on NellDB and SQLite; restart-style resolution selects the same session on both backends; indexes support the chosen SQLite ordering.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T12:34:37Z","created_by":"Sam Catlow","updated_at":"2026-08-03T12:34:37Z","dependencies":[{"issue_id":"archie-core-8u8.2","depends_on_id":"archie-core-8u8","type":"parent-child","created_at":"2026-08-03T22:34:37Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-8u8.1","title":"test(gateway): prove SQLite session rollback and reopen durability","description":"The SQLite SessionStore uses real transactions and WAL, but current tests only verify successful operations through the same open handle. Add adversarial file-backed tests that prove persisted session/message state survives close+reopen and that injected failures during Delete and ReplaceMessages roll the transaction and FTS index back to the original state.","acceptance_criteria":"A file-backed store is closed and reopened with sessions, canonical MessageID, SourceID, text, sender, and timestamps intact; PRAGMA quick_check returns ok; deterministic abort triggers force mid-Delete and mid-ReplaceMessages failures; after each failure the original session, history, counts, and search results remain unchanged; focused and race tests pass.","notes":"Implemented and independently reviewed 2026-08-03. Added file-backed close/reopen round-trip with PRAGMA quick_check plus trigger-injected mid-Delete and mid-ReplaceMessages rollback tests that verify session/history/count/FTS state. Focused gateway tests, gateway race suite, scoped lint, and format check pass. Fresh DeepSeek V4 Flash review found zero blockers; one cosmetic early-failure handle-cleanup note only.","status":"closed","priority":1,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T12:34:36Z","created_by":"Sam Catlow","updated_at":"2026-08-03T12:43:41Z","started_at":"2026-08-03T12:35:02Z","closed_at":"2026-08-03T12:43:41Z","close_reason":"Verified durability and rollback regression coverage; focused/race/lint/format green and independent review has no surviving findings.","dependencies":[{"issue_id":"archie-core-8u8.1","depends_on_id":"archie-core-8u8","type":"parent-child","created_at":"2026-08-03T22:34:35Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-963","title":"feat(gateway): durable message deduplication via upstream IDs","description":"gateway.Message carries no upstream/channel-native message ID, so a re-delivered Telegram update appends a duplicate turn. Add Message.ID and derive the NellDB document ID from it (time-prefixed to preserve the ScanSince ID tie-break), making redelivery an idempotent LWW upsert.","notes":"Third review 2026-08-03. Two architecture violations CONFIRMED against docs/architecture/messaging-and-work-intake.md and fixed.\n\nVIOLATION 1 (identity), doc lines 88-90: 'Every message has an immutable application-generated MessageID. Platform identifiers are external correlation, not substitutes for the canonical ID.' The Telegram message_id was being used AS the document identity. Fixed: Message.ID split into MessageID (canonical, application-generated, populated on read) and SourceID (channel-native correlation). newMessageID derives a UUIDv5 from (namespace, sessionID, sourceID) so the canonical ID is archie's own, deterministic for dedup, and session-scoped so a message copied into a branch gets its own identity. No SourceID means a random UUID.\n\nVIOLATION 2 (immutability), doc lines 112-114: 'The canonical message store MUST preserve messages as immutable records and represent later edits, deletions, and branches through related records or events.' A redelivered edit overwrote the stored record. Fixed: an existing canonical ID makes the write a no-op. TestMessageDeduplication's 'edited text updates in place' case asserted the violating behaviour and now asserts the record stands.\n\nAlso: saveMessageLocked honours an incoming MessageID, so re-saving history read from the store keeps its identity instead of minting a new one -- without this ReplaceMessages churned identities on every read-modify-write.\n\nREJECTED - Spec 1, 'resolveTimestamp produces arrival order rather than Message.At chronological order'. Refuted by the same document, line 128: 'Messages remain an append-only linear sequence within each conversation.' The monotonic clamp implements that contract. The previous review required the clamp to stop a reply preceding its prompt; this one asked for its removal. The architecture settles it.\n\nREJECTED - Spec 2, 'issue 963 requires a time-prefixed upstream document ID'. That text is my own earlier design note in this bead, not a specification, and it was superseded deliberately: encoding time in the key breaks dedup when the monotonic clamp moves a timestamp.\n\nFIXED - duplicate ID generation (Standards 4 / Spec 3): saveMessageLocked generated an ID and messageToDoc generated a second that the caller overwrote, consuming two sequence values per save. messageToDoc is now a free function taking the ID. The wrapping counter is gone entirely; TestMessageIDsAreUnique replaces the obsolete lexicographic-ordering test.\n\nFIXED - Standards 3 naming: ID -\u003e SourceID / MessageID.\n\nOUT OF SCOPE, needs Sam: doc line 107 requires 'durable SQLite round trips' for the canonical message store, and lines 92-107 require typed content, tool-call/tool-result correlation, and roles. That is the abg.16 rich-message-model epic, and it bears directly on the NellDB-vs-SQLite decision taken earlier in this session without reference to these docs.\n\ntask check clean, golangci-lint ./internal/gateway/... 0 issues, -race clean.","status":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T09:25:26Z","created_by":"Sam Catlow","updated_at":"2026-08-03T09:57:05Z","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-gih","title":"fix(gateway): synchronize sessionTracker.active","description":"sessionTracker.active is a plain map with no mutex. go-telegram/bot dispatches each update in its own goroutine, so resolve() writes it while getActive() reads it concurrently. Backend-agnostic Go data race.","notes":"Fixed. sessionTracker gained sync.RWMutex. resolve() reads under RLock, does its I/O unlocked, then commits via cacheActive() under Lock with a double-check so a racing caller's value wins and every caller returns the same session ID. setActive/getActive guarded.\n\nCorrection to the issue description: go-telegram/bot serves updates from a SINGLE worker synchronously (see the comment at internal/channels/telegram/telegram.go:470). The race is real because archie deliberately runs each turn off the caller's goroutine in submitTurn, not because the library fans out.\n\nVerified red: with the guards removed, TestSessionTrackerConcurrentResolve reports 5 DATA RACE warnings under -race. Restored, clean.","status":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T09:25:25Z","created_by":"Sam Catlow","updated_at":"2026-08-03T09:30:32Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-963","title":"feat(gateway): durable message deduplication via upstream IDs","description":"gateway.Message carries no upstream/channel-native message ID, so a re-delivered Telegram update appends a duplicate turn. Add Message.ID and derive the NellDB document ID from it (time-prefixed to preserve the ScanSince ID tie-break), making redelivery an idempotent LWW upsert.","notes":"ADVERSARIAL PASS 2026-08-04 (fresh reviewer). Does NOT close.\n\nClaims (b), (c), (d) HELD identically on both backends: the immutability no-op, original-timestamp retention on redelivery, and honouring an incoming MessageID. newMessageID is deterministic and session-scoped. /retry verified end to end against both real stores with a live Router -- correct text, MessageID, SourceID and re-populated addressing, and the re-save is a no-op.\n\nBLOCKED BY: archie-core-cz8 (/compress destroys the identity this bead establishes -- the guarantee survives only until the first compression), archie-core-i6q (redelivery dedups the stored turn but respond() still re-runs the model, so a duplicate assistant turn and a second billed call still happen), archie-core-la1 item 1 (/branch copies parent MessageIDs; the struct doc says MessageID is 'ignored on write' while both stores honour it).\n\nDEDUP COVERAGE: SourceID is set at exactly one site repo-wide (telegram.go:479). Email and webhook set none, so every SMTP or webhook retry appends. Email has an unused RFC 5322 Message-ID.\n\nREJECTION REVISITED: 'time-prefixed document ID' rejection upheld. The 'clamp vs Message.At' rejection is OVER-CLAIMED -- doc line 128 sits in the Conversation branches section and constrains ordering, not whether the sender's clock may be overwritten; a separate monotonic sequence field would satisfy it too. gateway.go:44-48 documents At as 'when the message happened' while the store persists a mutated value, and no test pins what a caller reads back after a clamp. Sam's call, not the reviewer's.\n\nOUT OF SCOPE, unimplemented: doc lines 112-114 require edits/deletions/branches be represented 'through related records or events'. Only the immutability half exists; an edit is dropped on the floor. Not live loss today (telegram.go:233 AllowedUpdates excludes edited_message), but this bead should not read as 'immutability done'.","status":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T09:25:26Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:02:26Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-gih","title":"fix(gateway): synchronize sessionTracker.active","description":"sessionTracker.active is a plain map with no mutex. go-telegram/bot dispatches each update in its own goroutine, so resolve() writes it while getActive() reads it concurrently. Backend-agnostic Go data race.","notes":"ADVERSARIAL PASS 2026-08-04 (fresh reviewer). The synchronization is CORRECT; the bead does not close on adjacent logic bugs.\n\nVERIFIED LOAD-BEARING: all four accesses to sessionTracker.active are guarded, no unguarded read or write anywhere in the package, no lock nesting or self-deadlock, no lock held across I/O or a channel send, every Unlock deferred. Stripping the RWMutex from all four sites produced 12 DATA RACE reports AND an assertion failure in TestSessionTrackerResolveIsStable, proving the double-check does real work rather than silencing the detector. Restored: -count=50 -race clean. PersonaRegistry.active is separately and correctly guarded.\n\nBLOCKED BY: archie-core-jex (/topic off poisons the cache with an empty session ID, sticky, reachable from webhook and email), archie-core-x35 (the double-check makes callers agree but the loser has already persisted its session, orphaning it), archie-core-7s3 (resolve picks an arbitrary session, not the most recent).","status":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T09:25:25Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:02:26Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-u4v","title":"Wire secret engines into provider discovery and execution","description":"Production creates only the env registry, never loads secret-engine plugins, and Provider lacks the documented api_key SecretRef. Implement startup plugin loading, backwards-compatible provider secret references, resolved provider discovery/runtime/container propagation, tests, release, and Carina deployment.","acceptance_criteria":"Provider api_key SecretRefs resolve through loaded engines at startup; existing api_key_env remains compatible; discovered providers, chat runtime, taskrun and containers receive resolved credentials without logging or serializing secret values; production composition tests and task check pass.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-30T17:52:08Z","created_by":"Sam Catlow","updated_at":"2026-07-30T22:48:38Z","started_at":"2026-07-30T17:52:13Z","closed_at":"2026-07-30T22:48:38Z","close_reason":"Live BWS discovery verified and ai-sdk openai-compatible fallback restored; 4+ provider catalog can now surface; full gate and final adversarial review pass","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-6he","title":"Telegram rejects model confirmation when clearing inline keyboard","description":"Selecting a model calls editMessageText with a typed nil reply_markup; Telegram rejects it as object expected, leaving the picker visible. Omit reply_markup when no keyboard is required and cover the request shape.","acceptance_criteria":"Selecting any model replaces the picker with metadata confirmation and the Telegram edit request omits reply_markup when clearing controls.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-30T17:46:25Z","created_by":"Sam Catlow","updated_at":"2026-07-30T17:47:08Z","started_at":"2026-07-30T17:46:29Z","closed_at":"2026-07-30T17:47:08Z","close_reason":"Telegram confirmation edits now omit nil reply_markup; regression test passes","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-v8x","title":"Unify Telegram provider and model selection around SDK catalog","description":"Replace the separate /provider and static configured-model surfaces with one /model provider-to-model wizard. Build the usable provider catalog from the local ai-sdk models.dev catalog plus environment credentials and explicit overrides, cache the filtered tool-capable catalog under the active config directory, and use the same resolved provider/model state across chat and execution paths. Remove the handwritten WellKnown table and remove external-framework references from the Archie tree.","acceptance_criteria":"/model first shows usable providers, then paginated tool-capable models, then atomically switches provider/model and reports model metadata and scope. /provider is absent from executable/menu/help surfaces. Catalog refresh is downloaded at daemon startup and cached beside configuration with safe cached fallback. Environment discovery and explicit overrides flow through chat, identities, subprocess and container/taskrun paths. Focused and composition tests cover discovery, pagination, callbacks and execution parity. A case-insensitive repository scan outside the explicit .references source tree finds no forbidden external-framework name.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-30T17:10:38Z","created_by":"Sam Catlow","updated_at":"2026-07-30T17:39:37Z","started_at":"2026-07-30T17:10:59Z","closed_at":"2026-07-30T17:39:37Z","close_reason":"Implemented SDK-backed provider discovery, unified Telegram model picker, safe catalog caching, and execution composition tests","dependency_count":0,"dependent_count":0,"comment_count":0} @@ -198,11 +198,13 @@ {"_type":"issue","id":"archie-core-s1r","title":"Test forge fakes missing LinkBranch method broke go vet/test for whole module","description":"forge.Forge gained LinkBranch(ctx, owner, repo, issueNumber, branch) error in the branch-linking feature (ff4c51e) but the hand-rolled test doubles (stubForge in cmd/archied/main_test.go, prCapturingForge in cmd/archie-agent/taskrun_test.go, testForge in internal/daemon/daemon_test.go, fakeForge in internal/forgerpc/forgerpc_test.go) never got the method added, so they stopped satisfying forge.Forge. This broke go vet ./... and go test ./... for the entire module, not just those 4 packages, since go vet type-checks all test files as part of module vet. Fixed by adding LinkBranch stubs to all four fakes.","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-24T03:04:53Z","created_by":"Sam Catlow","updated_at":"2026-07-24T03:04:58Z","closed_at":"2026-07-24T03:04:58Z","close_reason":"Added LinkBranch stub methods to stubForge, prCapturingForge, testForge, and fakeForge. go build/vet/test ./... now clean across the whole module.","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-633","title":"config.docker.toml missing required fields, no overlay merge implemented","description":"config.docker.toml was rewritten to be a docs-as-overlay file (comment says base+overlay merge) but internal/config.Load has no merge logic and docker-compose.yml mounts only config.docker.toml at /etc/archie/config.toml. It is missing bot_user, [forge], [dispatch], [models], [providers], [budgets] which Load requires -\u003e daemon fails to start in docker as currently configured. Implement real base+overlay config loading (or restore a full standalone docker config) so there is one source of truth.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-24T02:42:07Z","created_by":"Sam Catlow","updated_at":"2026-07-24T02:44:53Z","started_at":"2026-07-24T02:42:11Z","closed_at":"2026-07-24T02:44:53Z","close_reason":"Implemented config.LoadOverlay (base decode + overlay decode into same struct, then shared finalize/validate), wired -config-overlay flag in cmd/archied, fixed docker-compose.yml to mount both base config.toml and config.docker.toml overlay, minimized config.docker.toml to true diff-only overlay, added tests proving overlay-omitted required fields (bot_user, repos) still come from base.","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-u64","title":"Daemon: process multiple tasks concurrently (max_concurrency enforcement)","description":"Daemon currently processes one task at a time (docs/prds/archie-core-v2-architecture.md Phase 2). This is the core blocker between current state and any multi-agent scaling mode — needed before container max_concurrency or same-repo concurrency can matter. Wire the daemon's dispatch loop to run N tasks in parallel, respecting a configurable max_concurrency.","design":"internal/container/pool.go already enforces max_concurrency for container lifecycle — reuse that limit/pattern in the daemon's task dispatch rather than inventing a second concurrency control.","acceptance_criteria":"Daemon dispatch loop runs multiple tasks concurrently up to a configured max_concurrency limit; single-task-at-a-time behavior is gone.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-23T19:36:31Z","created_by":"Sam Catlow","updated_at":"2026-07-23T21:37:42Z","started_at":"2026-07-23T21:29:41Z","closed_at":"2026-07-23T21:37:42Z","close_reason":"Implemented concurrent SQLite and NATS task dispatch using containers.max_concurrency, with default same-repo serialization and race-tested dispatcher coverage.","dependency_count":0,"dependent_count":2,"comment_count":0} +{"_type":"issue","id":"archie-core-3cf.8","title":"Make activity and task context navigable","description":"The dashboard's live activity entries are not clickable, task detail does not provide a source-task/forge link, and the Tasks KPI strip sits directly against the table. Make activity events navigate to the relevant dashboard area, expose a clear source task action that opens the task's forge page when available, and restore visual separation between KPI cards and the task table. Add focused UI/runtime tests.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:25:09Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:27:58Z","started_at":"2026-08-03T16:25:10Z","closed_at":"2026-08-03T16:27:58Z","close_reason":"Implemented activity-to-task navigation, task source links using configured forge host, and Tasks KPI/table spacing. UI tests, build, and diff checks pass.","dependencies":[{"issue_id":"archie-core-3cf.8","depends_on_id":"archie-core-3cf","type":"parent-child","created_at":"2026-08-04T02:25:09Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-3cf.7","title":"Discover user-installed global skills alongside project skills","description":"The Web UI currently scans only the daemon work directory, so skills installed under the user's global ~/.agents/skills are invisible. Add global-skill discovery alongside project skills, preserve deterministic precedence for duplicate names, expose source/path in the API/UI, and keep workflow activation using the same merged catalogue. Add tests for configured and default roots.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:13:45Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:17:41Z","started_at":"2026-08-03T16:14:04Z","closed_at":"2026-08-03T16:17:41Z","close_reason":"Implemented layered project/shared/user-global skill discovery, deterministic precedence, global activation support, UI messaging, and tests.","dependencies":[{"issue_id":"archie-core-3cf.7","depends_on_id":"archie-core-3cf","type":"parent-child","created_at":"2026-08-04T02:13:45Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-7ve","title":"test(gateway): the conformance suite does not pin what it claims, and the backends already drift","description":"The commit message for 3eb00db claims the shared suite means NellDB and SQLite 'cannot drift'. Two confirmed divergences it does not catch:\n\n1. testReplaceMessagesIsFailureSafe (sessionstore_conformance_test.go:769) never induces a failure -- four happy-path cases asserting the post-condition of a SUCCESSFUL call. Swapping the write and delete loops in session_store.go:696-708 would leave it green. Only SQLite has a real abort test, and it pins rollback, the opposite failure mode. The backends genuinely differ here: SQLite is atomic (failure -\u003e clean rollback), NellDB is not (failure -\u003e duplicates). SQLite's semantics are better; the point is the suite does not know.\n\n2. NellDB's lastTS cache is never invalidated by deletes; SQLite recomputes MAX(ts). Save at 13:00, delete it, save with At=12:00 -\u003e NellDB persists 13:00:00.001Z, SQLite persists 12:00:00Z. Both pass the suite.\n\n3. GetByChannel ordering differs between backends and is unpinned (see the newest-first bead).\n\n4. applyCompress has zero test coverage: no test in the package calls it, none of its three error returns is exercised, and fakeSessionStore.ReplaceMessages is a slice assignment that cannot observe ordering or identity.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:53Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:53Z","dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-la1","title":"fix(gateway): doc comments contradict the implementation in three places","description":"Each of these actively misleads, and one already caused a real bug:\n\n1. gateway.go:23-27 says MessageID is 'Populated on read; ignored on write.' Both stores honour an incoming MessageID in preference to deriving one (session_store.go:588, session_store_sqlite.go:291). This is exactly the misreading behind /branch copying parent history into the child under the PARENT's canonical IDs -- CONFIRMED on both backends, and newMessageID's own doc claims the opposite ('the same upstream message copied into a branch gets its own identity'). Two branches from one parent produce three sessions holding the same MessageID.\n\n2. session_store.go:405-409 describes msgID and a disambiguating counter, both deleted in this commit, and now sits above messageIDNamespace describing the opposite of the current design.\n\n3. telegram.go:474-477 still says a redelivered update 'updates the stored turn' -- the exact behaviour the immutability fix removed.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:53Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:53Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-la1","title":"fix(gateway): doc comments contradict the implementation in three places","description":"Each of these actively misleads, and one already caused a real bug:\n\n1. gateway.go:23-27 says MessageID is 'Populated on read; ignored on write.' Both stores honour an incoming MessageID in preference to deriving one (session_store.go:588, session_store_sqlite.go:291). This is exactly the misreading behind /branch copying parent history into the child under the PARENT's canonical IDs -- CONFIRMED on both backends, and newMessageID's own doc claims the opposite ('the same upstream message copied into a branch gets its own identity'). Two branches from one parent produce three sessions holding the same MessageID.\n\n2. session_store.go:405-409 describes msgID and a disambiguating counter, both deleted in this commit, and now sits above messageIDNamespace describing the opposite of the current design.\n\n3. telegram.go:474-477 still says a redelivered update 'updates the stored turn' -- the exact behaviour the immutability fix removed.","status":"in_progress","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:53Z","created_by":"Sam Catlow","updated_at":"2026-08-04T12:23:28Z","started_at":"2026-08-04T12:23:28Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-le6","title":"fix(gateway): assorted confirmed defects around the compress and undo paths","description":"Small, individually confirmed, none blocking on their own:\n\n1. session_commands.go:563 -- the compression summary is persisted as a USER turn. CompressHistory emits it with Role 'system' (compression.go:118) but the write-back only maps 'assistant' -\u003e Identity, so system falls through to 'user'. The model replays '[Earlier conversation has been summarised...]' as if the human said it. (Retained bot turns are handled correctly.)\n\n2. session_commands.go:488 -- compressPreview reads RecentMessages(200) while reporting count from MessageCount. With 100 large + 250 tiny messages the preview says 'Compression not needed (350 messages, ~0 tokens)' while apply on the same session reports '350 -\u003e 24 (~100000 -\u003e ~3063 tokens)'. The two numbers in one sentence describe different histories, and the preview advises against a compression that is needed.\n\n3. session_commands.go:329 -- handleUndo discards the deleted count from DeleteRecentMessages, so /undo 10 failing after 6 removals reports failure while six messages are gone.\n\n4. session_store.go:626 -- nextTimestamp has no upper bound and lastTimestamp re-reads from the store, so one future-dated write (host clock 24h fast) pins the session's clock for its lifetime; every later At handed to callers is wrong by a day.\n\n5. session_store.go:268 -- Close() calls s.store.Close() on the SHARED nl.Store (in production the daemon's tasks/events log) and, unlike every other method, does not take s.mu. Nothing calls it today.\n\n6. session_store.go:429 -- newMessageID's UUIDv5 input sessionID+\"\\x00\"+sourceID is not injectively encoded: newMessageID('a\\x00b','c') == newMessageID('a','b\\x00c'). No reachable input today; hardening, not a live bug.\n\n7. turns.go:79-85 -- Turns.lanes grows without bound; a lane is inserted per session key and never deleted. No goroutine leak.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-03T16:01:53Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:01:53Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-3cf.5","title":"Add accessible interaction semantics across the dashboard","description":"Source review found navigation icons and a theme toggle that depend on visual glyphs or title text, and task rows are clickable table rows without keyboard semantics or an explicit expandable control. Audit the main pages for labels, focus visibility, keyboard operation, semantic headings and table behavior, status announcements, and sufficient non-color cues. Add automated DOM/accessibility-oriented regression tests for the critical controls.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-03T15:17:59Z","created_by":"Sam Catlow","updated_at":"2026-08-03T15:17:59Z","dependencies":[{"issue_id":"archie-core-3cf.5","depends_on_id":"archie-core-3cf","type":"parent-child","created_at":"2026-08-04T01:17:59Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} -{"_type":"issue","id":"archie-core-3cf.3","title":"Make dense dashboard views usable on narrow screens","description":"The responsive layout collapses the sidebar at 860px, but the dashboard relies on dense tables and multi-control filter rows without a documented table overflow/stacking treatment. Exercise dashboard, tasks, logs, workflows, settings, and channels at narrow viewport widths; fix clipping, horizontal scrolling ownership, control wrapping, and touch target sizing while preserving desktop density.","status":"in_progress","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T15:17:40Z","created_by":"Sam Catlow","updated_at":"2026-08-03T15:55:36Z","started_at":"2026-08-03T15:55:36Z","dependencies":[{"issue_id":"archie-core-3cf.3","depends_on_id":"archie-core-3cf","type":"parent-child","created_at":"2026-08-04T01:17:39Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-3cf.3","title":"Make dense dashboard views usable on narrow screens","description":"The responsive layout collapses the sidebar at 860px, but the dashboard relies on dense tables and multi-control filter rows without a documented table overflow/stacking treatment. Exercise dashboard, tasks, logs, workflows, settings, and channels at narrow viewport widths; fix clipping, horizontal scrolling ownership, control wrapping, and touch target sizing while preserving desktop density.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-03T15:17:40Z","created_by":"Sam Catlow","updated_at":"2026-08-03T16:08:59Z","started_at":"2026-08-03T15:55:36Z","closed_at":"2026-08-03T16:08:59Z","close_reason":"Completed responsive table containment across dashboard, tasks, settings, and workflows; added narrow-screen filter wrapping and grid shrink safeguards. Validated with ui npm test and npm run build; live daemon verification requires restarting the embedded UI bundle.","dependencies":[{"issue_id":"archie-core-3cf.3","depends_on_id":"archie-core-3cf","type":"parent-child","created_at":"2026-08-04T01:17:39Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-3cf.4","title":"Improve operator orientation and safe refresh behavior","description":"The current shell has a minimal brand/sidebar, repeated bare actions, and limited indication of data freshness or which filters are active. Define a small consistent page-toolbar pattern with last-updated/loading/error states, clearer action labels, and preserved filter/navigation state across refresh and route changes. Keep the visual system lightweight and consistent with the existing dark/light themes.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-03T15:17:40Z","created_by":"Sam Catlow","updated_at":"2026-08-03T15:17:40Z","dependencies":[{"issue_id":"archie-core-3cf.4","depends_on_id":"archie-core-3cf","type":"parent-child","created_at":"2026-08-04T01:17:40Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-3cf","title":"[EPIC] Web UI polish and enhancements","description":"Polish and extend the Archie dashboard against the supplied reference design. Keep the UI a trustworthy operator control room: show real state, explain auth/connectivity failures, remain usable on narrow screens, make interactions accessible, and follow the reference composition and visual system. Existing feature issues for dashboard chat, configuration editing, and logs remain separate unless a child below explicitly coordinates with them.","acceptance_criteria":"Authenticated dashboard renders meaningful KPI values; unauthorised access has a clear recovery path; core navigation, tables, controls, and task interactions are keyboard/screen-reader usable; dense views remain usable on narrow viewports; the dashboard follows the supplied reference composition and visual treatment; each child has focused UI tests or runtime verification.","status":"open","priority":2,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-03T15:17:25Z","created_by":"Sam Catlow","updated_at":"2026-08-03T15:20:01Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-wb2","title":"feat(container): pass registry auth on image pull","description":"internal/container/pool.go:305 calls p.cli.ImagePull(ctx, ref, client.ImagePullOptions{}) with RegistryAuth never set, so the daemon talks to the Docker Engine API with no credentials. Against a private registry (git.catlow.cloud) every pull answers 401 regardless of pull_policy.\n\ndocker login does NOT help: it writes ~/.docker/config.json, which only the CLI reads. The operator has to pull by hand with the CLI so the daemon's pull_policy=missing check finds the image already present. That workaround is currently documented in CLAUDE.md as a hard constraint rather than fixed.\n\nFix: populate ImagePullOptions.RegistryAuth with a base64-encoded registry.AuthConfig, sourced from ~/.docker/config.json or an explicit [containers] credential. Removes a documented footgun and makes pull_policy actually mean what it says against private registries.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-03T15:12:16Z","created_by":"Sam Catlow","updated_at":"2026-08-03T15:12:16Z","dependency_count":0,"dependent_count":0,"comment_count":0}