chore: cleanup of noisey beads files
This commit is contained in:
1 parent
fa0973dbd5
commit
d06e3ea73d
2 files changed
+3
-441
No files matched your search
+3
-1
@@ -61,7 +61,9 @@ dolt-pprof/
|
||||
# Corrupt backup directories (created by bd doctor --fix recovery)
|
||||
*.corrupt.backup/
|
||||
|
||||
# Backup data (auto-exported JSONL, local-only)
|
||||
# JSONL exports and backups are local interchange artifacts. Dolt is the
|
||||
# authoritative store and GitHub is the external issue surface.
|
||||
issues.jsonl
|
||||
backup/
|
||||
|
||||
# Per-project environment file (Dolt connection config, GH#2520)
|
||||
|
||||
@@ -1,440 +0,0 @@
|
||||
{"_type":"issue","id":"archie-core-dzx","title":"Remove duplicate archie-agent safe.directory setup","description":"## Problem\\ncmd/archie-agent/main.go configures git safe.directory inline and then calls markWorktreeSafe, so startup writes the same global git configuration twice.\\n\\n## Scope\\nKeep markWorktreeSafe as the single tested production path and remove the older inline exec.Command block/import. Add regression coverage proving startup wiring has exactly one authoritative safe-directory call.\\n\\n## Acceptance\\n- archie-agent startup invokes markWorktreeSafe exactly once\\n- no second inline safe.directory command remains in main.go\\n- cmd/archie-agent tests and repository quality gate pass","acceptance_criteria":"Single tested safe.directory setup path remains; duplicate inline command is removed; tests and task check pass","notes":"Red proof: TestMainConfiguresWorktreeSafetyOnce failed with 2 setup paths before implementation. Green proof: go test/vet/build ./cmd/archie-agent/... passed; golangci-lint --new-from-rev=HEAD reported 0 issues. Fresh adversarial review found no blockers. Full task check was not run because the working tree contains unrelated in-progress changes and task check rewrites files; scoped package gate used per repository protocol.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:09Z","created_by":"Sam Catlow","updated_at":"2026-08-13T16:13:48Z","started_at":"2026-08-13T16:10:24Z","closed_at":"2026-08-13T16:13:48Z","close_reason":"Removed duplicate inline safe.directory setup; markWorktreeSafe is now the single tested production path","external_ref":"https://github.com/samcharles93/archie-core/issues/470","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tje.1","title":"Extract archie-agent task subscription concern","description":"## Problem\\nmain.go owns boot task discovery and taskrun subscription selection in addition to process composition.\\n\\n## Scope\\nMove bootTaskID and subscribeTaskRuns into a concern-named cmd/archie-agent source file, preserving dedicated-container versus shared-queue behavior and existing tests.\\n\\n## Acceptance\\n- boot brief parsing and taskrun subscription selection are outside main.go\\n- behavior and logging remain unchanged\\n- focused tests and task check pass","acceptance_criteria":"Subscription concern is outside main.go with unchanged behavior; tests and task check pass","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","updated_at":"2026-08-13T16:11:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/471","dependencies":[{"issue_id":"archie-core-tje.1","depends_on_id":"archie-core-tje","type":"parent-child","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tje.2","title":"Extract archie-agent stage fetch loop","description":"## Problem\\nmain.go contains the stageBus contract and fetch-handle-ack loop, obscuring startup composition.\\n\\n## Scope\\nMove stageBus and runMainLoop into a stage-loop concern file without changing ack, nak, retry, cancellation, or shutdown semantics.\\n\\n## Acceptance\\n- stage loop is outside main.go\\n- all error and cancellation paths remain covered\\n- focused tests and task check pass","acceptance_criteria":"Stage loop is outside main.go with ack/nak/cancellation behavior preserved; tests and task check pass","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","updated_at":"2026-08-13T16:11:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/472","dependencies":[{"issue_id":"archie-core-tje.2","depends_on_id":"archie-core-tje","type":"parent-child","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tje.3","title":"Extract archie-agent MCP provider lifecycle","description":"## Problem\\nmain.go contains MCP transport selection, provider startup/discovery, registry population, and cleanup alongside process wiring.\\n\\n## Scope\\nMove mcpProviderSet, startMCPProviders, and cleanup into an MCP-provider concern file. Preserve optional-provider failure isolation and transport behavior.\\n\\n## Acceptance\\n- MCP provider lifecycle is outside main.go\\n- optional failures and cleanup semantics remain unchanged and tested\\n- task check passes","acceptance_criteria":"MCP lifecycle is outside main.go with failure isolation and cleanup preserved; tests and task check pass","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","updated_at":"2026-08-13T16:11:44Z","external_ref":"https://github.com/samcharles93/archie-core/issues/473","dependencies":[{"issue_id":"archie-core-tje.3","depends_on_id":"archie-core-tje","type":"parent-child","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tje.4","title":"Extract archie-agent stage request handling","description":"## Problem\\nmain.go decodes, executes, and responds to single-stage requests in the same file as process startup.\\n\\n## Scope\\nMove handle and its request/response orchestration into a stage-handler concern file after the MCP lifecycle seam is available. Preserve reply-address validation, provider setup, response encoding, and logging.\\n\\n## Acceptance\\n- stage request handling is outside main.go\\n- decode, reply, provider, execution, encode, and publish error paths remain covered\\n- task check passes","acceptance_criteria":"Stage request handling is outside main.go with all boundary error semantics preserved; tests and task check pass","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","updated_at":"2026-08-13T16:11:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/474","dependencies":[{"issue_id":"archie-core-tje.4","depends_on_id":"archie-core-tje","type":"parent-child","created_at":"2026-08-13T16:10:45Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-tje.4","depends_on_id":"archie-core-tje.3","type":"blocks","created_at":"2026-08-13T16:10:54Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tje","title":"Decompose cmd/archie-agent main.go by concern","description":"## Problem\\ncmd/archie-agent/main.go is 430 lines and mixes process startup, task subscription selection, stage-loop execution, MCP provider lifecycle, and request handling. This makes unrelated changes collide and obscures the composition boundary.\\n\\n## Scope\\nTrack small behavior-preserving extractions into concern-named files within cmd/archie-agent. Keep main.go focused on flags, startup ordering, construction, shutdown, and invoking the worker loop. No new packages or architecture changes.\\n\\n## Acceptance\\n- child tasks move one concern at a time with tests unchanged or improved\\n- main.go retains process-level input and composition only\\n- each child passes task check and fresh adversarial review","acceptance_criteria":"All child extractions complete; main.go contains process input and composition only; task check passes","status":"open","priority":2,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:24Z","created_by":"Sam Catlow","updated_at":"2026-08-13T16:11:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/475","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501304-434-efae0b99","title":"agent containers: git dubious-ownership causes all gates to fail","description":"## Problem\n\nAgent containers bind-mount the worktree from the host at `/data/worktree`, where the owning UID differs from the container user's UID. Git refuses to operate in such directories (\"fatal: detected dubious ownership in repository\"), and the Go toolchain calls git for VCS status during `go build`/`go test`/`go vet`.\n\nThis means every gate — baseline gate, build gate, TDD repro gate — fails immediately, before any real work begins. Agents burn tokens trying to fix the environment instead of working on the assigned issue.\n\n## Evidence\n\n- Task for issue #441 burned 557K tokens across 29 iterations and parked with `gate_failed_final` — the agent never reached the actual multi-forge fix\n- `go build` within the container fails with `error obtaining VCS status: exit status 128`\n- The agent's uncommitted `build_test.go` recognized the real cause: \"A pre-existing git dubious-ownership issue causes the build to fail\"\n\n## Fix\n\nAdd `git config --global --add safe.directory /data/worktree` at archie-agent startup. The worktree mount path is always `/data/worktree` (storage.WorktreeMountDir). The command is best-effort: if git isn't installed, the agent logs a warning and continues — it remains usable for repos without gate commands.\n\n## Files\n\n- `cmd/archie-agent/main.go`: run git safe.directory config after logger init","status":"open","priority":2,"issue_type":"bug","created_at":"2026-08-12T04:38:10Z","updated_at":"2026-08-12T04:38:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/468","source_system":"github:https://github.com/samcharles93/archie-core/issues/468:468","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501270-433-dc1a0bc2","title":"Telegram gateway: show tool calls inline during chat turns","description":"The Telegram chat agent returns only the final answer. The user cannot see which tools are being called, their parameters, or their results. This makes debugging agent behavior (hallucinations, wrong tool choices, footguns like `systemctl stop` vs `restart`) impossible from the chat side.\n\n## Desired behavior\n\nAfter each tool call completes, the gateway sends a compact inline message showing the tool name and a one-line summary of the result, before the next tool call or final answer. Similar to how Hermes surfaces tool calls in Telegram.\n\nExample format:\n```\n🔧 memory_edit — added entry\n🔧 terminal — systemctl --user stop archied (exit 0)\n🔧 terminal — systemctl --user start archied (exit 0)\n```\n\nThen the final answer.\n\n## Scope\n\n`internal/channels/telegram/` only. Behind a config flag `[chat.telegram] show_tool_calls = true` so it can be toggled.\n\n## Technical approach\n\nCurrently the call chain is:\n\n```\nsubmitTurn → router.RouteStream(turnCtx, gm, draft.onDelta)\n → r.LLMStream(ctx, msg, onDelta)\n → TurnRunner.Run(ctx, msg, onDelta)\n → prepared.Generate(ctx, req, onDelta)\n```\n\nOnly `onDelta` (text streaming) is threaded through. Tool calls happen inside `Generate` but there's no callback back to the gateway.\n\n### What needs to change\n\n1. **Add a tool-call observer callback** — either extend `LLMStreamResponder` signature or add a separate `OnToolCall` field to `gateway.Router` struct, plumbing it through `TurnRunner` → `TurnModel`/`PreparedTurnModel.Generate` so model providers can report tool invocations\n\n2. **Model provider integration** — the chat turn model (`cmd/archied/chat_turn_model.go`) and any provider-specific `Generate` implementations need to call the observer when a tool is executed, passing tool name + result summary\n\n3. **Telegram gateway wiring** — in `submitTurn` (`internal/channels/telegram/telegram.go`), if `show_tool_calls` config is true, wire the observer to send a compact inline message via `sendMessage` before the final reply\n\n4. **Config plumbing** — add `ShowToolCalls bool` to the Telegram gateway config struct and read it from `[chat.telegram] show_tool_calls` in `telegram_setup.go`\n\n### Key files\n\n| File | Role |\n|------|------|\n| `internal/gateway/gateway.go` | `RouteStream`, `Router` struct (add observer field) |\n| `internal/gateway/turn.go` | `TurnRunner.Run`, `PreparedTurnModel.Generate` signature |\n| `cmd/archied/chat_turn_model.go` | Model provider `Generate` — where tool calls execute |\n| `internal/channels/telegram/telegram.go` | `submitTurn` — wire observer + send messages |\n| `cmd/archied/telegram_setup.go` | Config reading + gateway construction |\n","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-12T04:20:52Z","updated_at":"2026-08-12T04:42:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/467","source_system":"github:https://github.com/samcharles93/archie-core/issues/467:467","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501247-432-31968e33","title":"webui/chat: surface per-task logs via API and a chat tool","description":"Part of #450. Depends on #453 (daemon subscriber).\n\nAdd `/api/tasks/{id}/logs`, built on `logging.Reader` the same way\n`/api/logs` is today (`internal/webui/api_logs.go`).\n\nAdd a chat tool so Archie can answer \"why did task N park?\" directly from\nTelegram or the webui chat, without an operator needing to open the\ndashboard. This is the surface that matters most for the deployment model\nin `CLAUDE.md`, where an operator may not be watching a dashboard at all.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-09T06:06:29Z","updated_at":"2026-08-09T09:16:44Z","closed_at":"2026-08-09T09:16:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/455","source_system":"github:https://github.com/samcharles93/archie-core/issues/455:455","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501221-431-6358f362","title":"daemon: subscribe agent system logs and route to task sink + dashboard feed","description":"Part of #450. Depends on #451 (task log sink) and #452 (agent publisher).\n\nSubscribe `agentexec.SubjectAgentWildcard` (\"archie.agent.\u003e\") for the\n`.system` suffix once at daemon startup. This is composition — wiring the\ndomain's log sink to the NATS subscription — so it belongs in `internal/app/`,\nnot in `internal/domain/workflow` or `internal/nats` directly.\n\nDemux by task ID, append each entry to that task's sink, and also publish it\ninto the existing `logging.Feed` so live task/container output appears on\nthe dashboard exactly like daemon output does today.\n\nAlso: prune a task's log directory when `nell.ArchiveTask`\n(`internal/nell/adapter.go`) archives it, so task logs share the task's own\nlifecycle instead of growing unbounded.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-09T06:06:27Z","updated_at":"2026-08-09T08:49:35Z","closed_at":"2026-08-09T08:49:36Z","external_ref":"https://github.com/samcharles93/archie-core/issues/454","source_system":"github:https://github.com/samcharles93/archie-core/issues/454:454","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501190-430-8c471d9f","title":"agentexec: publish agent logs to SubjectForSystem","description":"Part of #450. Depends on #451 (task log sink).\n\n`agentexec.SubjectForSystem` is documented as the return channel for \"log\ndumps, health, and PII warnings\" but has no publisher anywhere in the\ncodebase.\n\nIn `cmd/archie-agent/main.go`, replace the stderr-only `slog.Handler` with\none that tees to stderr (kept for operator debugging when a shell is\nattached to a live container) and publishes each record to\n`agentexec.SubjectForSystem(taskID)`. The agent already has its NATS client\nand task ID (`bootTaskID`, read from `\u003cworktree\u003e/.git/task.json`).\n\nPublishing must be fire-and-forget with a bounded local buffer — log\nshipping must never block or fail the run it's reporting on. A full buffer\ndrops the oldest entry, not the newest, and should log (locally, stderr\nonly) that it dropped something, once, not per-entry.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-09T06:06:26Z","updated_at":"2026-08-09T08:17:00Z","closed_at":"2026-08-09T08:17:01Z","external_ref":"https://github.com/samcharles93/archie-core/issues/453","source_system":"github:https://github.com/samcharles93/archie-core/issues/453:453","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501160-429-88420623","title":"logging: add a task-scoped log sink","description":"Part of #450.\n\nExtend `internal/logging` (it already owns its on-disk format end to end —\nsee `docs/architecture/organisation.md`) with a task-scoped writer producing\nthe same `logging.Entry` JSONL shape at\n`\u003cstate_dir\u003e/logs/tasks/\u003ctask_id\u003e/attempt-\u003cn\u003e.jsonl`, reusing the existing\nrotation (`MaxSizeMB`/`Keep`) semantics per task directory.\n\n`logging.Tail`, `logging.Query`, and `logging.Components` should operate on\na task's sink unchanged. No new package — this stays inside `internal/logging`\nper the \"no ceremonial layers\" rule.\n\nConfirm with the maintainer whether `internal/domain/workflow` importing\n`internal/logging` directly is acceptable for a domain package, or whether\nthe domain should declare its own sink interface with `internal/app` wiring\nthe concrete `internal/logging` implementation in. Default to the interface\nif in doubt — see `docs/architecture/organisation.md` dependency direction.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-09T06:06:24Z","updated_at":"2026-08-09T08:17:25Z","closed_at":"2026-08-09T08:17:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/452","source_system":"github:https://github.com/samcharles93/archie-core/issues/452:452","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501129-428-accd2926","title":"gate output: stop discarding it, put the real error in the park reason","description":"Part of #450.\n\n`StageBaselineGate` in `internal/domain/workflow/implement.go` runs each\n`[[repos.gate]]` command via `cmd.CombinedOutput()`, clips the output to\n200 characters into a `tc.Log.Warn` call, and discards the rest. The\neventual park error (`baseline red -- %s fails and builder could not\nauto-fix (status: %s)`) is built from `res.Status` alone.\n\nWrite the full `CombinedOutput()` to the task's log sink (see #451 for the\nsink itself; this can land first using a plain file write if the sink isn't\nready yet, then be migrated) and put a bounded tail (~2KB, not 200 bytes) of\nit into the returned error so it reaches the park reason.\n\nRed-then-green: write a test against `StageBaselineGate` that asserts the\nreturned error contains gate output beyond 200 characters when the gate\ncommand fails with a long message, confirm it fails today, then fix.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-09T06:06:22Z","updated_at":"2026-08-09T08:17:27Z","closed_at":"2026-08-09T08:17:28Z","external_ref":"https://github.com/samcharles93/archie-core/issues/451","source_system":"github:https://github.com/samcharles93/archie-core/issues/451:451","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501090-427-c465db57","title":"epic: task observability — capture and surface agent/gate output","description":"Design doc: `docs/architecture/observability.md` (this branch/PR).\n\n## Problem\n\nA task's real work happens in an ephemeral `archie-agent` container over\nNATS. Four things currently destroy the evidence of what it did:\n\n1. `cmd/archie-agent/main.go` logs to stderr only, and\n `internal/container/pool.go` creates containers with `AutoRemove: true` —\n the log dies with the container.\n2. `StageBaselineGate` (`internal/domain/workflow/implement.go`) captures\n full gate output via `CombinedOutput()`, clips it to 200 chars into a\n `Warn` log, and discards the rest — the park reason carries only a status\n string.\n3. `agentexec.Result` has no step-level transcript (tool calls, durations,\n errors).\n4. `agentexec.SubjectForSystem` is documented as the return channel for\n exactly this (\"log dumps, health... the daemon reads these for\n observability\") but has zero publishers and zero consumers anywhere in\n the codebase.\n\nConsequence: a task parked today with\n`stage baseline: baseline red -- go build ./... fails and builder could not\nauto-fix (status: parked)` and there was no way, from the dashboard or from\nchat, to see the actual `go build` error — the container that had it was\nalready gone.\n\nThis matters beyond convenience: archied is meant to run unattended for\nweeks (`CLAUDE.md` deployment model) and potentially for users other than\nits original operator. A system only debuggable by someone watching\n`docker ps` live doesn't meet that bar.\n\n## Decision\n\nNATS is the only transport this targets. `[agent] mode = \"nats\"` is the\nsupported deployment and the agent must already reach NATS to report any\nstage result — a container that can't reach NATS is a distinct, narrower\nfailure (connectivity) than this epic addresses (a connected container's own\noutput being unrecoverable). No new functionality goes into the in-process\nrunner, which is being migrated away.\n\n## Subtasks\n\nSee linked sub-issues.","status":"closed","priority":2,"issue_type":"epic","created_at":"2026-08-09T06:05:57Z","updated_at":"2026-08-09T09:29:41Z","closed_at":"2026-08-09T09:29:42Z","external_ref":"https://github.com/samcharles93/archie-core/issues/450","source_system":"github:https://github.com/samcharles93/archie-core/issues/450:450","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501063-426-9fce1209","title":"webui(chat): Send button passes the click event as sendMessage's retry arg, throws and no-ops","description":"`ui/src/chat/chat.js` line 283:\n\n```js\nsend.onclick = sendMessage;\n```\n\n`sendMessage(retry = null)` is assigned directly as a DOM `onclick` handler. The browser invokes `onclick` handlers with the triggering `MouseEvent` as the first argument, so every click calls `sendMessage(event)` -- the click event becomes `retry`. It's truthy and has no `.turn` property, so the very first line of the function:\n\n```js\nconst text = retry?.turn.text || composer.value.trim();\n```\n\nthrows `TypeError: can't access property \"text\", t.turn is undefined` (`t` being the minified param name) immediately, before any state changes (the disable/status-update code runs after this line). The click is silently swallowed -- no message sent, no visible error, Send just does nothing.\n\nReported live on carina 2026-08-09: clicking Send in the dashboard chat had no effect; browser console showed the above uncaught promise rejection at `index.js:77`.\n\n### Fix\n\n`send.onclick = () =\u003e sendMessage();` (matching the pattern already used for `newChat.onclick` a few lines up), so no arguments reach `sendMessage` from the click event.\n","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T16:31:50Z","updated_at":"2026-08-08T16:34:57Z","closed_at":"2026-08-08T16:34:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/447","source_system":"github:https://github.com/samcharles93/archie-core/issues/447:447","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501039-425-88078ff7","title":"channels: MarkRunning is never called, dashboard shows working channels stuck on 'Starting'","description":"`internal/channels.Manager` has `MarkRunning(id)` (`internal/channels/manager.go:68`), but nothing in `cmd/archied/main.go` or `cmd/archied/telegram_setup.go` ever calls it. Every channel start path only calls `MarkStarting` then, on failure, `MarkFailed` -- there's no success signal.\n\n`cmd/archied/telegram_setup.go` around line 100-111:\n\n```go\nif s.ChannelManager != nil {\n s.ChannelManager.MarkStarting(\"telegram\")\n}\ngo func() {\n if err := tg.Start(ctx, router); err != nil \u0026\u0026 ctx.Err() == nil {\n if s.ChannelManager != nil {\n s.ChannelManager.MarkFailed(\"telegram\", err.Error())\n }\n s.Log.Error(\"telegram gateway stopped\", \"err\", err)\n }\n}()\ns.Log.Info(\"telegram gateway started\")\n```\n\n`tg.Start()` blocks for as long as the gateway is healthy (long-poll loop), so there's no point where success can be observed by return value the way failure is. Same pattern for email/webhook in `cmd/archied/main.go` (`channelManager.MarkStarting(\"email\"/\"webhook\")` / `MarkFailed` only).\n\n### Impact\n\nThe Channels dashboard page shows a configured, actually-working channel stuck on \"Starting.\" forever -- confirmed live on carina: Telegram successfully polling, command menu registered, messages flowing, but `/api/channels` still reports `\"state\": \"starting\"` indefinitely.\n\n### Expected\n\nEach channel's start path needs a `MarkRunning(id)` call once it's actually confirmed up -- e.g. after the first successful long-poll/webhook-registration/listener-bind, not just at goroutine launch. Applies to telegram, email, and webhook.\n","status":"open","priority":2,"issue_type":"bug","created_at":"2026-08-08T16:27:19Z","updated_at":"2026-08-08T16:27:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/446","source_system":"github:https://github.com/samcharles93/archie-core/issues/446:446","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637501009-424-5b8332dd","title":"daemon: label dispatch trigger with empty label matches every open issue","description":"`internal/daemon/daemon.go` `pollIssuesWithConfig()`, the `\"label\"` (and `\"either\"`) trigger branch calls:\n\n```go\nissues, err := fg.IssuesWithLabel(ctx, repo.Owner, repo.Name, cfg.Label)\n```\n\n`cfg.Label` is a top-level `Config.Label` field (`internal/config/config.go:364`) -- a different field from `[dispatch.labels]`, which maps task *states* (queued/working/waiting/pr/parked) to their forge labels for a different purpose. It's easy to configure `[dispatch.labels]` and reasonably assume the label-trigger match target is covered, while leaving the actual `label` field that controls trigger matching unset.\n\n`GitHubClient.IssuesWithLabel` (`internal/forge/github.go:103`) passes that straight through as `Labels: []string{label}` to the GitHub issues-list API. With `label == \"\"`, GitHub does not filter by label at all -- it returns every open issue in the repo.\n\n### Impact (live incident, 2026-08-09)\n\nDeployed `dispatch.trigger = \"label\"` on carina without setting `label`. The daemon queued 124 unrelated open issues in one poll cycle (everything from epics to unrelated feature requests), and one reached a running agent container before it was caught and stopped manually.\n\n### Expected\n\n`pollIssuesWithConfig`'s `\"label\"` branch should refuse to poll (log an error and return, same as any other misconfiguration) when `cfg.Label` is empty, rather than silently falling through to an unfiltered API call. Ideally this is also caught at config-validation time (`internal/infrastructure/configuration/validate.go`) when `dispatch.trigger` is `\"label\"` or `\"either\"` and `label` is blank.\n","status":"open","priority":2,"issue_type":"bug","assignee":"samcharles93","created_at":"2026-08-08T16:26:41Z","updated_at":"2026-08-12T09:24:21Z","external_ref":"https://github.com/samcharles93/archie-core/issues/445","source_system":"github:https://github.com/samcharles93/archie-core/issues/445:445","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500980-423-12a63a68","title":"webui(chat): dynamic header content breaks the fixed no-scroll chat layout","description":"The Chat page's layout (`ui/src/chat/chat.css`) is built for a fixed, no-scroll chat window: `.chat-workspace` uses `grid-template-rows: auto minmax(0, 1fr) auto` with `overflow: hidden`, and only `.chat-transcript` (the message list) is meant to scroll. `.chat-page` only sets `min-height: calc(100vh - 5rem)`, not a fixed height.\n\nAny dynamic content injected above `.chat-layout` -- the status/error banner (see #443), extra status pills, a long \"Reload Telegram\"/\"Check updates\" row wrapping on a narrower viewport -- has no height budget accounted for, so it just pushes the whole grid down and grows total page height past the viewport. That breaks the intended design: the page itself scrolls instead of just the transcript.\n\nScreenshot: Chat page with the 501 error banner (see #443) visibly adding an extra row that isn't accounted for in the fixed layout.\n\n### Expected\n\nThe top status/banner region should have a bounded height (or the page should reserve space for it) so injecting a banner or wrapping the status pills never causes page-level scroll -- only `.chat-transcript` should ever scroll.\n","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T16:17:47Z","updated_at":"2026-08-08T16:45:42Z","closed_at":"2026-08-08T16:45:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/444","source_system":"github:https://github.com/samcharles93/archie-core/issues/444:444","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500953-422-01075562","title":"webui(chat): raw 501 error banner when update-check is unconfigured","description":"The Chat page shows a raw \"501 Not Implemented\" banner across the top when the release-update-check feature isn't configured. `POST /api/chat/update` correctly returns 501 when `chat.telegram.update_check_command` is unset in config (`cmd/archied/telegram_setup.go` `makeUpdateService` returns nil in that case, which is a legitimate, expected \"not configured\" state -- same category as an unconfigured channel).\n\nThe bug is in the frontend's handling of that response. `ui/src/chat/chat.js` `refreshUpdate()` is called unconditionally on page load (line ~365) with no guard, and its catch block does:\n\n```js\n} catch (err) {\n updatePanel.replaceChildren(el(\"span\", err.message || \"Updates unavailable\"));\n}\n```\n\nThis renders the raw fetch error text (including the literal HTTP status) directly into a visible page banner, rather than treating \"updates not configured\" as a quiet empty state -- the same pattern already used for an unconfigured channel on the Channels page (\"Not configured\", not an error).\n\n### Expected\n\nA 501/\"not configured\" response from `/api/chat/update` should render nothing (or a subtle \"update checks not configured\" note), not a raw HTTP error banner.\n\nScreenshot: Chat page, banner reading \"501 Not Implemented\" directly under the top status bar.\n","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T16:17:37Z","updated_at":"2026-08-08T16:44:14Z","closed_at":"2026-08-08T16:44:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/443","source_system":"github:https://github.com/samcharles93/archie-core/issues/443:443","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500926-421-7c63bcd3","title":"webui: Gate pulse card content should top-align with Finish setting up card","description":"On the dashboard's HEALTH section, the \"Gate pulse\" card doesn't visually align with the \"Finish setting up\" card next to it. \"Finish setting up\" is top-aligned (title, progress bar, checklist all stacked from the top), while \"Gate pulse\"'s empty-state content (\"No completed runs yet\" / \"Once Archie finishes a task...\") is vertically centered in the card, leaving large uneven whitespace above and below relative to its sibling.\n\nScreenshot: dashboard HEALTH row, two cards side by side -- left card (\"Finish setting up\") content flows from the top; right card (\"Gate pulse\") content floats centered.\n\n### Expected\n\nThe \"Gate pulse\" card's content (including its empty state) should top-align the same way \"Finish setting up\" does, so the two HEALTH cards read as one consistent row rather than two different layout patterns.\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T16:15:17Z","updated_at":"2026-08-08T16:15:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/442","source_system":"github:https://github.com/samcharles93/archie-core/issues/442:442","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500900-420-335d8bbb","title":"archied: [[repos]] entries can't span more than one forge","description":"`[forge]` is a single top-level block resolved once (`resolveForge` in `cmd/archied/main.go:332`) into one `forge.Forge` client, shared by every entry in `[[repos]]`. The `Repo` struct (`internal/config/config.go:56`) has no per-repo `type`/`host`/`token` override -- `owner`/`name` are the only identity fields, so every repo is assumed to live on whatever single forge the daemon is configured for.\n\nThis blocks a `[[repos]]` list spanning more than one forge (e.g. one repo on GitHub, another on a Gitea instance) under a single archied identity. Discovered live on carina 2026-08-09: switching `[forge]` to `type = \"github\"` for `archie-core` made the daemon start querying the `tau` repo entry (still Gitea-hosted) against `api.github.com`, producing repeated 404s (`get repo sam/tau: GET https://api.github.com/repos/sam/tau: 404 Not Found`) until the `tau` entry was removed as a workaround.\n\n### Expected\n\nEach `[[repos]]` entry should be able to declare (or inherit a default) its own forge type/host/token, and the daemon should resolve a forge client per repo rather than one globally, so repos on different forges can be dispatched from the same archied instance.\n\n### Workaround in place\n\n`tau`'s `[[repos]]` entry was removed from carina's `config.toml` so `archie-core` (now GitHub) doesn't try to poll it against the wrong forge. `tau` gets no automated dispatch from this instance until this is fixed or it gets a separate identity.\n","status":"open","priority":2,"issue_type":"bug","assignee":"samcharles93","created_at":"2026-08-08T16:09:53Z","updated_at":"2026-08-12T03:40:29Z","external_ref":"https://github.com/samcharles93/archie-core/issues/441","source_system":"github:https://github.com/samcharles93/archie-core/issues/441:441","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500871-419-5bee4d20","title":"fix(webui): open redirect in dashboard token-exchange handler","description":"CodeQL alert (`go/unvalidated-url-redirection`, medium severity): the dashboard token-exchange handler in `internal/webui/auth.go` redirected to a Location built directly from the incoming request's path and query, with no validation.\n\nA request whose path starts with `//` (e.g. `GET //evil.example/x?t=\u003ctoken\u003e`) causes `clean.RequestURI()` to reproduce `//evil.example/x` verbatim. Browsers treat a Location header starting with `//` as protocol-relative, so this redirects the client off-host after a legitimate token exchange -- a classic open-redirect via the Go `net/url` double-slash gotcha.\n\n### Fix\n\nAdded `sameOriginPath()` in `internal/webui/auth.go`, which collapses any leading `//` down to a single `/` before the value ever reaches `http.Redirect`. Covered by a red-then-green test in `internal/webui/auth_test.go` (`TestRequireToken_RedirectRejectsProtocolRelativePath`) that reproduces the exploit path and asserts the Location header is never protocol-relative.\n\nRef: [code-scanning alert #4](https://github.com/samcharles93/archie-core/security/code-scanning/4) (dismissed alerts #1-3 on that same scan were false positives -- allocations already bounded by `min()`, see their dismissal comments).\n","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T15:13:11Z","updated_at":"2026-08-08T15:48:10Z","closed_at":"2026-08-08T15:48:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/440","source_system":"github:https://github.com/samcharles93/archie-core/issues/440:440","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500839-418-cad065a6","title":"SOUL loader with per-turn reload and default fallback","description":"Load the SOUL file from the config dir into the identity slot of the rendered prompt, re-reading it per turn so an edit takes effect on the next message with no restart.\n\n### Acceptance Criteria\n\nSOUL content is rendered into the identity slot ahead of the invariant sections. An absent, empty or unreadable SOUL falls back to the shipped default identity rather than rendering nothing. Editing the file changes the next turn's prompt with no restart. A read error is logged once and degrades to the default; it never fails the turn. Size is bounded so an oversized SOUL cannot crowd out the rules.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:59:24Z","updated_at":"2026-08-08T14:59:24Z","external_ref":"https://github.com/samcharles93/archie-core/issues/439","source_system":"github:https://github.com/samcharles93/archie-core/issues/439:439","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500805-417-67db48ed","title":"Regression tests: Container pool — volume lifecycle, error paths, concurrent pool access","description":"internal/container/pool_test.go has 3 tests (grace period, JSON output, volume file). Missing: volume cleanup on error, concurrent pool access, container timeout during task, invalid task payload handling, Docker daemon unavailable error path.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:59:19Z","updated_at":"2026-08-08T14:59:22Z","closed_at":"2026-08-08T14:59:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/438","source_system":"github:https://github.com/samcharles93/archie-core/issues/438:438","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500776-416-600a66e5","title":"Surprisal sampling: embedding-backed strategies","description":"Implement the embedding-backed surprisal strategy behind the Sampler seam that wave 1 of the curator epic ships (cheap strategies: recency, random, all, staleness proxy). Surprisal scores memories by how surprising they are so the sampled reasoner's agentic budget is spent on the memories most likely to matter. DEFERRED by design: gated behind the embeddings capability (sibling issue 'Embeddings capability (prerequisite for surprisal sampling)') — pick up only after that lands.\n\n### Acceptance Criteria\n\nA Sampler implementation behind the same interface as the cheap strategies; selection is deterministic given fixed inputs. Algorithm: sample up to a candidate cap; build a k-NN graph over embedding vectors; row-normalize the adjacency with self-loops; power-iterate to the stationary distribution; surprisal = -log(stationary probability of the nearest point); select the highest-surprisal items. Degradation: content with no embedding is skipped; an embedding failure aborts sampling and falls back to free exploration - a sampling failure must never fail or crash a curator pass. Cost: the graph build is quadratic in the candidate cap; the cap is a named constant with a documented bound. Tests use synthetic vectors via httptest, never a live embedding service.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:59:16Z","updated_at":"2026-08-08T14:59:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/437","source_system":"github:https://github.com/samcharles93/archie-core/issues/437:437","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500752-415-434e5bb9","title":"Embeddings capability (prerequisite for surprisal sampling)","description":"Surprisal-based sampling (curator epic DESIGN) requires computing vector embeddings of memory content so memories can be scored by how surprising they are. Archie has no embedding capability today; the epic gates any surprisal-style sampling behind adding one. This issue tracks that prerequisite so it can be picked up independently of the curator epic's main work. The consumer is the embedding-backed surprisal sampler (sibling issue 'Surprisal sampling: embedding-backed strategies'). Embedding consumers must degrade gracefully: content with no embedding is skipped, and an embedding failure aborts sampling in favour of free exploration rather than crashing the pass.\n\n### Acceptance Criteria\n\nAn embedding client exists behind a narrow typed interface usable by in-process daemon components (curators first, other consumers later). Provider/model is config-driven (providers table + a role in [models]). A missing credential degrades per the credential-missing-degrades-not-fatal rule: capability reports unavailable, daemon still starts. Network calls carry timeouts; failures surface as reported errors, never a crash or a failed chat turn. Tests use httptest and never require a live embedding service.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:59:13Z","updated_at":"2026-08-08T14:59:13Z","external_ref":"https://github.com/samcharles93/archie-core/issues/436","source_system":"github:https://github.com/samcharles93/archie-core/issues/436:436","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500725-414-9d66a52b","title":"[EPIC] Curator engine: persistent memory-reasoning agent loops","description":"Introduce curators as their own engine family: long-running agent loops that reason over memory and perform small maintenance tasks, rather than one hardcoded background job. A curator is defined by a check-in interval, a tool set, and (once the memory engine family lands) an attached memory engine. It runs persistently while there is input and backs off to a cooldown when idle. Ship two reference curators -- a skill curator and a persistent-session-memory curator -- so the interface is proven against two consumers rather than designed around one.\n\n### Design\n\nThe design splits a cheap hot-path extractor from an expensive sampled reasoner, so agentic cost is never paid per message. Sampling chooses which memories deserve attention via surprisal-based scoring, implemented over embeddings through interchangeable strategies including a k-NN graph random walk. Archie has no embedding capability today, so any surprisal-style sampling is gated behind adding one.\n\n### Acceptance Criteria\n\nCurator is a conforming engine family per ARCHITECTURE.md 'Plugin engine rule (strict)': typed contract, owning registry/manager, start/health/stop, narrow typed host access. Curators are registered and configured declaratively, not hardcoded. The runtime supports persistent operation under load and cooldown when idle, with intervals configurable per curator. Both reference curators run against the shipped defaults. Curator activity is observable: what ran, when, what it changed, and why. A curator failure is isolated and never takes down the daemon or a chat turn.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:59:10Z","updated_at":"2026-08-08T15:34:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/435","source_system":"github:https://github.com/samcharles93/archie-core/issues/435:435","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500699-413-301bc587","title":"Regression tests: Yaegi extract packages smoke tests (wfextract, gateextract, pluginextract)","description":"Four extract packages have zero tests: internal/workflow/wfextract, internal/gate/gateextract, internal/plugin/pluginextract, and internal/workflow/wfextract. These are Yaegi symbol extractors that generate Go source exposing package symbols to Yaegi scripts. They fail loudly at build time if broken, but minimal smoke tests would catch regressions in the export format (correct symbol names, expected types, no missing exports).","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:59:05Z","updated_at":"2026-08-08T14:59:07Z","closed_at":"2026-08-08T14:59:08Z","external_ref":"https://github.com/samcharles93/archie-core/issues/434","source_system":"github:https://github.com/samcharles93/archie-core/issues/434:434","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500667-412-04faa3e7","title":"generalize Provider.APIKeyEnv / NATS.TokenEnv / Telegram.TokenEnv to SecretRef","description":"Follow-up to archie-core-xec, which only migrated Forge.TokenEnv (self-contained call site). Provider.APIKeyEnv is forwarded THREE different ways that all assume the secret is reachable by name in the daemon's own env, not resolved centrally:\n1. agentexec.NewRuntime -\u003e passes the env-var NAME into ai-sdk/runtime's AuthConfig.APIKeyEnv, which lazily os.Getenv's it later (external module, cannot change its contract).\n2. agentexec.WorkerEnvironment / subprocess.go WorkerEnvironment() -\u003e allowlist-forwards the NAME into a subprocess's environment for archie-agent to read itself.\n3. daemon.containerEnv() -\u003e already eagerly resolves via os.Getenv and injects NAME=value into a container env (this one generalizes cleanly).\n\nMigrating Provider.APIKeyEnv to SecretRef requires switching cases 1 and 2 from name-forwarding to eager-resolve-via-secret.Registry-then-inject-value (ai-sdk/runtime.AuthConfig.APIKey literal field already supports this per its ResolveAPIKey fallback chain -- no ai-sdk/runtime changes needed, just stop relying on its lazy os.Getenv path for non-env engines). Also migrate NATSConfig.TokenEnv and TelegramConfig.TokenEnv (each has a single simple os.Getenv call site, lower risk than Provider).\n\n### Design\n\nsecret.Registry must be threaded into agentexec.NewRuntime, WorkerEnvironment, and daemon.containerEnv (or a shared secret-resolution helper) so eager-resolve-then-inject replaces name-forwarding for engines other than the built-in env engine.\n\n### Acceptance Criteria\n\nProvider.APIKeyEnv, NATSConfig.TokenEnv, TelegramConfig.TokenEnv replaced with SecretRef; all three consumption paths (in-process runtime, subprocess worker env, container env) resolve via secret.Registry; task check passes; adversarial review finds zero surviving findings; explicit test proving a non-env engine (e.g. a fake test engine) correctly delivers a provider API key to agentexec.NewRuntime via the AuthConfig.APIKey literal field, not APIKeyEnv.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:59:02Z","updated_at":"2026-08-08T15:35:20Z","external_ref":"https://github.com/samcharles93/archie-core/issues/433","source_system":"github:https://github.com/samcharles93/archie-core/issues/433:433","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500634-411-e265a95c","title":"secret engine plugin: vault/openbao","description":"Ship a yaegi-loaded secrets engine plugin talking to Vault/OpenBao's HTTP KV API (net/http), following the internal/secret Engine interface from archie-core-xec.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:59Z","updated_at":"2026-08-08T14:58:59Z","external_ref":"https://github.com/samcharles93/archie-core/issues/432","source_system":"github:https://github.com/samcharles93/archie-core/issues/432:432","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500602-410-7a461d4d","title":"secret engine plugin: bws (Bitwarden Secrets Manager)","description":"Ship a yaegi-loaded secrets engine plugin wrapping the bws CLI (os/exec), following the internal/secret Engine interface from archie-core-xec.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:56Z","updated_at":"2026-08-08T14:58:56Z","external_ref":"https://github.com/samcharles93/archie-core/issues/431","source_system":"github:https://github.com/samcharles93/archie-core/issues/431:431","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500571-409-cdffe32a","title":"secret engine plugin: sops","description":"Ship a yaegi-loaded secrets engine plugin wrapping the sops CLI (os/exec), following the internal/secret Engine interface from archie-core-xec. Lives under the shipped engines directory, loaded the same way as custom engines to prove the extension point.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:53Z","updated_at":"2026-08-08T14:58:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/430","source_system":"github:https://github.com/samcharles93/archie-core/issues/430:430","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500522-408-28b934f6","title":"internal/secret: secrets-engine registry with yaegi extension interface","description":"Add a secret-management package that avoids hard-coding secrets backends. Defines an Engine interface (Name, Version, Resolve(ref string) (map[string]string, error)) that custom secrets engines implement as yaegi-interpreted .go plugins, loaded the same way internal/plugin.LoadDir already loads daemon plugins (main.Engine export, resolved via yaegiutil.Resolve). Includes a built-in compiled-in 'env' engine, a Registry type, and a config.SecretRef type ({Engine, Ref string}) that directly REPLACES the existing TokenEnv/APIKeyEnv string fields across config.go (Forge, Provider, NATSConfig, TelegramConfig, etc) -- no backwards-compatibility shim, this is a clean cutover since the end user is the repo owner, not an external customer base. Ships no third-party engines yet (sops/bws/vault-openbao are follow-up beads) but proves the extension point with the env engine and a directory-loaded custom engine in tests.\n\n### Design\n\nMirrors internal/plugin's Plugin interface (Name/Version) + one Resolve method. Built-in env engine is native Go (trivial, no yaegi needed) registered by default. Custom/shipped engines are yaegi .go files loaded from a configurable directory via yaegiutil.Resolve[Engine](i, src, \"main.Engine\").\n\n### Acceptance Criteria\n\ninternal/secret package exists with Engine interface, Registry, LoadDir (yaegi-based, mirrors internal/plugin conventions) -- DONE. config.Forge.Token (SecretRef) replaces Forge.TokenEnv end-to-end including per-identity validation -- DONE. Provider/NATS/Telegram migration deferred to archie-core-xec.4 (scope narrowed mid-implementation after discovering the name-forwarding architecture fork). task check passes -- DONE. Adversarial review found zero surviving findings after fix pass -- DONE.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:58:48Z","updated_at":"2026-08-08T15:34:43Z","closed_at":"2026-08-08T15:34:44Z","external_ref":"https://github.com/samcharles93/archie-core/issues/429","source_system":"github:https://github.com/samcharles93/archie-core/issues/429:429","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500488-407-73fd8953","title":"Discovery session: interview to produce agent personas PRD","description":"Sam has no implementation approach in mind yet for agent personas. Run a structured discovery interview (an agent grilling Sam with scoped questions, one round at a time) to extract: what a persona means concretely for this project, how it should relate to (or reuse) the existing skill/workflow system, whether personas are a prerequisite for or dependent on the multi-agent collaboration work, and what's explicitly out of scope. Write the findings up as docs/prds/agent-personas.md.\n\n### Acceptance Criteria\n\ndocs/prds/agent-personas.md exists, reflects Sam's actual answers (not assumptions), and is detailed enough that a future implementation session could break it into scoped, dependency-ordered beads issues the way the 5zh epic was.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:43Z","updated_at":"2026-08-08T14:58:45Z","closed_at":"2026-08-08T14:58:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/428","source_system":"github:https://github.com/samcharles93/archie-core/issues/428:428","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500458-406-c76b40dd","title":"Agent personas: specialized agents for specific task types","description":"Build on multi-agent collaboration with the concept of agent personas — agents with distinct roles/specializations (e.g. a reviewer persona, a security-focused persona, a specific-language expert persona) that perform specific kinds of tasks rather than one generic agent handling everything. Related to but separable from the multi-agent collaboration epic — personas could exist for single-agent-at-a-time dispatch too (picking the right persona for a task), or become one of the participants in multi-agent collaboration.\n\n### Acceptance Criteria\n\nA PRD exists (docs/prds/) covering: what a persona is (system prompt variant? skill-bundle variant? separate model/config?), how a task gets routed to the right persona, how personas relate to the existing skill/workflow system (internal/skill, internal/workflow), and whether personas need to exist before or after multi-agent collaboration lands. No code changes required to close this epic — the PRD is the deliverable.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:58:40Z","updated_at":"2026-08-08T14:58:40Z","external_ref":"https://github.com/samcharles93/archie-core/issues/427","source_system":"github:https://github.com/samcharles93/archie-core/issues/427:427","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500430-405-40bc3a73","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:58:34Z","updated_at":"2026-08-08T14:58:37Z","closed_at":"2026-08-08T14:58:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/426","source_system":"github:https://github.com/samcharles93/archie-core/issues/426:426","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500404-404-1dbc182c","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","created_at":"2026-08-08T14:58:31Z","updated_at":"2026-08-08T14:58:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/425","source_system":"github:https://github.com/samcharles93/archie-core/issues/425:425","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500376-403-f8a17424","title":"infrastructure/configuration: external input boundary","description":"Read docs/architecture/configuration.md. Create internal/infrastructure/configuration as the external config input boundary. It owns TOML/YAML decoding, env and secret references, base/overlay precedence, compatibility aliases, input validation, and provenance. It must NOT own domain behaviour. Preserve current LoadOverlay behaviour exactly and keep every existing TOML field name working. Translate the decoded input into the current internal/config.Config shape at the composition boundary as an explicitly-marked temporary adapter, so runtime behaviour is unchanged. Do not migrate consumers in this bead.\n\n### Acceptance Criteria\n\ninternal/infrastructure/configuration exists and is the loader used by cmd/archied. Old config files still load with identical effective values. task check clean. No consumer outside cmd/archied changed. The temporary adapter carries a comment naming its deletion condition.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:26Z","updated_at":"2026-08-08T14:58:29Z","closed_at":"2026-08-08T14:58:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/424","source_system":"github:https://github.com/samcharles93/archie-core/issues/424:424","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500339-402-d1d74f5e","title":"SetupPrompter interface and UI-agnostic setup flow","description":"Port tau's split: setup logic lives in a package that takes a SetupPrompter interface; the command layer supplies the terminal implementation. This is what makes setup testable without a TTY.\n\n### Acceptance Criteria\n\nSetup logic has no direct terminal dependency and is driven end to end in tests by a fake prompter. The terminal implementation provides a numbered Select and a non-echoing ReadSecret via golang.org/x/term, both cancellable on Ctrl+C via context. No TUI framework is introduced.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:58:21Z","updated_at":"2026-08-08T14:58:24Z","closed_at":"2026-08-08T14:58:25Z","external_ref":"https://github.com/samcharles93/archie-core/issues/423","source_system":"github:https://github.com/samcharles93/archie-core/issues/423:423","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500306-401-92ea58c8","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.\n\n### Acceptance Criteria\n\n/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":2,"issue_type":"feature","created_at":"2026-08-08T14:58:16Z","updated_at":"2026-08-08T14:58:18Z","closed_at":"2026-08-08T14:58:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/422","source_system":"github:https://github.com/samcharles93/archie-core/issues/422:422","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500274-400-88879bb2","title":"gateway: restore /whoami /profile /sessions /resume /agents handlers","description":"These five command handlers were lost during parallel merges of the Telegram\nworkers. The Router fields they need (Identity, Models, Sessions, Agents)\nalready exist; the handlers and their Route cases do not.\n\n18 tests in internal/gateway/gateway_test.go already specify the exact\nbehaviour. They are currently failing. Run them and make them pass:\n\n go test ./internal/gateway/...\n\nFailing: TestRouteWhoami, TestRouteWhoamiNoIdentity, TestRouteWhoamiWithModel,\nTestRouteProfile, TestRouteProfileNoIdentity, TestRouteSessionsEmpty,\nTestRouteSessionsNotConfigured, TestRouteSessionsError, TestRouteResumeNoArg,\nTestRouteResumeNotConfigured, TestRouteResumeNoMatch, TestRouteResumeAmbiguous,\nTestRouteResumeExactMatch, TestRouteAgentsEmpty, TestRouteAgentsNotConfigured,\nTestRouteAgentsWithTasks, TestRouteAgentsError, TestLocalCommandsIncludesNewCommands\n\nScope:\n- ONLY internal/gateway/. Do not touch any other package.\n- Read the tests first; they define the exact reply text fragments expected\n (\"not configured\", \"No sessions\", \"Usage\", etc). Do not invent wording.\n- Follow the shape of the existing handlers in gateway.go and\n session_commands.go: handleX methods on *Router returning (string, error).\n- A nil dependency means \"not configured\" and returns a reply, not an error.\n A dependency that returns an error must propagate it (see TestRouteSessionsError).\n- Add the new commands to the Route switch and to LocalCommands.\n\nConstraints:\n- Do NOT add //nolint or otherwise suppress lint findings. Fix issues properly.\n- Do NOT write architecture docs, ledgers, plans or new beads. Just the code.\n- Do NOT modify the tests to make them pass. The tests are correct.\n\nDone when: go build ./... , go vet ./... , gofmt -l . clean, and\ngo test ./internal/gateway/... passes with zero failures.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:11Z","updated_at":"2026-08-08T14:58:13Z","closed_at":"2026-08-08T14:58:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/421","source_system":"github:https://github.com/samcharles93/archie-core/issues/421:421","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500254-399-aeb0e932","title":"install.sh: linger detection claims success it did not verify","description":"install.sh greps 'loginctl show-user $USER' for 'Linger=no'. When show-user fails or prints nothing -- no logind session, a container, USER unset -- the grep fails and control falls to the else branch, which prints '[OK] User linger is already enabled.' Nothing was verified and linger is never enabled, so systemd --user dies at logout. Worst for someone installing on a remote box over SSH: Archie works while they are connected and stops when they disconnect. Discussed 2026-07-30, fix agreed but not applied.\n\n### Acceptance Criteria\n\nDetection tests for the positive (Linger=yes) and attempts enable-linger in every other case, including when show-user fails. Uses $(id -un) rather than $USER, which is unset in some container and cron contexts and would abort under set -u. enable-linger is idempotent so a redundant call is harmless. No branch claims linger is enabled without having observed it.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:58:05Z","updated_at":"2026-08-08T14:58:08Z","closed_at":"2026-08-08T14:58:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/420","source_system":"github:https://github.com/samcharles93/archie-core/issues/420:420","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500222-398-375b8172","title":"Durable scheduled agent tasks backed by Archie's task queue","description":"Add first-class one-shot, interval, and cron scheduling for Telegram agents. The scheduler decides when work is due but never executes an LLM or shell inline: it atomically enqueues a normal durable Archie task under the originating identity, and existing workers execute it with the usual tool, sandbox, lifecycle, and observability policies. Expose typed agent tools and Telegram management surfaces for create/list/status/pause/resume/delete/run-now, with delivery back to the originating chat.\n\n### Acceptance Criteria\n\nSchedules support one-shot timestamps, fixed intervals, and cron expressions with explicit timezone. Definitions and execution history survive daemon restarts. Due firing uses an atomic lease/idempotency key so concurrent daemons and crash recovery do not duplicate a scheduled occurrence. Scheduler callbacks only enqueue normal tasks; they never run agents or shell commands inline. Each schedule records owner identity, origin chat/thread, prompt/task payload, enabled capability policy, overlap policy, next run, last result, and delivery state. Authorized users can create/list/status/pause/resume/delete/run-now from chat and equivalent typed agent tools. Missed-run, long-running overlap, clock/DST, cancellation, queue failure, execution failure, and delivery failure semantics are explicit and tested with a fake clock. Cron-spawned tasks cannot recursively create schedules unless explicitly authorized. Library selection is documented and does not replace Archie's durable queue semantics.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:58:02Z","updated_at":"2026-08-08T14:58:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/419","source_system":"github:https://github.com/samcharles93/archie-core/issues/419:419","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500199-397-df317107","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.\n\n### Design\n\ninternal/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.\n\n### Acceptance Criteria\n\nDaemon dispatch loop runs multiple tasks concurrently up to a configured max_concurrency limit; single-task-at-a-time behavior is gone.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:57:57Z","updated_at":"2026-08-08T14:58:00Z","closed_at":"2026-08-08T14:58:01Z","external_ref":"https://github.com/samcharles93/archie-core/issues/418","source_system":"github:https://github.com/samcharles93/archie-core/issues/418:418","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500175-396-fef56da4","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.\n\n### Acceptance Criteria\n\nProvider 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":2,"issue_type":"bug","created_at":"2026-08-08T14:57:52Z","updated_at":"2026-08-08T14:57:55Z","closed_at":"2026-08-08T14:57:56Z","external_ref":"https://github.com/samcharles93/archie-core/issues/417","source_system":"github:https://github.com/samcharles93/archie-core/issues/417:417","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500149-395-b8fe5929","title":"[BUG] find fallback reports a cancelled walk as 'no matches found'","description":"runFindGoFallback's walk callback swallows every per-entry error (returns nil to skip inaccessible entries), so the only error that can escape filepath.WalkDir is ctx.Err() from the cancellation select. The guard 'if err != nil \u0026\u0026 !errors.Is(err, ctx.Err())' therefore never fires: on timeout or /stop the function falls through and returns whatever it had collected, or 'no matches found' when it had collected nothing. This is the same failure the grep exit-code bug had -- the model is told a search found nothing when the search did not finish. Behaviour predates 6d4e0be; the errors.Is autofix in that commit is behaviour-neutral here (errors.Is(err, nil) is false for non-nil err, matching the old err != ctx.Err() when the context is live).\n\n### Acceptance Criteria\n\nA find whose context is cancelled mid-walk returns an error result naming the cancellation, not 'no matches found' and not a silently partial list. Regression test in the style of TestGrepReportsSearchFailureRatherThanNoMatches.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:57:47Z","updated_at":"2026-08-08T15:35:09Z","closed_at":"2026-08-08T15:35:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/416","source_system":"github:https://github.com/samcharles93/archie-core/issues/416:416","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500130-394-584ce317","title":"Reconcile SOUL with PersonaRegistry and the six built-in personas","description":"Decide what happens to DefaultPersonas() (archie, helpful, concise, technical, creative, teacher) and the /personality command once SOUL owns identity. Options: SOUL replaces the default archie persona and the rest remain selectable style modifiers; or personas become seed templates a user copies into their SOUL; or personas are retired. Currently GetActive composes the baseline archie prompt with the selected persona, so the interaction with SOUL must be explicit rather than emergent.\n\n### Acceptance Criteria\n\nPrecedence between SOUL and a selected persona is defined and documented. /personality either keeps working with stated semantics or is removed deliberately. No path lets a persona selection blank out the user's SOUL without them asking.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:57:44Z","updated_at":"2026-08-08T14:57:44Z","external_ref":"https://github.com/samcharles93/archie-core/issues/415","source_system":"github:https://github.com/samcharles93/archie-core/issues/415:415","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500110-393-7a04f121","title":"Chat: real system prompt template for Archie (identity, tools, env)","description":"The chat agent's system prompt is the four-sentence static string in gateway.DefaultPersonas(). It carries no tool inventory, no environment/date block, and no instruction precedence, so the model invents its own capabilities -- it told Sam it 'only has the memory editing tool' and then offered to walk him through installing software it cannot install.\n\nTake the shape from tau: /work/apps/tau/internal/agent/templates/agent.md.tpl renders an agent body plus \u003ctools\u003e, \u003cguidelines\u003e, \u003cproject_context\u003e and \u003cenv\u003e blocks, and /work/apps/tau/internal/agent/spec/templates/tau.agent.md supplies identity, instruction precedence, core rules, communication rules and confirmation boundaries.\n\nKeep the existing PersonaRegistry as the style layer; the template is the substrate it renders into.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:57:39Z","updated_at":"2026-08-08T14:57:41Z","closed_at":"2026-08-08T14:57:42Z","external_ref":"https://github.com/samcharles93/archie-core/issues/414","source_system":"github:https://github.com/samcharles93/archie-core/issues/414:414","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500090-392-e6b1cbaf","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":2,"issue_type":"bug","created_at":"2026-08-08T14:57:33Z","updated_at":"2026-08-08T14:57:36Z","closed_at":"2026-08-08T14:57:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/413","source_system":"github:https://github.com/samcharles93/archie-core/issues/413:413","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500066-391-e36986c2","title":"Decide and implement the TOML write strategy","description":"Settle how setup persists config before any prompting code is written; everything else depends on it. BurntSushi/toml loses comments on re-marshal, and config.example.toml carries substantial inline documentation users are meant to read and edit by hand. Options: (a) generate a fresh commented config from a template on first run and only line-patch specific keys on re-run; (b) full re-marshal and accept losing comments; (c) adopt a comment-preserving TOML editor.\n\n### Design\n\nDecision: text-based line patching, not decode/re-marshal, not a comment-preserving TOML AST library (none exist for Go that are safe to depend on).\n\nNew package internal/infrastructure/configuration/tomlwrite:\n- Apply(src []byte, edits []Edit) ([]byte, error): for each {Table, Key, Value} edit, finds an active \"key = value\" line in that table and replaces just the value (preserving indent + trailing inline comment); else finds a commented \"# key = value\" line in that table, uncomments the table header and the line; else appends the key at the end of the table's content (or appends a brand new [table] section at EOF if the table doesn't exist at all, active or commented). Lines not named by an edit are copied through byte-for-byte.\n- Generate(template, edits) is Apply against configtemplate.Example (config.example.toml embedded at the module root via configtemplate.go, since go:embed can't reach outside its own directory tree -- this keeps config.example.toml the single source of truth instead of a second copy, which is exactly the drift bug this epic exists to fix).\n- Value callers pre-render TOML literals; String() and Ref(engine,key) helpers cover the two shapes setup needs (quoted strings, secret.SecretRef inline tables). Deliberately does not import internal/secret -- it edits text, not Go values.\n\nTrade-off: only understands single-line scalar/inline-table values. Does not handle multi-line arrays or [[array-of-tables]] (e.g. [[repos]]) -- those aren't setup's targets and must not be routed through this patcher.\n\nTests (internal/infrastructure/configuration/tomlwrite/tomlwrite_test.go) cover: active-key replace preserving trailing comment, active inline-table replace, commented-table uncomment-one-key-leave-siblings-commented, append into existing active table, append brand-new table, byte-identical-elsewhere on a single edit, byte-identical-elsewhere across two sequential runs (the rs9 acceptance criterion), and a full run against the real config.example.toml verified to decode via BurntSushi/toml and round-trip bot_user/forge.token correctly.\n\n`go build ./...` and `task check` pass clean; no other files touched.\n\n### Acceptance Criteria\n\nThe chosen strategy is documented with its trade-off. A first run produces a config a human can read and hand-edit afterwards. A second run changing one value leaves every other line, including comments, byte-identical -- asserted by a test. No strategy is adopted that silently discards user edits.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:57:28Z","updated_at":"2026-08-08T14:57:30Z","closed_at":"2026-08-08T14:57:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/412","source_system":"github:https://github.com/samcharles93/archie-core/issues/412:412","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500046-390-bb8eb36b","title":"Telegram: report installed gateway and runtime versions","description":"Add an authorized /version command as the installed-version prerequisite for component-aware /update. Telegram remains presentation-only; the composition root supplies installed component versions.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:57:22Z","updated_at":"2026-08-08T14:57:25Z","closed_at":"2026-08-08T14:57:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/411","source_system":"github:https://github.com/samcharles93/archie-core/issues/411:411","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637500022-389-a765fd7a","title":"Telegram: component-aware /update with approve or defer","description":"Add an /update control flow that checks for available releases, presents separate archied gateway and archie-agent runtime versions/changelog sections, and lets an authorized user approve or defer. Keep discovery and execution behind typed interfaces so Docker/Watchtower, package-manager, and other installations can supply their own updater without the Telegram gateway assuming a deployment mechanism.\n\n### Acceptance Criteria\n\n/update reports whether gateway and runtime updates are available, with separate version and changelog sections and explicit no-change wording. Telegram provides Approve and Defer actions restricted to authorized users. Deferral is persisted and suppresses repeated prompts according to an explicit policy. Approval calls a typed installation updater and reports progress/failure without claiming success early. No Watchtower-only or Docker-only behavior exists in the gateway package. Commands, menu, help, callback authorization, concurrency, persistence, and failure paths are tested.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:57:17Z","updated_at":"2026-08-08T14:57:20Z","closed_at":"2026-08-08T14:57:21Z","external_ref":"https://github.com/samcharles93/archie-core/issues/410","source_system":"github:https://github.com/samcharles93/archie-core/issues/410:410","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499992-388-15ec94cd","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:57:12Z","updated_at":"2026-08-08T14:57:14Z","closed_at":"2026-08-08T14:57:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/409","source_system":"github:https://github.com/samcharles93/archie-core/issues/409:409","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499965-387-1f257fda","title":"Audit archie-core repo for bugs/improvements, file as Gitea issues","description":"Fan out exploration subagents across internal/ subsystems to find bugs, tech debt, and enhancement opportunities. Each confirmed finding gets filed as a Gitea issue on git.catlow.cloud/sam/archie-core.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:57:06Z","updated_at":"2026-08-08T14:57:09Z","closed_at":"2026-08-08T14:57:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/408","source_system":"github:https://github.com/samcharles93/archie-core/issues/408:408","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499933-386-83646cce","title":"Curator contract, registry, and internal/curator package","description":"Stand up internal/curator as a package in its own right: the typed curator contract, the owning registry that controls registration and discovery, and the definition of a curator's declared shape (check-in interval, tool set, attached memory engine).\n\n### Acceptance Criteria\n\ninternal/curator owns a typed contract exposing real curator operations plus start/health/stop. A registry controls registration, discovery, and shutdown ordering, and defines failure isolation. Curators receive a narrow typed registrar and only the host services their declared capability requires -- never *daemon.Daemon or an untyped hook map. internal/plugin/architecture_test.go recognises curator as a conforming engine family.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:57:04Z","updated_at":"2026-08-08T14:57:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/407","source_system":"github:https://github.com/samcharles93/archie-core/issues/407:407","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499903-385-ed6b4aa1","title":"Telegram: remove task approval from the public command surface","description":"Existing /approve [identity=name] \u003ctask-id\u003e was inherited as chat-task lifecycle control, but Sam explicitly states task approvals are not a product requirement. Reserve /approve exclusively for dangerous-command approval. Remove task approval from Telegram command menu/help/router/public UX; retain or remove internal waiting_human task mechanics only after verifying workflow callers. Do not repurpose the command until the dangerous-command approval model (archie-core-alm.6) exists.\n\n### Acceptance Criteria\n\nTelegram no longer advertises or accepts task approval via /approve; no documentation/help describes task approvals; task lifecycle code is not broken for existing non-Telegram workflow paths; /approve remains unclaimed or is implemented only for the approved dangerous-command design.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:56:58Z","updated_at":"2026-08-08T14:57:01Z","closed_at":"2026-08-08T14:57:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/406","source_system":"github:https://github.com/samcharles93/archie-core/issues/406:406","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499872-384-7952eb47","title":"chat: mid-conversation context loss, undiagnosed","description":"Reported from a real Telegram transcript (29 Jul, ~09:47 AEST / 23:47 UTC 28\nJul). Turn 3 of a coherent conversation was answered with a fresh greeting as\nthough no history existed; turn 4 was coherent again.\n\nRuled out by evidence:\n- Not two processes racing the bot token. docker compose ps on carina shows a\n single archied container.\n- Not a restart. That container had 43h uptime spanning the whole exchange.\n- Not history compression. DefaultCompressionConfig protects the first 3 and\n last 20 messages and triggers at 50% of a 128k window; there were three\n messages.\n- Not a canned greeting. No such string exists in the codebase, so the reply\n was model-generated from little or no history.\n- Not the session-key namespace split fixed in 96ab167: the deployed image\n predates the session lifecycle commands entirely.\n\nBlocked on evidence, now unblocked: chat turns were completely unlogged (76\nlog lines covered two days, none a conversation). 96ab167 adds a \"chat turn\"\nlog line carrying session id, channel, thread and history depth.\n\nNext step when it recurs: check the chat turn log for that message. A session\nid differing from neighbouring turns points at key resolution (e.g. ThreadID\nappearing on one message); history_messages of 0 or 1 with a stable session id\npoints at the store read path.\n\nDo not close this by guessing. It needs one reproduction with the new log line.","status":"open","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:56:55Z","updated_at":"2026-08-08T15:34:18Z","external_ref":"https://github.com/samcharles93/archie-core/issues/405","source_system":"github:https://github.com/samcharles93/archie-core/issues/405:405","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499843-383-4eb46948","title":"Flaky: TestRunTaskExecutesBootstrapWorkflowEndToEnd races on NATS responders","description":"cmd/archie-agent. Intermittently fails with ParkReason 'stage prepare: archie.worktree.prepare: nats: no responders available for request'; passes on re-run (-count=3 clean). The test does not wait for the worktreerpc subscription to be established before dispatching. A flaky test in task check is poison: it trains everyone to re-run instead of read, which is how a real regression gets waved through.","status":"open","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:56:52Z","updated_at":"2026-08-08T14:56:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/404","source_system":"github:https://github.com/samcharles93/archie-core/issues/404:404","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499814-382-b27575d6","title":"Phase 5: the 56 lint findings Phase 4 left behind","description":"Discovered as a side effect of the 6d4e0be audit (archie-core-ifi), not as its\ngoal: running golangci-lint over the two packages I had touched showed findings\nin files nobody had flagged, so I ran it repo-wide.\n\nAll four children of archie-core-qa4 are closed and the epic reports \"4/4\ncomplete (100%) -- eligible for close\", but `golangci-lint run ./...` still\nreports 56 issues. The epic must not be closed on that prompt; its own\ndescription says the gate is RED until it closes, so closing it early declares\na green gate that does not exist.\n\nBreakdown: noctx 11, gocognit 11, gocritic 6, errcheck 6, nilerr 4, recvcheck 3,\nnestif 3, godox 3, sloglint 2, predeclared 2, funlen 2, gofumpt 1, cyclop 1,\nstaticcheck 0 (the one hit, configtemplate.go:6, is fixed).\n\nThe gocognit remainder is concentrated in exactly the functions Phase 4 named as\ndeferred -- cmd/archied/main.go run (106, the description predicted \"108-\u003e30\nremaining\" and it did not land), internal/workflow AgentStage.Stage (68),\nFeasibility and TDD (funlen), cmd/archie-agent startMCPProviders (45) -- plus\nthe whole of internal/tools/builtin: grepFallback 58, runFindGoFallback 57,\nmakeReadExecutor 56, makeGrepExecutor 41, makeShellExecutor 40, makeWriteExecutor\n38, suggestPaths 36. tomlwrite.Apply (82) is new, uncommitted-until-7fab597 code.\n\nREAD archie-core-qa4's notes before starting. Both known behaviour regressions\nfrom this epic came out of structural extraction, and every remaining gocognit\nsite is a structural extraction waiting to happen. The nilerr findings in\ngrep.go are not noise either -- see archie-core-ts9, where the same swallow in\nfind.go is a live false-negative bug. Fixing nilerr by \"returning the error\"\nwithout deciding what the caller does with it will change tool behaviour.\n\n### Acceptance Criteria\n\ngolangci-lint run ./... reports 0 issues, or every remaining finding has an explicit nolint with a reason. Each structural extraction lands with a behavioural test for the function it splits, per the discipline recorded in archie-core-qa4's notes.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:49Z","updated_at":"2026-08-08T14:56:49Z","external_ref":"https://github.com/samcharles93/archie-core/issues/403","source_system":"github:https://github.com/samcharles93/archie-core/issues/403:403","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499784-381-21fbaa99","title":"Phase 4: structural refactor (~28 issues)","description":"funlen, gocognit, cyclop, nestif, maintidx, interfacebloat. This IS the internal/config restructure already discussed (finalize at cognitive complexity 106, feature_config loadDirInto at 74) plus daemon process/checkWaiting. MUST BE LAST: refactoring moves line numbers and invalidates every other phase in flight. Fold into the config file-per-responsibility split rather than doing the same work twice.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:44Z","updated_at":"2026-08-08T14:56:46Z","closed_at":"2026-08-08T14:56:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/402","source_system":"github:https://github.com/samcharles93/archie-core/issues/402:402","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499750-380-d689ed89","title":"Phase 3: correctness findings needing judgement (~62 issues)","description":"nilerr (11: 6 in internal/agentexec inprocess.go/worker.go, 2 gateway), bodyclose (1), contextcheck (7), containedctx (2), fatcontext. SINGLE SESSION, sequential, no subagents: each nilerr site needs a read of whether the swallow is deliberate degradation or a real bug, and a context-free worker will silently convert deliberate behaviour into a change. Do nilerr FIRST -- highest bug probability in the whole set. BLOCKED on a policy decision for noctx (41 sites, mostly webui/worktree/store): fixing it means threading context through public APIs, which is an API change, not a lint fix.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:39Z","updated_at":"2026-08-08T14:56:41Z","closed_at":"2026-08-08T14:56:42Z","external_ref":"https://github.com/samcharles93/archie-core/issues/401","source_system":"github:https://github.com/samcharles93/archie-core/issues/401:401","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499722-379-670f62fc","title":"Phase 2: mechanical per-package fixes (~40 issues)","description":"forcetypeassert (24, internal/tools 20 + internal/memory 2, nearly all tests), predeclared (9, webui/ratelimit/memory), leftover unconvert. Purely mechanical, package-local, no design judgement. THE ONLY PHASE WORTH PARALLELISING. Partition by package: tools / webui / memory+ratelimit / secret. Use git worktree isolation -- other sessions edit this repo concurrently and stale diagnostics are a known hazard. Each worker verifies scoped: go test ./internal/X/... plus golangci-lint run ./internal/X/...","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:34Z","updated_at":"2026-08-08T14:56:36Z","closed_at":"2026-08-08T14:56:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/400","source_system":"github:https://github.com/samcharles93/archie-core/issues/400:400","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499692-378-45486e7d","title":"Phase 1: autofix pass (~35 issues)","description":"golangci-lint run --fix plus the formatters. Covers errorlint, fatcontext, gocritic, sloglint, usestdlibvars, usetesting, gci, gofumpt, goimports. Zero judgement. MUST run first: it touches formatting across every file and would conflict with anything in flight. Single command, single commit, verify with task check.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:28Z","updated_at":"2026-08-08T14:56:31Z","closed_at":"2026-08-08T14:56:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/399","source_system":"github:https://github.com/samcharles93/archie-core/issues/399:399","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499664-377-c2818afd","title":"[EPIC] Clear the 160 golangci-lint findings","description":"Config landed in 9298afd; the gate is RED until this epic closes. Four phases, ordered by risk and by what invalidates what. Structural refactor MUST be last: it moves line numbers and invalidates everything in flight.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:56:25Z","updated_at":"2026-08-08T15:34:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/398","source_system":"github:https://github.com/samcharles93/archie-core/issues/398:398","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499636-376-2f94082e","title":"Bind curators to memory engines","description":"Wire the attached-memory-engine part of a curator's declared shape once the memory engine family exists, so a curator reads and writes through the engine contract rather than a concrete store.\n\n### Acceptance Criteria\n\nA curator declares which memory engine it uses and receives it as a typed dependency. Swapping the configured engine changes where a curator's memories land with no change to the curator. A curator with no declared memory engine is a valid configuration and is rejected only if it attempts a memory operation.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:56:23Z","updated_at":"2026-08-08T14:56:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/397","source_system":"github:https://github.com/samcharles93/archie-core/issues/397:397","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499610-375-5e43fe37","title":"Consolidate duplicated NATS RPC client/server boilerplate","description":"internal/storerpc/storerpc.go, internal/worktreerpc/worktreerpc.go, internal/forgerpc/forgerpc.go each reimplement near-identical timeout/marshal/error-envelope helpers for NATS request/reply RPC. Extract shared helpers into a common package.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:17Z","updated_at":"2026-08-08T14:56:20Z","closed_at":"2026-08-08T14:56:21Z","external_ref":"https://github.com/samcharles93/archie-core/issues/396","source_system":"github:https://github.com/samcharles93/archie-core/issues/396:396","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499585-374-bf060b8b","title":"infrastructure/eventbus/nats: relocate NATS transport","description":"Create internal/infrastructure/eventbus/nats as a properly structured replacement for internal/nats. This is NOT a mechanical move: the existing code has no interfaces, leaks vendor types (Conn() *nats.Conn, PublishMsg(*nats.Msg), Fetch() jetstream.Msg) into all four consumers, uses a 7-positional-parameter publish with stringly-typed comma-separated labels, stores an unused logger, returns (nil, nil) for 'no message', and hardcodes stream/consumer/timeout config. Rebuild it with: separate files per concern; a Message wrapper so jetstream types stop crossing the boundary; Publisher/Consumer interfaces; a Config struct; sentinel errors; consistent %w wrapping; real logging. Then update cmd/archied, cmd/archie-agent, internal/daemon and internal/agentexec to the new API.\n\n### Acceptance Criteria\n\ninternal/nats no longer exists; internal/infrastructure/eventbus/nats has its contents. All imports updated. task check clean. Container and NATS behaviour unchanged.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:12Z","updated_at":"2026-08-08T14:56:15Z","closed_at":"2026-08-08T14:56:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/395","source_system":"github:https://github.com/samcharles93/archie-core/issues/395:395","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499562-373-11ad6000","title":"fix(nell): counters squat on the SDK-reserved meta: prefix, blocking all writes after restart","description":"TOTAL OUTAGE. No task can be queued and no event recorded; survives restarts.\n\ninternal/nell/adapter.go:946,952 store auto-increment counters at meta:task_id_counter and meta:event_id_counter. The NellDB SDK reserves the meta: prefix for its own bookkeeping (sdk/replicate.go:841 isInternalID = id[:5]==\"meta:\").\n\nDocDB.reindex() skips internal ids when rebuilding the in-memory rev cache (sdk/docdb.go:128-137), but the record stays in the log. So after a restart Get returns the counter doc WITH its _rev while d.revs has no entry, and putIn rejects exactly that: 'incomingRev != \"\" \u0026\u0026 !exists' -\u003e ErrConflict (sdk/docdb.go:213-217). Permanent.\n\nHits nextTaskID (every EnqueueIssue) and nextEventID (every InsertEvent). processNATSTask Naks on error so NATS redelivers forever.\n\nReproduced: internal/nell/counter_repro_test.go - open, insert, close, reopen, insert -\u003e ErrConflict in 7ms with no daemon/NATS/forge.\n\nSECOND DEFECT: isInternalID exists to exclude records from replication, so the two carina instances never converge their counters and would allocate COLLIDING task IDs. Masked only because allocation currently fails outright.\n\nFIX: move the keys out of the reserved namespace (counter:task_id / counter:event_id) AND migrate on open - the old doc is readable (only Put fails), and its next_id is load-bearing because restarting at 1 would reissue live task IDs. Also teach isMetaKey (adapter.go:803) to skip the new prefix so scans do not parse a counter as a task.\n\nREJECTED: stripping _rev before Put is one line and works, but leaves the prefix squat, leaves counters unreplicated, and turns a loud failure into silent last-write-wins.\n\nFull writeup: docs/incident-nelldb-counter-conflict.md","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:56:07Z","updated_at":"2026-08-08T14:56:09Z","closed_at":"2026-08-08T14:56:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/394","source_system":"github:https://github.com/samcharles93/archie-core/issues/394:394","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499539-372-295c7dd9","title":"Simplify Telegram model command surface","description":"Remove the redundant /models command from Telegram's published and executable command surface; retain /model selector. Make /help menu copy useful rather than self-referential.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:02Z","updated_at":"2026-08-08T14:56:04Z","closed_at":"2026-08-08T14:56:05Z","external_ref":"https://github.com/samcharles93/archie-core/issues/393","source_system":"github:https://github.com/samcharles93/archie-core/issues/393:393","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499513-371-52235c61","title":"Consolidate 6 duplicated Yaegi interpreter bootstraps","description":"internal/gate/gateeval/yaegi.go, internal/workflow/wfeval/yaegi.go, internal/workflow/skillbuild/skillbuild.go, internal/skillscript/yaegi.go, internal/plugin/plugin.go, internal/skill/plugin.go each hand-roll interp.New/i.Use(stdlib.Symbols)/panic-recovery. Extract a shared helper (new package, e.g. internal/yaegiutil) for interpreter construction + panic-safe eval, used by all six.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:55:56Z","updated_at":"2026-08-08T14:55:59Z","closed_at":"2026-08-08T14:56:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/392","source_system":"github:https://github.com/samcharles93/archie-core/issues/392:392","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499480-370-223df308","title":"Ship the file-writing store as the default memory engine","description":"Reframe internal/memory/builtin as the reference engine implementation behind the new contract, so the standard install keeps writing memories to files with no configuration and no behaviour change.\n\n### Acceptance Criteria\n\nThe builtin store implements the engine contract and registers as the default. A config that names no memory engine behaves exactly as today, verified by existing internal/memory tests continuing to pass unmodified where they assert behaviour rather than structure. Its lifecycle methods are real or explicit no-ops, not stubs that silently do nothing surprising.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:55:53Z","updated_at":"2026-08-08T14:55:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/391","source_system":"github:https://github.com/samcharles93/archie-core/issues/391:391","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499459-369-0770c1e8","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":"closed","priority":2,"issue_type":"bug","assignee":"samcharles93","created_at":"2026-08-08T14:55:50Z","updated_at":"2026-08-09T13:24:07Z","closed_at":"2026-08-09T13:24:08Z","external_ref":"https://github.com/samcharles93/archie-core/issues/390","source_system":"github:https://github.com/samcharles93/archie-core/issues/390:390","metadata":null,"labels":["bug","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499439-368-69670625","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:55:45Z","updated_at":"2026-08-08T14:55:47Z","closed_at":"2026-08-08T14:55:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/389","source_system":"github:https://github.com/samcharles93/archie-core/issues/389:389","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499419-367-d7b27566","title":"NATS transport: JetStream task queue + request-reply between daemon and archie-agent","description":"Phase 1 of docs/prds/archie-core-v2-architecture.md. internal/events.Bus (in-process pub/sub, already feeding SQLite + SSE) is the natural seam to replace the transport under. Daemon publishes tasks, archie-agent consumes, results return via NATS. Preserve current inprocess mode via [agent] mode default for local dev.\n\n### Design\n\nAdd optional [nats] config block (url, token_env), default anonymous auth for single-node, credentials required for multi-node per PRD sec.9 open question 2.\n\n### Acceptance Criteria\n\nDaemon can dispatch a task to archie-agent over NATS JetStream and receive results via request-reply; inprocess mode still works unchanged.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:55:39Z","updated_at":"2026-08-08T14:55:42Z","closed_at":"2026-08-08T14:55:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/388","source_system":"github:https://github.com/samcharles93/archie-core/issues/388:388","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499393-366-5c34a02a","title":"One optional MCP provider failing takes down the whole daemon","description":"internal/tools/provider/provider.go Start() is atomic by design -- 'Any failure rolls the complete family back' -- so a single failing provider unregisters every other provider including the builtins, capabilityHost.Start returns the error, and cmd/archied/main.go:655 exits 1. Under compose restart or systemd Restart=on-failure that is a crash loop. Observed 2026-07-30 on carina: mcp.desktop-commander could not start (missing unzip in the runtime image, fixed in 455fd6f) and archied restarted continuously, losing chat, the gateway and every builtin tool over one third-party npm package.\\n\\nAtomicity is correct for a provider the daemon requires. It is wrong for an external MCP server pulled from a registry at runtime, which is exactly the category that should be allowed to be absent -- the same reasoning applied to the forge in 518a1a0, where a missing credential now disables the capability rather than the daemon.\n\n### Design\n\nNeeds a required/optional distinction on the registration or manifest, which does not exist today. Keep the all-or-nothing path for required providers; the atomic batch semantics for tool visibility (tools appear only after Start and Discover both succeed) should hold per-provider either way. Relates to the plugin engine rule in ARCHITECTURE.md: failure isolation is explicitly the owning manager's responsibility.\n\n### Acceptance Criteria\n\nA provider can be declared optional. An optional provider that fails to start or discover is logged, excluded from the running set, and does not roll back the family or stop the daemon. A required provider keeps today's atomic rollback. Provider health reflects the degraded state so the failure is visible rather than silent. Regression test starts a family containing one failing optional provider and asserts the other providers' tools remain registered and Start returns nil.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:55:34Z","updated_at":"2026-08-08T15:34:05Z","closed_at":"2026-08-08T15:34:06Z","external_ref":"https://github.com/samcharles93/archie-core/issues/387","source_system":"github:https://github.com/samcharles93/archie-core/issues/387:387","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499369-365-d0a0d56c","title":"Telegram: separate task status from chat runtime status","description":"Split Telegram task and runtime status into distinct commands. MVP from Sam:\\n\\n/tasks:\\n- command name is exactly /tasks\\n- show only when running tasks exist; when none are running, explain how to set up workflows for continuous development\\n- let the user select a running task by its description/title; first verify task records actually carry usable titles/descriptions, otherwise treat that as a blocker\\n\\n/status:\\n- show session details\\n- show configured provider\\n- show configured model\\n- show installed plugins\\n- Hermes-style session metadata is the reference direction; exact fields can expand later\\n\\nDo not mix task state into /status.\n\n### Acceptance Criteria\n\n/tasks is the sole task-status command; it lists selectable running tasks by usable title/description, or gives workflow setup guidance when none run; implementation is blocked/escalated if task records lack usable titles. /status reports only chat/runtime state: session details, configured provider, configured model, and installed plugins. Task and runtime outputs do not mix. Telegram menu/help/executable parity and tests cover both commands.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:55:29Z","updated_at":"2026-08-08T14:55:32Z","closed_at":"2026-08-08T14:55:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/386","source_system":"github:https://github.com/samcharles93/archie-core/issues/386:386","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499346-364-107ec05b","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":2,"issue_type":"bug","created_at":"2026-08-08T14:55:24Z","updated_at":"2026-08-08T14:55:27Z","closed_at":"2026-08-08T14:55:28Z","external_ref":"https://github.com/samcharles93/archie-core/issues/385","source_system":"github:https://github.com/samcharles93/archie-core/issues/385:385","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499318-363-a3050cb6","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:55:19Z","updated_at":"2026-08-08T14:55:22Z","closed_at":"2026-08-08T14:55:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/384","source_system":"github:https://github.com/samcharles93/archie-core/issues/384:384","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499292-362-8b520db8","title":"Persistent volumes with TTL for container/worktree storage","description":"Phase 2 of docs/prds/archie-core-v2-architecture.md. Current worktree lifecycle is fresh-clone-per-task with status-driven cleanup, no TTL. Add persistent volume support with TTL-based expiry to avoid repeated full clones for repeated work on the same repo.\n\n### Acceptance Criteria\n\nContainer/worktree storage can persist across tasks for the same repo up to a configured TTL, with automatic cleanup after expiry.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:55:14Z","updated_at":"2026-08-08T15:35:47Z","closed_at":"2026-08-08T15:35:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/383","source_system":"github:https://github.com/samcharles93/archie-core/issues/383:383","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499268-361-285a7a81","title":"feat(webui): logs section - filterable, live-tailing","description":"There is no way to see archied's logs outside journalctl. Every event already flows through events.Bus into the store and out over SSE, so this is mostly presentation over existing data. Filterable by level and component, live-tailing the SSE stream, with history from the store for anything before the dashboard connected.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:55:09Z","updated_at":"2026-08-08T15:33:52Z","closed_at":"2026-08-08T15:33:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/382","source_system":"github:https://github.com/samcharles93/archie-core/issues/382:382","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499248-360-a6ac2616","title":"Regression tests: NATS RPC — request timeout, reply routing, error propagation","description":"internal/natsrpc/natsrpc.go has only 1 test (envelope round trip). Missing: request timeout handling, reply-to routing correctness, error propagation through the envelope, concurrent request isolation, reconnection behavior.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:55:03Z","updated_at":"2026-08-08T14:55:06Z","closed_at":"2026-08-08T14:55:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/381","source_system":"github:https://github.com/samcharles93/archie-core/issues/381:381","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499227-359-c3682a55","title":"Audit the remaining golangci-lint autofix changes in 6d4e0be","description":"Commit 6d4e0be applied a golangci-lint --fix batch across 8 files. One of the eight was a behaviour regression: the errorlint fix in internal/tools/builtin/grep.go rewrote 'if exitErr, ok := err.(*exec.ExitError); ok \u0026\u0026 exitErr.ExitCode() == 1' into 'errors.As(err, \u0026exitErr)' and dropped the exit-code check, so any ripgrep failure (bad pattern, unreadable path) was reported to the model as 'no matches found' -- the agent would state a file contains nothing on the strength of a search that never ran. Fixed in 782510d. The other seven changes were eyeballed as benign (naked return expanded, err != ctx.Err() -\u003e errors.Is) but were never verified individually. A one-in-eight regression rate does not justify trusting the remainder on inspection alone.\n\n### Acceptance Criteria\n\nEach remaining changed hunk in 6d4e0be is reviewed against its pre-fix behaviour, specifically for predicates that were narrowed or widened. internal/channels/telegram/model.go, internal/infrastructure/configuration/discovery.go, internal/tools/builtin/find.go, internal/tools/builtin/shell.go and the touched test files are covered. Any behaviour change found gets a regression test in the style of TestGrepReportsSearchFailureRatherThanNoMatches.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:54:58Z","updated_at":"2026-08-08T15:34:09Z","closed_at":"2026-08-08T15:34:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/380","source_system":"github:https://github.com/samcharles93/archie-core/issues/380:380","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499206-358-54f29252","title":"Skill curator (reference implementation)","description":"Ship a curator that maintains Archie's skills: reviewing, pruning, and improving skill definitions over time. One of the two consumers that validate the curator contract is general enough.\n\n### Acceptance Criteria\n\nRegisters and runs through the curator registry with no curator-specific special-casing in the runtime. Its changes to skills are observable and attributable to the curator. It operates within its declared tool set and cannot reach tools it did not declare.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:54:55Z","updated_at":"2026-08-08T14:54:55Z","external_ref":"https://github.com/samcharles93/archie-core/issues/379","source_system":"github:https://github.com/samcharles93/archie-core/issues/379:379","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499183-357-e3f7603f","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:54:50Z","updated_at":"2026-08-08T14:54:52Z","closed_at":"2026-08-08T14:54:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/378","source_system":"github:https://github.com/samcharles93/archie-core/issues/378:378","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499161-356-e424e40d","title":"[EPIC] Pluggable memory engine: typed family + external providers","description":"Make the memory subsystem a pluggable engine family so an external memory backend (Honcho, or a future alternative) can be bolted on without touching the agent loop, while the file-writing store ships as the default. internal/memory already has a Manager and lifecycle hooks (TurnStartHook, SessionEndHook, SessionSwitchHook); this epic promotes that into a conforming engine family per the strict plugin engine rule in ARCHITECTURE.md rather than inventing a parallel abstraction.\n\n### Design\n\nConstraint from the plugin engine rule: 'engine' requires a typed domain contract, an owning Registry or Manager, explicit lifecycle/health, and narrow typed registrars -- providers never receive *daemon.Daemon or untyped hook maps. The contract must express real memory operations (write observation, query, list, forget), not just Name/Version.\n\n### Acceptance Criteria\n\nMemory is a typed engine family with an owning registry/manager, start/health/stop lifecycle, and narrow typed host access, satisfying every invariant in ARCHITECTURE.md 'Plugin engine rule (strict)' and passing internal/plugin/architecture_test.go. The builtin file-writing store is the shipped default engine and remains the behaviour when nothing is configured. At least one external engine is implementable against the contract without changes to the agent loop or gateway. Engine selection and per-engine settings are configurable, validated, and documented. Failure of a non-default engine degrades to a reported error rather than taking down a turn.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:54:47Z","updated_at":"2026-08-08T14:54:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/377","source_system":"github:https://github.com/samcharles93/archie-core/issues/377:377","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499136-355-c766a8ee","title":"Quiet autonomous execution and correct forge linkage","description":"Reduce Archie forge noise and make issue/branch/PR lifecycle authoritative. Automatic plan/progress/retry/state-label comments must be disabled; human decisions must remain available through messaging and the Web UI; pushed task branches must be linked to their source issues through the forge API before PR creation.\n\n### Acceptance Criteria\n\nNo automatic plan/progress/retry/state-label comments are emitted; configured human decisions remain actionable through messaging or Web UI; the source issue has a forge branch link after push; PR creation does not rely on a comment or closing directive for linkage; focused tests cover both in-process and RPC forge paths.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:54:42Z","updated_at":"2026-08-08T14:54:44Z","closed_at":"2026-08-08T14:54:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/376","source_system":"github:https://github.com/samcharles93/archie-core/issues/376:376","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499114-354-e5b475b4","title":"Persistent session-memory curator (reference implementation)","description":"Ship a curator that maintains durable memory across sessions -- extracting and consolidating what is worth keeping from conversation history into the attached memory engine. The second contract consumer, and the one that exercises the curator/memory-engine binding.\n\n### Acceptance Criteria\n\nRegisters and runs through the registry with no special-casing. Writes through the memory engine contract rather than any concrete store. Extraction runs off the hot path so a chat turn never waits on it. What it wrote and why is inspectable. Honours the trigger-accounting invariant so its own writes do not reschedule it.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:54:39Z","updated_at":"2026-08-08T14:54:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/375","source_system":"github:https://github.com/samcharles93/archie-core/issues/375:375","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499092-353-ed4800d2","title":"Regression tests: NellDB adapter — edge cases, error recovery, concurrent access","description":"internal/nell/adapter_test.go has 7 tests covering the happy path. Missing: corrupted log recovery, concurrent Enqueue/ClaimNext, Get/List with empty store, oversized event payloads, context cancellation during operations, observer callback error isolation.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:54:34Z","updated_at":"2026-08-08T14:54:36Z","closed_at":"2026-08-08T14:54:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/374","source_system":"github:https://github.com/samcharles93/archie-core/issues/374:374","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499063-352-c2b85c1a","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.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:54:29Z","updated_at":"2026-08-08T15:34:03Z","closed_at":"2026-08-08T15:34:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/373","source_system":"github:https://github.com/samcharles93/archie-core/issues/373:373","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499041-351-b4253aa3","title":"Link pushed task branch to source issue before opening PR","description":"After the task branch is successfully pushed, call the forge branch-link operation for the source issue, then create the PR without relying on a PR comment or Closes directive to associate it. Propagate link failures and cover Gitea plus forge RPC behavior.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:54:23Z","updated_at":"2026-08-08T14:54:26Z","closed_at":"2026-08-08T14:54:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/372","source_system":"github:https://github.com/samcharles93/archie-core/issues/372:372","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499018-350-0fc03bf9","title":"Per-repo allow_concurrent override for same-repo multi-agent work","description":"Concurrent agents on the same repo are blocked by default (worktree conflict). PRD sec.9 open question 5 proposes a per-repo config override (allow_concurrent = true) for repos where parallel work is safe (different base branches, different packages). Deferred to Phase 2 in the PRD; depends on the daemon supporting concurrent task dispatch at all.\n\n### Acceptance Criteria\n\nRepos with allow_concurrent = true in [[repos]] config can have multiple agents working simultaneously without worktree collisions; repos without it keep current serialized behavior.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:54:18Z","updated_at":"2026-08-08T14:54:21Z","closed_at":"2026-08-08T14:54:22Z","external_ref":"https://github.com/samcharles93/archie-core/issues/371","source_system":"github:https://github.com/samcharles93/archie-core/issues/371:371","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498998-349-fe936acb","title":"config.example.toml has no token_env placeholder under [chat.telegram]","description":"TelegramConfig.TokenEnv (internal/config/config.go:536) is a real, used field (cmd/archied/telegram_setup.go reads it via os.Getenv), but the commented [chat.telegram] block in config.example.toml only documents update_check_command / update_install_command -- there is no \"# token_env = ...\" line. An operator reading the example file to learn what's configurable would not discover this key exists.\n\nDiscovered while implementing archie-core-rs9 and testing tomlwrite.Apply against the real template: setting chat.telegram.token_env for the first time falls through to Apply's \"key not found in table\" path (uncomment header, append key), which works fine -- this is a documentation completeness gap in the template, not a functional blocker for archie-core-cbk.\n\n### Acceptance Criteria\n\nAdd a commented `# token_env = \"...\"` line (with a short comment on what it should point to, e.g. an env var containing the @BotFather token) under the commented [chat.telegram] block in config.example.toml, matching the style of the other commented-out optional fields.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:54:15Z","updated_at":"2026-08-08T14:54:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/370","source_system":"github:https://github.com/samcharles93/archie-core/issues/370:370","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498978-348-c221a031","title":"Export configuration.Validate for archied setup to call","description":"The ewk epic's acceptance criteria (and archie-core-cbk's, by inheritance) require: \"Every config it writes passes configuration.Validate, verified by a test that runs setup non-interactively and validates the output.\" That identifier does not exist. internal/infrastructure/configuration/validate.go defines only an unexported validate(cfg *config.Config) error, called from one place: loader.go:178 inside Loader.Load's own decode-then-validate sequence. There is no way for code outside the configuration package -- e.g. `archied setup` after it builds a config.Config in memory but before writing it to disk -- to run the same validation.\n\nDiscovered while implementing archie-core-rs9 (TOML write strategy). Not fixed there: rs9's scope was the text-patching mechanism, not wiring setup's actual validation step, and exporting validate() is really part of cbk's job (the thing that needs to call it).\n\n### Acceptance Criteria\n\nconfiguration package exposes a callable that runs the same checks as the current unexported validate() against a config.Config value in memory (either export validate itself, or add a thin Validate(cfg *config.Config) error wrapper -- whichever fits the package's existing exported-surface conventions). Loader.Load continues to use it internally with no behavior change. A test outside the package (e.g. in cbk's setup tests) can call it directly without going through file I/O.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:54:10Z","updated_at":"2026-08-08T14:54:13Z","closed_at":"2026-08-08T14:54:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/369","source_system":"github:https://github.com/samcharles93/archie-core/issues/369:369","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498957-347-60ea9b86","title":"[EPIC] archied setup: interactive first-run configuration","description":"Move config generation out of install.sh and into the daemon as 'archied setup', so the thing that writes config.toml is the same code that reads it. install.sh currently hand-rolls TOML and has already drifted from the schema once: it hardcoded the GitHub token key and the Gitea host, so a Gitea install produced a config naming a token the installer never wrote. Modelled on tau's 'tau setup' (internal/cli/setup.go, internal/app/setup.go), adapted for archie's TOML config and existing secret-reference indirection.\n\n### Design\n\nPort from tau: the CLI/app split behind a SetupPrompter interface so business logic is UI-agnostic and testable without a terminal; plain-stdio Select and hidden ReadSecret (golang.org/x/term) racing ctx.Done for Ctrl+C -- no TUI dependency; atomic temp+rename writes. DIVERGENCE FROM TAU: tau surgically patches YAML nodes to preserve comments. archie uses BurntSushi/toml, which does not preserve comments across a decode/encode round trip, so a full re-marshal would destroy config.example.toml's documentation. Decide this explicitly -- see the child issue. Secrets differ too: archie already has secret.SecretRef{engine,key} indirection, so setup writes the reference into TOML and the value into the env engine's store; that is archie's equivalent of tau's config.yaml/auth.yaml split and should be used rather than reinvented.\n\n### Acceptance Criteria\n\ninstall.sh no longer generates config.toml; it invokes archied setup. Setup is idempotent and re-runnable against an existing config without clobbering unrelated settings. Every config it writes passes configuration.Validate, verified by a test that runs setup non-interactively and validates the output. Secrets never reach config.toml or argv: config holds a secret reference, the value goes to the env file at 0600 via atomic write. Prompts for secrets do not echo. A non-TTY invocation without sufficient input fails with a clear message rather than writing a partial config.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:54:07Z","updated_at":"2026-08-08T14:54:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/368","source_system":"github:https://github.com/samcharles93/archie-core/issues/368:368","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498934-346-eeaf0e27","title":"telegram: publish /new /retry /undo in menu and help","description":"TestPublishedCommandsMatchExecutableCommandSurface in\ninternal/channels/telegram/telegram_test.go fails: /new, /retry and /undo are\nexecutable commands but are missing from the published command menu and the\nhelp text, so users cannot discover them.\n\nRun: go test ./internal/channels/telegram/...\n\nScope:\n- ONLY internal/channels/telegram/. Do not touch any other package.\n- Read the test to see how it derives the executable command surface, then add\n the three commands to whichever menu/help structures it compares against.\n- Match the existing entries' wording style and ordering conventions.\n\nConstraints:\n- Do NOT add //nolint or otherwise suppress lint findings.\n- Do NOT modify the test to make it pass. The test is correct: these commands\n really are missing from the menu.\n- Do NOT write architecture docs, ledgers, plans or new beads.\n\nDone when: go build ./... , go vet ./... , gofmt -l . clean, and\ngo test ./internal/channels/telegram/... passes.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:54:02Z","updated_at":"2026-08-08T14:54:04Z","closed_at":"2026-08-08T14:54:05Z","external_ref":"https://github.com/samcharles93/archie-core/issues/367","source_system":"github:https://github.com/samcharles93/archie-core/issues/367:367","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498907-345-c44f5f9e","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":2,"issue_type":"bug","created_at":"2026-08-08T14:53:56Z","updated_at":"2026-08-08T14:53:59Z","closed_at":"2026-08-08T14:54:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/366","source_system":"github:https://github.com/samcharles93/archie-core/issues/366:366","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498881-344-49bb8398","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.\n\n### Acceptance Criteria\n\nRoot cause is demonstrated with code path, live evidence, and a focused reproducer; affected ordering contract and correct fix seam are identified.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:53:51Z","updated_at":"2026-08-08T15:33:36Z","closed_at":"2026-08-08T15:33:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/365","source_system":"github:https://github.com/samcharles93/archie-core/issues/365:365","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498858-343-be43924c","title":"install.sh: REPO_URL points at a repository that does not exist","description":"install.sh:26 sets REPO_URL to https://github.com/samcharles93/archie-core.git, which is not reachable; origin is https://git.catlow.cloud/sam/archie-core.git. Only affects the path where the installer is not run from a local clone -- i.e. the curl-to-shell install this script exists to serve. Sam is working locally for now and deliberately deferred this on 2026-07-30; filed so it is not forgotten before any public install path is offered.\n\n### Acceptance Criteria\n\nREPO_URL resolves to a repository the installer can actually clone, or the clone path is removed in favour of requiring a local checkout.","status":"open","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:53:48Z","updated_at":"2026-08-08T14:53:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/364","source_system":"github:https://github.com/samcharles93/archie-core/issues/364:364","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498831-342-8b3b4c26","title":"Dedup skillbuild.BuildRegistry/AugmentRegistry and align with wfeval.loadStage","description":"internal/workflow/skillbuild/skillbuild.go:41 BuildRegistry and :97 AugmentRegistry are near copy-paste merge loops. Also skillbuild.loadStage and wfeval.loadStage independently implement the same 'Yaegi plugin exports Stage()' loading pattern and have already diverged (skillbuild has a legacy positional-fields fallback wfeval lacks). Share the merge loop and the stage-loading logic.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:53:43Z","updated_at":"2026-08-08T14:53:46Z","closed_at":"2026-08-08T14:53:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/363","source_system":"github:https://github.com/samcharles93/archie-core/issues/363:363","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498804-341-8d311cf6","title":"Setup steps: operator, provider, models, forge, chat channel","description":"The archie equivalent of tau's provider+model flow. Steps: (1) operator display name -\u003e [chat].operator; (2) LLM provider -\u003e [providers.\u003cname\u003e] class and api_key_env, with the key value stored via the secret engine; (3) models per role -\u003e [models] triage/planner/builder, plus the optional [chat].models catalog; (4) forge -\u003e github/gitea/none with host and a token reference, explicitly optional now that a missing forge credential only disables the forge; (5) chat channel -\u003e Telegram bot token, optional. bot_user must always be written because validation requires it when no [[identities]] exist.\n\n### Acceptance Criteria\n\nEach step is skippable where the underlying setting is optional, and skipping leaves a valid config. Forge selection defaults to none rather than assuming a forge. The token key written into config matches the key the value was stored under, for every forge type -- the exact drift that broke the installer. Local model discovery (Ollama) is offered when available and degrades to free text when not.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:53:38Z","updated_at":"2026-08-08T14:53:41Z","closed_at":"2026-08-08T14:53:42Z","external_ref":"https://github.com/samcharles93/archie-core/issues/362","source_system":"github:https://github.com/samcharles93/archie-core/issues/362:362","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498781-340-929108e6","title":"install.sh: unknown flags are silently ignored","description":"The 'for arg in $@' case statement has no default branch, so a mistyped flag does nothing and the installer proceeds with defaults. '--no-systmd' installs the systemd service the user was trying to skip. Options discussed 2026-07-30: (a) reject unknown args with exit 1; (b) warn on stderr and continue; (c) reject unknown --flags but ignore bare words. Recommendation was (a) -- this is an interactive installer run by hand, typos dominate, and silent wrong behaviour is the worst outcome; the forward-compatibility argument for (b) does not apply while there is no ecosystem of wrapper scripts. Awaiting Sam's decision.\n\n### Acceptance Criteria\n\nA mistyped flag produces a clear diagnostic rather than silently different behaviour. The chosen policy is applied consistently and reflected in --help.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:53:33Z","updated_at":"2026-08-08T14:53:36Z","closed_at":"2026-08-08T14:53:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/361","source_system":"github:https://github.com/samcharles93/archie-core/issues/361:361","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498753-339-18a876ed","title":"install.sh: --force is advertised but does nothing","description":"FORCE_BUILD is initialised at install.sh:42 and set at :67 by --force, then never read. --help advertises '--force Force rebuild binaries even if up to date', so the flag is documented, accepted, and inert. The build step always rebuilds unconditionally, which means the flag is either redundant (delete it and the help line) or the up-to-date check it implies was never written.\n\n### Acceptance Criteria\n\nEither the flag and its help text are removed, or an up-to-date check exists that --force actually bypasses. No advertised flag is inert.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:53:28Z","updated_at":"2026-08-08T14:53:30Z","closed_at":"2026-08-08T14:53:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/360","source_system":"github:https://github.com/samcharles93/archie-core/issues/360:360","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498723-338-ca9b163b","title":"Telegram: announce newly installed Archie releases","description":"When archied starts after an installed release upgrade, notify authorized Telegram users once with an exact component-aware rundown from CHANGELOG.md. Present archied as THE GATEWAY and archie-agent as THE RUNTIME, explicitly saying when either component has no changes. Persist announced versions per recipient so ordinary restarts do not repeat notifications.\n\n### Acceptance Criteria\n\nRepository has a maintained component-aware CHANGELOG.md. On an installed version advance, each configured authorized Telegram user receives one concise message with separate THE GATEWAY and THE RUNTIME sections and explicit no-change wording where applicable. Announced component versions are persisted and duplicate restarts do not repeat. First-run and development builds have explicit non-spam behavior. Parsing, version transition, persistence failure, and delivery failure paths are tested.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:53:24Z","updated_at":"2026-08-08T15:35:13Z","external_ref":"https://github.com/samcharles93/archie-core/issues/359","source_system":"github:https://github.com/samcharles93/archie-core/issues/359:359","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498694-337-f829f27b","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).","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:53:19Z","updated_at":"2026-08-08T15:33:34Z","closed_at":"2026-08-08T15:33:35Z","external_ref":"https://github.com/samcharles93/archie-core/issues/358","source_system":"github:https://github.com/samcharles93/archie-core/issues/358:358","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498672-336-dd628434","title":"Regression tests: Events bus — multi-subscriber ordering, slow-consumer isolation","description":"internal/events/events.go has only 2 tests (fan-out + close). Missing: multi-subscriber delivery ordering guarantees, slow-consumer isolation (one slow subscriber shouldn't block others), publish-after-close behavior, buffer overflow semantics.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:53:14Z","updated_at":"2026-08-08T14:53:16Z","closed_at":"2026-08-08T14:53:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/357","source_system":"github:https://github.com/samcharles93/archie-core/issues/357:357","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498650-335-ab2a80b5","title":"Telegram: controlled execution and checkpoint commands","description":"Design /rollback [number] filesystem checkpoints, /stop background process termination, /approve and /deny for dangerous commands. /approve is RESERVED exclusively for dangerous-command approval; it must not be interpreted as task approval. The pending-command UX is inline selection buttons: Approve this time, Approve Permanently, Deny. Define the exact policy scope/lifetime for permanent approval, callback authorization, expiry, audit persistence, and cancellation. Requires a real sandbox/process/checkpoint authority; do not create commands that claim control over host processes or filesystem state Archie does not own.\n\n### Acceptance Criteria\n\nFor every pending dangerous command, Telegram renders authorized inline buttons exactly representing Approve this time, Approve Permanently, and Deny. Callbacks are recipient-bound, expiring, single-use, auditable, and cannot authorize a changed command. Permanent approval scope/lifetime is explicit. /approve exclusively controls this policy; /deny controls the same policy. Authority boundaries match actual sandbox/process ownership; tests cover authorization, expiry, replay, denial, and failure.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:53:08Z","updated_at":"2026-08-08T14:53:11Z","closed_at":"2026-08-08T14:53:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/356","source_system":"github:https://github.com/samcharles93/archie-core/issues/356:356","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498620-334-26d50d74","title":"Telegram: resilient session lifecycle and context commands","description":"Design gateway/runtime-owned commands that remain usable when LLM credits are exhausted: /start acknowledgement without a reply; /new [name] with /reset alias; /topic [off|help|session-id] for Telegram DM topic sessions; /retry; /undo [N]; /title [name]; /branch [name] with /fork alias; /compress [here [N]|focus topic|--preview|--dry-run] with /compact alias. Define session history, branching, retry/undo atomicity, context accounting, and persistence before implementation.\n\n### Acceptance Criteria\n\nEvery command has explicit session/history semantics and safe aliases; unavailable LLM credits do not block gateway/runtime commands; tests cover persistence, edge cases, and topic/session scoping.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:53:03Z","updated_at":"2026-08-08T14:53:05Z","closed_at":"2026-08-08T14:53:06Z","external_ref":"https://github.com/samcharles93/archie-core/issues/355","source_system":"github:https://github.com/samcharles93/archie-core/issues/355:355","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498591-333-533a0527","title":"Telegram: model scope and personality selection","description":"Extend /model to support Hermes-like /model [model] [--provider name] [--global|--session] [--refresh], with persisted default behaviour. Add /personality [name] for predefined personalities. Design global-versus-session ownership, provider filtering, persistence, refresh semantics, validity when credits are exhausted, and interaction with existing model selector before implementation.\n\n### Acceptance Criteria\n\n/model scope and persistence are explicit and tested; provider/model selection cannot be ambiguous; /personality operates on a defined catalog and session scope; existing Telegram selector behaviour remains coherent.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:52:58Z","updated_at":"2026-08-08T14:53:00Z","closed_at":"2026-08-08T14:53:01Z","external_ref":"https://github.com/samcharles93/archie-core/issues/354","source_system":"github:https://github.com/samcharles93/archie-core/issues/354:354","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498563-332-cfeef92a","title":"Telegram: multi-home-channel command","description":"When multiple home channels are introduced, design /sethome with /set_home alias to set a chat as a home channel. Define identity ownership, overwrite/confirmation rules, group authorization, persistence, and relationship to sessions before implementation.\n\n### Acceptance Criteria\n\nBlocked on the multiple-home-channel model; once unblocked, both aliases have identical safe behaviour, persist correctly, and are covered by authorization and migration tests.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:52:55Z","updated_at":"2026-08-08T14:52:55Z","external_ref":"https://github.com/samcharles93/archie-core/issues/353","source_system":"github:https://github.com/samcharles93/archie-core/issues/353:353","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498538-331-749d8d2e","title":"Telegram: access, profile, and session navigation commands","description":"Design and add Hermes-like /whoami, /profile, /resume [name], /sessions, plus /agents (active agents/running tasks). Determine Archie's actual role/access model, profile/home representation, session naming and browsing UX, persistence, authorization, and the relationship between /agents and the already-specified /tasks command before implementation.\n\n### Acceptance Criteria\n\nEach command accurately reports or navigates Archie-owned state; session listing/resume is safe and scoped; output/menu/help/tests are complete.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:52:50Z","updated_at":"2026-08-08T14:52:52Z","closed_at":"2026-08-08T14:52:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/352","source_system":"github:https://github.com/samcharles93/archie-core/issues/352:352","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498507-330-acc5cc12","title":"Telegram: steer and standing goal controls","description":"Design and add Hermes-like /steer \u003cprompt\u003e (inject after next tool call without interruption), /goal [text|draft \u003ctext\u003e|show|pause|resume|clear|status|wait \u003cpid\u003e|unwait], /subgoal [text|remove N|clear], and /queue \u003cprompt\u003e with aliases /q, /background \u003cprompt\u003e with aliases /bg and /btw. Define persistence, lifecycle, interaction with streaming/tool calls, task versus chat session ownership, background execution, and admin authorization before implementation.\n\n### Acceptance Criteria\n\nSemantics are explicitly designed and tested; steer injection timing is deterministic; goals/subgoals persist with correct pause/resume/clear/wait behaviour; commands are authorized and do not corrupt active work.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:52:45Z","updated_at":"2026-08-08T14:52:47Z","closed_at":"2026-08-08T14:52:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/351","source_system":"github:https://github.com/samcharles93/archie-core/issues/351:351","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498479-329-34397790","title":"[EPIC] Telegram: Hermes-style session and control commands","description":"Bring the frequently used Hermes control surface to Archie Telegram without copying Hermes semantics blindly. Design each command against Archie's actual session, task, goal, authorization, and future multi-home-channel models before implementation.\n\n### Acceptance Criteria\n\nCommand behaviour, authorization, persistence, and Telegram UX are specified and implemented in focused child work; menu/help remain aligned; no command claims state Archie does not own.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:52:42Z","updated_at":"2026-08-08T14:52:42Z","external_ref":"https://github.com/samcharles93/archie-core/issues/350","source_system":"github:https://github.com/samcharles93/archie-core/issues/350:350","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498451-328-976f53c2","title":"isForgeDisabled is duplicated in cmd/archied","description":"resolveForge in cmd/archied/main.go needs the none/off/disabled predicate, but the identical helper in internal/infrastructure/configuration is unexported, so 518a1a0 copied it with a comment noting the duplication. Two copies of a validation predicate drift: adding a fourth disabled-alias in one place silently leaves the other accepting it.\n\n### Acceptance Criteria\n\nOne definition of the disabled-forge predicate, referenced by both the configuration package and cmd/archied. The comment noting the duplication is removed with it.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:38Z","updated_at":"2026-08-08T14:52:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/349","source_system":"github:https://github.com/samcharles93/archie-core/issues/349:349","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498420-327-bacadaae","title":"feat(config): edit configuration from the dashboard (hybrid file + DB)","description":"Goal: change runtime-tunable settings from the web UI without hand-editing TOML.\n\nDecision (Sam, 2026-08-04): HYBRID, file stays primary. config.toml remains authoritative for bootstrap; a DB layer holds only runtime-tunable values as an overlay. Making the DB primary would move the thing that decides whether the daemon can boot into the thing the daemon must boot to read, and would lose the property that config is editable with any editor independent of daemon health.\n\nThe file format is NOT the blocker. Three things are, in this order:\n\n1. Config is passed BY VALUE. daemon.Daemon{Cfg config.Config} and workflow.Cfg config.Config each hold a copy made at construction, so mutating a central config would never reach them. Subsystems must read through an accessor or receive change events instead of holding snapshots. This is the real prerequisite.\n\n2. There is no reload path. No fsnotify, no SIGHUP, nothing -- Load runs once at startup. Changing the source without this only changes WHERE values come from, not WHEN.\n\n3. Startup is a hard gate. cmd/archied/main.go:588-598 exits the daemon when an MCP provider fails to start. A UI that writes bad config could brick the next boot, which is worse from a DB than from a file you can open in an editor. Writes need validation before persist, and a documented recovery path.\n\nAlready in our favour: internal/infrastructure/configuration/ is a real loader package (discovery, feature files, extras, defaults, validation, provenance, tomlwrite) and is already multi-source across TOML and YAML. A DB source is a new decoder alongside decodeTOML/decodeYAML, not a rewrite. provenance.go already tracks where each value came from, which is what the UI needs to show 'this came from the file, this from the DB'.\n\nRead-only config viewing already ships in the dashboard's Configuration section.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:35Z","updated_at":"2026-08-08T14:52:35Z","external_ref":"https://github.com/samcharles93/archie-core/issues/348","source_system":"github:https://github.com/samcharles93/archie-core/issues/348:348","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498391-326-bd841843","title":"Verify: MCP client capability for archie agents","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:30Z","updated_at":"2026-08-08T14:52:33Z","closed_at":"2026-08-08T14:52:34Z","external_ref":"https://github.com/samcharles93/archie-core/issues/347","source_system":"github:https://github.com/samcharles93/archie-core/issues/347:347","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498363-325-5853a9dd","title":"MCP client capability for archie agents","description":"Sam wants archie to be able to connect to MCP servers as a client (consume external tools/data sources from within agent workflows), analogous to how Claude Code itself uses MCP. Design and implement as a Layer 2 core plugin or agent-loop tool integration, depending on findings from wiring the plugin loader (archie-core-abg.2). Per docs/prds/multi-agent-collaboration.md phase E.\n\n### Acceptance Criteria\n\nAn agent workflow stage can call a tool exposed by a configured external MCP server, with the connection configured via daemon config or a core plugin.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:27Z","updated_at":"2026-08-08T14:52:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/346","source_system":"github:https://github.com/samcharles93/archie-core/issues/346:346","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498342-324-c4b0ec25","title":"Investigate agent-to-agent handoff within a single task workflow","description":"Sam wants agent-to-agent collaboration on a single task (plan -\u003e implement -\u003e review handoff), not just parallel identities. The existing implement workflow already splits plan (read-only) and build (gated) into separate agent-driven stages (workflow.Stage sequencing). Investigate how much of 'agent handoff' is genuinely new work vs. reframing/extending the existing stage model (e.g. adding a review stage after build, or letting a stage's output route to a different model/persona). This ties into the sibling agent-personas epic (archie-core-x96). Write findings before committing to an implementation approach. Per docs/prds/multi-agent-collaboration.md phase D.\n\n### Acceptance Criteria\n\nA short findings note states whether agent-to-agent handoff can be built as new workflow.Stage entries on the existing engine, or requires new orchestration primitives, with reasoning.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:22Z","updated_at":"2026-08-08T14:52:24Z","closed_at":"2026-08-08T14:52:25Z","external_ref":"https://github.com/samcharles93/archie-core/issues/345","source_system":"github:https://github.com/samcharles93/archie-core/issues/345:345","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498317-323-5d157fad","title":"Verify: Web UI: extend dashboard to bidirectional chat","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:17Z","updated_at":"2026-08-08T14:52:19Z","closed_at":"2026-08-08T14:52:20Z","external_ref":"https://github.com/samcharles93/archie-core/issues/344","source_system":"github:https://github.com/samcharles93/archie-core/issues/344:344","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498293-322-9abeec56","title":"Web UI: extend dashboard to bidirectional chat","description":"internal/webui is currently a read-only SSE dashboard. Extend it to a bidirectional chat surface implementing the same chat channel plugin interface built for Telegram, so the web UI gets status Q\u0026A and spawn/control parity too. Per docs/prds/multi-agent-collaboration.md phase C.\n\n### Acceptance Criteria\n\nThe web UI supports sending messages to archie and receiving responses, using the same chat channel interface and daemon-gatekeeping behavior as the Telegram channel.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:12Z","updated_at":"2026-08-08T15:35:42Z","closed_at":"2026-08-08T15:35:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/343","source_system":"github:https://github.com/samcharles93/archie-core/issues/343:343","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498271-321-617d39db","title":"Verify: Multi-session chat memory + slash commands","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:07Z","updated_at":"2026-08-08T14:52:09Z","closed_at":"2026-08-08T14:52:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/342","source_system":"github:https://github.com/samcharles93/archie-core/issues/342:342","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498244-320-1e3ab1cc","title":"Multi-session chat memory + slash commands","description":"Chat channels need conversation memory that persists across sessions, distinct from the existing per-task /data/memory.jsonl sketch in the v2 architecture PRD (which is task/project scoped, not conversation scoped). Also add slash-command support in chat (/status, /spawn, /approve, /cancel) per docs/prds/multi-agent-collaboration.md phase C. Depends on the chat channel interface existing first.\n\n### Acceptance Criteria\n\nA conversation started on a chat channel retains context across the operator closing and reopening the client. /status, /spawn, /approve, /cancel are recognized slash commands with documented behavior.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:52:02Z","updated_at":"2026-08-08T15:35:45Z","closed_at":"2026-08-08T15:35:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/341","source_system":"github:https://github.com/samcharles93/archie-core/issues/341:341","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498223-319-4fbc4c52","title":"Telegram voice message transcription","description":"Hermes has STT enabled (local whisper + OpenAI whisper). Sam doesn't need full STT, but wants Telegram voice messages transcribed to text for the agent. Telegram voice messages arrive as audio attachments (voice note type, OGG/Opus format).\n\nScope:\n- Detect voice message type from MessageEvent\n- Transcribe using OpenAI whisper API (or local whisper via Ollama)\n- Inject transcription into message text before routing to LLM\n- Cache transcriptions to avoid re-transcribing duplicate messages","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:59Z","updated_at":"2026-08-08T14:51:59Z","external_ref":"https://github.com/samcharles93/archie-core/issues/340","source_system":"github:https://github.com/samcharles93/archie-core/issues/340:340","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498194-318-8037193b","title":"Webhook platform adapter","description":"Hermes has webhook platform enabled (port 8644, HMAC secret). Sam confirmed webhooks are a must-have. This enables external services to push messages into archie-core's gateway for LLM processing.\n\nScope:\n- WebhookAdapter implementing gateway.Gateway interface\n- HTTP server with configurable host/port\n- Per-route HMAC validation\n- Deliver-only mode (inbound messages, no outbound send)\n- Idempotency cache for webhook deliveries\n- Prompt templates for transforming webhook payloads into messages","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:53Z","updated_at":"2026-08-08T14:51:56Z","closed_at":"2026-08-08T14:51:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/339","source_system":"github:https://github.com/samcharles93/archie-core/issues/339:339","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498163-317-3b29d768","title":"Telegram topic thread support","description":"Sam's Hermes has 19 active Telegram topic threads. archie-core's Telegram channel treats all chats as flat DMs. Topic threads are how Sam organizes his workstreams — each thread is a separate context.\n\nScope:\n- Detect message_thread_id in Telegram updates\n- Route to correct session based on platform+chat_id+thread_id (SessionSource already has thread_id field)\n- Create/switch sessions per topic thread\n- /status and /model commands scoped to the thread","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:48Z","updated_at":"2026-08-08T14:51:50Z","closed_at":"2026-08-08T14:51:51Z","external_ref":"https://github.com/samcharles93/archie-core/issues/338","source_system":"github:https://github.com/samcharles93/archie-core/issues/338:338","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498140-316-57777bfb","title":"Regression tests: Telegram channel — message routing, command handling, middleware, splitting","description":"Telegram channel tests are structural only (5 tests: Name, New, StartWithoutToken, Webhook 503, lifecycle). Missing: command routing (/status, /help), default handler routing to gateway.Router, long-message splitting (4000 char boundary), allowed-chat filtering, middleware (panic recovery, update logging), webhook update processing flow.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:51:43Z","updated_at":"2026-08-08T14:51:45Z","closed_at":"2026-08-08T14:51:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/337","source_system":"github:https://github.com/samcharles93/archie-core/issues/337:337","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498113-315-a82884f8","title":"Chat channel plugin interface + Telegram channel","description":"No chat/messaging code exists today (confirmed: grep for Telegram across the repo returns nothing outside a skills-PRD example). Define a chat channel plugin interface (parallel to forge.Forge) and implement Telegram as the first channel, with a read-only /status command reading daemon/task state. Full spawn/control action parity (the write side of the interview requirement) is split into archie-core-abg.13 since it needs its own task-creation semantics for chat-initiated (non-issue-backed) tasks. Per docs/prds/multi-agent-collaboration.md phase C.\n\n### Acceptance Criteria\n\nA chat.Channel interface exists (Name, Listen, Send or similar) implemented by a Telegram channel using the Bot HTTP API (long polling, no new heavy dependency). Sam can message the bot /status and get a real answer about current daemon/task state. Channel is wired into daemon startup behind an optional [chat] config block (absent = disabled, matching the [nats]/[containers] pattern).","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:38Z","updated_at":"2026-08-08T14:51:40Z","closed_at":"2026-08-08T14:51:41Z","external_ref":"https://github.com/samcharles93/archie-core/issues/336","source_system":"github:https://github.com/samcharles93/archie-core/issues/336:336","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498086-314-35debf0f","title":"Web Chat: support typed dangerous approvals","description":"Make shared Web Chat accept Telegram-equivalent /approve and /deny for pending dangerous action IDs, while preserving numeric task approval and supporting permanent approval.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:33Z","updated_at":"2026-08-08T14:51:35Z","closed_at":"2026-08-08T14:51:36Z","external_ref":"https://github.com/samcharles93/archie-core/issues/335","source_system":"github:https://github.com/samcharles93/archie-core/issues/335:335","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498059-313-92278623","title":"Web Chat: handle typed update command","description":"Make /update a shared gateway command using the same release update service and response formatter as Telegram, so Web typed commands and update controls behave consistently.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:27Z","updated_at":"2026-08-08T14:51:30Z","closed_at":"2026-08-08T14:51:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/334","source_system":"github:https://github.com/samcharles93/archie-core/issues/334:334","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637498028-312-d9943ea4","title":"Web Chat: capability-aware command discovery","description":"Expose structured command metadata in Web Chat help and include optional update and dangerous-action commands only when their capabilities are enabled.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:22Z","updated_at":"2026-08-08T14:51:24Z","closed_at":"2026-08-08T14:51:25Z","external_ref":"https://github.com/samcharles93/archie-core/issues/333","source_system":"github:https://github.com/samcharles93/archie-core/issues/333:333","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497985-311-a6872ae5","title":"Web Chat: share dangerous action approval workflow","description":"Extract the dangerous sandbox authority contract from Telegram and add an optional Web approval service for checkpoint rollback and process stop. The UI must remain hidden when no daemon-owned authority is configured and must require explicit approve, permanent approve, or deny decisions.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:17Z","updated_at":"2026-08-08T14:51:19Z","closed_at":"2026-08-08T14:51:20Z","external_ref":"https://github.com/samcharles93/archie-core/issues/332","source_system":"github:https://github.com/samcharles93/archie-core/issues/332:332","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497952-310-9c0ade87","title":"Web Chat: expose scoped Telegram restart","description":"Share Telegram's scoped /restart behavior with Web Chat. Add a daemon-owned restart callback, shared router command, authenticated Web endpoint, and explicit UI control without restarting the whole daemon.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:11Z","updated_at":"2026-08-08T14:51:14Z","closed_at":"2026-08-08T14:51:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/331","source_system":"github:https://github.com/samcharles93/archie-core/issues/331:331","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497923-309-2492398c","title":"Web Chat: render Telegram-style Markdown replies","description":"Render chat history and completed streamed replies with safe Markdown blocks, inline emphasis, links, code, lists, and quotes so the Web Chat matches Telegram's rich reply presentation.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:06Z","updated_at":"2026-08-08T14:51:08Z","closed_at":"2026-08-08T14:51:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/330","source_system":"github:https://github.com/samcharles93/archie-core/issues/330:330","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497894-308-b9665aea","title":"Web Chat: expose Telegram update workflow","description":"Expose the Telegram update check, defer, and approved install workflow in the Web Chat UI using the shared release update service. Preserve snapshot validation and explicit installation controls.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:51:00Z","updated_at":"2026-08-08T14:51:03Z","closed_at":"2026-08-08T14:51:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/329","source_system":"github:https://github.com/samcharles93/archie-core/issues/329:329","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497874-307-af25e33d","title":"Web Chat: refine workspace composition and composer UX","description":"Align the Web Chat page with the approved workspace inspiration: compact left conversation rail, centered empty state, quiet controls, and a composer-first layout while retaining existing sessions, streaming, commands, model, and personality controls.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:50:54Z","updated_at":"2026-08-08T14:50:57Z","closed_at":"2026-08-08T14:50:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/328","source_system":"github:https://github.com/samcharles93/archie-core/issues/328:328","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497847-306-524508fd","title":"Capability host: manifests, lifecycle, health, and typed family installation","description":"Replace the inert metadata-only daemon plugin inventory with a capability host that validates plugin manifests and coordinates lifecycle without adding generic domain hooks. The host owns module identity/API compatibility/dependency ordering/start/health/stop state; typed family registries remain responsible for capability registration. Wire it into archied startup/shutdown and expose status without passing *daemon.Daemon to plugins.\n\n### Design\n\nKeep plugin.Plugin exactly Name/Version. Add a validated Manifest and lifecycle vocabulary in internal/plugin plus a Host that manages manifests and lifecycle only. Capability packages receive narrow typed registrars; the host must not become an any-typed service locator. Start in dependency order, roll back a partially failed start, stop in reverse order, isolate panics/errors, and return immutable health snapshots. Preserve existing Yaegi loading through an adapter or manifest synthesis for metadata-only legacy plugins.\n\n### Acceptance Criteria\n\nManifest validation covers stable ID, semantic version, host API compatibility, declared capability kinds, dependencies, permissions, and optional config schema. Duplicate IDs, missing dependencies, cycles, incompatible API versions, and invalid manifests fail deterministically. Host lifecycle tests prove dependency-ordered start, rollback, reverse stop, health aggregation, idempotent shutdown, and panic/error isolation. archied owns one host and starts/stops it. plugin.Plugin remains metadata-only and architecture tests pass. task check and lint are green apart from explicitly identified concurrent baseline failures; fresh adversarial review has no surviving findings.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:50:49Z","updated_at":"2026-08-08T15:33:40Z","closed_at":"2026-08-08T15:33:41Z","external_ref":"https://github.com/samcharles93/archie-core/issues/327","source_system":"github:https://github.com/samcharles93/archie-core/issues/327:327","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497825-305-cc16d654","title":"Implement multi-identity daemon core (archie + winter as one process)","description":"Replace single Config.BotUser with the confirmed multi-identity config shape. Daemon runs multiple bot identities concurrently (each with its own forge token, repo list, model/provider config), dispatching through the existing shared NATS/container pipeline. Validate by migrating the two real carina processes (archie: bot_user=archie, repos=[archie-core,tau], deepseek models; winter: bot_user=winter, repos=[tau], local llama.cpp models) onto one daemon. Per docs/prds/multi-agent-collaboration.md phase B.\n\n### Acceptance Criteria\n\nOne archied process on carina replaces the current two (archie config.toml + winter.toml), producing the same dispatch behavior (issue polling, task claiming, PR flow) for both identities as the two separate processes did. No regression in existing single-identity config compatibility (old single-BotUser configs still work or have a documented migration path).","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:50:43Z","updated_at":"2026-08-08T14:50:46Z","closed_at":"2026-08-08T14:50:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/326","source_system":"github:https://github.com/samcharles93/archie-core/issues/326:326","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497798-304-203ce9ef","title":"MVP: migrate Hermes profiles, memory, skills, and session state","description":"The copied live Hermes instance contains root plus agile-lead, dev, and local-agent profiles with distinct models, gateways, memories, SOUL prompts, skills, sessions, and cron state. archie-core currently has forge identities but no profile-scoped gateway/tool/memory/workspace composition and no importer. Define the mapping into archie-core identities/profiles and build a one-time idempotent migration plus cutover rehearsal.\n\n### Acceptance Criteria\n\nDocument and implement the mapping for all copied profiles -- MAPPING DOCUMENTED (docs/prds/hermes-migration-dry-run.md), NOT YET IMPLEMENTED (blocked on abg.36). Import SOUL/USER/MEMORY/skills/session/cron without secrets -- NOT STARTED (design-blocked on abg.36, see report). Produce a dry-run report -- DONE. Rehearse dual-run/shadow validation and rollback-safe cutover checklist -- NOT STARTED.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:50:40Z","updated_at":"2026-08-08T15:34:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/325","source_system":"github:https://github.com/samcharles93/archie-core/issues/325:325","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497773-303-d6467862","title":"MVP: make chat-originated tasks native and controllable","description":"The current /spawn path fabricates an issue number and enqueues it as if it were forge-backed, always against the first repo. The task schema has no source or identity, the workflow later performs forge labels/comments against a nonexistent issue, and /approve and /cancel are absent. Add a native chat task source routed through the same daemon-owned workflow and review gates without pretending a forge issue exists.\n\n### Acceptance Criteria\n\nChat can select identity, repo, and workflow; /spawn creates a durable native task with a real task ID; daemon processing avoids forge-only operations when no forge artifact exists; /approve and /cancel enforce authorization and valid state transitions; end-to-end tests cover spawn through completion, approval, cancellation, restart recovery, and invalid cross-identity control.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:50:34Z","updated_at":"2026-08-08T15:33:42Z","closed_at":"2026-08-08T15:33:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/324","source_system":"github:https://github.com/samcharles93/archie-core/issues/324:324","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497749-302-d1cb75e0","title":"MVP: complete multi-identity composition and task ownership routing","description":"The multi-identity types are not instantiated by cmd/archied, and the identity loop still polls with root Config fields then drains into root Forge, Trees, Config, and repo lookup. Tasks do not persist source identity. Complete the end-to-end ownership path so overlapping repo assignments for archie and winter cannot be claimed or acted on by the wrong identity.\n\n### Acceptance Criteria\n\nAll items now DONE and build-verified: composition root builds every identity with its own forge/worktree -- DONE + VERIFIED (go build ./cmd/... passes). Task records carry identity -- DONE. NATS messages carry identity -- DONE. Polling/claiming/processing/labels/comments/pushes/PRs use owning identity -- DONE for in-process execution (documented gap for container mode, tracked separately, does not block this bead). Production-shaped two-identity-same-repo isolation test -- DONE (4 tests, race-clean).","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:50:29Z","updated_at":"2026-08-08T15:33:44Z","closed_at":"2026-08-08T15:33:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/323","source_system":"github:https://github.com/samcharles93/archie-core/issues/323:323","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497724-301-9a5dee08","title":"MVP: run gateway conversations through the full agent/tool loop","description":"The Telegram responder currently calls runtime.Chat with MaxSteps=1 and no tool set. Email and webhook routers receive a nil responder. The central tool registry is empty/unconsumed; MCP transports are started without initialize/list/register/stop; the memory manager is not part of chat; skills and guardrails are not available to gateway turns. Replace the one-shot responder with one shared session-scoped conversational agent path used by Telegram, email, and webhook, preserving archie-core's daemon-owned safety boundaries.\n\n### Acceptance Criteria\n\nA gateway turn can use approved built-in tools, configured MCP tools, memory, skills, compression, and guardrails through a multi-step agent loop; Telegram, email, and webhook share this path; tool transports are initialized, discovered, registered, and shut down; an end-to-end test proves an inbound message causes a tool call and a delivered reply.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:50:26Z","updated_at":"2026-08-08T15:33:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/322","source_system":"github:https://github.com/samcharles93/archie-core/issues/322:322","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497696-300-d4138aac","title":"Audit Hermes-to-archie-core MVP takeover gaps","description":"Compare the copied live Hermes state in .hermes-carina with archie-core's current runtime and backlog. Determine the minimum remaining work for archie-core to replace Hermes on carina, explicitly excluding the in-flight secret engine and provider/config work.\n\n### Acceptance Criteria\n\nDocument current capability parity, concrete blockers, minimum migration sequence, and non-MVP deferrals with file and issue evidence; do not modify implementation code.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:50:21Z","updated_at":"2026-08-08T15:34:41Z","closed_at":"2026-08-08T15:34:42Z","external_ref":"https://github.com/samcharles93/archie-core/issues/321","source_system":"github:https://github.com/samcharles93/archie-core/issues/321:321","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497667-299-031fd93f","title":"Agent personalities/personas system","description":"Hermes has 14 personalities (catgirl, concise, creative, helpful, hype, kawaii, noir, philosopher, pirate, shakespeare, surfer, teacher, technical, uwu). Sam uses these. Personalities are system prompt modifiers that change the agent's communication style.\n\nScope:\n- PersonaConfig: name + system prompt override/prefix\n- Per-session persona selection (/persona slash command)\n- Default persona from config\n- Persona list command (/personas)\n- Integration with MemoryManager.BuildSystemPrompt() (persona prompt inserted before memory context)","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:50:15Z","updated_at":"2026-08-08T14:50:18Z","closed_at":"2026-08-08T14:50:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/320","source_system":"github:https://github.com/samcharles93/archie-core/issues/320:320","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497638-298-6d3204b3","title":"Context compression for long-running sessions","description":"Hermes config has compression enabled at 0.5 threshold, protecting first 3 and last 20 messages. Sam confirmed this is a must-have for long-running sessions. Without compression, context windows fill up and sessions degrade.\n\nScope:\n- Compression threshold (fraction of context window used)\n- Target compression ratio\n- Protect first N / last N messages from compression\n- Integrate with MemoryManager (pre-compress hook already defined: OnPreCompressProvider)\n- Use the existing StreamingContextScrubber for fence-stripping during compression","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:50:10Z","updated_at":"2026-08-08T14:50:13Z","closed_at":"2026-08-08T14:50:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/319","source_system":"github:https://github.com/samcharles93/archie-core/issues/319:319","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497610-297-648ba1c8","title":"Wire guardrails, memory, and MCP servers into daemon agent loop","description":"Tools P1 (guardrails, classification, budget), memory system (Manager, builtin provider, scrubber), and MCP transport are all built and tested but NOT called from cmd/archied/main.go. The daemon creates an agentexec.Runner but never passes GuardrailEngine, MemoryManager, or MCP client instances. This is THE blocker to using archie-core in place of Hermes.\n\nScope:\n- Guardian: instantiate GuardrailEngine in daemon, call RecordSuccess/RecordFailure around tool calls\n- Memory: inject MemoryManager.BuildSystemPrompt() into agent system prompt, wire HandleToolCall for memory tool routing\n- MCP: instantiate configured MCP servers from config, register their tools, wire into agent tool dispatch\n- Classification: use ToolClassification to gate parallel vs serial execution in the tool dispatcher","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:50:05Z","updated_at":"2026-08-08T14:50:07Z","closed_at":"2026-08-08T14:50:08Z","external_ref":"https://github.com/samcharles93/archie-core/issues/318","source_system":"github:https://github.com/samcharles93/archie-core/issues/318:318","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497583-296-b5349e37","title":"Verify: Integrate NellDB as persistent memory and configuration backend","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:50:00Z","updated_at":"2026-08-08T14:50:02Z","closed_at":"2026-08-08T14:50:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/317","source_system":"github:https://github.com/samcharles93/archie-core/issues/317:317","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497556-295-9095895c","title":"Integrate NellDB as persistent memory and configuration backend","description":"Replace SQLite+FTS5+file-based storage with NellDB, Sam's existing distributed document database. NellDB provides:\\n\\n- **nell.Store interface**: Put, Get, Delete, List, ListAll, Query, GetChangesSince, SearchSimilar (vector search)\\n- **sdk.DocDB**: Document database with MVCC revisions\\n- **logstore**: Durable Zstd-compressed append-only log\\n- **sdk.Replicator**: Multi-primary HTTP replication with HLC knowledge vectors\\n- **Vector search**: HNSW + PCA + PQ for semantic memory\\n- **HTTP server**: Standalone binary on port 9342\\n\\nPlan:\\n\\n1. Add NellDB as a dependency (go get github.com/samcharles93/NellDB)\\n2. Create internal/nell/ adapter package wrapping nell.Store for archie-core's data models\\n3. Collections: sessions, messages, memory, config, tasks\\n4. Replace internal/store (SQLite) with NellDB backend\\n5. Replace file-based MEMORY.md with nell collections + vector search\\n6. Wire into cmd/archied/main.go as the storage backend\\n\\nThis gives archie-core multi-primary replication for free — two archied instances on different hosts can sync state without a central database.\\n\\nRef: /work/apps/nell-engine/ (store.go, types.go, sdk/docdb.go, server/)\n\n### Acceptance Criteria\n\narchied starts with a NellDB backend instead of SQLite. Sessions and messages persist across restarts. Vector search returns semantically similar messages. Two archied instances can replicate state via nell sync.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:49:54Z","updated_at":"2026-08-08T14:49:57Z","closed_at":"2026-08-08T14:49:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/316","source_system":"github:https://github.com/samcharles93/archie-core/issues/316:316","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497528-294-5c3de4cb","title":"Design pass: multi-identity daemon config shape","description":"Config.BotUser (internal/config) is a single global field -- the root blocker for running multiple bot identities (archie, winter) in one daemon instead of N processes. docs/prds/multi-agent-collaboration.md sec.4 sketches a [[identities]] TOML shape but flags the open question unresolved: does each identity get its own poll loop/goroutine feeding shared NATS/container dispatch, or does one loop iterate all identities? Needs a short design doc answering this before Phase B implementation starts, since it affects rate-limit isolation between identities.\n\n### Acceptance Criteria\n\nA design note (added to multi-agent-collaboration.md or a new doc) confirms the identity config shape and the poll-loop-per-identity vs single-loop decision, with reasoning tied to failure isolation (one identity's forge outage must not starve another's dispatch).","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:49Z","updated_at":"2026-08-08T14:49:52Z","closed_at":"2026-08-08T14:49:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/315","source_system":"github:https://github.com/samcharles93/archie-core/issues/315:315","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497505-293-bb1da2e9","title":"Verify: Scale-to-zero: idle detection and dormant quiesce","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:44Z","updated_at":"2026-08-08T14:49:47Z","closed_at":"2026-08-08T14:49:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/314","source_system":"github:https://github.com/samcharles93/archie-core/issues/314:314","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497472-292-8bddcc8f","title":"Scale-to-zero: idle detection and dormant quiesce","description":"Scale-to-zero idle detection:\\n\\n1. **Idle predicate**: running_agent_count == 0 AND seconds_since_last_inbound \u003e idle_timeout AND no live background work.\\n2. **Dormant transition**: Signal relay transport to close socket (supervisor preserved).\\n3. **Wake trigger**: Inbound message on wake URL resumes gateway.\\n4. **Structural precondition**: Only arms when messaging is relay-only or absent AND a wake URL is registered.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 6 (scale_to_zero.py)\n\n### Acceptance Criteria\n\nWhen no messages arrive for the configured idle timeout (with no active agents), the gateway transitions to dormant. An inbound message wakes it.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:49:41Z","updated_at":"2026-08-08T14:49:41Z","external_ref":"https://github.com/samcharles93/archie-core/issues/313","source_system":"github:https://github.com/samcharles93/archie-core/issues/313:313","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497444-291-019ea8e3","title":"Verify: Context compression: aux model summarization pipeline","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:36Z","updated_at":"2026-08-08T14:49:38Z","closed_at":"2026-08-08T14:49:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/312","source_system":"github:https://github.com/samcharles93/archie-core/issues/312:312","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497421-290-7ec1407d","title":"Context compression: aux model summarization pipeline","description":"Conversation compression pipeline:\\n\\n1. **Auxiliary model client**: Dedicated cheap/fast model for summarization. Probes context window feasibility at startup.\\n2. **Compression templates**: Structured summaries with Resolved/Pending question tracking. Head and tail context protection.\\n3. **Iterative summary merging**: Multiple compression rounds, tool output pruning before LLM summarization.\\n4. **Session splitting**: Rotate session_id on compression, link child → parent.\\n5. **Image size recovery**: Re-encode oversized base64 images at smaller size.\\n6. **Pluggable context engine**: ABC with should_compress/compress/on_session_end lifecycle for third-party replacements.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 1.2 (conversation_compression.py, context_compressor.py, context_engine.py)\n\n### Acceptance Criteria\n\nWhen a conversation approaches context limit, the auxiliary model summarizes middle turns. Session rotates to a child session. The agent continues without losing context.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:49:33Z","updated_at":"2026-08-08T14:49:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/311","source_system":"github:https://github.com/samcharles93/archie-core/issues/311:311","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497395-289-8308ccd7","title":"Verify: WebhookAdapter: declarative filters","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:28Z","updated_at":"2026-08-08T14:49:30Z","closed_at":"2026-08-08T14:49:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/310","source_system":"github:https://github.com/samcharles93/archie-core/issues/310:310","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497373-288-22cb0426","title":"Verify: WebhookAdapter: HTTP server with per-route HMAC validation","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:23Z","updated_at":"2026-08-08T14:49:25Z","closed_at":"2026-08-08T14:49:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/309","source_system":"github:https://github.com/samcharles93/archie-core/issues/309:309","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497353-287-96a3e24c","title":"MS Graph webhook adapter: validationToken handshake","description":"Implement MS Graph webhook adapter with validationToken handshake for subscription verification, clientState verification, and CIDR IP allowlisting.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:20Z","updated_at":"2026-08-08T14:49:20Z","external_ref":"https://github.com/samcharles93/archie-core/issues/308","source_system":"github:https://github.com/samcharles93/archie-core/issues/308:308","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497328-286-9c985f28","title":"WebhookAdapter: idempotency cache","description":"Implement TTL-based idempotency cache to deduplicate retried webhook deliveries. Cache based on webhook event ID and route.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:17Z","updated_at":"2026-08-08T14:49:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/307","source_system":"github:https://github.com/samcharles93/archie-core/issues/307:307","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497299-285-f4780816","title":"WebhookAdapter: deliver_only mode","description":"Implement deliver_only mode that skips agent processing and directly renders the prompt template as a deliverable (e.g. plain text, HTML, JSON response).","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:14Z","updated_at":"2026-08-08T14:49:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/306","source_system":"github:https://github.com/samcharles93/archie-core/issues/306:306","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497271-284-573ca138","title":"WebhookAdapter: prompt templates with dot-notation","description":"Implement prompt template system with dot-notation variable interpolation ({pull_request.title}, {__raw__}) for building dynamic prompts from webhook payloads.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:10Z","updated_at":"2026-08-08T14:49:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/305","source_system":"github:https://github.com/samcharles93/archie-core/issues/305:305","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497242-283-03662140","title":"WebhookAdapter: script transforms","description":"Support external script transforms per route. Allow bash/python scripts to transform incoming webhook payloads before processing.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:07Z","updated_at":"2026-08-08T14:49:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/304","source_system":"github:https://github.com/samcharles93/archie-core/issues/304:304","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497221-282-f0a2975e","title":"WebhookAdapter: declarative filters","description":"Implement declarative webhook filters with operators: all/any/not, field resolution, equals/contains/regex comparisons, and in_file lookups.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:04Z","updated_at":"2026-08-08T14:49:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/303","source_system":"github:https://github.com/samcharles93/archie-core/issues/303:303","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497194-281-b64beb0c","title":"Verify: MS Graph webhook adapter: validationToken handshake","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:59Z","updated_at":"2026-08-08T14:49:02Z","closed_at":"2026-08-08T14:49:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/302","source_system":"github:https://github.com/samcharles93/archie-core/issues/302:302","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497167-280-a0e27bae","title":"Verify: WebhookAdapter: idempotency cache","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:54Z","updated_at":"2026-08-08T14:48:56Z","closed_at":"2026-08-08T14:48:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/301","source_system":"github:https://github.com/samcharles93/archie-core/issues/301:301","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497138-279-e3ca0f19","title":"Verify: WebhookAdapter: deliver_only mode","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:48Z","updated_at":"2026-08-08T14:48:51Z","closed_at":"2026-08-08T14:48:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/300","source_system":"github:https://github.com/samcharles93/archie-core/issues/300:300","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497115-278-6a6e0b24","title":"Verify: WebhookAdapter: prompt templates with dot-notation","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:43Z","updated_at":"2026-08-08T14:48:46Z","closed_at":"2026-08-08T14:48:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/299","source_system":"github:https://github.com/samcharles93/archie-core/issues/299:299","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497095-277-8f046e5a","title":"Verify: WebhookAdapter: script transforms","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:38Z","updated_at":"2026-08-08T14:48:41Z","closed_at":"2026-08-08T14:48:42Z","external_ref":"https://github.com/samcharles93/archie-core/issues/298","source_system":"github:https://github.com/samcharles93/archie-core/issues/298:298","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497066-276-35fe7db3","title":"WebhookAdapter: HTTP server with per-route HMAC validation","description":"Implement WebhookAdapter as an HTTP server supporting per-route HMAC validation: GitHub X-Hub-Signature-256, GitLab X-Gitlab-Token, and a generic V2 timestamp-bound HMAC scheme.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:35Z","updated_at":"2026-08-08T14:48:35Z","external_ref":"https://github.com/samcharles93/archie-core/issues/297","source_system":"github:https://github.com/samcharles93/archie-core/issues/297:297","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497036-275-8838629e","title":"Webhook platform: generic inbound adapter with HMAC + filters + templates","description":"Generic webhook platform adapter:\\n\\n1. **HTTP server**: Receives POSTs from external services (GitHub, GitLab, Stripe, etc.). Per-route configuration.\\n2. **HMAC validation**: GitHub (X-Hub-Signature-256), GitLab (X-Gitlab-Token), Svix/AgentMail, generic V2 (timestamp-bound replay protection), legacy V1.\\n3. **Declarative filters**: all/any/not, field resolution (dot-notation), equals/contains/regex, in_file.\\n4. **Script transforms**: External bash/python scripts per route that transform or filter payloads.\\n5. **Prompt templates**: Dot-notation template rendering from webhook payloads ({pull_request.title}).\\n6. **deliver_only mode**: Skip agent, render prompt as deliverable message (push notifications at zero LLM cost).\\n7. **Idempotency cache**: TTL-based dedup of webhook retries.\\n\\nRef: docs/prds/hermes-gap-analysis.md (webhook.py, webhook_filters.py, msgraph_webhook.py)\n\n### Acceptance Criteria\n\nA GitHub webhook lands on /webhooks/github, passes HMAC validation, renders a prompt from the PR payload, and the agent responds. Duplicate deliveries are deduped.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:48:32Z","updated_at":"2026-08-08T14:48:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/296","source_system":"github:https://github.com/samcharles93/archie-core/issues/296:296","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637497009-274-3b7c3bb9","title":"Verify: API server: OpenAI-compatible REST endpoint for sessions and runs","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:27Z","updated_at":"2026-08-08T14:48:29Z","closed_at":"2026-08-08T14:48:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/295","source_system":"github:https://github.com/samcharles93/archie-core/issues/295:295","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496982-273-2078b865","title":"API server: OpenAI-compatible REST endpoint for sessions and runs","description":"OpenAI-compatible REST API for external tool integration:\\n\\n1. **Chat Completions**: POST /v1/chat/completions — stateless, with X-Hermes-Session-Id for continuity.\\n2. **Responses API**: POST /v1/responses — stateful via previous_response_id.\\n3. **Sessions**: CRUD + fork for session management.\\n4. **Runs**: POST /v1/runs (returns run_id immediately), GET /v1/runs/{id} (status), GET /v1/runs/{id}/events (SSE stream), POST /v1/runs/{id}/approval and /stop (resolve or interrupt).\\n5. **Models**: GET /v1/models — list configured models.\\n6. **Health**: GET /health (simple), GET /health/detailed (authenticated readiness).\\n\\nThis enables Open WebUI, LobeChat, and other OpenAI-compatible frontends to use archie-core as a backend.\\n\\nRef: docs/prds/hermes-gap-analysis.md (api_server.py)\n\n### Acceptance Criteria\n\ncurl -X POST /v1/chat/completions with a model and messages returns a streaming response. Sessions persist across requests via session ID. Runs can be stopped mid-execution.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:48:24Z","updated_at":"2026-08-08T14:48:24Z","external_ref":"https://github.com/samcharles93/archie-core/issues/294","source_system":"github:https://github.com/samcharles93/archie-core/issues/294:294","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496953-272-2c7c1c68","title":"Verify: Shutdown watchdog: out-of-loop os.Exit backstop","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:19Z","updated_at":"2026-08-08T14:48:21Z","closed_at":"2026-08-08T14:48:22Z","external_ref":"https://github.com/samcharles93/archie-core/issues/293","source_system":"github:https://github.com/samcharles93/archie-core/issues/293:293","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496931-271-cb92cf19","title":"Verify: Drain control: marker file and instantiation epoch","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:14Z","updated_at":"2026-08-08T14:48:16Z","closed_at":"2026-08-08T14:48:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/292","source_system":"github:https://github.com/samcharles93/archie-core/issues/292:292","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496911-270-7c404435","title":"Verify: Health endpoint: GET /health and GET /health/detailed","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:08Z","updated_at":"2026-08-08T14:48:11Z","closed_at":"2026-08-08T14:48:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/291","source_system":"github:https://github.com/samcharles93/archie-core/issues/291:291","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496890-269-ff65f3be","title":"Verify: Readiness probes: multi-check subsystem probe","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:03Z","updated_at":"2026-08-08T14:48:06Z","closed_at":"2026-08-08T14:48:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/290","source_system":"github:https://github.com/samcharles93/archie-core/issues/290:290","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496863-268-ac378cff","title":"systemd notify: sd_notify integration with loop-progress sampling","description":"Integrate sd_notify (systemd service notification) to signal readiness and watchdog status. Sample loop progress to periodically send WATCHDOG=1 notifications.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:00Z","updated_at":"2026-08-08T14:48:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/289","source_system":"github:https://github.com/samcharles93/archie-core/issues/289:289","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496842-267-8b2984f9","title":"Shutdown watchdog: out-of-loop os.Exit backstop","description":"Implement a shutdown watchdog with out-of-loop os.Exit as a backstop. After drain timeout, wait 60s grace period then force-exit to prevent hung processes.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:57Z","updated_at":"2026-08-08T14:47:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/288","source_system":"github:https://github.com/samcharles93/archie-core/issues/288:288","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496817-266-06b64a72","title":"Drain control: marker file and instantiation epoch","description":"Implement drain control using a .drain_request.json marker file. Validate against instantiation epoch to distinguish stale drain requests from current ones.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:54Z","updated_at":"2026-08-08T14:47:54Z","external_ref":"https://github.com/samcharles93/archie-core/issues/287","source_system":"github:https://github.com/samcharles93/archie-core/issues/287:287","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496789-265-b052b772","title":"Health endpoint: GET /health and GET /health/detailed","description":"Implement GET /health (simple liveness check) and GET /health/detailed (authenticated, returns per-subsystem readiness status with individual probe results).","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:51Z","updated_at":"2026-08-08T14:47:51Z","external_ref":"https://github.com/samcharles93/archie-core/issues/286","source_system":"github:https://github.com/samcharles93/archie-core/issues/286:286","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496762-264-b9b31724","title":"Verify: systemd notify: sd_notify integration with loop-progress sampling","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:46Z","updated_at":"2026-08-08T14:47:49Z","closed_at":"2026-08-08T14:47:50Z","external_ref":"https://github.com/samcharles93/archie-core/issues/285","source_system":"github:https://github.com/samcharles93/archie-core/issues/285:285","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496732-263-54b6686b","title":"Readiness probes: multi-check subsystem probe","description":"Implement readiness probes for: state_db (read-only probe), config (parse check), disk usage (\u003c90%), model (configured), and gateway state (connected adapters).","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:43Z","updated_at":"2026-08-08T14:47:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/284","source_system":"github:https://github.com/samcharles93/archie-core/issues/284:284","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496703-262-1e49aef1","title":"Operations: readiness probes + drain control + systemd notify","description":"Production operations infrastructure:\\n\\n1. **Readiness probes**: Multi-check system — state_db (read-only probe), config (parse check), disk (\u003c90%), model (configured), gateway (running/draining + connected count). Return overall ok or degraded.\\n2. **Drain control**: Marker file (~/.archie/.drain_request.json) for external drain triggers. Instantiation epoch (boot_id + PID 1 start time) to distinguish restart types.\\n3. **Shutdown watchdog**: Out-of-loop os.Exit backstop if shutdown exceeds leash (drain timeout + 60s grace).\\n4. **systemd notify**: sd_notify integration — watchdog with loop-progress sampling, ready status on startup.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 9-10 (readiness.py, drain_control.py, shutdown_watchdog.py, systemd_notify.py)\n\n### Acceptance Criteria\n\nGET /health returns JSON with per-subsystem status. systemd watchdog fires if the event loop stalls. Drain requests initiate graceful shutdown.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:47:39Z","updated_at":"2026-08-08T14:47:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/283","source_system":"github:https://github.com/samcharles93/archie-core/issues/283:283","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496672-261-89720990","title":"Verify: Blueprint catalog parameterized templates typed slots","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:34Z","updated_at":"2026-08-08T14:47:37Z","closed_at":"2026-08-08T14:47:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/282","source_system":"github:https://github.com/samcharles93/archie-core/issues/282:282","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496637-260-c68601e9","title":"Verify: Ticker engine configurable interval parallel sequential pools","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:29Z","updated_at":"2026-08-08T14:47:32Z","closed_at":"2026-08-08T14:47:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/281","source_system":"github:https://github.com/samcharles93/archie-core/issues/281:281","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496609-259-3e1f6fc3","title":"Verify: Job store JSON file cross-process file locking","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:24Z","updated_at":"2026-08-08T14:47:26Z","closed_at":"2026-08-08T14:47:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/280","source_system":"github:https://github.com/samcharles93/archie-core/issues/280:280","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496579-258-7af1f026","title":"Job execution: claim, heartbeat, success/failure tracking","description":"Implement job execution lifecycle: claim jobs to prevent duplicate execution, send heartbeats during execution, and track success/failure outcomes via the delivery router.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:21Z","updated_at":"2026-08-08T14:47:21Z","external_ref":"https://github.com/samcharles93/archie-core/issues/279","source_system":"github:https://github.com/samcharles93/archie-core/issues/279:279","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496550-257-aa2c1a68","title":"CronScheduler provider interface","description":"Define the CronScheduler provider interface with methods: name(), start(stop_event, adapters, loop, interval). This is the plugin contract for scheduler implementations.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:18Z","updated_at":"2026-08-08T14:47:18Z","external_ref":"https://github.com/samcharles93/archie-core/issues/278","source_system":"github:https://github.com/samcharles93/archie-core/issues/278:278","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496521-256-e0857b1f","title":"Lifecycle guard: reject dangerous commands in job specs","description":"Implement lifecycle guard to reject dangerous commands in job cron specs, including gateway restart, systemctl, launchctl, pkill and similar operations.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:15Z","updated_at":"2026-08-08T14:47:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/277","source_system":"github:https://github.com/samcharles93/archie-core/issues/277:277","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496490-255-43c9106f","title":"Blueprint catalog: parameterized templates with typed slots","description":"Implement a catalog of parameterized job templates with typed slots: time, enum, text, weekdays. Include form schema for UI generation.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:12Z","updated_at":"2026-08-08T14:47:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/276","source_system":"github:https://github.com/samcharles93/archie-core/issues/276:276","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496459-254-ed0462dd","title":"Ticker engine: configurable interval, parallel/sequential pools","description":"Implement ticker engine with configurable check interval and support for both parallel and sequential thread pools for job execution.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:09Z","updated_at":"2026-08-08T14:47:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/275","source_system":"github:https://github.com/samcharles93/archie-core/issues/275:275","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496431-253-92ea5490","title":"Verify: Job execution claim heartbeat success failure tracking","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:03Z","updated_at":"2026-08-08T14:47:06Z","closed_at":"2026-08-08T14:47:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/274","source_system":"github:https://github.com/samcharles93/archie-core/issues/274:274","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496398-252-f770672f","title":"Verify: CronScheduler provider interface","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:58Z","updated_at":"2026-08-08T14:47:00Z","closed_at":"2026-08-08T14:47:01Z","external_ref":"https://github.com/samcharles93/archie-core/issues/273","source_system":"github:https://github.com/samcharles93/archie-core/issues/273:273","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496373-251-16ef9e90","title":"Verify: Lifecycle guard reject dangerous commands job specs","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:52Z","updated_at":"2026-08-08T14:46:55Z","closed_at":"2026-08-08T14:46:56Z","external_ref":"https://github.com/samcharles93/archie-core/issues/272","source_system":"github:https://github.com/samcharles93/archie-core/issues/272:272","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496345-250-fd367e28","title":"Job store: JSON file with cross-process file locking","description":"Implement per-profile job store using JSON file at ~/.archie/cron/jobs.json with cross-process file locking via fcntl to prevent concurrent access.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:49Z","updated_at":"2026-08-08T14:46:49Z","external_ref":"https://github.com/samcharles93/archie-core/issues/271","source_system":"github:https://github.com/samcharles93/archie-core/issues/271:271","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496320-249-be6d9a20","title":"Cron/scheduling: job store, ticker, blueprints","description":"Scheduled automation system:\\n\\n1. **Job store**: JSON file per profile (~/.archie/cron/jobs.json) with cross-process file locking. CRUD operations.\\n2. **Ticker engine**: Configurable interval, parallel/sequential thread pools, delivery resolution via DeliveryRouter.\\n3. **Blueprints**: Parameterized automation templates with typed slots (time, enum, text, weekdays). Form schema for CLI/gateway consumption.\\n4. **Lifecycle guard**: Rejects cron job specs containing dangerous commands (gateway restart, systemctl, launchctl, pkill).\\n\\nRef: docs/prds/hermes-gap-analysis.md section 1 (cron/)\n\n### Acceptance Criteria\n\nA cron job can be created to send a daily status summary. Jobs persist across restarts. Dangerous commands are rejected at creation time.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:46:46Z","updated_at":"2026-08-08T14:46:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/270","source_system":"github:https://github.com/samcharles93/archie-core/issues/270:270","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496292-248-1048ea68","title":"Verify: Delivery system: router, ledger, dead targets, wake","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:41Z","updated_at":"2026-08-08T14:46:44Z","closed_at":"2026-08-08T14:46:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/269","source_system":"github:https://github.com/samcharles93/archie-core/issues/269:269","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496264-247-25b84f1a","title":"Delivery system: router, ledger, dead targets, wake","description":"Outbound message delivery infrastructure built on NATS JetStream (already provides guaranteed delivery, dead-letter queues, ack/nak, dedup — no need for a separate actor engine like Hollywood).\\n\\n1. **DeliveryTarget**: Parse strings like 'telegram:12345' or 'discord:channel:thread'. Resolve to platform adapter.\\n2. **DeliveryRouter**: Route content to configured targets, handle truncation, silence-narration filtering.\\n3. **DeliveryLedger**: JetStream consumer with max-deliver=3, ack-wait configurable per target. Crash recovery via NATS redelivery (no separate SQLite ledger needed).\\n4. **DeadTargetRegistry**: Persistent JSON tracking of confirmed-dead targets (deleted groups, kicked bots). Self-healing on successful send.\\n5. **Wake delivery**: Use NATS request/reply for async delivery to push-capable adapters.\n\n### Acceptance Criteria\n\nA cron job can schedule a message for delivery. If the target is unreachable, the ledger retries. If the bot is kicked from a group, the target is registered dead and skipped.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:46:38Z","updated_at":"2026-08-08T14:46:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/268","source_system":"github:https://github.com/samcharles93/archie-core/issues/268:268","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496241-246-d405239f","title":"Rate limiting: brute-force lockout with escalating delays","description":"Implement brute-force lockout mechanism with escalating delay intervals on successive failures, integrated with the pairing system.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:33Z","updated_at":"2026-08-08T15:35:28Z","closed_at":"2026-08-08T15:35:29Z","external_ref":"https://github.com/samcharles93/archie-core/issues/267","source_system":"github:https://github.com/samcharles93/archie-core/issues/267:267","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496213-245-3655c4e7","title":"Rate limiting: per-user limiter with configurable window","description":"Implement a per-user rate limiter with configurable time window and max requests. Track usage per user/platform combination.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:28Z","updated_at":"2026-08-08T15:35:26Z","closed_at":"2026-08-08T15:35:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/266","source_system":"github:https://github.com/samcharles93/archie-core/issues/266:266","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496187-244-42f8e12d","title":"SlashAccessPolicy: admin/non-admin command gating","description":"Implement SlashAccessPolicy with allow_admin_from and user_allowed_commands settings to gate slash commands by user role.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:25Z","updated_at":"2026-08-08T14:46:25Z","external_ref":"https://github.com/samcharles93/archie-core/issues/265","source_system":"github:https://github.com/samcharles93/archie-core/issues/265:265","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496164-243-0c2e54a6","title":"Gateway auth mixin: per-platform env var patterns","description":"Support per-platform env var patterns for allowed users, e.g. TELEGRAM_ALLOWED_USERS, DISCORD_ALLOWED_USERS, SLACK_ALLOWED_USERS, etc.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:22Z","updated_at":"2026-08-08T14:46:22Z","external_ref":"https://github.com/samcharles93/archie-core/issues/264","source_system":"github:https://github.com/samcharles93/archie-core/issues/264:264","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496136-242-30ccc9fe","title":"Gateway auth mixin: layered authorization pipeline","description":"Implement GatewayAuthorizationMixin with layered auth: allowlists → role auth → relay delegation → pairing → deny, as a composable middleware for the gateway.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:19Z","updated_at":"2026-08-08T14:46:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/263","source_system":"github:https://github.com/samcharles93/archie-core/issues/263:263","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496114-241-98b956ab","title":"PairingStore: atomic file writes with per-platform files","description":"Implement atomic file writes (write to temp, rename) with chmod 0600. Store per-platform state in pending.json, approved.json, rate_limits.json files.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:14Z","updated_at":"2026-08-08T15:35:30Z","closed_at":"2026-08-08T15:35:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/262","source_system":"github:https://github.com/samcharles93/archie-core/issues/262:262","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496088-240-f0adc281","title":"PairingStore: expiry, quotas, rate limits, lockout","description":"Implement 1-hour code expiry, max 3 pending codes per platform, rate limit of 1 request per 10 minutes per user, and lockout after 5 failed attempts.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:09Z","updated_at":"2026-08-08T15:35:32Z","closed_at":"2026-08-08T15:35:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/261","source_system":"github:https://github.com/samcharles93/archie-core/issues/261:261","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496060-239-b9383a6c","title":"PairingStore: salted SHA-256 hashing with constant-time comparison","description":"Hash pairing codes with salted SHA-256 and compare using crypto/subtle.ConstantTimeCompare (secrets.compare_digest equivalent in Go).\n\n### Acceptance Criteria\n\nSalted SHA-256 hashing with constant-time comparison -- DONE, adversarially reviewed, zero blocking findings.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:04Z","updated_at":"2026-08-08T15:35:36Z","closed_at":"2026-08-08T15:35:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/260","source_system":"github:https://github.com/samcharles93/archie-core/issues/260:260","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496033-238-f07a2243","title":"ratelimit.Limiter: evict stale per-key entries to bound memory","description":"internal/ratelimit's Limiter.hits map never removes entries for (platform, userID) pairs that stop being used -- a user who fires once and never again leaves a permanent (eventually-empty-slice) map entry for the life of the process. Not a bug today since the package isn't wired into any caller yet, but flagged by adversarial review as needing an eviction/TTL story before it's wired into a long-running daemon path handling many distinct/cycling identities (otherwise an eventual memory leak / DoS vector).","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:46:00Z","updated_at":"2026-08-08T14:46:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/259","source_system":"github:https://github.com/samcharles93/archie-core/issues/259:259","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496003-237-5db40fa7","title":"Verify: Rate limiting brute-force lockout escalating delays","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:55Z","updated_at":"2026-08-08T14:45:58Z","closed_at":"2026-08-08T14:45:59Z","external_ref":"https://github.com/samcharles93/archie-core/issues/258","source_system":"github:https://github.com/samcharles93/archie-core/issues/258:258","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495973-236-ccc9b014","title":"Verify: Rate limiting per-user limiter configurable window","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:50Z","updated_at":"2026-08-08T14:45:52Z","closed_at":"2026-08-08T14:45:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/257","source_system":"github:https://github.com/samcharles93/archie-core/issues/257:257","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495952-235-20b3d817","title":"Verify: SlashAccessPolicy admin non-admin command gating","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:45Z","updated_at":"2026-08-08T14:45:47Z","closed_at":"2026-08-08T14:45:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/256","source_system":"github:https://github.com/samcharles93/archie-core/issues/256:256","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495922-234-14e1779d","title":"Verify: Gateway auth mixin per-platform env var patterns","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:40Z","updated_at":"2026-08-08T14:45:42Z","closed_at":"2026-08-08T14:45:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/255","source_system":"github:https://github.com/samcharles93/archie-core/issues/255:255","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495897-233-99c934d9","title":"Verify: Gateway auth mixin layered authorization pipeline","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:35Z","updated_at":"2026-08-08T14:45:37Z","closed_at":"2026-08-08T14:45:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/254","source_system":"github:https://github.com/samcharles93/archie-core/issues/254:254","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495877-232-32e435b6","title":"Verify: PairingStore atomic file writes per-platform files","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:29Z","updated_at":"2026-08-08T14:45:32Z","closed_at":"2026-08-08T14:45:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/253","source_system":"github:https://github.com/samcharles93/archie-core/issues/253:253","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495856-231-4cac2988","title":"Verify: PairingStore expiry quotas rate limits lockout","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:24Z","updated_at":"2026-08-08T14:45:26Z","closed_at":"2026-08-08T14:45:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/252","source_system":"github:https://github.com/samcharles93/archie-core/issues/252:252","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495828-230-ff0c004e","title":"Verify: PairingStore salted SHA-256 hashing constant-time comparison","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:19Z","updated_at":"2026-08-08T14:45:21Z","closed_at":"2026-08-08T14:45:22Z","external_ref":"https://github.com/samcharles93/archie-core/issues/251","source_system":"github:https://github.com/samcharles93/archie-core/issues/251:251","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495798-229-a5b67d87","title":"Verify: PairingStore cryptographic code generation","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:13Z","updated_at":"2026-08-08T14:45:16Z","closed_at":"2026-08-08T14:45:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/250","source_system":"github:https://github.com/samcharles93/archie-core/issues/250:250","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495768-228-95177772","title":"PairingStore: cryptographic code generation","description":"Generate 8-character pairing codes from a 32-char unambiguous alphabet (excluding 0, O, 1, I) using crypto/rand.\n\n### Acceptance Criteria\n\n8-char pairing codes from 32-char unambiguous alphabet via crypto/rand -- DONE, adversarially reviewed, zero findings.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:08Z","updated_at":"2026-08-08T15:35:34Z","closed_at":"2026-08-08T15:35:35Z","external_ref":"https://github.com/samcharles93/archie-core/issues/249","source_system":"github:https://github.com/samcharles93/archie-core/issues/249:249","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495743-227-dad8a377","title":"Security: pairing device auth + per-platform authorization","description":"Authorization infrastructure to match Hermes parity:\\n\\n1. **PairingStore**: Cryptographic code generation (8-char from 32-char unambiguous alphabet, no 0/O/1/I), salted SHA-256 hashing, constant-time comparison, 1-hour expiry, rate limiting (1/10min per user), lockout after 5 failures. File-backed with atomic writes (chmod 0600).\\n\\n2. **Auth mixin**: Layered authorization for gateway messages: per-platform allowlists → role auth → relay delegation → pairing store → deny. Per-platform env var patterns (TELEGRAM_ALLOWED_USERS, DISCORD_ALLOWED_USERS, etc.).\\n\\n3. **Slash command access**: Admin/non-admin command gating. Admin users (allow_admin_from) get all commands. Non-admin get user_allowed_commands. help and whoami always allowed.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 5\n\n### Acceptance Criteria\n\nUnknown users receive a pairing code instead of agent access. Admin users can run all slash commands. Unauthorized users get a configurable response (pair or ignore).","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:45:05Z","updated_at":"2026-08-08T14:45:05Z","external_ref":"https://github.com/samcharles93/archie-core/issues/248","source_system":"github:https://github.com/samcharles93/archie-core/issues/248:248","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495719-226-9547d89c","title":"Verify: Session persistence: SQLite+FTS5 conversation store","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:45:00Z","updated_at":"2026-08-08T14:45:02Z","closed_at":"2026-08-08T14:45:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/247","source_system":"github:https://github.com/samcharles93/archie-core/issues/247:247","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495693-225-bbf3bc3b","title":"Session persistence: SQLite+FTS5 conversation store","description":"Persistent conversation history with full-text search, backed by NellDB (replaces the original SQLite+FTS5 plan since NellDB is Sam's existing distributed store with built-in vector search).\\n\\n1. **Collections**: sessions, messages — namespaced in NellDB.\\n2. **Vector search**: NellDB's SearchSimilar for semantic memory recall (upgrades the original FTS5 text-only search).\\n3. **Replication**: Multi-primary sync via nell.Replicator — two archied instances share conversation state.\\n4. **HLC ordering**: Causal ordering for messages across nodes.\\n5. **Durable backend**: logstore.OpenLog for Zstd-compressed append-only persistence.\\n\\nNellDB replaces both SQLite+FTS5 (conversation store) and file-based MEMORY.md, using a single dependency.\n\n### Acceptance Criteria\n\nConversation history persists across daemon restarts. FTS5 search returns relevant messages. Compression creates child sessions without data loss.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:44:55Z","updated_at":"2026-08-08T14:44:57Z","closed_at":"2026-08-08T14:44:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/246","source_system":"github:https://github.com/samcharles93/archie-core/issues/246:246","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495666-224-5a91253f","title":"Verify: CLI: command registry framework with plugin-contributed commands","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:49Z","updated_at":"2026-08-08T14:44:52Z","closed_at":"2026-08-08T14:44:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/245","source_system":"github:https://github.com/samcharles93/archie-core/issues/245:245","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495642-223-81391a5c","title":"CLI: command registry framework with plugin-contributed commands","description":"Interactive CLI framework to match Hermes parity. Not a dashboard — just a command-line interface for operational control.\\n\\n1. **CommandDef registry**: Name, description, category, handler, aliases. Commands register themselves at init time.\\n2. **Subcommands**: Plugin-contributed commands via a RegisterCommand hook.\\n3. **Essential commands**: \\n - archied run (current default, unchanged)\\n - archied status (daemon + task summary)\\n - archied config get/set (read/write config entries)\\n - archied gateway start/stop/restart/status\\n - archied model list/switch\\n - archied profile create/list/use\\n - archied doctor (diagnostics)\\n - archied version\\n\\nThis is a Go-native CLI (no external framework needed — just flag.FlagSet and consistent patterns). The gateway already works; this adds the CLI surface for managing it.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 6\n\n### Acceptance Criteria\n\narchied status shows daemon health + task counts. archied config get bot_user works. archied gateway status shows connected platforms. Plugin-registered commands appear in help output.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:44:46Z","updated_at":"2026-08-08T14:44:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/244","source_system":"github:https://github.com/samcharles93/archie-core/issues/244:244","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495615-222-685bcd3a","title":"Wire Layer 2 core plugin loader into archied startup","description":"internal/plugin/plugin.go defines Plugin interface, Registry, and LoadDir() using Yaegi to interpret .go files from a directory, but nothing in cmd/archied/main.go calls it. Wire ~/.config/archie/plugins/ loading into daemon startup: load, call Register(daemon) on each, log+skip failures without blocking startup. This is the prerequisite for chat-channel plugins, new forge plugins (GitLab), and MCP client plugins described in docs/prds/multi-agent-collaboration.md phase A.\n\n### Design\n\nReuse internal/plugin/plugin.go as-is per the v2 PRD reconciliation note (sec.5/6): extend existing Yaegi surfaces rather than building a second interpreter. Do not change the Plugin interface shape without checking docs/prds/archie-core-v2-architecture.md sec.5 first.\n\n### Acceptance Criteria\n\narchied loads .go plugin files from ~/.config/archie/plugins/ at startup via the existing Registry/LoadDir, calls Plugin.Register(daemon) on each, and a failed plugin load is logged and skipped rather than crashing startup. Existing daemon startup tests remain green.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:41Z","updated_at":"2026-08-08T14:44:44Z","closed_at":"2026-08-08T14:44:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/243","source_system":"github:https://github.com/samcharles93/archie-core/issues/243:243","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495595-221-1be8cf34","title":"Verify: Feature-based config: split monolithic config.toml into modular files","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:36Z","updated_at":"2026-08-08T14:44:39Z","closed_at":"2026-08-08T14:44:40Z","external_ref":"https://github.com/samcharles93/archie-core/issues/242","source_system":"github:https://github.com/samcharles93/archie-core/issues/242:242","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495565-220-164b9018","title":"Feature-based config: split monolithic config.toml into modular files","description":"Sam's explicit directive: move to feature-based YAML config files in conf.d/ (Linux convention) instead of one monolithic config.toml.\\n\\n## Design\\n\\n- ~/.config/archie/config.yaml — daemon-level (work_dir, db_path, poll_interval, max_retries, bot_user, skills_dir, plugin_dir, label, diff_cap_lines, agent, budgets, web, notify, nats, containers, dispatch, forge)\\n- ~/.config/archie/conf.d/gateway.yaml — chat channels, platform configs\\n- ~/.config/archie/conf.d/tools.yaml — MCP servers, tool policy\\n- ~/.config/archie/conf.d/memory.yaml — memory provider config\\n- ~/.config/archie/conf.d/models.yaml — LLM providers and model role mappings\\n- ~/.config/archie/conf.d/identities.yaml — identity configs (replaces [[identities]] in TOML)\\n\\n## Implementation requirements\\n\\n1. New function: LoadDir(baseDir, overlayDir string) (Config, error)\\n2. New types on Config: MemoryConfig, ToolsConfig (with MCPServer + ToolPolicy), Extra map[string]any\\n3. Feature files as top-level YAML keys (memory.yaml has provider, provider_config, session_ttl; tools.yaml has mcp_servers, tool_policy; models.yaml has models, providers, etc.)\\n4. Legacy support: if config.yaml absent, fall back to config.toml via existing Load function\\n5. Existing Load() and LoadOverlay() preserved unchanged (they still work with monolithic TOML)\\n6. Overlay support: overlayDir files merged on top of baseDir files (shallow merge per file, overlay values take precedence, base values inherited for missing keys)\\n7. Validation: unknown feature files error (prevent typos like config.gaeway.yaml), duplicate feature files error (same name in root and conf.d/), malformed YAML errors\\n8. Missing feature files mean feature disabled (zero values, no error)\\n9. YAML parser: gopkg.in/yaml.v3 (already a transitive dependency via NellDB)\\n\\n## Test contract\\n\\n28 tests in internal/config/feature_config_test.go define the COMPLETE spec. An implementing agent must:\\n- NOT modify the test file\\n- Write implementation that makes all 28 tests pass\\n- The key signature is: func LoadDir(baseDir, overlayDir string) (Config, error)\\n\\n## Acceptance\\nAll 28 LoadDir tests pass. Existing Load/LoadOverlay tests pass. go build ./... clean. No config.toml parsing capability is lost.\n\n### Acceptance Criteria\n\nA new feature (e.g. MCP) can be configured by adding one new TOML file. No changes to existing config parsing code are needed. Legacy monolithic config.toml still works.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:44:31Z","updated_at":"2026-08-08T14:44:34Z","closed_at":"2026-08-08T14:44:35Z","external_ref":"https://github.com/samcharles93/archie-core/issues/241","source_system":"github:https://github.com/samcharles93/archie-core/issues/241:241","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495531-219-48ade5c2","title":"MemoryManager notify_memory_tool_write","description":"Implement notify_memory_tool_write() in MemoryManager that mirrors built-in memory tool writes to external providers. When the agent uses the built-in memory tool (add/replace/remove), external providers receive a notification so they can stay in sync.\n\n### Acceptance Criteria\n\nAfter any successful built-in memory tool write, MemoryManager calls external provider's on_memory_write(content) hook\nThe notification is asynchronous and goes through the background sync pipeline\nThe notification includes the full content of what was written and the action type (add/replace/remove)\nIf no external provider is active, the call is a no-op\nExternal provider can choose to ignore the notification if it doesn't implement the hook","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:26Z","updated_at":"2026-08-08T15:35:00Z","closed_at":"2026-08-08T15:35:01Z","external_ref":"https://github.com/samcharles93/archie-core/issues/240","source_system":"github:https://github.com/samcharles93/archie-core/issues/240:240","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495499-218-2db0c621","title":"MemoryManager prefetch with timeout","description":"Implement prefetch in MemoryManager with an 8-second default timeout. If a provider's prefetch is still running from the previous turn, skip it rather than queue another. This prevents memory lookups from blocking the agent loop.\n\n### Acceptance Criteria\n\nprefetch(ctx, query) accepts a context with configurable timeout (default 8s)\nIf a provider is still prefetching from the previous turn, the new prefetch is skipped (not queued)\nA provider-level mutex or state flag tracks in-flight prefetch operations\nTimeout causes context cancellation which the provider should respect\nResults from prefetch are stored for retrieval in system_prompt_block()\nMetrics/logging track prefetch duration, timeouts, and skips","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:21Z","updated_at":"2026-08-08T14:44:24Z","closed_at":"2026-08-08T14:44:25Z","external_ref":"https://github.com/samcharles93/archie-core/issues/239","source_system":"github:https://github.com/samcharles93/archie-core/issues/239:239","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495472-217-6571ca92","title":"MemoryManager background sync pipeline","description":"Implement a serialized background sync pipeline in MemoryManager using a single-worker ThreadPoolExecutor pattern. All write operations from external providers are serialized through one worker to guarantee write ordering and prevent concurrent mutations.\n\n### Acceptance Criteria\n\nA single-worker goroutine/worker pool processes queued sync operations\nWrite operations are submitted to the pipeline and processed in FIFO order\nCaller receives a channel/future for optional completion notification\nWrite ordering is guaranteed - operations don't reorder\nPipeline has a configurable buffer size (default 100)\nPipeline drains on shutdown with configurable timeout\nErrors from sync operations are logged but don't crash the pipeline","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:16Z","updated_at":"2026-08-08T14:44:19Z","closed_at":"2026-08-08T14:44:20Z","external_ref":"https://github.com/samcharles93/archie-core/issues/238","source_system":"github:https://github.com/samcharles93/archie-core/issues/238:238","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495444-216-9651dd7b","title":"MemoryManager orchestrator","description":"Implement MemoryManager that orchestrates the built-in memory provider plus at most one external provider. Key responsibilities: provider registration and lifecycle, tool schema merging from all active providers, runtime dispatch of tool calls to the correct provider, enforcement of the one-external-provider limit.\n\n### Acceptance Criteria\n\nMemoryManager is in internal/memory/manager package\nConstructor accepts the built-in provider + optional external provider\nRegistering a second external provider returns an error\nget_tool_schemas() merges schemas from all active providers\nhandle_tool_call() routes calls to the owning provider\nProvides accessor methods for the current active provider(s)\nGracefully handles all provider being nil/empty","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:10Z","updated_at":"2026-08-08T14:44:13Z","closed_at":"2026-08-08T14:44:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/237","source_system":"github:https://github.com/samcharles93/archie-core/issues/237:237","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495414-215-2d338cba","title":"MemoryProvider backup paths support","description":"Add backup_paths() to MemoryProvider: returns a list of file paths outside HERMES_HOME that should be included in backups. External providers (e.g., SQLite, vector stores) may store data outside the main home directory, and this ensures backup completeness.\n\n### Acceptance Criteria\n\nBackupProvider interface with backup_paths() returning []string\nReturned paths are absolute file or directory paths\nReturns empty slice for providers with no external data\nMemoryManager aggregates backup paths from all active providers\nPaths are included in any backup/restore workflow","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:05Z","updated_at":"2026-08-08T14:44:08Z","closed_at":"2026-08-08T14:44:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/236","source_system":"github:https://github.com/samcharles93/archie-core/issues/236:236","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495389-214-bfbf2cbe","title":"MemoryProvider config helpers","description":"Add config helper interfaces to MemoryProvider: get_config_schema() returns a JSON Schema describing the provider's configuration, save_config(values, hermes_home) validates and persists configuration. These enable dynamic provider configuration through the config system.\n\n### Acceptance Criteria\n\nConfigSchemaProvider defines get_config_schema() returning map[string]any in JSON Schema format\nSaveConfigProvider defines save_config(values map[string]any, hermesHome string) error\nSchema is used to validate user-provided config values before saving\nsave_config writes to a provider-specific location under hermes_home\nProviders without config support simply don't implement the interfaces","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:44:00Z","updated_at":"2026-08-08T14:44:02Z","closed_at":"2026-08-08T14:44:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/235","source_system":"github:https://github.com/samcharles93/archie-core/issues/235:235","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495361-213-342ec6c9","title":"Verify: Shutdown drain with timeout and abandoned-write tracking","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:55Z","updated_at":"2026-08-08T14:43:57Z","closed_at":"2026-08-08T14:43:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/234","source_system":"github:https://github.com/samcharles93/archie-core/issues/234:234","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495338-212-efce3445","title":"Verify: Threat scanning integration for memory content","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:50Z","updated_at":"2026-08-08T14:43:52Z","closed_at":"2026-08-08T14:43:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/233","source_system":"github:https://github.com/samcharles93/archie-core/issues/233:233","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495318-211-15271789","title":"Verify: Frozen snapshot pattern for memory injection","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:45Z","updated_at":"2026-08-08T14:43:47Z","closed_at":"2026-08-08T14:43:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/232","source_system":"github:https://github.com/samcharles93/archie-core/issues/232:232","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495297-210-dee8210c","title":"MemoryProvider lifecycle hooks","description":"Add lifecycle hook interfaces to MemoryProvider: on_turn_start(), on_session_end(), on_session_switch(), on_pre_compress(), on_memory_write(content), on_delegation(). These allow providers to react to session lifecycle events for state management and context maintenance.\n\n### Acceptance Criteria\n\nEach lifecycle hook is a separate optional sub-interface (e.g., TurnStartHook, SessionEndHook, SessionSwitchHook, PreCompressHook, MemoryWriteHook, DelegationHook)\nInterfaces are defined alongside MemoryProvider in the same package\nMemoryManager calls hooks at appropriate points in the agent lifecycle\nHooks have access to relevant context (session_id, content, etc.)\nAll hooks are called asynchronously to avoid blocking the main loop","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:40Z","updated_at":"2026-08-08T14:43:43Z","closed_at":"2026-08-08T14:43:44Z","external_ref":"https://github.com/samcharles93/archie-core/issues/231","source_system":"github:https://github.com/samcharles93/archie-core/issues/231:231","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495277-209-bca515f3","title":"Verify: MemoryManager notify_memory_tool_write","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:35Z","updated_at":"2026-08-08T14:43:37Z","closed_at":"2026-08-08T14:43:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/230","source_system":"github:https://github.com/samcharles93/archie-core/issues/230:230","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495248-208-cbb2cc1c","title":"Verify: MemoryManager prefetch with timeout","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:30Z","updated_at":"2026-08-08T14:43:32Z","closed_at":"2026-08-08T14:43:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/229","source_system":"github:https://github.com/samcharles93/archie-core/issues/229:229","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495220-207-a289b434","title":"Verify: MemoryManager background sync pipeline","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:25Z","updated_at":"2026-08-08T14:43:27Z","closed_at":"2026-08-08T14:43:28Z","external_ref":"https://github.com/samcharles93/archie-core/issues/228","source_system":"github:https://github.com/samcharles93/archie-core/issues/228:228","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495192-206-5c518bca","title":"Verify: Built-in memory tool actions: add, replace, remove","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:20Z","updated_at":"2026-08-08T14:43:22Z","closed_at":"2026-08-08T14:43:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/227","source_system":"github:https://github.com/samcharles93/archie-core/issues/227:227","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495167-205-f6e83151","title":"Verify: Built-in memory tool: file-backed persistent memory","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:15Z","updated_at":"2026-08-08T14:43:18Z","closed_at":"2026-08-08T14:43:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/226","source_system":"github:https://github.com/samcharles93/archie-core/issues/226:226","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495146-204-2bbb81f5","title":"Verify: Tool schema normalization for memory providers","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:10Z","updated_at":"2026-08-08T14:43:13Z","closed_at":"2026-08-08T14:43:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/225","source_system":"github:https://github.com/samcharles93/archie-core/issues/225:225","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495125-203-c2f13af1","title":"Verify: StreamingContextScrubber","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:05Z","updated_at":"2026-08-08T14:43:08Z","closed_at":"2026-08-08T14:43:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/224","source_system":"github:https://github.com/samcharles93/archie-core/issues/224:224","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495098-202-6b4a7fa3","title":"Verify: MemoryManager orchestrator","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:43:00Z","updated_at":"2026-08-08T14:43:02Z","closed_at":"2026-08-08T14:43:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/223","source_system":"github:https://github.com/samcharles93/archie-core/issues/223:223","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495068-201-2dd5277c","title":"Verify: MemoryProvider backup paths support","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:54Z","updated_at":"2026-08-08T14:42:57Z","closed_at":"2026-08-08T14:42:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/222","source_system":"github:https://github.com/samcharles93/archie-core/issues/222:222","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495041-200-836fb5ba","title":"Verify: MemoryProvider config helpers","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:49Z","updated_at":"2026-08-08T14:42:51Z","closed_at":"2026-08-08T14:42:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/221","source_system":"github:https://github.com/samcharles93/archie-core/issues/221:221","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637495012-199-eaacf19a","title":"MemoryProvider optional methods","description":"Add optional methods to the MemoryProvider interface: system_prompt_block(), prefetch(query), queue_prefetch(query), sync_turn(user, assistant), handle_tool_call(name, args), shutdown(). These are defined as separate interface extensions that providers can opt into via type assertion.\n\n### Acceptance Criteria\n\nOptional behavior is defined via separate sub-interfaces (e.g., PrefetchProvider, SyncTurnProvider, ShutdownProvider)\nMemoryManager checks via type assertion at runtime which optional interfaces a provider implements\nEach optional interface has clear doc comments\nDefault no-op behavior when a provider doesn't implement an optional interface","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:44Z","updated_at":"2026-08-08T14:42:47Z","closed_at":"2026-08-08T14:42:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/220","source_system":"github:https://github.com/samcharles93/archie-core/issues/220:220","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494992-198-7aab9fbc","title":"Verify: MemoryProvider lifecycle hooks","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:39Z","updated_at":"2026-08-08T14:42:42Z","closed_at":"2026-08-08T14:42:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/219","source_system":"github:https://github.com/samcharles93/archie-core/issues/219:219","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494966-197-726021ca","title":"Verify: MemoryProvider optional methods","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:34Z","updated_at":"2026-08-08T14:42:37Z","closed_at":"2026-08-08T14:42:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/218","source_system":"github:https://github.com/samcharles93/archie-core/issues/218:218","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494940-196-c5b68ef3","title":"Verify: MemoryProvider interface (abstract)","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:29Z","updated_at":"2026-08-08T14:42:31Z","closed_at":"2026-08-08T14:42:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/217","source_system":"github:https://github.com/samcharles93/archie-core/issues/217:217","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494913-195-df92d717","title":"Shutdown drain with timeout and abandoned-write tracking","description":"Implement graceful shutdown drain for MemoryManager with a bounded timeout. In-flight sync operations are given a configurable deadline to complete. Operations that don't finish within the deadline are tracked as abandoned writes for diagnostics.\n\n### Acceptance Criteria\n\nShutdown(ctx) method on MemoryManager with context-based deadline\nIn-flight sync pipeline operations are given N seconds (default 10) to complete\nAbandoned writes (those exceeding the deadline) are logged with: provider name, operation type, age\nshutdown() is called on all active providers in reverse registration order\nAfter shutdown, no new operations are accepted\nProvider shutdown respects the same deadline\nAbandoned-write counter is accessible for health/status reporting","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:24Z","updated_at":"2026-08-08T14:42:26Z","closed_at":"2026-08-08T14:42:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/216","source_system":"github:https://github.com/samcharles93/archie-core/issues/216:216","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494880-194-86baeb74","title":"Threat scanning integration for memory content","description":"Integrate threat scanning for all memory content writes. Before persisting any memory content (add/replace/remove), scan the content for potentially dangerous patterns (injection attempts, sensitive data leakage, prompt injection in stored memory).\n\n### Acceptance Criteria\n\nA ScanContent(content string) function or hook is called before every memory write\nScans cover: prompt injection patterns, sensitive data patterns (API keys, passwords, tokens)\nConfigurable to reject (block the write) or warn (allow with log) on suspicious content\nIntegration point at the MemoryManager level so it applies to all providers\nResults are logged for audit\nConfig flag to disable scanning for development","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:19Z","updated_at":"2026-08-08T15:34:55Z","closed_at":"2026-08-08T15:34:56Z","external_ref":"https://github.com/samcharles93/archie-core/issues/215","source_system":"github:https://github.com/samcharles93/archie-core/issues/215:215","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494853-193-12981021","title":"Frozen snapshot pattern for memory injection","description":"Implement the frozen snapshot pattern: memory content is read at session start and injected into the system prompt as a snapshot. On write, files are updated immediately but the system prompt is NOT changed mid-session. Only the next session picks up the new snapshot.\n\n### Acceptance Criteria\n\nAt session start, MEMORY.md and USER.md are read and formatted into a system prompt block\nThis formatted block becomes part of the session's system prompt (frozen for the session duration)\nWhen a memory write occurs, the files are updated immediately on disk\nThe in-memory snapshot for the current session is NOT updated\nThe next session reads the fresh files and creates a new frozen snapshot\nConfig flag to disable frozen snapshot (always read fresh) for testing","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:14Z","updated_at":"2026-08-08T14:42:16Z","closed_at":"2026-08-08T14:42:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/214","source_system":"github:https://github.com/samcharles93/archie-core/issues/214:214","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494829-192-fa7ea3e2","title":"Built-in memory tool actions: add, replace, remove","description":"Implement the three core memory tool actions: add (appends new content to a section), replace (replaces content using substring matching to find the target), remove (deletes content using substring matching). These act on the MEMORY.md/USER.md files.\n\n### Acceptance Criteria\n\nTool exposes three actions: add, replace, remove\nadd(target_section, content) appends to or creates a named section\nreplace(target_section, substring, replacement) finds first match of substring in section and replaces it\nremove(target_section, substring) removes the matching line/block from the section\nSubstring matching is exact, case-sensitive by default (configurable)\nActions return clear success/error messages including the affected section and character count\nTool validates section names (alphanumeric + spaces, max 64 chars)\nSize bounds are checked before any write (reject if would exceed max file size)","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:09Z","updated_at":"2026-08-08T14:42:11Z","closed_at":"2026-08-08T14:42:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/213","source_system":"github:https://github.com/samcharles93/archie-core/issues/213:213","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494804-191-0907551f","title":"Built-in memory tool: file-backed persistent memory","description":"Implement the built-in file-backed memory tool that persists to MEMORY.md and USER.md files. This replaces the current ephemeral memoryNotes system with durable on-disk storage that survives restarts and sessions.\n\n### Acceptance Criteria\n\nBuilt-in provider lives in internal/memory/builtin package\nMEMORY.md stores persistent agent memory (facts, preferences, state across sessions)\nUSER.md stores user-provided context (background, instructions, preferences)\nBoth files are bounded (configurable max size, default 100KB per file)\nFiles are read at provider initialization and written on every mutation\nFile format is plain markdown with sections\nThread-safe reads and writes (sync.RWMutex)\nFiles live under the profile's memory directory (e.g., ~/.config/archie/profiles/{profile}/memory/)","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:42:04Z","updated_at":"2026-08-08T14:42:06Z","closed_at":"2026-08-08T14:42:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/212","source_system":"github:https://github.com/samcharles93/archie-core/issues/212:212","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494784-190-fb7ac8fd","title":"Tool schema normalization for memory providers","description":"Implement tool schema normalization that handles both bare tools (just Function definition) and wrapped OpenAI-style tool schemas from memory providers. Ensures all provider-exported tools are normalized to a consistent format before being merged into the agent's tool list.\n\n### Acceptance Criteria\n\nNormalizer package detects whether a schema is bare (map with 'name' top-level) or wrapped (map with 'type':'function', 'function':{...})\nConverts both formats to a canonical internal representation\nHandles edge cases: missing required fields, extra unknown fields\nSchema normalization happens at registration time, not per-turn\nErrors on truly invalid schemas with clear messages\nRound-trips through JSON marshal/unmarshal","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:59Z","updated_at":"2026-08-08T14:42:01Z","closed_at":"2026-08-08T14:42:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/211","source_system":"github:https://github.com/samcharles93/archie-core/issues/211:211","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494756-189-de46559c","title":"StreamingContextScrubber","description":"Implement a stateful StreamingContextScrubber that strips \u003cmemory-context\u003e...\u003c/memory-context\u003e fence spans from streaming text output. Must handle partial chunks that split across fence boundaries, maintain state between chunks, and only emit clean text downstream.\n\n### Acceptance Criteria\n\nScrubber is in internal/memory/scrubber package\nImplements an io.Writer or callback interface for processing streaming chunks\nStrips \u003cmemory-context\u003e ... \u003c/memory-context\u003e fences including the tags themselves\nHandles partial chunks where fence tags span chunk boundaries (maintains state)\nHandles missing closing tags (closes at end of stream)\nDoesn't interfere with non-memory-context content\nZero allocations in the hot path (reuses buffers)\nFully tested with edge cases: partial open/close, nested tags, empty content","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:53Z","updated_at":"2026-08-08T14:41:56Z","closed_at":"2026-08-08T14:41:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/210","source_system":"github:https://github.com/samcharles93/archie-core/issues/210:210","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494728-188-1b439b27","title":"MemoryProvider interface (abstract)","description":"Define the core MemoryProvider interface with required methods: name(), is_available(), initialize(session_id), get_tool_schemas(). This is the contract that all memory providers (built-in and external/plugin) must implement.\n\n### Acceptance Criteria\n\nMemoryProvider is defined as a Go interface in a new internal/memory/provider package\nname() returns a unique human-readable string identifying the provider\nis_available() returns true when the provider is ready for use\ninitialize(session_id) prepares the provider for a given session\nget_tool_schemas() returns the tool definitions the provider exports to the agent\nClean godoc comments on all methods","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:48Z","updated_at":"2026-08-08T14:41:51Z","closed_at":"2026-08-08T14:41:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/209","source_system":"github:https://github.com/samcharles93/archie-core/issues/209:209","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494691-187-3f76aa73","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\n\n### Acceptance Criteria\n\nAn 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":2,"issue_type":"epic","created_at":"2026-08-08T14:41:43Z","updated_at":"2026-08-08T14:41:46Z","closed_at":"2026-08-08T14:41:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/208","source_system":"github:https://github.com/samcharles93/archie-core/issues/208:208","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494663-186-5bf24e2b","title":"Multimodal result envelope handling","description":"Implement a multimodal result envelope type (is_multimodal flag, text summary, subdir hint). When tools return multimodal content (images, audio, video, documents), wrap the result in an envelope that provides a text summary for context-feed while storing the actual media at a hinted subdirectory path.\n\n### Acceptance Criteria\n\nMultimodal result envelope type implemented (tools.MultimodalResult) and wired into the MCP client's tool-call handler with progressive disclosure (text summary always present, media persisted to a hinted subdirectory only when configured) -- DONE. Adversarially reviewed with all findings fixed and regression-tested -- DONE.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:38Z","updated_at":"2026-08-08T15:35:24Z","closed_at":"2026-08-08T15:35:25Z","external_ref":"https://github.com/samcharles93/archie-core/issues/207","source_system":"github:https://github.com/samcharles93/archie-core/issues/207:207","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494637-185-295ff0a1","title":"File checkpointing before mutating operations","description":"Implement file checkpointing: before any tool that modifies state (file writes, config changes, etc.) executes, snapshot the relevant files or state sections so they can be rolled back on failure. This provides safety guards for mutating tool operations.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:35Z","updated_at":"2026-08-08T14:41:35Z","external_ref":"https://github.com/samcharles93/archie-core/issues/206","source_system":"github:https://github.com/samcharles93/archie-core/issues/206:206","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494612-184-ac5f855f","title":"Per-turn aggregate budget enforcement (200K char cap)","description":"Implement a per-turn aggregate output budget of 200,000 characters. Track cumulative tool result sizes within a turn. When the budget is exceeded, auto-spill the largest results to disk. Enforce a hard stop at the budget limit with clear reporting to the user.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:30Z","updated_at":"2026-08-08T15:35:02Z","closed_at":"2026-08-08T15:35:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/205","source_system":"github:https://github.com/samcharles93/archie-core/issues/205:205","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494585-183-63b2b2a2","title":"Concurrent tool dispatch with execution gating","description":"Implement concurrent tool dispatch with execution gating classes: never-parallel (e.g. state mutators), parallel-safe (e.g. read-only tools), and path-scoped (same-path tools are serialized, different paths run in parallel). Use sync primitives and a gating engine to classify and schedule tool invocations correctly.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:25Z","updated_at":"2026-08-08T14:41:27Z","closed_at":"2026-08-08T14:41:28Z","external_ref":"https://github.com/samcharles93/archie-core/issues/204","source_system":"github:https://github.com/samcharles93/archie-core/issues/204:204","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494559-182-410c3c4c","title":"Sequential tool dispatch with per-result previews and error handling","description":"Build the sequential tool dispatch pipeline: invoke tools one-at-a-time, capture per-result previews (truncated output for context-feed), and implement error classification with graceful fallback. Each result should produce a short preview snippet for inclusion in the conversation context.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:22Z","updated_at":"2026-08-08T15:35:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/203","source_system":"github:https://github.com/samcharles93/archie-core/issues/203:203","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494538-181-e4631b2f","title":"feat(gateway): task_list and task_spawn chat tools","description":"/spawn, /approve and /cancel are slash commands only a human types (internal/gateway/gateway.go:299-401), so 'what are you working on?' has no tool path, even though TaskCreator/TaskController (internal/gateway/tasks.go) are one import away.\n\ninternal/gateway/tasks.go gains a narrow read interface chatTaskLister (ListChatTasks(ctx, identity, limit) ([]ChatTaskSummary, error)), keeping gateway independent of internal/store; the daemon adapts store.Store.Tasks.\n\ninternal/gateway/task_tools.go (new): TaskTools(lister, creator, identity) returning task_list and task_spawn, both bound to the calling gateway's identity so the model never supplies it.\n\ntask_approve and task_cancel are deliberately excluded: waiting_human is the one point in the lifecycle where a person must act and /approve is that gate. Chat input is an untrusted path (a forge issue body or inbound email quoted into a turn is model-visible text), so a tool that approves Archie's own work removes the only human checkpoint. Add behind an operator flag defaulting to off if wanted later.\n\nWired into chatGenerateOptions, merged over the registry-built set.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:41:19Z","updated_at":"2026-08-08T14:41:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/202","source_system":"github:https://github.com/samcharles93/archie-core/issues/202:202","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494512-180-38b8f04b","title":"feat(tools): web_fetch tool with dial-time SSRF protection","description":"Archie has no web access of any kind and no MCP server configured to substitute, so it cannot open a URL pasted into chat.\n\nNew package internal/tools/webfetch, registered directly in cmd/archied/main.go beside skill_activate.\n\nSchema: url (required), raw (bool, skip HTML extraction).\n\n- http/https scheme allowlist.\n- SSRF protection in DialContext, NOT as a pre-flight URL check: resolve the host, reject loopback/private/link-local/unspecified/multicast, then dial the vetted IP. A pre-flight URL check leaves a DNS-rebinding hole, and this daemon runs on a host with the Docker socket and NATS reachable on 172.19.0.1.\n- CheckRedirect caps hops and re-applies the scheme check.\n- Body capped by io.LimitReader; result then capped by the per-tool limit.\n- text/html -\u003e readable text via golang.org/x/net/html; text/*, json, xml as-is; anything else an error naming content type and size.\n- Non-2xx returns status plus a short excerpt.\n\nConfig [tools.web_fetch]: enabled, timeout, max_bytes, allow_private_networks (default false). Defaults via configuration.applyDefaults.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:41:16Z","updated_at":"2026-08-08T14:41:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/201","source_system":"github:https://github.com/samcharles93/archie-core/issues/201:201","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494482-179-e23fe15a","title":"Firecracker substrate for sandboxed MCP code tools","description":"Replace the interim daemon-container code MCP execution path with a real Firecracker boundary. Extend or extract the gorev POC to support a long-lived bidirectional guest process, explicit workspace import/export, per-turn filesystem checkpoints, lifecycle/health, and concurrent-instance-safe networking. Then adapt the MCP provider launcher without changing the chat/tool contract.\n\n### Acceptance Criteria\n\nMCP server code and tool execution occur inside a Firecracker VM; the guest cannot access daemon-host files outside the imported workspace; changes export deterministically; pre-change checkpoints support /restore; lifecycle cleanup survives crashes; tests prove the configured provider cannot silently fall back to host execution.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:41:13Z","updated_at":"2026-08-08T14:41:13Z","external_ref":"https://github.com/samcharles93/archie-core/issues/200","source_system":"github:https://github.com/samcharles93/archie-core/issues/200:200","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494450-178-67d1e003","title":"Wire MCP tool servers for the chat agent, sandboxed","description":"The chat agent has only memory_edit and skill_activate, so it cannot act on the codebase. cfg.Tools.MCPServers + the stdio transport are the designed extension point (configuredMCPProvider in cmd/archied/main.go already builds providers from config). Sam's requirement is to expose specific capabilities narrowly rather than granting host access, and he has a Firecracker sandbox POC at /work/clones/gorev (firecracker/sandbox) intended for exactly this.\n\n### Acceptance Criteria\n\nMCP servers are configurable per deployment and discovered into the chat agent tool loop. A narrowly scoped code MCP server runs in the daemon container against an explicitly configured workspace and can make a code change end to end. Firecracker execution remains a requirement tracked separately in archie-core-abg.17.44.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:41:10Z","updated_at":"2026-08-08T15:34:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/199","source_system":"github:https://github.com/samcharles93/archie-core/issues/199:199","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494422-177-3ec91c84","title":"wire MCP per-server parallel-tool-calls flag into config and daemon startup","description":"Follow-up to archie-core-abg.17.20, which added mcp.Client.parallelToolCalls + WithParallelToolCalls(bool) at the client-API level (adversarially reviewed, race-clean). Nothing currently sets it: config.MCPServer (internal/config/config.go) has no field for it, and both NewClient call sites (cmd/archied/main.go:510's mcp.NewClient, and internal/tools/provider/mcp/provider.go:85's protocol.NewClient) construct clients without the option -- so the flag has zero effect in production as things stand today.\n\n### Acceptance Criteria\n\nconfig.MCPServer gains a ParallelToolCalls bool field (default false, matching the client's safe-by-default); both NewClient call sites read it and pass mcp.WithParallelToolCalls(cfg value) accordingly; a config-driven test proves a server configured with parallel_tool_calls=true actually gets a parallel-opted Client.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:41:07Z","updated_at":"2026-08-08T14:41:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/198","source_system":"github:https://github.com/samcharles93/archie-core/issues/198:198","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494393-176-72def734","title":"Tool-provider engine: lifecycle registry with MCP and memory providers","description":"Build the typed tool-provider capability family over the central tools registry. Providers declare a plugin manifest, lifecycle/health, and discover executable ToolEntry values. Add adapters for memory.Manager and configured MCP servers, perform MCP initialize/tools-list/tools-call, register handlers atomically with collision rollback, translate available entries to ai-sdk core.ToolSet, and wire consumers so registered tools are actually callable rather than dead daemon fields.\n\n### Design\n\ninternal/tools owns Provider and ProviderRegistry; Provider is a typed domain contract and uses the shared plugin manifest/lifecycle vocabulary. The registry owns provider registration and tool indexing while the capability host orchestrates cross-family lifecycle. Memory is adapted without changing internal/memory concurrent work. MCP provider wraps the existing stdio transport without modifying its concurrent implementation, adds protocol client behavior in new files, prefixes/sanitizes server tool names deterministically, and retains original MCP names for calls. Never advertise a tool on an execution path that cannot invoke its handler; explicitly proxy or omit tools across subprocess/NATS boundaries.\n\n### Acceptance Criteria\n\nProvider registration is atomic and rejects duplicate provider/tool IDs without partial state. Start/discovery failure rolls back tools and lifecycle; stop removes availability and shuts providers down in reverse order. Memory provider tools appear in the central registry and execute through memory.Manager. A fake MCP server proves initialize, initialized notification where supported, tools/list discovery, tools/call execution, JSON-RPC errors, shutdown, and name mapping. Available tools convert to valid ai-sdk core.ToolSet and are used by the gateway conversational loop and supported agent execution paths; unsupported remote paths do not advertise unusable handlers. Configuration creates providers through typed factories. Focused/race tests, lint, task check, and fresh adversarial review pass subject only to documented concurrent baseline failures.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:41:02Z","updated_at":"2026-08-08T15:33:38Z","closed_at":"2026-08-08T15:33:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/197","source_system":"github:https://github.com/samcharles93/archie-core/issues/197:197","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494356-175-95ef90cb","title":"Verify: MCP client: per-server parallel tool call opt-in flag","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:57Z","updated_at":"2026-08-08T14:40:59Z","closed_at":"2026-08-08T14:41:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/196","source_system":"github:https://github.com/samcharles93/archie-core/issues/196:196","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494316-174-99f3da5d","title":"Per-tool result size limits with spill-to-disk","description":"Implement max_result_size_chars enforcement on each ToolEntry. When a tool result exceeds its limit, auto-spill large outputs to disk and return a reference/location instead of the full content. This prevents memory blowout from oversized tool results.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:51Z","updated_at":"2026-08-08T14:40:54Z","closed_at":"2026-08-08T14:40:55Z","external_ref":"https://github.com/samcharles93/archie-core/issues/195","source_system":"github:https://github.com/samcharles93/archie-core/issues/195:195","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494286-173-c18d767f","title":"Verify: MCP client: server-initiated sampling","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:46Z","updated_at":"2026-08-08T14:40:48Z","closed_at":"2026-08-08T14:40:49Z","external_ref":"https://github.com/samcharles93/archie-core/issues/194","source_system":"github:https://github.com/samcharles93/archie-core/issues/194:194","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494259-172-30e1fe15","title":"Verify: MCP client: SSE transport","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:41Z","updated_at":"2026-08-08T14:40:43Z","closed_at":"2026-08-08T14:40:44Z","external_ref":"https://github.com/samcharles93/archie-core/issues/193","source_system":"github:https://github.com/samcharles93/archie-core/issues/193:193","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494236-171-ad4542b3","title":"Verify: MCP client: HTTP/StreamableHTTP transport","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:35Z","updated_at":"2026-08-08T14:40:38Z","closed_at":"2026-08-08T14:40:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/192","source_system":"github:https://github.com/samcharles93/archie-core/issues/192:192","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494211-170-2bd8e4fb","title":"Verify: Multimodal result envelope handling","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:30Z","updated_at":"2026-08-08T14:40:33Z","closed_at":"2026-08-08T14:40:34Z","external_ref":"https://github.com/samcharles93/archie-core/issues/191","source_system":"github:https://github.com/samcharles93/archie-core/issues/191:191","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494187-169-a9952930","title":"Verify: File checkpointing before mutating operations","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:25Z","updated_at":"2026-08-08T14:40:27Z","closed_at":"2026-08-08T14:40:28Z","external_ref":"https://github.com/samcharles93/archie-core/issues/190","source_system":"github:https://github.com/samcharles93/archie-core/issues/190:190","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494159-168-66ef9d93","title":"Verify: Context-pressure threshold gating","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:20Z","updated_at":"2026-08-08T14:40:22Z","closed_at":"2026-08-08T14:40:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/189","source_system":"github:https://github.com/samcharles93/archie-core/issues/189:189","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494137-167-1cb48767","title":"Verify: Progressive tool disclosure (bridge tools)","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:17Z","updated_at":"2026-08-08T15:34:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/188","source_system":"github:https://github.com/samcharles93/archie-core/issues/188:188","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494115-166-708ff496","title":"Verify: Guardrail decision engine: warning vs hard-stop","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:12Z","updated_at":"2026-08-08T14:40:14Z","closed_at":"2026-08-08T14:40:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/187","source_system":"github:https://github.com/samcharles93/archie-core/issues/187:187","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494093-165-b5b75fde","title":"Verify: Mutating tool classification set","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:07Z","updated_at":"2026-08-08T14:40:09Z","closed_at":"2026-08-08T14:40:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/186","source_system":"github:https://github.com/samcharles93/archie-core/issues/186:186","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494068-164-fbdfd9d4","title":"Verify: Idempotent tool classification set","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:01Z","updated_at":"2026-08-08T14:40:04Z","closed_at":"2026-08-08T14:40:05Z","external_ref":"https://github.com/samcharles93/archie-core/issues/185","source_system":"github:https://github.com/samcharles93/archie-core/issues/185:185","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494041-163-961e45bb","title":"Tool availability checks with TTL caching","description":"Implement the check_fn pattern for tool availability predicates (e.g. 'is Docker running'). Results should be TTL-cached (e.g. 30s check interval) with a failure grace period (e.g. 60s before re-checking on error). This prevents redundant checking on every invocation while keeping availability fresh.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:58Z","updated_at":"2026-08-08T15:35:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/184","source_system":"github:https://github.com/samcharles93/archie-core/issues/184:184","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637494011-162-ab684953","title":"Verify: Tool guardrails: ToolCallGuardrailConfig","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:53Z","updated_at":"2026-08-08T14:39:56Z","closed_at":"2026-08-08T14:39:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/183","source_system":"github:https://github.com/samcharles93/archie-core/issues/183:183","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493979-161-0e2f821f","title":"Verify: Per-turn aggregate budget enforcement (200K char cap)","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:48Z","updated_at":"2026-08-08T14:39:51Z","closed_at":"2026-08-08T14:39:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/182","source_system":"github:https://github.com/samcharles93/archie-core/issues/182:182","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493958-160-063454b8","title":"Verify: Concurrent tool dispatch with execution gating","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:45Z","updated_at":"2026-08-08T15:34:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/181","source_system":"github:https://github.com/samcharles93/archie-core/issues/181:181","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493932-159-ee61b7c9","title":"Verify: Sequential tool dispatch with per-result previews and error handling","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:42Z","updated_at":"2026-08-08T15:34:49Z","external_ref":"https://github.com/samcharles93/archie-core/issues/180","source_system":"github:https://github.com/samcharles93/archie-core/issues/180:180","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493907-158-9de8c923","title":"Verify: Per-tool result size limits with spill-to-disk","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:37Z","updated_at":"2026-08-08T15:34:51Z","closed_at":"2026-08-08T15:34:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/179","source_system":"github:https://github.com/samcharles93/archie-core/issues/179:179","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493884-157-e7cc3387","title":"Verify: Tool availability checks with TTL caching","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:34Z","updated_at":"2026-08-08T15:34:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/178","source_system":"github:https://github.com/samcharles93/archie-core/issues/178:178","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493861-156-1a362d40","title":"Verify: MCP client: stdio transport (subprocess management)","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:29Z","updated_at":"2026-08-08T14:39:31Z","closed_at":"2026-08-08T14:39:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/177","source_system":"github:https://github.com/samcharles93/archie-core/issues/177:177","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493832-155-60ae40d1","title":"Verify: Central tool registry singleton with Register() + discovery","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:23Z","updated_at":"2026-08-08T14:39:26Z","closed_at":"2026-08-08T14:39:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/176","source_system":"github:https://github.com/samcharles93/archie-core/issues/176:176","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493806-154-2252fd98","title":"Verify: ToolEntry data type definition","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:18Z","updated_at":"2026-08-08T14:39:21Z","closed_at":"2026-08-08T14:39:22Z","external_ref":"https://github.com/samcharles93/archie-core/issues/175","source_system":"github:https://github.com/samcharles93/archie-core/issues/175:175","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493784-153-d27e27ae","title":"MCP client: per-server parallel tool call opt-in flag","description":"Add a per-server configuration flag to opt-in to parallel tool calls in the MCP client. When enabled, the client may dispatch multiple tool calls to the same MCP server concurrently. When disabled, all calls to that server are serialized. This respects server-side concurrency limitations.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:13Z","updated_at":"2026-08-08T15:35:22Z","closed_at":"2026-08-08T15:35:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/174","source_system":"github:https://github.com/samcharles93/archie-core/issues/174:174","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493762-152-3a3bbfa7","title":"Central tool registry singleton with Register() + discovery","description":"Implement a global tool registry singleton with a Register() method. Add file-system discovery that scans tools/*.go for registry.Register calls to auto-register tools at startup. This is the core infrastructure that all tool registration and lookup depends on.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:07Z","updated_at":"2026-08-08T14:39:10Z","closed_at":"2026-08-08T14:39:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/173","source_system":"github:https://github.com/samcharles93/archie-core/issues/173:173","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493736-151-85e57902","title":"MCP client: server-initiated sampling","description":"Implement MCP server-initiated sampling support: when the MCP server sends a sampling request, route it to the LLM and return the sampled response. This enables MCP servers to request LLM completions as part of tool execution (e.g. for sub-agent delegation within a tool).","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:04Z","updated_at":"2026-08-08T14:39:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/172","source_system":"github:https://github.com/samcharles93/archie-core/issues/172:172","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493701-150-f57e2e2b","title":"MCP client: SSE transport","description":"Implement MCP SSE (Server-Sent Events) transport: establish SSE connection to MCP servers, handle event stream parsing, manage reconnection with backoff, and translate SSE events to the unified MCP transport interface. This enables real-time streaming from MCP servers.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:59Z","updated_at":"2026-08-08T14:39:02Z","closed_at":"2026-08-08T14:39:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/171","source_system":"github:https://github.com/samcharles93/archie-core/issues/171:171","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493676-149-96f35179","title":"MCP client: HTTP/StreamableHTTP transport","description":"Implement MCP HTTP/StreamableHTTP transport: make JSON-RPC requests over HTTP/HTTPS with support for streamable HTTP responses. Handle connection lifecycle, keep-alive, reconnection, and error classification for remote MCP servers accessed via HTTP.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:54Z","updated_at":"2026-08-08T14:38:56Z","closed_at":"2026-08-08T14:38:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/170","source_system":"github:https://github.com/samcharles93/archie-core/issues/170:170","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493651-148-5a1e6482","title":"MCP client: stdio transport (subprocess management)","description":"Implement the MCP stdio transport: spawn and manage MCP server subprocesses, handle stdin/stdout JSON-RPC message framing, subprocess lifecycle (start/stop/restart), and auto-restart with exponential backoff. This is the foundational MCP transport that most local MCP servers use.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:48Z","updated_at":"2026-08-08T14:38:51Z","closed_at":"2026-08-08T14:38:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/169","source_system":"github:https://github.com/samcharles93/archie-core/issues/169:169","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493624-147-3a7826d5","title":"Context-pressure threshold gating","description":"Implement context-pressure threshold gating: when the combined size of tool schemas exceeds a configurable percentage of the LLM context window, automatically switch to progressive tool disclosure mode (bridge tools). Monitor context usage and toggle between full disclosure and bridge-tool mode dynamically.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:43Z","updated_at":"2026-08-08T14:38:46Z","closed_at":"2026-08-08T14:38:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/168","source_system":"github:https://github.com/samcharles93/archie-core/issues/168:168","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493594-146-10de5e79","title":"Progressive tool disclosure (bridge tools)","description":"Implement the progressive tool disclosure pattern with three bridge tools: tool_search (search available tools by keyword), tool_describe (return full schema for one tool), and tool_call (invoke a tool by name after discovery). This keeps the LLM's tool schema footprint small while providing full access to the tool arsenal on demand.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:40Z","updated_at":"2026-08-08T15:34:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/167","source_system":"github:https://github.com/samcharles93/archie-core/issues/167:167","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493566-145-06408456","title":"Guardrail decision engine: warning vs hard-stop","description":"Implement the guardrail decision engine that uses ToolCallGuardrailConfig thresholds to decide between sending a warning to the LLM or issuing a hard-stop (aborting the tool loop). Considers exact_failure_warn_after, same_tool_failure_warn_after, and no_progress_warn_after. Must track per-session and per-turn counters.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:35Z","updated_at":"2026-08-08T14:38:37Z","closed_at":"2026-08-08T14:38:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/166","source_system":"github:https://github.com/samcharles93/archie-core/issues/166:166","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493546-144-8a3074d2","title":"Mutating tool classification set","description":"Define and maintain a classification set of mutating (mutation-capable) tools. These tools can modify state and require serialization, checkpointing, and stricter guardrail monitoring. The set should be extensible via registration metadata and feed into dispatch gating and checkpointing decisions.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:29Z","updated_at":"2026-08-08T14:38:32Z","closed_at":"2026-08-08T14:38:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/165","source_system":"github:https://github.com/samcharles93/archie-core/issues/165:165","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493519-143-983868b0","title":"Idempotent tool classification set","description":"Define and maintain a classification set of idempotent (read-only) tools. These tools can be safely retried and run in parallel. The set should be extensible via registration metadata. Classification feeds into dispatch gating, guardrail decisions, and budget enforcement.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:24Z","updated_at":"2026-08-08T14:38:27Z","closed_at":"2026-08-08T14:38:28Z","external_ref":"https://github.com/samcharles93/archie-core/issues/164","source_system":"github:https://github.com/samcharles93/archie-core/issues/164:164","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493493-142-952276dc","title":"Tool guardrails: ToolCallGuardrailConfig","description":"Implement the ToolCallGuardrailConfig struct with thresholds: exact_failure_warn_after (how many exact same failures before warning), same_tool_failure_warn_after (same-tool consecutive failures), and no_progress_warn_after (total tool calls without completing the turn goal). This is the configuration layer for the guardrail decision engine.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:19Z","updated_at":"2026-08-08T14:38:22Z","closed_at":"2026-08-08T14:38:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/163","source_system":"github:https://github.com/samcharles93/archie-core/issues/163:163","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493467-141-ffb91b17","title":"ToolEntry data type definition","description":"Design and implement the ToolEntry data type carrying: name, toolset (which tool group this belongs to), schema (JSON Schema for invocation), handler (function ref), check_fn (availability predicate), requires_env (env vars needed), is_async (async/sync distinction), description, emoji, max_result_size_chars (per-tool result cap), and dynamic_schema_overrides (runtime schema mutations). This is the foundational type that everything in the tools subsystem builds upon.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:14Z","updated_at":"2026-08-08T14:38:16Z","closed_at":"2026-08-08T14:38:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/162","source_system":"github:https://github.com/samcharles93/archie-core/issues/162:162","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493439-140-2cee2e9b","title":"[EPIC] Tools: central registry, MCP client, guardrails","description":"Central tool infrastructure to match Hermes parity:\\n\\n1. **Tool registry**: A central registry where tool modules register themselves with name, schema, handler, toolset membership, and availability check. Dynamic discovery of built-in tools. This replaces the current pattern of manually constructing core.ToolSet maps per invocation.\\n\\n2. **MCP client**: Connect to external MCP servers via stdio, HTTP/StreamableHTTP, or SSE transport. Discover their tools and register them into the tool registry. Support automatic reconnection with backoff, configurable timeouts, per-server parallel tool call opt-in.\\n\\n3. **Guardrails**: Tool-call loop detection (repeated calls, repeated failures, no-progress loops). Idempotent/mutating tool classification. Warning vs hard-stop decisions.\\n\\n4. **Progressive disclosure**: When tool schemas exceed a context-window threshold, replace them with bridge tools (tool_search/tool_describe/tool_call) and surface on demand. Core tools are always visible.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 3\n\n### Acceptance Criteria\n\nMCP servers can be configured with a TOML block and their tools appear alongside built-ins. The agent loop is protected against tool-call loops. Tool schemas stay within context budget.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:38:11Z","updated_at":"2026-08-08T14:38:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/161","source_system":"github:https://github.com/samcharles93/archie-core/issues/161:161","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493413-139-d157cc71","title":"SessionSource struct for platform identity","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:06Z","updated_at":"2026-08-08T14:38:08Z","closed_at":"2026-08-08T14:38:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/160","source_system":"github:https://github.com/samcharles93/archie-core/issues/160:160","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493387-138-cad8e7a7","title":"Platform capability flags for adapters","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:02Z","updated_at":"2026-08-08T14:38:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/159","source_system":"github:https://github.com/samcharles93/archie-core/issues/159:159","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493357-137-35af7083","title":"BasePlatformAdapter interactive UX methods (clarify, approval, pickers)","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:59Z","updated_at":"2026-08-08T14:37:59Z","external_ref":"https://github.com/samcharles93/archie-core/issues/158","source_system":"github:https://github.com/samcharles93/archie-core/issues/158:158","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493329-136-49b39c78","title":"BasePlatformAdapter optional methods (typing, edit, delete, media)","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:57Z","updated_at":"2026-08-08T14:37:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/157","source_system":"github:https://github.com/samcharles93/archie-core/issues/157:157","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493304-135-95070200","title":"BasePlatformAdapter interface with required methods","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:51Z","updated_at":"2026-08-08T14:37:54Z","closed_at":"2026-08-08T14:37:55Z","external_ref":"https://github.com/samcharles93/archie-core/issues/156","source_system":"github:https://github.com/samcharles93/archie-core/issues/156:156","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493282-134-cf46838e","title":"EphemeralReply type with auto-delete TTL","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:48Z","updated_at":"2026-08-08T14:37:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/155","source_system":"github:https://github.com/samcharles93/archie-core/issues/155:155","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493254-133-444ec94e","title":"Telegram: interactive /model selector","description":"When /model is invoked without an argument, present Telegram-native interactive controls rather than only plain text usage. Use the pinned go-telegram/bot SDK inline keyboard and callback query APIs; preserve /model provider/model for typed selection and enforce the existing sender allowlist on callbacks.\n\n### Acceptance Criteria\n\nAn allowlisted user invoking /model receives an inline keyboard of configured models with the active model marked; tapping a model switches it through gateway.ModelManager, acknowledges the callback, and updates the message; unauthorized or malformed callbacks cannot switch models; empty model catalogs degrade safely.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:37:45Z","updated_at":"2026-08-08T15:34:28Z","external_ref":"https://github.com/samcharles93/archie-core/issues/154","source_system":"github:https://github.com/samcharles93/archie-core/issues/154:154","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493230-132-7ab58e77","title":"Telegram: comprehensive truthful /help output","description":"The live /help response lists only /status and /help and still says LLM chat is not wired, despite the gateway supporting model, task, restart, and free-text chat paths. Replace the stale hardcoded copy with a complete, maintainable command guide that matches the registered menu and actual router behavior.\n\n### Acceptance Criteria\n\n/help describes every published command with accurate usage, includes free-text chat behavior, no longer claims chat is unwired, and a regression test fails if the published command menu and help surface drift.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:37:42Z","updated_at":"2026-08-08T15:34:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/153","source_system":"github:https://github.com/samcharles93/archie-core/issues/153:153","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493205-131-a3dd2b53","title":"Telegram: /restore to revert the last change","description":"Operator escape hatch requested alongside /restart: revert the last change from chat when an agent-authored change breaks something, without needing shell access to the host. Gateway-scoped.\n\n### Acceptance Criteria\n\nAdmin-only (allowlisted sender). Reverts the last change and reports what was reverted. Safe to run when there is nothing to revert.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:37:39Z","updated_at":"2026-08-08T15:35:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/152","source_system":"github:https://github.com/samcharles93/archie-core/issues/152:152","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493175-130-d2de1e70","title":"Telegram: /restart command to reload gateway config","description":"Operator escape hatch: restart the chat gateway from chat to pick up config changes (notably the allowlist) or recover from a wedged adapter, without shell access to the host.\n\n### Acceptance Criteria\n\n/restart is admin-only (allowlisted sender). Re-reads config and restarts the gateway. Replies with the outcome. In-flight agent tasks are not killed.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:37:34Z","updated_at":"2026-08-08T15:34:35Z","closed_at":"2026-08-08T15:34:36Z","external_ref":"https://github.com/samcharles93/archie-core/issues/151","source_system":"github:https://github.com/samcharles93/archie-core/issues/151:151","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493149-129-8a9ae7dc","title":"Telegram: register command menu via SetMyCommands","description":"The bot never calls SetMyCommands, so Telegram shows no command menu and the commands the Router implements (/status, /help, /models, /model, /spawn, /approve, /cancel) are undiscoverable. Asking the bot for /commands makes the LLM answer that it has none, which is wrong.\n\n### Acceptance Criteria\n\nSetMyCommands is called at startup with the commands the Router actually handles. Failure is logged, not fatal.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:29Z","updated_at":"2026-08-08T14:37:31Z","closed_at":"2026-08-08T14:37:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/150","source_system":"github:https://github.com/samcharles93/archie-core/issues/150:150","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493121-128-2acad290","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.\n\n### Acceptance Criteria\n\nAllowlist 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":2,"issue_type":"task","created_at":"2026-08-08T14:37:23Z","updated_at":"2026-08-08T14:37:26Z","closed_at":"2026-08-08T14:37:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/149","source_system":"github:https://github.com/samcharles93/archie-core/issues/149:149","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493099-127-80cacb10","title":"Telegram: stream LLM replies via sendMessageDraft","description":"Chat replies currently block for the whole LLM turn, then arrive as one message. The typing indicator masks the wait but shows no progress. go-telegram/bot exposes SendMessageDraft (see examples/streaming_draft) and ai-sdk's runtime.ChatStream already returns core.StreamResult with a TextStream \u003c-chan string, so both halves exist -- only the gateway seam is missing, since gateway.LLMResponder is func(ctx, Message) (string, error) and cannot emit partial output.\n\n### Acceptance Criteria\n\nGateway exposes an optional streaming responder; Router falls back to the blocking path when unset. Telegram adapter streams deltas into a draft, then finalises with a formatted SendMessage. Draft updates are throttled to respect Telegram rate limits. Streaming failure falls back to a normal send rather than losing the reply.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:37:18Z","updated_at":"2026-08-08T14:37:21Z","closed_at":"2026-08-08T14:37:22Z","external_ref":"https://github.com/samcharles93/archie-core/issues/148","source_system":"github:https://github.com/samcharles93/archie-core/issues/148:148","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493073-126-94d9735e","title":"Verify: Code-fence-aware message truncation","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:13Z","updated_at":"2026-08-08T14:37:16Z","closed_at":"2026-08-08T14:37:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/147","source_system":"github:https://github.com/samcharles93/archie-core/issues/147:147","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493049-125-05c6a3ae","title":"Verify: TextBatchAggregator for rapid-fire text events","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:08Z","updated_at":"2026-08-08T14:37:11Z","closed_at":"2026-08-08T14:37:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/146","source_system":"github:https://github.com/samcharles93/archie-core/issues/146:146","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493021-124-bf78e658","title":"SendResult struct with retry/error classification","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:03Z","updated_at":"2026-08-08T14:37:05Z","closed_at":"2026-08-08T14:37:06Z","external_ref":"https://github.com/samcharles93/archie-core/issues/145","source_system":"github:https://github.com/samcharles93/archie-core/issues/145:145","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492996-123-4b30bea1","title":"Verify: BasePlatformAdapter interactive UX methods (clarify, approval, pickers)","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:57Z","updated_at":"2026-08-08T14:37:00Z","closed_at":"2026-08-08T14:37:01Z","external_ref":"https://github.com/samcharles93/archie-core/issues/144","source_system":"github:https://github.com/samcharles93/archie-core/issues/144:144","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492974-122-c896cf70","title":"Verify: EphemeralReply type with auto-delete TTL","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:52Z","updated_at":"2026-08-08T14:36:54Z","closed_at":"2026-08-08T14:36:55Z","external_ref":"https://github.com/samcharles93/archie-core/issues/143","source_system":"github:https://github.com/samcharles93/archie-core/issues/143:143","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492949-121-e66acb9d","title":"Verify: Media utilities: cache, validate, deliver images/audio/video/documents","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:46Z","updated_at":"2026-08-08T14:36:49Z","closed_at":"2026-08-08T14:36:50Z","external_ref":"https://github.com/samcharles93/archie-core/issues/142","source_system":"github:https://github.com/samcharles93/archie-core/issues/142:142","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492923-120-205afd82","title":"Verify: MessageDeduplicator with TTL-based dedup cache","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:41Z","updated_at":"2026-08-08T14:36:44Z","closed_at":"2026-08-08T14:36:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/141","source_system":"github:https://github.com/samcharles93/archie-core/issues/141:141","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492899-119-4a36c05d","title":"Verify: Platform capability flags for adapters","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:36Z","updated_at":"2026-08-08T14:36:39Z","closed_at":"2026-08-08T14:36:40Z","external_ref":"https://github.com/samcharles93/archie-core/issues/140","source_system":"github:https://github.com/samcharles93/archie-core/issues/140:140","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492871-118-10b004b7","title":"Verify: BasePlatformAdapter optional methods (typing, edit, delete, media)","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:30Z","updated_at":"2026-08-08T14:36:33Z","closed_at":"2026-08-08T14:36:34Z","external_ref":"https://github.com/samcharles93/archie-core/issues/139","source_system":"github:https://github.com/samcharles93/archie-core/issues/139:139","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492846-117-74830208","title":"Verify: SendResult struct with retry/error classification","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:25Z","updated_at":"2026-08-08T14:36:28Z","closed_at":"2026-08-08T14:36:29Z","external_ref":"https://github.com/samcharles93/archie-core/issues/138","source_system":"github:https://github.com/samcharles93/archie-core/issues/138:138","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492823-116-c2596130","title":"Verify: SessionStore interface and implementation","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:20Z","updated_at":"2026-08-08T14:36:23Z","closed_at":"2026-08-08T14:36:24Z","external_ref":"https://github.com/samcharles93/archie-core/issues/137","source_system":"github:https://github.com/samcharles93/archie-core/issues/137:137","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492794-115-e32e88a6","title":"Verify: SessionContext struct for session metadata","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:15Z","updated_at":"2026-08-08T14:36:18Z","closed_at":"2026-08-08T14:36:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/136","source_system":"github:https://github.com/samcharles93/archie-core/issues/136:136","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492768-114-518ed5eb","title":"Verify: SessionContext struct for session metadata","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:04Z","updated_at":"2026-08-08T14:36:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/135","source_system":"github:https://github.com/samcharles93/archie-core/issues/135:135","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492745-113-664325b9","title":"Verify: SessionSource struct for platform identity","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:01Z","updated_at":"2026-08-08T14:36:02Z","closed_at":"2026-08-08T14:36:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/134","source_system":"github:https://github.com/samcharles93/archie-core/issues/134:134","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492718-112-aee893c7","title":"Rich MessageEvent struct with all gateway fields","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:57Z","updated_at":"2026-08-08T14:35:59Z","closed_at":"2026-08-08T14:36:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/133","source_system":"github:https://github.com/samcharles93/archie-core/issues/133:133","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492690-111-5138a572","title":"Verify: BasePlatformAdapter interface with required methods","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:54Z","updated_at":"2026-08-08T14:35:55Z","closed_at":"2026-08-08T14:35:56Z","external_ref":"https://github.com/samcharles93/archie-core/issues/132","source_system":"github:https://github.com/samcharles93/archie-core/issues/132:132","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492668-110-d16dc2ae","title":"Verify: Rich MessageEvent struct with all gateway fields","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:50Z","updated_at":"2026-08-08T14:35:52Z","closed_at":"2026-08-08T14:35:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/131","source_system":"github:https://github.com/samcharles93/archie-core/issues/131:131","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492640-109-820d4da3","title":"Verify: MessageType enum for gateway messages","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:47Z","updated_at":"2026-08-08T14:35:48Z","closed_at":"2026-08-08T14:35:49Z","external_ref":"https://github.com/samcharles93/archie-core/issues/130","source_system":"github:https://github.com/samcharles93/archie-core/issues/130:130","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492617-108-33718282","title":"TEST Verify: MessageType enum for gateway messages","description":"### Acceptance Criteria\n\nTEST TASK, DELETE ME","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:43Z","updated_at":"2026-08-08T14:35:45Z","closed_at":"2026-08-08T14:35:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/129","source_system":"github:https://github.com/samcharles93/archie-core/issues/129:129","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492590-107-92482ef1","title":"Media utilities: cache, validate, deliver images/audio/video/documents","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:41Z","updated_at":"2026-08-08T14:35:41Z","external_ref":"https://github.com/samcharles93/archie-core/issues/128","source_system":"github:https://github.com/samcharles93/archie-core/issues/128:128","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492559-106-5ea2315d","title":"Code-fence-aware message truncation","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:39Z","updated_at":"2026-08-08T14:35:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/127","source_system":"github:https://github.com/samcharles93/archie-core/issues/127:127","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492528-105-c2b3caab","title":"TextBatchAggregator for rapid-fire text events","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:37Z","updated_at":"2026-08-08T14:35:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/126","source_system":"github:https://github.com/samcharles93/archie-core/issues/126:126","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492498-104-1bde76ae","title":"MessageDeduplicator with TTL-based dedup cache","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:35Z","updated_at":"2026-08-08T14:35:35Z","external_ref":"https://github.com/samcharles93/archie-core/issues/125","source_system":"github:https://github.com/samcharles93/archie-core/issues/125:125","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492468-103-72e44236","title":"SessionStore interface and implementation","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:31Z","updated_at":"2026-08-08T14:35:33Z","closed_at":"2026-08-08T14:35:34Z","external_ref":"https://github.com/samcharles93/archie-core/issues/124","source_system":"github:https://github.com/samcharles93/archie-core/issues/124:124","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492437-102-17365d0d","title":"SessionContext struct for session metadata","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:28Z","updated_at":"2026-08-08T14:35:29Z","closed_at":"2026-08-08T14:35:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/123","source_system":"github:https://github.com/samcharles93/archie-core/issues/123:123","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492407-101-905534ce","title":"MessageType enum for gateway messages","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:24Z","updated_at":"2026-08-08T14:35:26Z","closed_at":"2026-08-08T14:35:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/122","source_system":"github:https://github.com/samcharles93/archie-core/issues/122:122","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492378-100-8edacefc","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\n\n### Acceptance Criteria\n\nNew 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":2,"issue_type":"epic","created_at":"2026-08-08T14:35:22Z","updated_at":"2026-08-08T14:35:22Z","external_ref":"https://github.com/samcharles93/archie-core/issues/121","source_system":"github:https://github.com/samcharles93/archie-core/issues/121:121","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492349-99-6ad44f3f","title":"Add /models (list) gateway-local command","description":"Companion to /model: list available models/providers from the daemon config. Gateway-local (no LLM).\n\n### Acceptance Criteria\n\n/models lists configured providers and model names with the currently-active one flagged.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:19Z","updated_at":"2026-08-08T14:35:20Z","closed_at":"2026-08-08T14:35:21Z","external_ref":"https://github.com/samcharles93/archie-core/issues/120","source_system":"github:https://github.com/samcharles93/archie-core/issues/120:120","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492324-98-bf9bcf76","title":"Add /model gateway-local command to change active LLM model","description":"Sam's gateway requirement: the gateway must handle /model changes without involving the LLM. Add a /model \u003cprovider/model\u003e slash command to gateway.Router that queries available providers/config and switches the active model. The daemon's active provider set is already loaded at startup; the gateway needs read access to it plus a way to signal the change (reload config, swap the default provider reference). Per /goal and Hermes gateway patterns.\n\n### Acceptance Criteria\n\nA chat user can run /model \u003cname\u003e to switch the active LLM model, handled entirely by the gateway without LLM involvement. Response confirms the new model name.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:15Z","updated_at":"2026-08-08T14:35:17Z","closed_at":"2026-08-08T14:35:18Z","external_ref":"https://github.com/samcharles93/archie-core/issues/119","source_system":"github:https://github.com/samcharles93/archie-core/issues/119:119","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492297-97-6bd3efa1","title":"Regression tests: Chat write actions — /approve and /cancel through daemon review gate","description":"archie-core-abg.13 closed with /spawn implemented but /approve and /cancel deferred. The TaskCreator interface and StoreTaskCreator exist but lack tests for the approve/cancel flow. Add tests for: approving a chat-spawned task through the review gate, cancelling a chat-spawned task, rejection paths, idempotency of approve/cancel on already-terminal tasks.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:11Z","updated_at":"2026-08-08T14:35:13Z","closed_at":"2026-08-08T14:35:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/118","source_system":"github:https://github.com/samcharles93/archie-core/issues/118:118","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492273-96-b5271a80","title":"Chat channel write actions: spawn/approve/cancel through daemon review gate","description":"Follow-up to archie-core-abg.5 (channel interface + read-only Telegram). Define the semantics for chat-triggered dispatch (there is no Gitea issue behind a chat-initiated task -- needs its own store/task creation path) and wire /spawn, /approve, /cancel slash commands through the same daemon review/gatekeeping that issue-driven dispatch uses. Blocked on abg.5 (interface must exist first) and should be sequenced after multi-identity daemon core (abg.4) settles how identity maps to chat sessions.\n\n### Acceptance Criteria\n\nA chat slash command can create and dispatch a real task (not just query existing state), going through daemon-side permission checks in code, not agent prompt instructions. /approve and /cancel act on in-flight tasks.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:08Z","updated_at":"2026-08-08T14:35:10Z","closed_at":"2026-08-08T14:35:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/117","source_system":"github:https://github.com/samcharles93/archie-core/issues/117:117","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492253-95-300769c0","title":"Design pass: multi-user support (identity/session model)","description":"Sam wants the architecture to not foreclose multiple people using their own archie agent eventually, even though this isn't required for the first implementation slices. Needs its own design pass: how do chat sessions, identities, and permissions extend beyond single-operator (Sam) without being built now. Per docs/prds/multi-agent-collaboration.md sec.1 item 8 and phase E -- explicitly non-blocking for phases A-D.\n\n### Acceptance Criteria\n\nA design note describes how the identity/session model introduced in archie-core-abg.3/abg.4 and the chat channel work in abg.5/abg.6 could extend to multiple operators later, without requiring changes to this PRD's phases A-D to accommodate it.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:04Z","updated_at":"2026-08-08T14:35:06Z","closed_at":"2026-08-08T14:35:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/116","source_system":"github:https://github.com/samcharles93/archie-core/issues/116:116","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492227-94-c0c98395","title":"Verify: SSH / remote execution agent tool","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:01Z","updated_at":"2026-08-08T14:35:02Z","closed_at":"2026-08-08T14:35:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/115","source_system":"github:https://github.com/samcharles93/archie-core/issues/115:115","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492201-93-2f82d915","title":"SSH / remote execution agent tool","description":"Sam wants agents to be able to SSH into boxes / execute remotely as a capability, not just operate on local worktrees. Design as an explicit, permission-scoped agent tool (environmental constraint, not a prompt rule, per ARCHITECTURE.md design decision #1) -- credentials and target hosts must be daemon-configured, not agent-chosen. Per docs/prds/multi-agent-collaboration.md phase E.\n\n### Acceptance Criteria\n\nAn agent workflow stage can execute a command on a daemon-configured remote host via SSH, scoped to an explicit allowlist of hosts/commands set in daemon config, not free-form agent-chosen targets.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:59Z","updated_at":"2026-08-08T14:34:59Z","external_ref":"https://github.com/samcharles93/archie-core/issues/114","source_system":"github:https://github.com/samcharles93/archie-core/issues/114:114","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492177-92-6c4e48be","title":"Verify: GitLab forge plugin","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:55Z","updated_at":"2026-08-08T14:34:57Z","closed_at":"2026-08-08T14:34:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/113","source_system":"github:https://github.com/samcharles93/archie-core/issues/113:113","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492156-91-7231125d","title":"GitLab forge plugin","description":"internal/forge currently implements GitHub REST polling only; Gitea forge exists per ARCHITECTURE.md 'planned' list -- check current status before starting. Sam wants GitLab addable without it being hardcoded into core: implement as a Layer 2 core plugin against the forge.Forge interface, once the plugin loader (archie-core-abg.2) is wired. Per docs/prds/multi-agent-collaboration.md phase E.\n\n### Acceptance Criteria\n\nA GitLab forge plugin implements forge.Forge and is loadable via the core plugin mechanism, verified against a real or test GitLab instance for issue polling and PR/MR creation.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:53Z","updated_at":"2026-08-08T14:34:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/112","source_system":"github:https://github.com/samcharles93/archie-core/issues/112:112","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492137-90-71540aeb","title":"Discovery session: interview to produce multi-agent collaboration PRD","description":"Sam has no implementation approach in mind yet for multi-agent collaboration. Run a structured discovery interview (an agent grilling Sam with scoped questions, one round at a time — not guessing or proposing a design upfront) to extract: the concrete use cases driving this (what does 'multiple agents working in combination' look like day to day?), constraints from the existing archie-core architecture (daemon/worktree/dispatch/RPC boundaries built in the 5zh epic), and what's explicitly out of scope. Write the findings up as docs/prds/multi-agent-collaboration.md.\n\n### Acceptance Criteria\n\ndocs/prds/multi-agent-collaboration.md exists, reflects Sam's actual answers (not assumptions), and is detailed enough that a future implementation session could break it into scoped, dependency-ordered beads issues the way the 5zh epic was.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:50Z","updated_at":"2026-08-08T15:35:38Z","closed_at":"2026-08-08T15:35:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/111","source_system":"github:https://github.com/samcharles93/archie-core/issues/111:111","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492113-89-a9c21168","title":"Multi-agent collaboration: many agents working together","description":"Support multiple agents working in combination — not just one agent per task in isolation, but agents coordinating with each other (e.g. on the same repo, the same task, or a decomposed set of related tasks). Scope, coordination model, and conflict-avoidance strategy are all undefined — this is exploratory. No implementation approach has been decided yet.\n\n### Acceptance Criteria\n\nA PRD exists (docs/prds/) covering: what 'multiple agents working in combination' means concretely for archie-core, how agents discover/hand off work to each other, how conflicts (same repo, same worktree, shared state) are avoided or resolved, and what changes to daemon/workflow/dispatch are implied. No code changes required to close this epic — the PRD is the deliverable.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:34:48Z","updated_at":"2026-08-08T15:35:40Z","external_ref":"https://github.com/samcharles93/archie-core/issues/110","source_system":"github:https://github.com/samcharles93/archie-core/issues/110:110","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492083-88-a3a3fbff","title":"Evaluate internal/workflow architecture and APIs","description":"Perform a read-only, repository-grounded evaluation of internal/workflow. Identify correctness, definition clarity, reuse, interface ownership, coupling, testability, and maintainability improvements, with concrete evidence and prioritized recommendations.\n\n### Acceptance Criteria\n\nAssessment covers package definitions, consumers, subpackages, tests, and architecture invariants; findings are prioritized with file references and actionable recommendations; no code or git changes are made.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:44Z","updated_at":"2026-08-08T15:35:18Z","closed_at":"2026-08-08T15:35:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/109","source_system":"github:https://github.com/samcharles93/archie-core/issues/109:109","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492059-87-2f0e575d","title":"Regression tests: internal/gate — GateContext, Finding types, Yaegi evaluation","description":"internal/gate/gate.go has zero tests. GateContext and Finding are the runtime types that custom gate scripts receive. The Yaegi evaluation path (gateeval) has tests, but the gate package itself has none. Add tests for type construction, finding validation, and integration with the gate evaluation pipeline.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:40Z","updated_at":"2026-08-08T14:34:42Z","closed_at":"2026-08-08T14:34:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/108","source_system":"github:https://github.com/samcharles93/archie-core/issues/108:108","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492031-86-0fcaccc0","title":"Honcho memory engine as the external-provider proof","description":"Implement an engine backed by Honcho (plastic-labs/honcho, cloned at /work/clones/honcho) to prove the seam holds for a real external backend. Honcho's model is Workspace -\u003e Peer -\u003e Session -\u003e Message with asynchronously derived conclusions queried back as representations; its dual-peer convention has the assistant observe others without self-modelling. Treat this as validation of the contract, not as a dependency of the default install.\n\n### Acceptance Criteria\n\nThe engine satisfies the contract with no changes to the agent loop or gateway. Archie runs unchanged when it is not configured. Its network calls carry timeouts and its failures degrade to reported errors rather than failing a turn. Any mapping decision between Archie sessions/identities and Honcho peers/sessions is documented. Unit tests use httptest and never require a live Honcho instance, per the repo testing rule.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:34:38Z","updated_at":"2026-08-08T14:34:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/107","source_system":"github:https://github.com/samcharles93/archie-core/issues/107:107","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492005-85-03c595e7","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.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:35Z","updated_at":"2026-08-08T15:34:01Z","closed_at":"2026-08-08T15:34:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/106","source_system":"github:https://github.com/samcharles93/archie-core/issues/106:106","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491986-84-5137df75","title":"feat(gateway): version the SQLite session schema before cutover","description":"OpenSQLiteSessionStore currently runs CREATE IF NOT EXISTS statements with no schema version or transactional migration record. Before production wiring, add the smallest deterministic schema-version mechanism so future upgrades cannot silently leave a partially evolved database.\n\n### Acceptance Criteria\n\nA fresh database records the current schema version; opening a supported older fixture migrates transactionally and preserves data; unsupported newer versions fail with an actionable error; migration failure leaves the prior schema/data usable; schema initialization and upgrades are covered by file-backed tests.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:34:33Z","updated_at":"2026-08-09T12:33:31Z","closed_at":"2026-08-09T12:33:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/105","source_system":"github:https://github.com/samcharles93/archie-core/issues/105:105","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491959-83-a36ef6d7","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.\n\n### Acceptance Criteria\n\nTable-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.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:29Z","updated_at":"2026-08-08T15:33:57Z","closed_at":"2026-08-08T15:33:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/104","source_system":"github:https://github.com/samcharles93/archie-core/issues/104:104","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491929-82-a7e181a7","title":"fix(gateway): round-trip SourceID through every SessionStore backend","description":"SQLite persists and returns Message.SourceID, but the NellDB adapter derives MessageID from SourceID and then discards SourceID from the stored document. External correlation metadata therefore changes across backend selection and cannot be exported from NellDB during migration.\n\n### Acceptance Criteria\n\nThe shared conformance suite requires SourceID to round-trip without becoming the canonical MessageID; NellDB persists and reads source_id with empty-field compatibility for older records; SQLite remains conformant; redelivery deduplication and immutable content semantics remain unchanged.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:34:26Z","updated_at":"2026-08-08T15:33:54Z","closed_at":"2026-08-08T15:33:55Z","external_ref":"https://github.com/samcharles93/archie-core/issues/103","source_system":"github:https://github.com/samcharles93/archie-core/issues/103:103","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491902-81-d4c231f6","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.\n\n### Acceptance Criteria\n\nThe 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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:34:22Z","updated_at":"2026-08-08T14:34:24Z","closed_at":"2026-08-08T14:34:25Z","external_ref":"https://github.com/samcharles93/archie-core/issues/102","source_system":"github:https://github.com/samcharles93/archie-core/issues/102:102","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491876-80-74417b6f","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.\n\n### Acceptance Criteria\n\nA 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.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:18Z","updated_at":"2026-08-08T15:33:59Z","closed_at":"2026-08-08T15:34:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/101","source_system":"github:https://github.com/samcharles93/archie-core/issues/101:101","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491855-79-803fa759","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.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:16Z","updated_at":"2026-08-09T12:33:30Z","closed_at":"2026-08-09T12:33:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/100","source_system":"github:https://github.com/samcharles93/archie-core/issues/100:100","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491830-78-20363259","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:34:12Z","updated_at":"2026-08-08T14:34:14Z","closed_at":"2026-08-08T14:34:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/99","source_system":"github:https://github.com/samcharles93/archie-core/issues/99:99","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491805-77-78d888a3","title":"Curator runtime: persistent loop with idle cooldown","description":"Implement the loop that runs a registered curator: continuous operation while work is available, backing off to a configured cooldown when there is nothing to do, waking on new input, and honouring per-curator check-in intervals.\n\n### Acceptance Criteria\n\nA curator with pending input runs without waiting for its next interval; an idle curator consumes no meaningful CPU and wakes on new input. Cooldown and check-in interval are configurable per curator. Loop timing is tested with a fake clock, not wall-clock sleeps. Shutdown is clean and bounded: an in-flight curator pass is cancelled via context and the daemon does not block indefinitely on it. A panicking curator is recovered and isolated from other curators and from the agent loop.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:34:10Z","updated_at":"2026-08-08T15:34:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/98","source_system":"github:https://github.com/samcharles93/archie-core/issues/98:98","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491783-76-9a0778db","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:34:08Z","updated_at":"2026-08-09T12:33:32Z","closed_at":"2026-08-09T12:33:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/97","source_system":"github:https://github.com/samcharles93/archie-core/issues/97:97","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491754-75-8e621216","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:34:04Z","updated_at":"2026-08-08T14:34:06Z","closed_at":"2026-08-08T14:34:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/96","source_system":"github:https://github.com/samcharles93/archie-core/issues/96:96","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491729-74-ee80f814","title":"Daemon: every task/event write fails with 'sdk: revision conflict' after NellDB v0.3.0 bump — counter RMW permanently broken","description":"## Symptom (observed 2026-08-05, task dev session)\n\n- Every 1m poll logs `issue queued` for the same open issue (sam/archie-core#8) again.\n- Every attempt logs `event sink insert failed: err=\"sdk: revision conflict\"` (cmd/archied/main.go:373, the event-sink goroutine calling st.InsertEvent).\n- The daemon's own task consumer logs `nats enqueue failed: err=\"sdk: revision conflict\"` (internal/daemon/daemon.go:599, calling Store.EnqueueIssue) and NAKs; JetStream redelivers to max-deliver 3 (triples of errors every ~2 min in the log).\n- The task doc is never persisted, so the enqueue dedup check always passes and the poll re-queues forever. Work never reaches the agent; dashboard shows a stuck/no-op task.\n\n## Exact cause\n\nCommit 44f914c bumped github.com/samcharles93/NellDB v0.2.5 -\u003e v0.3.0 touching only go.mod/go.sum. v0.3.0 changed the DocDB rev-cache rebuild:\n\n- v0.2.5 sdk/docdb.go reindex() indexed EVERY record by rec.ID, including Archie's meta:task_id_counter / meta:event_id_counter docs.\n- v0.3.0 sdk/docdb.go reindex() skips any id where isInternalID() is true (sdk/replicate.go:841: id[:5] == \"meta:\"), intended only for the SDK's own meta:clock/meta:vector bookkeeping but prefix-matching Archie's counter docs too.\n- v0.3.0 putIn (sdk/docdb.go:208-216) keeps the same conflict rule as v0.2.5: incomingRev != \"\" \u0026\u0026 !exists -\u003e sdk.ErrConflict.\n\nArchie's Adapter.nextCounter (internal/nell/adapter.go:957) is a Get -\u003e mutate -\u003e Put RMW that supplies the _rev returned by Get (joinDoc copies the payload, which putIn re-stamps with _rev). After any restart the counter docs are present in the log but absent from the rev cache, so exists=false and every counter Put conflicts. The counter doc can never be written again, so the cache is never repopulated — the failure is permanent for the lifetime of the DB, every process run, from the first poll.\n\nRepro (standalone, module cache, v0.3.0): open log, Put meta:task_id_counter, close, reopen, Get (rev e.g. \"1-69bfa51d...\"), Put with that rev -\u003e \"sdk: revision conflict\". First run of a fresh DB succeeds (empty-rev init Put is allowed); every subsequent process restart fails.\n\nWhy tests are green: OpenMemory/fresh-log tests initialize the counter via empty-rev Put within the same process; TestPersistenceAcrossRestart reopens a real log but only reads (TaskByIssue) and never exercises the counter RMW after reopen. The production path (restart an existing log, then enqueue) is untested.\n\n## Evidence\n\n- go.mod: github.com/samcharles93/NellDB v0.3.0 (no replace).\n- git show 44f914c --stat: go.mod, go.sum, .gitignore only; internal/nell/ untouched since.\n- Module cache diff !nell!d!b@v0.2.5 vs @v0.3.0: sdk/docdb.go reindex()/putIn(), sdk/replicate.go isInternalID.\n- /tmp/nell-repro: deterministic ErrConflict on counter RMW after reopen.\n\n## Fix direction\n\nOptions, in order of preference: (1) pin back to v0.2.5 (verified-2026-07-28 semantics) until adapter is migrated; (2) stop supplying _rev in nextCounter (drop rev from the RMW doc before Put — v0.3.0 continues the chain from the cached rev when incomingRev == \"\"), but that breaks the MVCC chain for the counter when the cache lacks it; (3) upstream: isInternalID should match exact SDK ids (meta:clock, meta:vector), not the meta: prefix, or reindex should index meta docs. Any fix must add a red test: open persisted log, EnqueueIssue, reopen, EnqueueIssue again -\u003e no conflict.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:34:01Z","updated_at":"2026-08-08T14:34:03Z","closed_at":"2026-08-08T14:34:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/95","source_system":"github:https://github.com/samcharles93/archie-core/issues/95:95","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491701-73-7673d55f","title":"Restore a clean repository-wide golangci-lint baseline","description":"Repository-wide golangci-lint currently reports 39 pre-existing findings (32 errcheck and 7 staticcheck) across NATS/RPC/container code and older tests. Remediate the findings without weakening lint configuration so golangci-lint run ./... is a reliable required gate.\n\n### Acceptance Criteria\n\ngolangci-lint run ./... exits successfully with no findings; affected cleanup/error paths handle or explicitly document ignored errors; existing race tests remain green.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:33:57Z","updated_at":"2026-08-08T14:33:59Z","closed_at":"2026-08-08T14:34:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/94","source_system":"github:https://github.com/samcharles93/archie-core/issues/94:94","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491672-72-4a4e5b2b","title":"Remove source-project references from Archie","description":"Remove every tau reference outside the explicitly preserved Beads data and docs-2/README.md. Delete copied product-specific documentation and accompanied rationale rather than mechanically renaming it. Retain reusable documentation-generation and VitePress scaffolding only after removing source-specific coupling. Update code, tests, archives, and architecture documents so archie-core contains no unauthorized tau references.\n\n### Acceptance Criteria\n\nrg 'tau' -ow excluding .beads/** and docs-2/README.md returns zero; retained tools and documentation scaffolding contain no source-project imports, paths, product claims, or rationale; relevant validation passes.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:33:54Z","updated_at":"2026-08-08T15:34:22Z","closed_at":"2026-08-08T15:34:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/93","source_system":"github:https://github.com/samcharles93/archie-core/issues/93:93","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491645-71-2d81161f","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.\n\n### Acceptance Criteria\n\nSelecting any model replaces the picker with metadata confirmation and the Telegram edit request omits reply_markup when clearing controls.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:33:50Z","updated_at":"2026-08-08T14:33:52Z","closed_at":"2026-08-08T14:33:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/92","source_system":"github:https://github.com/samcharles93/archie-core/issues/92:92","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491624-70-91cbc6a8","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:33:47Z","updated_at":"2026-08-08T14:33:48Z","closed_at":"2026-08-08T14:33:49Z","external_ref":"https://github.com/samcharles93/archie-core/issues/91","source_system":"github:https://github.com/samcharles93/archie-core/issues/91:91","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491603-69-e341793a","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":2,"issue_type":"bug","created_at":"2026-08-08T14:33:43Z","updated_at":"2026-08-08T14:33:45Z","closed_at":"2026-08-08T14:33:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/90","source_system":"github:https://github.com/samcharles93/archie-core/issues/90:90","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491577-68-07f7730b","title":"Seed a default SOUL without clobbering user edits","description":"Write a starter SOUL on first run and allow upgrading untouched scaffolding in place, following Hermes' is_legacy_template_soul approach: compare normalised content against known-shipped templates, which carry zero user intent, and only replace on an exact match.\n\n### Acceptance Criteria\n\nFirst run seeds a documented starter SOUL. A SOUL matching a known shipped template can be upgraded in place. A SOUL the user has edited in any way is never modified. Comparison normalises line endings and trailing whitespace so a CRLF checkout does not defeat it.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:33:41Z","updated_at":"2026-08-08T14:33:41Z","external_ref":"https://github.com/samcharles93/archie-core/issues/89","source_system":"github:https://github.com/samcharles93/archie-core/issues/89:89","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491549-67-7357f187","title":"Register storerpc/forgerpc/worktreerpc servers in archied startup","description":"Depends on the TaskContext interface refactor. cmd/archied/main.go builds the Daemon with Store/Forge/Trees but never registers the storerpc.Server/forgerpc.Server/worktreerpc.Server handlers, so archie-agent's RPC calls currently have no responder in production. Wire all three Register(nc) calls into archied's startup when cfg.NATS is configured, alongside the existing NATS client connect.\n\n### Acceptance Criteria\n\nWhen [nats] is configured, archied subscribes to all storerpc/forgerpc/worktreerpc subjects at startup; an archie-agent container can successfully call Store/Forge/worktree operations against a running archied.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:33:38Z","updated_at":"2026-08-08T14:33:39Z","closed_at":"2026-08-08T14:33:40Z","external_ref":"https://github.com/samcharles93/archie-core/issues/88","source_system":"github:https://github.com/samcharles93/archie-core/issues/88:88","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491521-66-0ded6f7d","title":"daemon.go: hand off whole task to archie-agent in sandboxed NATS+container mode","description":"Depends on the archie-agent full-task handler existing. internal/daemon/daemon.go's process() currently always calls workflow.Route/workflow.Run itself, dispatching per-stage LLM calls to d.Agent (NATSRunner does this over NATS today). When d.Nats != nil \u0026\u0026 d.ContainerPool != nil (the sandboxed path this whole PRD phase targets), process() should instead publish one 'run whole task' message to archie-agent and await its completion report, skipping local workflow.Route/workflow.Run entirely. inprocess/subprocess modes (no container pool) keep calling workflow.Run in the daemon exactly as today — this only changes behavior for the fully-sandboxed path.\n\n### Acceptance Criteria\n\nWith containers enabled, daemon.process() delegates the entire task to archie-agent in one round trip; without containers, behavior is unchanged (verified by existing daemon tests continuing to pass).","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:33:34Z","updated_at":"2026-08-08T14:33:36Z","closed_at":"2026-08-08T14:33:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/87","source_system":"github:https://github.com/samcharles93/archie-core/issues/87:87","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491495-65-603b3823","title":"archie-agent: run full task (workflow.Route + workflow.Run) via RPC-backed TaskContext","description":"The actual stage-loop move for archie-core-5zh, depending on the TaskConfig payload and TaskContext interface refactor. cmd/archie-agent gains a handler for a new 'run whole task' NATS message (task summary + TaskConfig + repo config, no secrets). On receipt it: builds its own workflow.Registry via skillbuild.BuildRegistry against its mounted worktree (/data/worktree — same pattern the daemon already uses, no registry needs to cross the wire); calls workflow.Route itself; builds a TaskContext using storerpc.Client (Store), forgerpc.Client (Forge), and a hybrid Trees (worktreerpc.Client for Prepare/Push, a local *worktree.Manager with no token for CommitAll/Diff/ChangedFiles/ChangedLines against the bind-mounted dir); calls workflow.Run; reports completion once instead of round-tripping per stage.\n\n### Acceptance Criteria\n\nWhen agent.mode=nats and containers are enabled, archie-agent runs an entire task's workflow (all stages) per invocation, not one stage per round trip; inprocess/subprocess modes are unaffected.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:33:31Z","updated_at":"2026-08-08T14:33:32Z","closed_at":"2026-08-08T14:33:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/86","source_system":"github:https://github.com/samcharles93/archie-core/issues/86:86","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491474-64-f086bf4c","title":"TaskContext interface refactor: Forge/Store/Trees as trimmed interfaces","description":"Groundwork for archie-core-5zh.4. workflow.TaskContext currently types Forge/Store/Trees as concrete daemon types (forge.Forge interface already, *store.Store, *worktree.Manager). Define trimmed interfaces in internal/workflow scoped to exactly the methods stages call (Forge: Comment/CloseIssue/CreatePR/SetStateLabel; Store: Update/Transition; Trees: Prepare/CommitAll/Push/Diff/ChangedFiles/ChangedLines) so storerpc.Client, forgerpc.Client, and a worktreerpc-backed implementation can satisfy them from inside archie-agent, while *store.Store/*worktree.Manager and the real forge.Forge implementations keep satisfying them unchanged for the daemon's existing inprocess/subprocess paths.\n\n### Acceptance Criteria\n\nTaskContext.Forge/Store/Trees are interface-typed; daemon.go compiles and all existing tests pass unchanged (concrete types satisfy the new interfaces structurally); no behavior change for inprocess/subprocess modes.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:33:27Z","updated_at":"2026-08-08T14:33:29Z","closed_at":"2026-08-08T14:33:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/85","source_system":"github:https://github.com/samcharles93/archie-core/issues/85:85","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491449-63-75cdd245","title":"Curated TaskConfig payload for archie-agent (no secrets)","description":"Groundwork for archie-core-5zh.4. workflow.TaskContext.Cfg (config.Config) is read throughout stages (Models, Budgets, Dispatch incl. label mapping, DiffCapLines, Notify.Webhook, Forge.Host) but the full Config also carries forge/NATS credentials that must never enter the agent container. Add a config.TaskConfig struct — same field names/shapes as the subset config.Config exposes (Models, Budgets, Dispatch, DiffCapLines, Notify, Forge) — with json tags, plus a constructor (e.g. config.Config.ForTask()) that builds it from the daemon's live config. Add json tags to config.Repo's remaining fields (only AllowConcurrent has them today) since tc.Repo also needs to cross the wire.\n\n### Acceptance Criteria\n\nconfig.TaskConfig marshals/unmarshals via JSON and carries exactly the fields workflow stages read; no token/credential field is reachable from it; config.Repo fully round-trips through JSON.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:33:23Z","updated_at":"2026-08-08T14:33:25Z","closed_at":"2026-08-08T14:33:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/84","source_system":"github:https://github.com/samcharles93/archie-core/issues/84:84","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491429-62-088b752f","title":"Move workflow.Route/workflow.Run stage loop into archie-agent","description":"Final step of archie-core-5zh, depends on the Store/Forge/push RPC proxies existing. Move workflow.Route + workflow.Run's stage-loop execution from internal/daemon/daemon.go's process() into cmd/archie-agent, using the RPC proxies for Store/Forge/push and reimplementing CustomStages discovery (wfeval.Discover) agent-side against the already-mounted worktree. daemon.process() keeps worktree prepare + container acquire/release, then hands off the whole task to archie-agent in one NATS round trip instead of one round trip per stage.\n\n### Acceptance Criteria\n\nworkflow.Route and workflow.Run execute inside archie-agent, not archied, when agent.mode=nats; archie-agent handles a full task (not a single stage) per invocation; inprocess/subprocess modes keep working unchanged.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:33:20Z","updated_at":"2026-08-08T14:33:22Z","closed_at":"2026-08-08T14:33:23Z","external_ref":"https://github.com/samcharles93/archie-core/issues/83","source_system":"github:https://github.com/samcharles93/archie-core/issues/83:83","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491398-61-00fd3006","title":"Move workflow.Route/workflow.Run stage loop into archie-agent","description":"Final step of archie-core-5zh, depends on the Store/Forge/push RPC proxies existing. Move workflow.Route + workflow.Run's stage-loop execution from internal/daemon/daemon.go's process() into cmd/archie-agent, using the RPC proxies for Store/Forge/push and reimplementing CustomStages discovery (wfeval.Discover) agent-side against the already-mounted worktree. daemon.process() keeps worktree prepare + container acquire/release, then hands off the whole task to archie-agent in one NATS round trip instead of one round trip per stage.\n\n### Acceptance Criteria\n\nworkflow.Route and workflow.Run execute inside archie-agent, not archied, when agent.mode=nats; archie-agent handles a full task (not a single stage) per invocation; inprocess/subprocess modes keep working unchanged.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:30:27Z","updated_at":"2026-08-08T14:30:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/82","source_system":"github:https://github.com/samcharles93/archie-core/issues/82:82","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491369-60-9827e75e","title":"Worktree push RPC proxy: archie-agent → archied for git push","description":"Phase 1 groundwork for archie-core-5zh. worktree.Manager.Push needs the forge HTTPS push token (held daemon-side, used via an askpass helper). Trees.Prepare/CommitAll/Diff/ChangedFiles/ChangedLines are local git operations against the already-mounted worktree and can run agent-side unchanged (containers already bind-mount /data/worktree) — only Push needs to be proxied back to the daemon, which holds the credential.\n\n### Acceptance Criteria\n\narchie-agent can request a git push over NATS; archied performs the authenticated push using its held token and replies with success/failure; the push token is never sent to or stored in the agent container.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:30:22Z","updated_at":"2026-08-08T14:30:25Z","closed_at":"2026-08-08T14:30:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/81","source_system":"github:https://github.com/samcharles93/archie-core/issues/81:81","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491347-59-5ee3ba8f","title":"Forge RPC proxy: archie-agent → archied for forge API calls","description":"Phase 1 groundwork for archie-core-5zh. Stages call Forge.SetStateLabel/Comment/CreatePR/CloseIssue/CreateIssue/React/RepliesAfter mid-workflow. Forge holds live API tokens (Gitea/GitHub) that must stay daemon-side per the PRD's 'daemon never runs untrusted code, owns all secrets' boundary. Once workflow.Run moves into archie-agent, these calls need to become NATS request/reply RPCs to the daemon rather than shipping forge credentials into the agent container.\n\n### Acceptance Criteria\n\narchie-agent can invoke the forge.Forge interface methods used by workflow stages over NATS; archied executes them against the real forge client and replies; no forge API tokens are present in the agent container.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:30:17Z","updated_at":"2026-08-08T14:30:20Z","closed_at":"2026-08-08T14:30:21Z","external_ref":"https://github.com/samcharles93/archie-core/issues/80","source_system":"github:https://github.com/samcharles93/archie-core/issues/80:80","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491320-58-16416f9c","title":"Store RPC proxy: archie-agent → archied for task state mutations","description":"Phase 1 groundwork for archie-core-5zh. workflow.Run calls tc.Store.Update every stage and tc.Store.Transition on terminal outcomes — Store wraps a direct SQLite *sql.DB handle that only the daemon owns. Once workflow.Run moves into archie-agent, these calls need to become NATS request/reply RPCs to the daemon (the sole DB owner), reusing the existing AgentRequestMessage/reply-inbox plumbing pattern (internal/agentexec/nats.go) rather than giving the agent container direct DB access.\n\n### Acceptance Criteria\n\narchie-agent can call Store.Update and Store.Transition equivalents over NATS; archied executes them against SQLite and replies; no direct DB access from the agent container.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:30:13Z","updated_at":"2026-08-08T14:30:15Z","closed_at":"2026-08-08T14:30:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/79","source_system":"github:https://github.com/samcharles93/archie-core/issues/79:79","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491292-57-9f430b7d","title":"Promote archie-agent to per-task process; move workflow routing out of archied","description":"cmd/archie-agent exists but only executes one workflow stage per invocation over the internal/agentexec stdin/stdout JSON protocol (v1). Phase 1 of the PRD requires promoting it to the PRD's per-task process model, moving workflow.Route/workflow.Run out of archied and into archie-agent.\n\n### Acceptance Criteria\n\nworkflow.Route and workflow.Run execute inside archie-agent, not archied; archie-agent handles a full task (not a single stage) per invocation.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:30:08Z","updated_at":"2026-08-08T14:30:10Z","closed_at":"2026-08-08T14:30:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/78","source_system":"github:https://github.com/samcharles93/archie-core/issues/78:78","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491267-56-5f42c656","title":"Disable automatic forge comments and state labels","description":"Remove automatic plan/progress/retry/dead/state-label noise from normal execution. Preserve internal logs/events and retain only comments explicitly required by an operator decision flow, exposed through messaging or Web UI.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:30:03Z","updated_at":"2026-08-08T14:30:52Z","closed_at":"2026-08-08T14:30:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/77","source_system":"github:https://github.com/samcharles93/archie-core/issues/77:77","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491240-55-307c90b4","title":"Document Hermes capabilities missing from Archie","description":"Investigate Hermes' available features and commands, compare them with Archie, and publish a simple Markdown TODO checklist excluding Kanban.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:29:58Z","updated_at":"2026-08-08T14:30:01Z","closed_at":"2026-08-08T14:30:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/76","source_system":"github:https://github.com/samcharles93/archie-core/issues/76:76","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491213-54-c614e36e","title":"Configuration boundary and ownership review","description":"Run the first focused architecture campaign for the configuration refactor. Trace the current TOML/YAML loaders, defaults, validation, overlays, secret references, identity/repository settings, worker snapshots, container/NATS passthrough, and every production consumer. Produce a field-level current-to-target ownership ledger and decide the smallest behavior-preserving migration slice. Do not edit runtime code until ownership, input DTO boundaries, provenance requirements, schema generation boundary, compatibility semantics, and deletion criteria are recorded.\n\n### Acceptance Criteria\n\nA reproducible current-state trace covers entrypoints, loaders, consumers, process boundaries, tests, deployment passthrough, and decoded-but-unwired fields; every in-scope setting has one current owner, target owner, scope, validation/provenance behavior, and migration disposition; base/overlay and secret compatibility semantics are explicit; the first implementation slice has an observable outcome, bounded change cone, parity tests, rollback, and deletion criterion; no unresolved semantic decision is left for the implementer to invent.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:29:54Z","updated_at":"2026-08-08T15:34:20Z","closed_at":"2026-08-08T15:34:21Z","external_ref":"https://github.com/samcharles93/archie-core/issues/75","source_system":"github:https://github.com/samcharles93/archie-core/issues/75:75","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491190-53-fd55949d","title":"Docsgen: emit deterministic contract data JSON","description":"Begin the generated-documentation implementation with the smallest vertical slice: normalize the existing Archie contract schemas into deterministic JSON under docs-2/data/generated for VitePress consumption, without generating Markdown pages. Preserve the nested tools module and existing source-of-truth imports.\n\n### Acceptance Criteria\n\nA failing test first proves docsgen emits valid generated JSON at the data path; repeated generation is byte-identical; tools tests and vet pass; generated-documentation.md reflects the agreed data-loader architecture.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:29:49Z","updated_at":"2026-08-08T15:35:11Z","closed_at":"2026-08-08T15:35:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/74","source_system":"github:https://github.com/samcharles93/archie-core/issues/74:74","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491161-52-8eba0a42","title":"Define target project organisation and restructuring rules","description":"Run a package-by-package architecture grilling session, establish the target DDD and semi-microservice organisation, record strict restructuring requirements and package destinations, and produce docs/prds/01-project-management.md as the durable handoff.\n\n### Acceptance Criteria\n\nThe PRD records agreed project-wide organisation rules, bounded-context and service/plugin boundaries, dependency constraints, migration principles, and the destination of each reviewed package. Decisions are confirmed one at a time with the user before the document is finalized.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:29:44Z","updated_at":"2026-08-08T15:34:24Z","closed_at":"2026-08-08T15:34:25Z","external_ref":"https://github.com/samcharles93/archie-core/issues/73","source_system":"github:https://github.com/samcharles93/archie-core/issues/73:73","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491134-51-17a55e60","title":"install.sh delegates config generation to archied setup","description":"Remove the TOML-generating branches from install.sh and call the binary it just built. Ends the class of bug where the installer's idea of the config schema drifts from the daemon's.\n\n### Acceptance Criteria\n\ninstall.sh contains no TOML templates and no sed-patching of config files. It invokes archied setup for a fresh install and skips it when a config already exists. A non-interactive install still produces a valid config or fails loudly. The forge_block helper and its awk splice are deleted.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:29:41Z","updated_at":"2026-08-08T14:29:41Z","external_ref":"https://github.com/samcharles93/archie-core/issues/72","source_system":"github:https://github.com/samcharles93/archie-core/issues/72:72","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491106-50-63558a04","title":"Enforce typed plugin engine architecture rule","description":"Cement the repository invariant that a plugin engine is a typed capability family with an owning registry/manager and lifecycle semantics, never a generic daemon hook. Add one canonical architecture rule referenced by both AGENTS.md and CLAUDE.md, record it in Beads memory, and add an executable architecture test that prevents drift without touching the concurrently edited secret/config packages.\n\n### Acceptance Criteria\n\nA canonical rule defines typed domain contract, owning registry/manager, lifecycle and health expectations, narrow host access, and trust boundaries; AGENTS.md and CLAUDE.md both surface the rule through their shared source; an architecture test fails for generic plugin-hook expansion or an engine interface without a family manager; focused tests and task check pass; fresh adversarial review has no surviving findings.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:29:37Z","updated_at":"2026-08-08T15:34:37Z","closed_at":"2026-08-08T15:34:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/71","source_system":"github:https://github.com/samcharles93/archie-core/issues/71:71","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491079-49-3c54bae3","title":"Port tau internal/indexing (codesearch) into archie-core","description":"First slice of the tau cherry-pick strategy. Copy-and-mutate (NOT extract to pkg/ - Sam's decision: exporting would force designing metrics/session/logger seams upfront before archie-core knows which it wants differently).\n\ntau/internal/indexing is the cheapest high-value lift: 512 LoC, one file, and its only tau coupling is 3 calls to config.WorkspaceIndexDir()/WorkspaceIndexDBPath(). Nothing else in tau imports it.\n\nMutations: replace the global config path helpers with explicit constructor params (archie-core passes config, no globals); add the workspace-codesearch helper subcommand to archied since the manager deliberately runs google/codesearch in a child process (upstream fatal exits + mmap leaks must not kill the daemon).\n\nEach lifted file carries a provenance header (source path + tau commit) so a future refresh is a diff, not archaeology.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:29:32Z","updated_at":"2026-08-08T14:31:17Z","closed_at":"2026-08-08T14:31:18Z","external_ref":"https://github.com/samcharles93/archie-core/issues/70","source_system":"github:https://github.com/samcharles93/archie-core/issues/70:70","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491053-48-fe78cd53","title":"Gateway: unknown slash commands must not reach the LLM","description":"Unknown slash commands currently fall through to free-text LLM chat, causing fabricated command behavior such as /memories claims and false statements about files or model identity. Make slash command recognition deterministic and answer unknown commands locally with guidance to /help, while preserving free-text chat and supported Telegram bootstrap commands.\n\n### Acceptance Criteria\n\nAny unrecognized leading slash command is answered locally and never invokes or streams from the LLM. The reply identifies the command as unknown and points to /help. Recognized commands and ordinary free text retain existing behavior. Telegram /start has an explicit deterministic behavior. Tests cover unknown commands with arguments and @gateway mentions, streaming routing, /start, and LLM non-invocation.","status":"open","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:29:29Z","updated_at":"2026-08-08T14:30:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/69","source_system":"github:https://github.com/samcharles93/archie-core/issues/69:69","metadata":null,"labels":["bug","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491030-47-0e6fd3b6","title":"[EPIC] SOUL file: user-authored agent identity","description":"Move Archie's identity and tone out of compiled Go constants and into a user-editable SOUL file. Root cause of a real defect on 2026-07-29: heyarchie answered 'Hey are you there?' with 'I'm here. What do you need?', which reads as demanding the user justify getting in touch. The fix required editing DefaultPersonas() in internal/gateway/persona.go and rebuilding -- personality is not tunable without a compile. Modelled on Hermes (SOUL.md occupies the identity slot in the stable tier, DEFAULT_AGENT_IDENTITY is the fallback when absent, re-read per message so no restart is needed) and openclaw, which injects SOUL.md alongside AGENTS.md.\n\n### Design\n\nTHE BOUNDARY IS THE POINT. The existing layering rule (recorded in the chat-system-prompt-design memory) is that PersonaRegistry is the style layer only and rules live in the template, so switching persona cannot strip the agent's rules or tool inventory. SOUL inherits exactly that constraint: it owns identity, name, register and warmth, and must not be able to touch core_rules -- otherwise 'be terse' in a SOUL silently disarms the no-fabrication rules. Steal from Hermes: is_legacy_template_soul upgrades untouched scaffolding in place but never overwrites a SOUL the user actually edited. This is the first of the three identity layers agreed with Sam on 2026-07-30: invariants (template, nobody edits at runtime) / SOUL (user-authored) / representation (curator-derived, proposes only).\n\n### Acceptance Criteria\n\nA user can name their agent and define its personality by editing a file, with no rebuild and no restart. An absent or empty SOUL falls back to the shipped default identity. SOUL cannot weaken the invariants: \u003cinstruction_precedence\u003e, \u003ccore_rules\u003e, the \u003ctools\u003e block and \u003cenv\u003e stay in the template and remain unreachable from SOUL, enforced by a test. A SOUL the user has customised is never overwritten by an upgrade.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:29:27Z","updated_at":"2026-08-08T14:29:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/68","source_system":"github:https://github.com/samcharles93/archie-core/issues/68:68","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637491000-46-c3ca37cf","title":"Make Archie the user-facing identity","description":"Remove internal gateway terminology from Telegram replies and establish an Archie default system prompt so chat does not drift into generic assistant identity.\n\n### Acceptance Criteria\n\nTelegram help and restart copy call the assistant Archie; default chat persona identifies Archie and forbids unverified claims or vendor impersonation; tests and task check pass.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:29:22Z","updated_at":"2026-08-08T14:30:55Z","closed_at":"2026-08-08T14:30:56Z","external_ref":"https://github.com/samcharles93/archie-core/issues/67","source_system":"github:https://github.com/samcharles93/archie-core/issues/67:67","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490974-45-ede6ebfa","title":"worktree.Manager gets an empty token when the forge degrades","description":"Since 518a1a0 a missing forge credential disables the forge instead of stopping archied. resolveForge returns an empty token in that case and cmd/archied/main.go still hands it to worktree.Manager{Token: token}. If repos are configured while the forge is disabled, clone/push fails at push time rather than at startup. This is the intended trade -- a deferred error beats a crash loop -- but the failure is currently discovered late and its message will not explain that the cause is an unconfigured forge.\n\n### Acceptance Criteria\n\nA worktree operation attempted with no forge credential fails with a message naming the missing forge configuration as the cause, rather than a bare git transport error. Alternatively the manager refuses the operation up front. Either way the operator can tell why from the error alone.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:29:17Z","updated_at":"2026-08-08T14:30:57Z","closed_at":"2026-08-08T14:30:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/66","source_system":"github:https://github.com/samcharles93/archie-core/issues/66:66","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490947-44-52870687","title":"Expose quiet execution and decision controls in messaging and Web UI","description":"Make the no-comment/no-label behavior and human approval or retry decisions controllable through existing messaging channels and the Web UI. Do not reintroduce issue comments as the control plane; show the same persisted task state and actions in both surfaces.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:29:12Z","updated_at":"2026-08-08T14:31:19Z","closed_at":"2026-08-08T14:31:20Z","external_ref":"https://github.com/samcharles93/archie-core/issues/65","source_system":"github:https://github.com/samcharles93/archie-core/issues/65:65","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490923-43-d4bb914b","title":"MCP servers are re-fetched from npm on every daemon start","description":"config.docker.toml launches desktop-commander with 'npx -y @wonderwhy-er/desktop-commander@0.2.46'. The container has no persistent npm cache, so every restart re-resolves and re-downloads the package and its puppeteer browser payload. That is slow, makes startup depend on npm registry availability, and turns a registry outage or a yanked version into a daemon outage. It also amplified the crash loop observed on 2026-07-30, since each restart repeated the whole download.\n\n### Acceptance Criteria\n\nDaemon startup does not depend on reaching the npm registry. Either the MCP servers are installed into the image at build time and invoked directly, or the npm cache is persisted across restarts. Startup time no longer scales with the size of the server's dependency tree.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:29:09Z","updated_at":"2026-08-08T14:29:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/64","source_system":"github:https://github.com/samcharles93/archie-core/issues/64:64","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490896-42-a32bec11","title":"Web Chat: expose provider-aware active model and personality selectors","description":"Make the Web Chat selector state match Telegram: expose the active model/provider and the active personality for the current Web session, group models by provider when the manager supports it, and render those states in the UI. Preserve graceful fallback for managers without provider metadata.\n\n### Design\n\nUse the existing ModelManager, ProviderModelManager, and PersonaRegistry contracts. Keep the existing models/personas fields backward compatible while adding structured provider/active fields.\n\n### Acceptance Criteria\n\nSessions API returns active model/provider data and current-session personality state; provider-aware model options are grouped and selectable; selecting a provider/model/personality updates the shared gateway state; focused Go and UI/browser tests cover active and fallback states.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:29:05Z","updated_at":"2026-08-08T14:31:21Z","closed_at":"2026-08-08T14:31:22Z","external_ref":"https://github.com/samcharles93/archie-core/issues/63","source_system":"github:https://github.com/samcharles93/archie-core/issues/63:63","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490869-41-01cbe0c4","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","created_at":"2026-08-08T14:29:00Z","updated_at":"2026-08-08T14:31:23Z","closed_at":"2026-08-08T14:31:24Z","external_ref":"https://github.com/samcharles93/archie-core/issues/62","source_system":"github:https://github.com/samcharles93/archie-core/issues/62:62","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490840-40-590ad4cb","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","created_at":"2026-08-08T14:28:55Z","updated_at":"2026-08-08T14:31:25Z","closed_at":"2026-08-08T14:31:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/61","source_system":"github:https://github.com/samcharles93/archie-core/issues/61:61","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490815-39-45528ea3","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":2,"issue_type":"feature","created_at":"2026-08-08T14:28:52Z","updated_at":"2026-08-08T14:31:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/60","source_system":"github:https://github.com/samcharles93/archie-core/issues/60:60","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490788-38-90d76956","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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:28:47Z","updated_at":"2026-08-08T14:31:29Z","closed_at":"2026-08-08T14:31:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/59","source_system":"github:https://github.com/samcharles93/archie-core/issues/59:59","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490760-37-147373cd","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","created_at":"2026-08-08T14:28:43Z","updated_at":"2026-08-08T14:31:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/58","source_system":"github:https://github.com/samcharles93/archie-core/issues/58:58","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490735-36-521c78cb","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","created_at":"2026-08-08T14:28:38Z","updated_at":"2026-08-08T14:31:32Z","closed_at":"2026-08-08T14:31:33Z","external_ref":"https://github.com/samcharles93/archie-core/issues/57","source_system":"github:https://github.com/samcharles93/archie-core/issues/57:57","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490708-35-38424ead","title":"Replace Skills with a bundled Extensions center","description":"Build an Extensions center with typed Skills, Workflows, Tools/MCP, Plugins, and Integrations inventories. Add a compiled bundled catalog whose optional capabilities are disabled by default, required core capabilities are non-disableable, configuration-backed enablement requires restart, and runtime state distinguishes available, enabled, active, degraded, skipped, and pending restart. Keep plugin.Plugin metadata-only and use family-owned controllers.\n\n### Acceptance Criteria\n\nExtensions inventories reconcile configured, bundled, discovered, and active state truthfully. Optional bundled capabilities can be enabled or disabled through safe configuration saves; core capabilities cannot. Provider failures and capability health are visible, integrations link to Configuration, and no remote/arbitrary-URL installation path exists. Architecture guard, tests, UI build, task check, viewport inspection, and fresh adversarial review pass.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:28:36Z","updated_at":"2026-08-08T14:31:34Z","external_ref":"https://github.com/samcharles93/archie-core/issues/56","source_system":"github:https://github.com/samcharles93/archie-core/issues/56:56","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490675-34-0f23cd4a","title":"Add safe structured configuration and truthful channel state","description":"Select TOML files, YAML files, or configuration directories through one production format-neutral resolver while retaining the TOML default; expose secret-free effective configuration, schemas, provenance, revision, pending/restart state; validate and atomically patch the owning highest-precedence source with comment preservation and backups; move memory status into Configuration; and report channel lifecycle and supported reload actions through a typed manager.\n\n### Acceptance Criteria\n\nProduction composition accepts TOML, YAML, and directory sources with exact precedence/provenance. Candidate validation and optimistic saves handle invalid input, stale/concurrent revisions, permissions and write failures without secret disclosure or running-config mutation. Comments and untouched fields survive. Memory redirects into Configuration. Channels distinguish configured from running health and only supported reloads are actionable. Tests, UI build, task check, viewport inspection, and fresh adversarial review pass.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:28:33Z","updated_at":"2026-08-08T15:48:11Z","closed_at":"2026-08-08T15:48:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/55","source_system":"github:https://github.com/samcharles93/archie-core/issues/55:55","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490645-33-d23934fe","title":"Separate daemon logs and activity and expose executable workflows","description":"Provide a logging-owned bounded daemon slog feed with live stream and optional durable history, keep lifecycle activity on the existing events stream, make selectors truthful, preserve live entries across history refresh, expose the executable workflow registry including zero-run definitions and statistics, and admit Start work requests through normal work intake. Include audit activity for work requests.\n\n### Acceptance Criteria\n\nLive daemon logs continue when durable file history is disabled and the UI explains that limitation. History refresh does not clear or duplicate live entries. Activity remains separate. Workflow inventory includes installed zero-run workflows and ordered stages. Start work validates identity, repository, workflow, title, and instructions and produces an ordinary admitted queued task. Tests, UI build, task check, viewport inspection, and fresh adversarial review pass.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:28:30Z","updated_at":"2026-08-08T15:48:11Z","closed_at":"2026-08-08T15:48:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/54","source_system":"github:https://github.com/samcharles93/archie-core/issues/54:54","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490619-32-2293a24d","title":"Make navigation and task controls operational","description":"Deliver the immediate operator UX slice: always-labelled responsive navigation with compact Jump to search; direct dashboard attention/running links; versioned Setup complete dismissal; lifecycle-safe task controls in expanded and responsive surfaces; and shared taskstate validation for cancel, stop, approve, reject, retry, abandon, PR links, and per-task archive. Preserve same-origin authenticated JSON mutations and emit activity events.\n\n### Acceptance Criteria\n\nNavigation labels and Jump to remain keyboard and screen-reader usable at wide, constrained, 899px, and mobile widths. Dashboard links focus the correct task/filter. Setup dismissal resets when setup becomes incomplete. Every task state exposes only its valid actions and backend optimistic-state checks reject stale or illegal actions. Relevant tests, UI build, task check, live viewport inspection, and fresh adversarial review pass.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:28:25Z","updated_at":"2026-08-08T15:33:48Z","closed_at":"2026-08-08T15:33:49Z","external_ref":"https://github.com/samcharles93/archie-core/issues/53","source_system":"github:https://github.com/samcharles93/archie-core/issues/53:53","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490593-31-bcb624f5","title":"Keep streamed local-command replies visible in Web chat","description":"The Web chat receives a successful SSE done response for local commands such as /status, renders it, then immediately calls selectSession, which clears the transcript and reloads persisted messages. Local-command exchanges are not persisted, so the command and response disappear. Preserve the live transcript after a successful send while still refreshing session metadata.\n\n### Acceptance Criteria\n\nSending /status in the Web chat leaves both the user command and returned status visible; normal streamed replies remain visible; session catalogue metadata still refreshes; focused frontend tests and the repository quality gate pass.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:28:20Z","updated_at":"2026-08-08T15:33:50Z","closed_at":"2026-08-08T15:33:51Z","external_ref":"https://github.com/samcharles93/archie-core/issues/52","source_system":"github:https://github.com/samcharles93/archie-core/issues/52:52","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490564-30-12d5a4c7","title":"Fix Web Chat nil update service panic","description":"Fix the typed-nil *releaseupdate.Service injected into ChatUpdateService when update checking is unconfigured. Make the Web Chat update endpoints return a controlled not-configured response and add service nil-receiver safety as needed. Preserve the regression test in archie-core-3cf.19 and run focused tests plus task check.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:28:16Z","updated_at":"2026-08-08T14:31:01Z","closed_at":"2026-08-08T14:31:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/51","source_system":"github:https://github.com/samcharles93/archie-core/issues/51:51","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490536-29-f1dab2c4","title":"Make dashboard authentication and connectivity failures actionable","description":"Opening the bare dashboard hash URL returns a raw 401 text response telling the operator to find the startup URL; the authenticated dashboard also showed reconnecting while activity rows were visible. Provide a browser-facing auth recovery state or clear redirect guidance, distinguish initial load failure from SSE reconnecting, and expose a retry path without requiring source or log knowledge. Cover token, API, SSE, and daemon-unavailable states.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:28:13Z","updated_at":"2026-08-08T14:31:42Z","external_ref":"https://github.com/samcharles93/archie-core/issues/50","source_system":"github:https://github.com/samcharles93/archie-core/issues/50:50","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490511-28-e299e25f","title":"Add regression test for nil Web Chat update service","description":"The Web Chat update endpoint receives a typed-nil *releaseupdate.Service through ChatUpdateService when update checking is unconfigured. Add a regression test proving the endpoint returns a controlled not-configured response instead of panicking. Do not implement the fix in this task.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:28:08Z","updated_at":"2026-08-08T14:31:03Z","closed_at":"2026-08-08T14:31:04Z","external_ref":"https://github.com/samcharles93/archie-core/issues/49","source_system":"github:https://github.com/samcharles93/archie-core/issues/49:49","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490484-27-a8483db4","title":"Web Chat: render rich Markdown during streamed replies","description":"Telegram drafts render Markdown while a turn is streaming. Web Chat currently appends deltas as plain text and only renders rich output after completion. Keep the live assistant bubble semantically rich throughout SSE updates, including safe handling of partial Markdown.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:28:03Z","updated_at":"2026-08-08T14:31:44Z","closed_at":"2026-08-08T14:31:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/48","source_system":"github:https://github.com/samcharles93/archie-core/issues/48:48","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490459-26-4b407a88","title":"Web Chat: split component markup and presentation files","description":"Refactor the Web Chat out of a large JavaScript-built markup blob. Keep HTML structure in a dedicated template, CSS in dedicated chat styles, Markdown rendering in its own module, and interaction/rendering behavior in focused modules while preserving current API behavior.\n\n### Acceptance Criteria\n\nChat has dedicated HTML, CSS, Markdown, view, catalog, panel, render, and state modules; chat.js contains only chat-specific coordination and event wiring with no static markup blob; npm tests/build and task check pass; Playwright confirms chat interactions and Markdown rendering.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:27:58Z","updated_at":"2026-08-08T14:28:00Z","closed_at":"2026-08-08T14:28:01Z","external_ref":"https://github.com/samcharles93/archie-core/issues/47","source_system":"github:https://github.com/samcharles93/archie-core/issues/47:47","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490433-25-84898952","title":"Web Chat: restore Telegram-compatible Markdown rendering","description":"Ensure assistant history and streamed replies render Markdown consistently in the split Web Chat component, matching Telegram-visible formatting. The renderer must remain a dedicated module and be covered by UI and Playwright tests.\n\n### Acceptance Criteria\n\nHistory and streamed assistant bubbles use the same dedicated safe Markdown renderer; supported Markdown constructs render as semantic HTML; raw markup is not shown for supported constructs; unsafe links remain inert; tests and task check pass.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:27:53Z","updated_at":"2026-08-08T14:27:56Z","closed_at":"2026-08-08T14:27:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/46","source_system":"github:https://github.com/samcharles93/archie-core/issues/46:46","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490406-24-1ff5173c","title":"Web Chat: cancel server-side turns from Stop","description":"Make the Web Chat Stop action cancel the server-side gateway turn lane and discard queued turns, matching Telegram behavior. Add an authenticated cancel endpoint, wire the shared ChatService to gateway.Turns, and cover API/UI behavior.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:27:49Z","updated_at":"2026-08-08T14:27:51Z","closed_at":"2026-08-08T14:27:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/45","source_system":"github:https://github.com/samcharles93/archie-core/issues/45:45","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490377-23-4a9d1f52","title":"Chat parity: align shared and Telegram command catalogs","description":"Align command discovery with the commands actually handled by the shared gateway and Telegram adapter while preserving Telegram’s intentional hidden dangerous approval commands.\n\n### Design\n\nKeep command execution unchanged. Extend the existing catalog entries with accurate descriptions and preserve the existing dangerous-command hiding rule; do not duplicate dispatch logic.\n\n### Acceptance Criteria\n\nThe shared gateway catalog includes /start and Telegram publishes /start; Telegram’s intentionally hidden /approve and /deny remain executable but undiscoverable; capability-specific dangerous commands remain correctly gated in Web; tests assert the published Telegram menu covers the non-hidden executable command surface.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:27:44Z","updated_at":"2026-08-08T14:31:05Z","closed_at":"2026-08-08T14:31:06Z","external_ref":"https://github.com/samcharles93/archie-core/issues/44","source_system":"github:https://github.com/samcharles93/archie-core/issues/44:44","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490350-22-ffaa5152","title":"Web Chat: add contextual session lifecycle controls","description":"Expose Telegram session lifecycle actions directly in the Web Chat workspace while continuing to route them through the shared gateway.\n\n### Design\n\nUse a native details popover in the workspace header, prompt only for title/branch names, and keep compression destructive work behind the existing gateway preview command. Do not add Web-only session semantics or duplicate command implementations.\n\n### Acceptance Criteria\n\nAn active Web session exposes retry, undo, title, branch, and compression preview actions; actions use shared commands, refresh the selected session/history, handle missing sessions and failures visibly, and remain keyboard accessible. Browser verification covers command dispatch and session refresh.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:27:39Z","updated_at":"2026-08-08T14:31:46Z","closed_at":"2026-08-08T14:31:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/43","source_system":"github:https://github.com/samcharles93/archie-core/issues/43:43","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490328-21-c983ea46","title":"Web Chat: revalidate update snapshot before installation","description":"Make the Web update approval path match Telegram by requiring the displayed snapshot and rechecking available component versions immediately before installation.\n\n### Design\n\nExport the existing releaseupdate available-version comparison instead of duplicating it. Keep the existing in-progress mutex and progress response.\n\n### Acceptance Criteria\n\nWeb install requests include the displayed snapshot; the server rejects changed or missing snapshots without installing; unchanged snapshots install once; the shared comparison logic is tested and used by Telegram and Web.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:27:34Z","updated_at":"2026-08-08T14:31:07Z","closed_at":"2026-08-08T14:31:08Z","external_ref":"https://github.com/samcharles93/archie-core/issues/42","source_system":"github:https://github.com/samcharles93/archie-core/issues/42:42","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490300-20-af3a358e","title":"Web Chat: render Telegram-style Markdown tables","description":"Extend the Web Chat Markdown renderer to preserve table structure and strikethrough formatting supported by Telegram rich replies.\n\n### Design\n\nKeep the existing dependency-free renderer. Recognize a table only when a header row is immediately followed by a Markdown separator row, parse cells without innerHTML, and reuse inlineMarkdown for cell content.\n\n### Acceptance Criteria\n\nPipe-delimited Markdown tables render as semantic table/thead/tbody elements with inline formatting; strikethrough renders as del; malformed pipe text remains ordinary text; safe DOM construction is preserved and Playwright verifies the rendered structure.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:27:30Z","updated_at":"2026-08-08T14:31:48Z","closed_at":"2026-08-08T14:31:49Z","external_ref":"https://github.com/samcharles93/archie-core/issues/41","source_system":"github:https://github.com/samcharles93/archie-core/issues/41:41","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490273-19-c97b9ebc","title":"Web Chat: add Telegram-parity slash command palette","description":"Make the Web Chat composer discoverable like Telegram command entry: when the operator types /, show the available shared command catalog, filter it as they type, and allow keyboard or pointer selection to insert a command without submitting it.\n\n### Design\n\nKeep the gateway as the command source of truth. Implement the palette in the vanilla chat composer with role=listbox/option semantics, bounded results, and no new backend endpoint.\n\n### Acceptance Criteria\n\nTyping / opens an accessible command list; filtering matches command names and descriptions; ArrowUp/ArrowDown/Enter/Escape and pointer selection work; selected commands retain the existing command semantics; the palette uses the capability-aware command catalog returned by the sessions API and is verified in browser.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:27:25Z","updated_at":"2026-08-08T14:31:50Z","closed_at":"2026-08-08T14:31:51Z","external_ref":"https://github.com/samcharles93/archie-core/issues/40","source_system":"github:https://github.com/samcharles93/archie-core/issues/40:40","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490248-18-17079a75","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":2,"issue_type":"bug","created_at":"2026-08-08T14:27:22Z","updated_at":"2026-08-08T14:31:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/39","source_system":"github:https://github.com/samcharles93/archie-core/issues/39:39","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490224-17-26cbc53b","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.\n\n### Acceptance Criteria\n\nAuthenticated 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","created_at":"2026-08-08T14:27:19Z","updated_at":"2026-08-08T14:27:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/38","source_system":"github:https://github.com/samcharles93/archie-core/issues/38:38","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490203-16-7a9da5ab","title":"ContainerRunner: implement agentexec.Runner against Docker for sandboxed execution","description":"Phase 2 of docs/prds/archie-core-v2-architecture.md. agentexec.Runner (InProcessRunner/SubprocessRunner) is an interface deliberately designed to be swapped for a container-backed runner without touching workflow orchestration. internal/container/pool.go already handles Docker lifecycle (pull, create, start, release, orphan recovery). Implement ContainerRunner against the existing Runner interface.\n\n### Design\n\nDo not redesign the execution boundary — implement strictly against the existing Runner interface per its doc comments.\n\n### Acceptance Criteria\n\nContainerRunner implements agentexec.Runner, runs tasks in ephemeral Docker containers with workspace bind-mounted, and is selectable via [agent] mode = \"nats\" + containers.enabled = true.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:27:14Z","updated_at":"2026-08-08T14:31:52Z","closed_at":"2026-08-08T14:31:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/37","source_system":"github:https://github.com/samcharles93/archie-core/issues/37:37","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490173-15-39c844b1","title":"Eliminate intermittent JetStream TempDir teardown race","description":"An intermittent full-suite race failure shows TestConnectAndPublish cleaning its testing.TempDir while JetStream is still removing the ARCHIE_TASKS msgs directory. The package subsequently passed five race iterations, so the timing window is narrow.\\n\\n## Steps to Reproduce\\n1. Run: go test -race -count=1 ./...\\n2. Repeat until internal/nats TestConnectAndPublish fails during TempDir RemoveAll with: unlinkat .../jetstream/$G/streams/ARCHIE_TASKS/msgs: directory not empty.\\n3. Compare with: go test -race -count=5 ./internal/nats.\\n\\nMake embedded NATS shutdown and storage cleanup deterministic before TempDir cleanup.\n\n### Acceptance Criteria\n\nRepeated race runs of internal/nats and the full repository do not race TempDir cleanup against JetStream file removal; the test explicitly waits for server/storage shutdown.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:27:09Z","updated_at":"2026-08-08T14:31:11Z","closed_at":"2026-08-08T14:31:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/36","source_system":"github:https://github.com/samcharles93/archie-core/issues/36:36","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490145-14-dd1e68f3","title":"Fix chat command palette keyboard interaction","description":"The chat slash-command palette remains open after the slash is removed or Escape is pressed, and its results cannot be navigated with ArrowUp/ArrowDown. Add regression tests and restore expected keyboard behavior.\n\n### Acceptance Criteria\n\nBackspace/removing the slash closes the palette; Escape closes it; ArrowUp and ArrowDown move the active option; Enter activates the highlighted option; the focused option is exposed accessibly; UI tests and project quality gates pass.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:27:05Z","updated_at":"2026-08-08T14:31:13Z","closed_at":"2026-08-08T14:31:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/35","source_system":"github:https://github.com/samcharles93/archie-core/issues/35:35","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490125-13-6dea21ca","title":"Trim the remaining agent skills to factual reference","description":"The .agents/skills/ library is 4283 lines across 12 skills. An audit found most carry useful facts buried in process ceremony. Five worst offenders were already parked at /work/apps/archie-skills-parked. Trim what remains to roughly 2200 lines total. KEEP: concrete commands, package anchors, config wiring tables, NellDB shapes, symptom-to-diagnostic indexes, known regressions, domain glossary, operational hazards, false-confidence warnings. CUT: mandated N-step procedures, handoff templates, evidence packets, acceptance checklists, ownership/deletion/rollback field lists, sibling-skill routing prose, repeated 'reject unless' instructions, dated tool snapshots. Preserve every skill's YAML frontmatter name and description. Do not delete any skill file outright.\n\n### Acceptance Criteria\n\nTotal line count of .agents/skills/*/*.md is between 1900 and 2500. All 12 skills still exist with valid frontmatter. No factual command, path, or table was lost - only procedure and ceremony. go build ./... still clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:27:00Z","updated_at":"2026-08-08T14:27:02Z","closed_at":"2026-08-08T14:27:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/34","source_system":"github:https://github.com/samcharles93/archie-core/issues/34:34","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490097-12-bf415ffb","title":"SOUL cannot override the prompt invariants","description":"Enforce the boundary that makes SOUL safe to hand to users: it supplies identity and style, and cannot reach the instruction hierarchy, core rules, tool inventory or env block.\n\n### Acceptance Criteria\n\nA test renders a hostile SOUL that attempts to countermand core_rules and asserts the invariant sections are still present and intact. The boundary is documented where the layering rule already lives so the next person editing the template does not quietly relax it.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:26:57Z","updated_at":"2026-08-08T14:26:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/33","source_system":"github:https://github.com/samcharles93/archie-core/issues/33:33","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490069-11-e245c170","title":"Memory engine contract and owning registry","description":"Define the typed memory engine interface and the registry that owns provider registration, discovery, and lifecycle. This is the load-bearing design step: everything else in the epic is written against this contract.\n\n### Acceptance Criteria\n\nA typed interface exposes real memory operations beyond identity metadata. An owning Registry/Manager controls registration, init, start, health, and stop, and defines failure isolation and shutdown ordering. Providers receive only a typed registrar and the host services their capability declares. internal/plugin/architecture_test.go passes with memory recognised as a conforming engine family. Stateless providers may declare explicit no-op lifecycle.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:54Z","updated_at":"2026-08-08T14:31:54Z","external_ref":"https://github.com/samcharles93/archie-core/issues/32","source_system":"github:https://github.com/samcharles93/archie-core/issues/32:32","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490043-10-711c450a","title":"Config surface for memory engine selection and settings","description":"Add validated configuration for choosing a memory engine and supplying its per-engine settings, following the existing config conventions in internal/config and internal/infrastructure/configuration.\n\n### Acceptance Criteria\n\nEngine choice and per-engine settings are expressible in config.toml with toml/yaml/json tags matching repo convention. Validation rejects an unknown engine name with a clear error naming the valid set, in the style of the existing forge.type validation. Defaults resolve so an absent section keeps the builtin engine. config.example.toml documents the section.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:51Z","updated_at":"2026-08-08T14:31:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/31","source_system":"github:https://github.com/samcharles93/archie-core/issues/31:31","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637490011-9-d5e4f9a4","title":"Telegram: provider selector filters model choices","description":"Add an authorized native /provider inline selector. The selected provider scopes /model so only configured model references belonging to that provider are shown; e.g. openrouter/openai/gpt-5.6 must not appear under provider openai. Selecting a provider establishes a valid active model for that provider when necessary, and /status reports active provider and model.\n\n### Acceptance Criteria\n\n/provider displays configured providers as an inline keyboard and marks the active provider. Authorized callbacks switch provider; unauthorized, malformed, stale, and duplicate callbacks fail safely. /model shows only models whose first reference segment matches the selected provider and uses unambiguous labels. Switching provider leaves the chat responder on a valid model from that provider. /status includes active provider and full model reference. Menu/help/executable parity and concurrent access are tested.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:49Z","updated_at":"2026-08-08T14:31:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/30","source_system":"github:https://github.com/samcharles93/archie-core/issues/30:30","metadata":null,"labels":["enhancement","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637489985-8-13b9d8a8","title":"Document the memory engine family in ARCHITECTURE.md","description":"Record the memory engine family alongside the existing engine documentation so the contract, its lifecycle guarantees, and the trust boundary for third-party memory backends are written down where the plugin engine rule already lives.\n\n### Acceptance Criteria\n\nARCHITECTURE.md describes the memory engine contract, its owning manager, lifecycle and failure isolation, and states the trust boundary for an out-of-process or third-party memory backend. The shared CLAUDE.md/AGENTS.md source is updated if the rule surface changes.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:26:46Z","updated_at":"2026-08-08T14:26:46Z","external_ref":"https://github.com/samcharles93/archie-core/issues/29","source_system":"github:https://github.com/samcharles93/archie-core/issues/29:29","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637489959-7-6c8cdec2","title":"fix(telegram): honour retry_after on 429 instead of the library's fixed backoff","description":"go-telegram/bot v1.22.0 get_updates.go discards TooManyRequestsError.RetryAfter and applies its own 100ms-doubling backoff capped at 5s. Against retry_after:5 that is ~12 further requests inside the silence window, which escalated a brief 429 on carina into sustained 429s, 502s and request timeouts over several minutes.\n\nFixed in internal/channels/telegram/ratelimit.go: WithErrorsHandler is invoked synchronously from the polling loop before the library applies its own backoff, so blocking there honours the interval without patching the dependency. errors.As unwraps the library's fmt.Errorf wrap; capped at maxRetryAfter=60s; releases immediately on context cancellation so /restart during a 429 does not block.\n\nUpstream report drafted for https://github.com/go-telegram/bot/issues -- suggested fix is to prefer RetryAfter over incErrTimeout in the error branch.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:26:41Z","updated_at":"2026-08-08T14:26:44Z","closed_at":"2026-08-08T14:26:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/28","source_system":"github:https://github.com/samcharles93/archie-core/issues/28:28","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637489932-6-1f803e02","title":"Curator observability surface","description":"Give curator activity visibility: which curators are registered, when each last ran, what it changed, and why. Background agents mutating memory unobserved is the failure mode this epic most needs to avoid.\n\n### Acceptance Criteria\n\nRegistered curators, their schedule state, and their recent activity are inspectable at runtime. Each recorded action carries enough context to answer why it happened. Surfaced through the existing observability paths rather than a bespoke channel.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:38Z","updated_at":"2026-08-08T14:32:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/27","source_system":"github:https://github.com/samcharles93/archie-core/issues/27:27","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637489903-5-fde58498","title":"CLI: technical design interview and PRD for command surface","description":"Run a technical design interview with Sam before making any CLI implementation decisions. Produce a reviewed PRD/specification for the user-facing archie CLI: goals, personas, installation/distribution, configuration and state model, commands/subcommands/flags, output and machine-readable contracts, auth/host targeting, update lifecycle, error semantics, compatibility/migration, and acceptance tests. The eventual implementation must use urfave/cli/v3; do not use or introduce urfave/cli/v2. No CLI code is in scope until Sam approves the resulting PRD.\n\n### Acceptance Criteria\n\nInterview captures Sam's intended CLI workflows and non-goals; PRD defines the complete command surface and state/transport ownership without assumptions; PRD specifies urfave/cli/v3; Sam explicitly approves the PRD before implementation work is created.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:26:34Z","updated_at":"2026-08-08T14:26:36Z","closed_at":"2026-08-08T14:26:37Z","external_ref":"https://github.com/samcharles93/archie-core/issues/26","source_system":"github:https://github.com/samcharles93/archie-core/issues/26:26","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637489876-4-35aced49","title":"feat(config): optional file logging","description":"archied writes slog JSON to stdout only; under systemd journald is the sole copy, and running by hand leaves nothing. Add a log_file config field so there is a durable copy independent of journald. Prerequisite for the webui logs view showing anything from before the dashboard connected.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:26:29Z","updated_at":"2026-08-08T14:26:31Z","closed_at":"2026-08-08T14:26:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/25","source_system":"github:https://github.com/samcharles93/archie-core/issues/25:25","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637489857-3-24abe68c","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.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:26:24Z","updated_at":"2026-08-08T15:33:31Z","closed_at":"2026-08-08T15:33:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/24","source_system":"github:https://github.com/samcharles93/archie-core/issues/24:24","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637489834-2-109e7cab","title":"[BUG] /model \u003cname\u003e asked the router for a doubled model name","description":"The nestif extraction in 651de0a pulled --provider parsing out of parseModelRest into extractProviderFlag, which took the modelParts slice by pointer and appended every non-provider field to it. The caller's own loop then appended the same fields again, so every field of the model name was duplicated: '/model gpt-5.6' resolved to 'gpt-5.6 gpt-5.6' and SetActiveModel rejected it as an unknown model. '/model gpt-5.6 --provider openai' was worse -- the space-separated provider value was no longer consumed with its flag, giving 'gpt-5.6 gpt-5.6 openai'. Direct model switching over Telegram was broken for anything but a bare --refresh or a provider-only switch. Found while auditing 6d4e0be for archie-core-ifi: the naked return in the same function could not be regression-tested until the function produced correct values.\n\n### Design\n\nTwo ways to fix the double append were available. Rejected: keep the helper\nsignature and delete the caller's default-branch append. That restores correct\noutput but leaves the shape intact -- a helper holding a pointer to the\ncaller's accumulator, with two loops over the same fields -- so the next person\nwho adds a field type has the same trap waiting. It also does not fix the\nspace-separated provider value, because the helper returns early on the first\n--provider and never sees the fields after it.\n\nChosen: splitProviderFlag returns (provider, remaining) and is the sole\naccumulator. One loop owns the fields, and there is no shared slice to append\nto twice. The index loop is kept deliberately -- i++ after reading a\nspace-separated value is what removes it with its flag, and converting that to\na range loop is precisely what 651de0a did wrong.\n\nLast --provider wins if repeated, matching the pre-651de0a behaviour rather\nthan the buggy helper's first-wins. Not worth a flag: /model does not document\nrepeating it.\n\n### Acceptance Criteria\n\nparseModelRest returns the model name exactly once for bare names, scope flags, and both --provider spellings, with a regression test asserting field count rather than string equality.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:26:19Z","updated_at":"2026-08-08T15:34:07Z","closed_at":"2026-08-08T15:34:08Z","external_ref":"https://github.com/samcharles93/archie-core/issues/23","source_system":"github:https://github.com/samcharles93/archie-core/issues/23:23","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637489768-1-2fd8288f","title":"Trigger accounting: curator output must not feed its own trigger","description":"Establish the invariant that work a curator produces does not count toward the condition that schedules the next curator run. The scheduler must explicitly exclude derived curator output from the observation threshold: counting it would inflate the threshold and create a feedback loop, so a curator that writes memories must not thereby schedule itself again.\n\n### Acceptance Criteria\n\nDerived curator output is distinguishable from primary input at the point the trigger is evaluated. A curator that writes memories does not thereby schedule itself again. There is a regression test that would fail if derived output were counted, with the feedback-loop rationale recorded in the test so the guard is not removed as redundant.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:26:17Z","updated_at":"2026-08-08T15:34:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/22","source_system":"github:https://github.com/samcharles93/archie-core/issues/22:22","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
Reference in new issue
Block a user