chore(beads): stop tracking issues.jsonl/interactions.jsonl in git
Dolt is the source of truth and already syncs via its own git+ remote (bd dolt push/pull). Committing the JSONL export separately produced a steady stream of no-op "chore(beads)" commits that skewed commit counts without adding information. Untrack the export files, disable export.auto/git-add, and drop the beads-commit step from CLAUDE.md's Session Completion Protocol.
This commit is contained in:
1 parent
b51fffe235
commit
659e914cf1
5 files changed
+17
-901
No files matched your search
+5
-6
@@ -54,14 +54,13 @@
|
||||
# Disabled by default; enable only when an integration needs fresh .beads/issues.jsonl.
|
||||
# Use relative paths under .beads/ for JSONL import/export filenames.
|
||||
export:
|
||||
auto: true
|
||||
auto: false
|
||||
path: issues.jsonl
|
||||
interval: 60s
|
||||
# issues.jsonl is tracked (see .beads/.gitignore), so the export must be
|
||||
# staged with the commit that triggers it. With git-add off, the 60s
|
||||
# auto-export would leave a tracked file permanently dirty in git status
|
||||
# and block rebases and checkouts until stashed.
|
||||
git-add: true
|
||||
# issues.jsonl/interactions.jsonl are .gitignore'd local-only files --
|
||||
# Dolt (synced via sync.remote) is the source of truth. Leave auto off
|
||||
# and git-add off; do not re-track these in git.
|
||||
git-add: false
|
||||
import:
|
||||
path: issues.jsonl
|
||||
# Integration settings (access with 'bd config get/set')
|
||||
|
||||
@@ -1,221 +0,0 @@
|
||||
{"id":"int-ca573b1f243d5e820077aadb21af8595","kind":"field_change","created_at":"2026-08-15T12:27:33.967613847Z","actor":"Sam Catlow","issue_id":"archie-core-1786637491053-48-fe78cd53","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Verified against current main: Route/RouteStream reject unrecognized slash commands before any LLM call (gateway.go:299-318, 449-462), /start is deterministic in both gateway and Telegram handlers, and full test matrix from acceptance criteria exists (gateway_test.go:106-133, gateway_stream_test.go:54-88, telegram_test.go:135-157). Confirmed by fresh code-tracing pass, not just prior user experience."}}
|
||||
{"id":"int-73ca4d209481e52e20c00c128fc6a3ca","kind":"field_change","created_at":"2026-08-15T12:41:34.047451864Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942519-17-5999d55b","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}}
|
||||
{"id":"int-2193ae15ea3e5922294ec78dffe4958a","kind":"field_change","created_at":"2026-08-15T13:36:38.960683238Z","actor":"Sam Catlow","issue_id":"archie-core-1786637489985-8-13b9d8a8","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Documented the memory engine contract, owning manager, lifecycle/failure isolation, and third-party trust boundary in ARCHITECTURE.md; focused memory tests pass."}}
|
||||
{"id":"int-b91f90f48c3115e8d29a3f60e88408e5","kind":"field_change","created_at":"2026-08-17T14:22:09.796781498Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942324-9-509793a0","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Pivoted after design review: value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain. The real gap was engine refresh (bws caches once per process). Replaced by fresh-resolving sops/vault/age engines (beads #409/#411/age). Remote secret-input contract kept as design doc in #505; value-entry UX deferred until a writable engine without a mobile path exists."}}
|
||||
{"id":"int-aa88000af2cd016d26841a6fa4abf2c4","kind":"field_change","created_at":"2026-08-17T14:33:51.558458038Z","actor":"Sam Catlow","issue_id":"archie-core-1786637500571-409-cdffe32a","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Shipped sops engine plugin in examples/secret-engines/sops.go (commit 24faf53): CLI-based, SOPS_FILE env, fresh resolve per call."}}
|
||||
{"id":"int-6b8ec518ed64d18eb751748c5f7f5f59","kind":"field_change","created_at":"2026-08-17T14:33:52.021744933Z","actor":"Sam Catlow","issue_id":"archie-core-1786637500634-411-e265a95c","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Shipped vault/openbao engine plugin in examples/secret-engines/vault.go (commit 24faf53): CLI-based, VAULT_ADDR/VAULT_TOKEN, key 'path/field' or VAULT_SECRET_PATH prefix."}}
|
||||
{"id":"int-e941581f53a51660e0f0a5ffceb7c826","kind":"field_change","created_at":"2026-08-17T14:33:52.146335715Z","actor":"Sam Catlow","issue_id":"archie-core-q5w4","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Shipped age engine plugin in examples/secret-engines/age.go (commit 24faf53): CLI-based, AGE_FILE/AGE_IDENTITY, key=value lines."}}
|
||||
{"id":"int-919adde47b5f87215812a10a78993f09","kind":"field_change","created_at":"2026-08-17T14:34:47.896559702Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499872-384-7952eb47","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Confirmed fixed by Sam; no longer reproducible"}}
|
||||
{"id":"int-7850f0a34c140822fcc3881f5175c0a3","kind":"field_change","created_at":"2026-08-17T14:37:45.280994322Z","actor":"Sam Catlow","issue_id":"archie-core-1786749700580-5-e3878224","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Already fixed by e7d3925 (2026-07-29, predates this bead). Release() force-kills the container via context.WithoutCancel + ContainerStop/ContainerRemove(Force:true) regardless of cancellation; in-process path checks ctx.Err() between workflow stages. The stage_loop.go path the bead's writeup blames is dead code -- nothing publishes to archie.agent.* subjects in the current architecture. Verified via fresh read-only investigation, file:line citations on both passes."}}
|
||||
{"id":"int-7ba0339215268f38be520cb017075b23","kind":"field_change","created_at":"2026-08-17T22:38:44.985412822Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490248-18-17079a75","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Already fixed by 170fe02 (2026-08-05), predating this bead's 2026-08-08 runtime inspection -- the inspected deployment was serving a stale build. el() in ui/src/base/dom.js was treating a falsy scalar first child (0, '', false) as a missing attrs object and dropping it, so any stat tile whose value was 0 (Working now, Needs you, Tokens used before any usage) rendered a blank headline. Fixed with dedicated regression coverage in ui/test/dom.test.js (el renders a falsy numeric value instead of dropping it, statTile renders a zero headline value, etc.) -- all 9 tests pass. Verified ui/dist rebuilds byte-identical to the committed tree, so the fix ships in the current binary. The token-outlook-specific root cause (missing agent_finish event rows) is tracked separately in archie-core-1786748942590-20-c21c728b per this bead's own notes and is out of scope here."}}
|
||||
{"id":"int-3d9bd8b487035a359ea21d03b1e2d160","kind":"field_change","created_at":"2026-08-17T22:38:57.071131764Z","actor":"Sam Catlow","issue_id":"archie-core-1786749700580-5-e3878224","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Root cause found after Sam confirmed live testing still showed the task's in-flight tool calls/generation continuing tens of seconds to ~2 minutes after /stop reported success. internal/container/pool.go Release() always slept the configured GracePeriod and always used Docker's default ~10s graceful SIGTERM-then-SIGKILL timeout, even when the release was happening because the task's context had just been cancelled by /stop -- so a cancelled task's container (and the in-flight work inside it) could sit doing nothing for up to GracePeriod+~10s before actually dying. Fixed with a new releaseDecision(ctx, grace) helper: a cancelled ctx now skips the grace sleep entirely and requests an immediate SIGKILL (ContainerStopOptions.Timeout=0) instead of a graceful wait; a live ctx (normal completion) keeps the original behaviour byte-for-byte. Red-then-green with 3 new unit tests (internal/container/pool_test.go), task check clean, adversarially reviewed by a fresh subagent with zero blocking findings -- context-chain trace, Docker Timeout=0 semantics, and struct-equivalence for the unchanged path were all independently verified against the moby client source."}}
|
||||
{"id":"int-c4d48841525c9702ecbb52e8c01af769","kind":"field_change","created_at":"2026-08-17T22:40:01.727639644Z","actor":"Sam Catlow","issue_id":"archie-core-1786749700606-6-bf6aa32d","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Confirmed root cause: agent containers run as root (no USER in Dockerfile, no userns-remap anywhere in docker-compose.yml/internal/container/pool.go), so a commit the agent writes to the bind-mounted worktree lands owned by UID 0 on the host. The daemon later reads those same loose objects to push, running as its own non-root host user -- 'openat objects/../..: permission denied'. Fixed: containerEnv() now passes the daemon's own os.Getuid()/os.Getgid() as WORKTREE_UID/WORKTREE_GID; hybridTrees.Push (the single choke point before the push RPC) chowns the worktree back to that owner first. Adversarial review (fresh subagent) found one real bug in the first pass -- chownTree used os.Chown, which follows symlinks and fails on a legitimately-tracked-but-dangling symlink, which would have aborted a push that would otherwise have succeeded (worse than the original bug). Fixed with os.Lchown plus a regression test proving it against a dangling symlink. Full task check clean; all other review findings (full-tree walk cost, minor test-hygiene notes) were judged non-blocking by the reviewer."}}
|
||||
{"id":"int-798164dc314631bdfc1d20b4684b59f8","kind":"field_change","created_at":"2026-08-17T22:42:58.869292319Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942495-16-0d6ea565","extra":{"field":"status","new_value":"in_progress","old_value":"open"}}
|
||||
{"id":"int-c19649ae61fe5c71fa1a64258dbc98c9","kind":"field_change","created_at":"2026-08-18T15:51:15.311055291Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942495-16-0d6ea565","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Shipped in archied v1.9.10 (commit 95290d1, feat(update): stream live progress and roll back failed updates automatically) -- live progress reporting, version summary, and automatic rollback on failed updates all landed and released."}}
|
||||
{"id":"int-410272072a4bf54ef8e44517f197a133","kind":"field_change","created_at":"2026-08-18T15:51:15.930052316Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942345-10-50a04c62","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic."}}
|
||||
{"id":"int-ded36d77c1a5f4fd478271753fad1271","kind":"field_change","created_at":"2026-08-18T15:51:15.934011477Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942364-11-47ec9e60","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic."}}
|
||||
{"id":"int-d139f0f1a14ab44a6bd0e87bb8e60865","kind":"field_change","created_at":"2026-08-18T15:51:15.937866765Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942391-12-7988cdca","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic."}}
|
||||
{"id":"int-61dd3ff4049e450b1f52f68a8fe1b27e","kind":"field_change","created_at":"2026-08-18T15:51:15.941687801Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942414-13-14bd990e","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic."}}
|
||||
{"id":"int-fc6126a227bf87610456c9bc282d4634","kind":"field_change","created_at":"2026-08-18T15:51:15.945433325Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942438-14-abe5ddd0","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic."}}
|
||||
{"id":"int-b6e06d7e49ee35af64ad21b7b99a7f67","kind":"field_change","created_at":"2026-08-18T15:51:15.949055267Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942463-15-78823975","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic."}}
|
||||
{"id":"int-726497f741b07352a4f67d3ba8be8c5b","kind":"field_change","created_at":"2026-08-18T15:53:29.554375007Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490011-9-d5e4f9a4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Superseded: confirmed by Sam that there is no longer a separate /provider command -- grepped the codebase and no '/provider' command exists in internal/gateway or internal/channels/telegram. /model now handles provider scoping directly."}}
|
||||
{"id":"int-7096095a0791399004afa1648103b4d4","kind":"field_change","created_at":"2026-08-18T16:05:12.750527752Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490923-43-d4bb914b","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: configuredMCPProvider (cmd/archied/main.go) now sets NPM_CONFIG_CACHE under the daemon's persistent work_dir and NPM_CONFIG_PREFER_OFFLINE=true for any npx-launched MCP server (matched by base name so an absolute-path npx still qualifies), so a daemon restart reuses a warm npm cache instead of re-resolving/re-downloading from the registry every time -- the amplifier behind the 2026-07-30 crash loop. Guards an empty workDir explicitly (unreachable in production since config defaulting runs first, but matches memoryProvider's existing precedent for the same defense). Adversarially reviewed by a fresh subagent; findings addressed: narrowed an overclaim that this also covers a package's own separate downloads (e.g. Playwright/Puppeteer fetching browser binaries via CDN, which NPM_CONFIG_CACHE does not touch), and closed the absolute-path-command gap. Full task check clean. The identical, arguably-worse instance in internal/app/agentworker/mcp_providers.go (every per-task ephemeral container, not just daemon restarts) needs real new infra -- a persistent Docker volume bind-mounted into task containers, which doesn't exist yet -- so it's filed separately as archie-core-qk8m rather than folded into this scoped fix."}}
|
||||
{"id":"int-0379f6f196262497f6642169c943afd6","kind":"field_change","created_at":"2026-08-20T12:55:17.903920351Z","actor":"Sam Catlow","issue_id":"archie-core-3jag","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed in fix/persona-overconfidence (fba80e3): reworded core rule 1 and added rules 8/9 to the chat agent system prompt enforcing this-turn verification before labelling claims verified/confirmed."}}
|
||||
{"id":"int-0e6d7b43d42215a9a41b1736f4b049d7","kind":"field_change","created_at":"2026-08-20T12:57:02.748858938Z","actor":"Sam Catlow","issue_id":"archie-core-1786637501009-424-5b8332dd","extra":{"field":"status","new_value":"in_progress","old_value":"open"}}
|
||||
{"id":"int-dec9f9d1307c51147ea510842ef80d1a","kind":"field_change","created_at":"2026-08-20T13:02:18.330112565Z","actor":"Sam Catlow","issue_id":"archie-core-1786637501009-424-5b8332dd","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed in fix/label-dispatch-empty-label (31efdcf): pollIssuesWithConfig/pollEitherWithConfig now refuse the label poll when cfg.Label is empty, and validateDispatch rejects the misconfiguration at load time. Adversarially reviewed; one weak test strengthened to actually verify assignee matches survive."}}
|
||||
{"id":"int-c00194f10222de956f7ad8987d09a9fb","kind":"field_change","created_at":"2026-08-20T13:24:15.962276702Z","actor":"Sam Catlow","issue_id":"archie-core-1786637500602-410-7a461d4d","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Already delivered as a compiled-in engine, not a plugin. internal/secret/bws.go implements secret.Engine and shells out to the bws CLI via os/exec (commit 3ae59c9, 2026-07-31); NewRegistry/DefaultRegistry register it under the name \"bws\" alongside \"env\". It is documented in config.example.toml and ARCHITECTURE.md:208, and config.example.toml:64 uses it as the worked example. Shipping a second yaegi implementation under examples/secret-engines/ would register the same name \"bws\", and Registry.Register is last-write-wins over LoadDir, so the plugin would silently shadow the compiled-in engine -- two authoritative paths for one behaviour, which the architecture contract prohibits. Reopen only if the intent is to REPLACE the compiled-in engine with a plugin (which would also need bws removed from NewRegistry and the docs updated)."}}
|
||||
{"id":"int-907fab8ee9218dfc52e1b312ccdde513","kind":"field_change","created_at":"2026-08-21T15:00:54.642569071Z","actor":"Sam Catlow","issue_id":"archie-core-7d5u.1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Decided and documented in docs/prds/event-sources-and-reactions.md, satisfying this bead's own acceptance criterion (a one-page decision naming the packages it touches and stating whether plugins-and-extensions.md needs amending -- it does not).\n\nAnswers: (1) in-process typed families, no out-of-process dispatch -- archie has no existing extension-process boundary and neither epic's stated payoff needs one. (2) Reaction delivery reuses internal/eventbus's Publisher/Consumer contract (PublishUnique + Ack/Nak already provide at-least-once with dedup), but NOT the existing nats.Client as-is: it hardcodes Retention: jetstream.WorkQueuePolicy (client.go:65) for the competing-consumer ARCHIE_TASKS stream, which silently starves a second consumer on overlapping subjects per CLAUDE.md's documented trap -- reactions need fan-out, so retention needs to become a Config field and reactions get their own stream. (3) Reactions in these two epics are producer-only (cheap wake via curator's WakeOnPrimaryInput pattern, or produce real work via the existing pollNATS->publishTask path) -- no veto/mutate-in-flight-work capability is being built here; that belongs to archie-core-h019 if it's ever needed. (4) No single generic Source interface -- forge intake reuses workintake.TaskEnvelope unchanged (its IdempotencyKey is already keyed on owner/repo/number, not delivery source, so a webhook-sourced envelope naturally dedups against a poll-discovered one for free); chat webhook stays internal/channels/webhook, unmodified; what's genuinely new and shared is a small cross-cutting package for HMAC/rate-limit/approval/capture mechanics, owned by neither domain."}}
|
||||
{"id":"int-15527c6640daf7df72a4876d8e82864c","kind":"field_change","created_at":"2026-08-21T15:26:01.152938969Z","actor":"Sam Catlow","issue_id":"archie-core-7d5u.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Built internal/webhookguard: VerifyHMAC (behavior-preserving extraction from internal/channels/webhook, which now calls it instead of keeping a private copy), RateLimiter (per-source token bucket, independent budgets, observable rejection), RedactPayload (key-name heuristic matching gateway/stream.go's marker list, but -- deliberately unlike that function -- redacts only values under sensitive keys and leaves ordinary strings/numbers/bools untouched, since a captured payload exists to be inspected for field mapping in t2db.3).\n\nAll four acceptance criteria met and independently confirmed by a fresh adversarial review with zero surviving findings: HMAC extraction is byte-for-byte behavior-preserving (diffed against the deleted function); rate limiter hand-traced correct on two scenarios plus race-clean under -race; redaction's divergence from gateway/stream.go verified by reading both functions side by side; zero non-stdlib imports confirmed by grep. The reviewer also mutation-tested both the redaction and rate-limit guards (disabled each in turn) and confirmed the test suite catches both, then reverted and re-verified go test -race and git status were clean.\n\ntask check exit 0, golangci-lint 0 issues (one forcetypeassert finding was caught and fixed properly during build, not suppressed), gofumpt clean. All 10 pre-existing internal/channels/webhook tests pass unmodified; the one now-redundant unit test was removed with a comment pointing to where its coverage relocated."}}
|
||||
{"id":"int-ccb87c91023dbaa6718ae2f7564d38cc","kind":"field_change","created_at":"2026-08-21T18:51:09.120109805Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Built capture storage + endpoint: docs/prds/event-capture-storage.md decides SQLite over NATS JetStream (NATS not unconditionally available pre-7d5u.2, capture's single-writer/single-reader access pattern doesn't need JetStream fan-out/replay). internal/store/captures.go adds captured_events table + InsertCapture (prune-on-write by retention age and row count) + ListCaptures. internal/webui/api_capture.go adds POST /webhooks/capture/{source}, unauthenticated (bypasses requireToken like /healthz), applying webhookguard redaction before persisting and a per-remote-address rate limit + hard body-size cap before that. New [capture] config section with documented defaults. Adversarial self-review (the usual fresh subagent pass hit a session API limit mid-run, so this was a manual re-read with the same checklist) caught and fixed three real bugs before landing: (1) body-size cap silently unenforced when unset -- added a hardcoded fallback floor since it's the only bound on a SINGLE payload's size; (2) rate limiter was keyed by the request's own unregistered source path segment, violating webhookguard.RateLimiter's documented bounded-key-space assumption -- an attacker could rotate the segment to bypass the limit and grow the bucket map unbounded; rekeyed to remote address; (3) retention prune used time.RFC3339Nano, whose variable-width trimmed fractional seconds break lexicographic string comparison in `WHERE received_at < ?` (an exact-second timestamp can sort after a later fractional one) -- switched to fixed-width RFC3339. All three have regression tests verified to fail against the pre-fix code. task check clean, golangci-lint zero new findings repo-wide."}}
|
||||
{"id":"int-772ca35948f33ac9ada8096eceeb7144","kind":"field_change","created_at":"2026-08-21T19:17:03.32765544Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.2","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"GET /api/captures (token-gated, memory/skills-style enabled:false-not-an-error when Captures is nil) plus a new /captures dashboard page: recent captures newest-first, expandable per-row to explore redacted payload/headers pretty-printed. Live updates reuse the existing operator-activity event pipeline (Server.emit -> Events.Publish -> the /events SSE stream) as an invalidation signal, refetching the list rather than merging partial event data. Every row shows an 'Unbound' pill today since no binding model exists yet (t2db.4 wires the real distinction). Frontend follows the tasks/task-row.js precedent: row rendering split into capture-row.js for unit testing without the page's fetch/SSE wiring. Adversarial review (fresh subagent, full pass) found one real severe bug before merge: the live SSE event was embedding the full (up to 256KiB) redacted body/headers into the events table, which has no retention/row-count prune anywhere in the codebase -- silently defeating t2db.1's disk-bound guarantee for an unauthenticated, only-rate-limited endpoint. Fixed: the live event now carries just {id, source} as a pure invalidation signal; the dashboard refetches the authoritative list. Two smaller findings (untested Data[\"id\"] field the frontend's dedup depended on; a received_at precision mismatch between live and REST-fetched copies) were resolved as a side effect of that fix. task check clean, golangci-lint zero new findings."}}
|
||||
{"id":"int-ca26e9b428d406303510eea34c2c8d05","kind":"field_change","created_at":"2026-08-21T19:18:55.467881536Z","actor":"Sam Catlow","issue_id":"archie-core-7d5u.2","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Embedded NATS wired into production startup: mode=embedded/external/off resolves from url, daemon owns the in-process server lifecycle, Retention parameterized for a future fan-out reaction stream. task check + lint clean; adversarial review zero surviving findings. Committed 2c7db34."}}
|
||||
{"id":"int-484f5673b3d49ea1731bec29e2a84074","kind":"field_change","created_at":"2026-08-22T09:01:53.455811598Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Payload field mapping: domain (internal/domain/mapping), SQLite store (internal/store/mappings.go), HTTP API (internal/webui/api_mapping.go), and dashboard editor (ui/src/mappings) shipped. PRD at docs/prds/payload-field-mapping.md. task check green; adversarial review found 4 issues (stale preview after rename, duplicate field names, hardcoded capture scan window, malformed path silently reinterpreted), all fixed and re-verified."}}
|
||||
{"id":"int-0606ca827b33f964b6a5de2f5f4a1966","kind":"field_change","created_at":"2026-08-22T09:21:16.136296742Z","actor":"Sam Catlow","issue_id":"archie-core-7d5u.4","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"GitHub webhook receiver shipped: [forge] intake=poll|webhook|both, shared MatchesDispatch predicate (case-insensitive assignee, case-sensitive label) consumed by poller and receiver, HMAC-verified, publishes via shared PublishTask. Adversarial self-review found and fixed 3 real defects (boot-crashing secret-resolve hard-fail under intake=both, assignee case-sensitivity mismatch vs GitHub's own filter, silent multi-identity misdispatch) before landing. task check + lint clean. Committed 41e43dc."}}
|
||||
{"id":"int-fe2b5654477a99738b27c129267c3636","kind":"field_change","created_at":"2026-08-22T09:45:14.980953288Z","actor":"Sam Catlow","issue_id":"archie-core-h019.1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"One-page decision written at docs/prds/adversarial-self-review.md: reviewer runs in a second workspace (container or in-process) pointed at a .git-stripped snapshot of the reviewed commit, never the implementer's worktree; findings contract is workflow.ReviewFinding, owned by internal/domain/workflow, reported via a structured capture tool; a surviving error-level finding sets StatusParked (not WaitingHuman -- epic wording named two different states, this resolves which); model/effort reuse the existing Models[role] map and per-stage budget override, gated by a new opt-in Repo.ReviewEnabled so h019.4 doesn't gate every repo on an uncalibrated reviewer before h019.5 lands."}}
|
||||
{"id":"int-0f63389a86a8600c181ac3a924308b2d","kind":"field_change","created_at":"2026-08-22T09:45:16.096384559Z","actor":"Sam Catlow","issue_id":"archie-core-7d5u.5","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Investigated first: the dedup mechanism (TaskEnvelope.IdempotencyKey + PublishUnique + JetStream Nats-Msg-Id dedup) and the shared dispatch predicate were already fully wired by 7d5u.4 -- no double-dispatch code change was needed. Closed the two real gaps: (1) internal/infrastructure/eventbus/nats/dedup_test.go is a new regression test proving PublishUnique actually suppresses a duplicate publish on the same WorkQueuePolicy stream ARCHIE_TASKS uses in production; (2) internal/forge/webhook/receiver.go gained Status()/GET support tracking authenticated deliveries vs successful publishes separately, so a wedged or non-delivering receiver is observable rather than indistinguishable from an idle repo. AC's poll/webhook parity clause (disabling webhook still polls) is satisfied architecturally with no code change possible to violate it -- verified Cycle()/Run() never reference cfg.Forge.Intake anywhere in internal/daemon; only setupForgeWebhook in cmd/archied/bootstrap.go gates the webhook HTTP server. Adversarial review pass (fresh subagent, -race) found zero blocking issues; closed two minor coverage gaps it flagged."}}
|
||||
{"id":"int-3e1f713978e40f4b6520cc291177cf75","kind":"field_change","created_at":"2026-08-22T10:27:03.528690276Z","actor":"Sam Catlow","issue_id":"archie-core-1786637492559-106-5ea2315d","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented code-fence-aware Telegram message splitting with bounded continuation handling and regression coverage"}}
|
||||
{"id":"int-ad830c0a3520aa4ce3b8cfa312e025b1","kind":"field_change","created_at":"2026-08-22T10:43:32.929553169Z","actor":"Sam Catlow","issue_id":"archie-core-ippu","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: TurnRecord now persists tool-call activity alongside ResponseText; the completed-duplicate replay path replays it via stream.ToolCall before the text. Prior-reply fallback documented as deliberately text-only (crash race with no persisted tool record). Commit 86a9731, task check clean, adversarial review clean (0 findings)."}}
|
||||
{"id":"int-d9f51ffd469b2da49ca85951b83749f4","kind":"field_change","created_at":"2026-08-22T10:51:28.14819806Z","actor":"Sam Catlow","issue_id":"archie-core-1786637493205-131-a3dd2b53","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-ac3e88053eb75fae03ab1f8365844175","kind":"field_change","created_at":"2026-08-22T10:56:58.663854981Z","actor":"Sam Catlow","issue_id":"archie-core-j8b4","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented persistent session transcript, cross-session memory, and staged plugin storage"}}
|
||||
{"id":"int-d145e6fe5da65f8df6e433afcf8b02e8","kind":"field_change","created_at":"2026-08-22T11:13:23.297308578Z","actor":"Sam Catlow","issue_id":"archie-core-qk8m","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: MCP npm servers for per-task containers now reuse a persistent npm cache. Added mcp.NpmCacheEnv (shared with the daemon-side fix), an always-on archie-cache-mcp-npm Docker volume mounted at /data/cache/mcp-npm on every task container regardless of ecosystem, and wired it into internal/app/agentworker/mcp_providers.go's stdio transport construction. Adversarial review found zero surviving findings."}}
|
||||
{"id":"int-c1baa90874e9de48952955e52a5760d2","kind":"field_change","created_at":"2026-08-22T11:47:02.381816994Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented per-dispatch publication grants, removed sandbox-selected prepare/path authority, made repository worktree keys collision-free, and added fail-closed legacy migration/cleanup coverage."}}
|
||||
{"id":"int-3eca62d9ff92647ebeb091e5afe7e80a","kind":"field_change","created_at":"2026-08-22T11:47:02.632518654Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.2","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented per-dispatch publication grants, removed sandbox-selected prepare/path authority, made repository worktree keys collision-free, and added fail-closed legacy migration/cleanup coverage."}}
|
||||
{"id":"int-389951a8f299a389cbb0432044362797","kind":"field_change","created_at":"2026-08-22T11:55:19.903017141Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Retry refresh now removes all non-HEAD worktree content including ignored output while preserving .git, tracked symlinks, and gitlinks; missing bases fail closed."}}
|
||||
{"id":"int-56c541cf59441d3b82a65bc0ee53e38c","kind":"field_change","created_at":"2026-08-22T11:55:20.137923996Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.4","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Retry refresh now removes all non-HEAD worktree content including ignored output while preserving .git, tracked symlinks, and gitlinks; missing bases fail closed."}}
|
||||
{"id":"int-91757c22c0f3dff173e70e5eeff9447c","kind":"field_change","created_at":"2026-08-22T11:59:36.859035164Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.5","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Three-dot diff operations now fail closed when base and HEAD have no common ancestor; regression covers Diff, ChangedFiles, and ChangedLines."}}
|
||||
{"id":"int-2fceaface0b1804f99343a043a446532","kind":"field_change","created_at":"2026-08-22T12:16:02.43722871Z","actor":"Sam Catlow","issue_id":"archie-core-azbo","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Removed the unwired BasePlatformAdapter, SendResult, ChatInfo, and their test-only stub. CapabilitiesOf is absent from the current checkout/history. Gateway and worktree tests pass. task check passes all packages except the pre-existing tracked agentworker architecture failure archie-core-hqst."}}
|
||||
{"id":"int-41f3180369b3e3d59287b8b661403433","kind":"field_change","created_at":"2026-08-22T15:03:38.692577153Z","actor":"Sam Catlow","issue_id":"archie-core-1786637493329-136-49b39c78","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Media portion delivered: gateway.MediaSender + telegramMediaSender + TurnStream.Media wiring in Telegram's liveReply. Typing/edit/delete indicators from this issue's original scope are NOT done -- splitting them out if still wanted, since they're unrelated to the video-gen work that drove this."}}
|
||||
{"id":"int-46b6d680396e11becb59162374a2ab2d","kind":"field_change","created_at":"2026-08-22T15:34:28.584715451Z","actor":"Sam Catlow","issue_id":"archie-core-3ghy","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Shipped and verified: task check equivalent (fmt/vet/build/test/lint) is clean across every touched package, red-then-green throughout. See the issue description for what's in scope and what's explicitly deferred."}}
|
||||
{"id":"int-5acd1f65b747a819d5989f2cbd6555f9","kind":"field_change","created_at":"2026-08-22T18:14:27.709722923Z","actor":"Sam Catlow","issue_id":"archie-core-bia3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Release blockers fixed and pushed to main: ea76432 restored the media delivery result without reviving BasePlatformAdapter; ef2abd1 and bf72384 made the ClaimTurn regression isolate its intended race and yield between bounded SQLITE_BUSY retries. Full task check and fresh adversarial reviews passed."}}
|
||||
{"id":"int-5dbcbfe3c8952f34e98764ab2cbd8385","kind":"field_change","created_at":"2026-08-22T18:14:27.90016743Z","actor":"Sam Catlow","issue_id":"archie-core-mzok","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Release blockers fixed and pushed to main: ea76432 restored the media delivery result without reviving BasePlatformAdapter; ef2abd1 and bf72384 made the ClaimTurn regression isolate its intended race and yield between bounded SQLITE_BUSY retries. Full task check and fresh adversarial reviews passed."}}
|
||||
{"id":"int-c0a168ef2d814e50f8a7da0977803cf9","kind":"field_change","created_at":"2026-08-23T12:16:00.770399554Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942540-18-9af78536","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Deprioritized: prompt-level fix landed in fba80e3 (archie-core-3jag/GH#524) covers the general overconfidence pattern. Not worth mechanical enforcement (postcondition checks, tool-result verification) unless this recurs — revisit with stronger prompting first if it does."}}
|
||||
{"id":"int-995acdba52b55d8b0e6672f6992776ae","kind":"field_change","created_at":"2026-08-23T12:23:14.012827011Z","actor":"Sam Catlow","issue_id":"archie-core-w35v","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: themed .wf-form input/select/textarea in workflows.css to match the dark theme."}}
|
||||
{"id":"int-4efd5606f47f481644632143278c7467","kind":"field_change","created_at":"2026-08-23T12:58:06.612102627Z","actor":"Sam Catlow","issue_id":"archie-core-nln7","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: dashboard installs now get a ReportPath, and Server.Run relays/verifies/clears the phase-2 report on boot via a new KindUpdateReport SSE event. Adversarial review clean."}}
|
||||
{"id":"int-8c5d7ad3a23429d7067aa61abb1663d8","kind":"field_change","created_at":"2026-08-23T13:18:03.290726019Z","actor":"Sam Catlow","issue_id":"archie-core-1786751948782-3-837a8fd0.1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: archie-agent's build is now stamped (installtype + agentworker.Version), and it reports both back to the daemon in every taskrun.Response. daemon.AgentStatus records the latest observation; daemonRunningVersions includes the agent component once one lands. Adversarial review clean (one nice-to-have comment added)."}}
|
||||
{"id":"int-ef61375b05a90bf9dd2556180d1415f8","kind":"field_change","created_at":"2026-08-23T13:28:53.602582269Z","actor":"Sam Catlow","issue_id":"archie-core-1786751948782-3-837a8fd0.2","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: Component gained InstallType/Reference, populated via Service.Enrich from installtype.Type() (daemon), observed AgentStatus (agent), and [nats] config (third-party). Adversarial review clean (one lint-consistency nit fixed: use config.NATSMode* constants instead of raw strings)."}}
|
||||
{"id":"int-781cec687e88474013c495d0540b6cdd","kind":"field_change","created_at":"2026-08-23T13:33:21.1202539Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490815-39-45528ea3","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-00d1661f1d257b2236cbd4465f4c39ab","kind":"field_change","created_at":"2026-08-23T13:36:51.728538277Z","actor":"Sam Catlow","issue_id":"archie-core-1786751948782-3-837a8fd0.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: GET /api/version + Configuration-page 'Update status' card, sourced from the InstallType/Reference/RunningVersions plumbing landed in .1/.2. Adversarial review found one real bug (Installed=='' with Available set incorrectly returned update_available instead of unknown) and one test gap (present-but-empty running-version map entry) -- both fixed, tests added, all green."}}
|
||||
{"id":"int-3692dd90f21567b32a55aeea992fc247","kind":"field_change","created_at":"2026-08-23T13:36:52.845688289Z","actor":"Sam Catlow","issue_id":"archie-core-1786751948782-3-837a8fd0","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"All 5 design points landed: installtype package + fail-closed dispatcher + post-install Verify (3fb4857/c25799e, prior work), archie-agent build stamping + NATS status self-report (.1), Component.InstallType/Reference enrichment (.2), and GET /api/version + Configuration status block (.3). Each sub-issue passed an independent adversarial review pass."}}
|
||||
{"id":"int-7191af3e85066b68e54e0a230bebdcaa","kind":"field_change","created_at":"2026-08-23T15:34:38.78246011Z","actor":"Sam Catlow","issue_id":"archie-core-tzzn","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented compact fenced tool progress, schema/input suppression, bounded output, error status rendering, and regression coverage. Existing workspace exclusion keeps task agents rooted to their worktree."}}
|
||||
{"id":"int-515845d1ec5f05f8235d7c783c4c85b4","kind":"field_change","created_at":"2026-08-23T22:37:28.469553593Z","actor":"Sam Catlow","issue_id":"archie-core-1787489595853-6-50e11603","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate epic; canonical versions are archie-core-t2db (#541), archie-core-7d5u (#547), and archie-core-h019 (#552) with proper work breakdown"}}
|
||||
{"id":"int-5822698bc0a7fbf38f19de76ce8239b8","kind":"field_change","created_at":"2026-08-23T22:37:28.54753591Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596426-13-e24a2c83","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate epic; canonical versions are archie-core-t2db (#541), archie-core-7d5u (#547), and archie-core-h019 (#552) with proper work breakdown"}}
|
||||
{"id":"int-2c0fdd1b8ef3d2544631e66e9256a596","kind":"field_change","created_at":"2026-08-23T22:37:28.616346608Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596754-17-3b1639d9","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate epic; canonical versions are archie-core-t2db (#541), archie-core-7d5u (#547), and archie-core-h019 (#552) with proper work breakdown"}}
|
||||
{"id":"int-3745f04a427462219e754900166b0747","kind":"field_change","created_at":"2026-08-23T22:39:29.465123804Z","actor":"Sam Catlow","issue_id":"archie-core-1787489595508-2-98c4b849","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-8c03284d0ab07cdd6eeafc8a13df4e94","kind":"field_change","created_at":"2026-08-23T22:39:29.517364936Z","actor":"Sam Catlow","issue_id":"archie-core-1787489595596-3-e2c56185","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-6f64acb9ad5afc8a63d756e32c801887","kind":"field_change","created_at":"2026-08-23T22:39:29.55960528Z","actor":"Sam Catlow","issue_id":"archie-core-1787489595777-5-bc238550","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-c0cc2bce4187076ac4ad952458875124","kind":"field_change","created_at":"2026-08-23T22:39:29.610435241Z","actor":"Sam Catlow","issue_id":"archie-core-1787489595942-7-3ec33776","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-52ba3a752e8c6003add39f0e07a2839b","kind":"field_change","created_at":"2026-08-23T22:39:29.655650025Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596025-8-afa6f721","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-1ab9d84650c5b002065e5489f1dc3bb4","kind":"field_change","created_at":"2026-08-23T22:39:29.700291737Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596102-9-3ec24fcd","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-54008c40d7b62c330f50551c6dfd35f1","kind":"field_change","created_at":"2026-08-23T22:39:29.744584834Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596182-10-d1e59e32","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-ed29c6020e0e13c0dfae8115d2d98dda","kind":"field_change","created_at":"2026-08-23T22:39:29.793561788Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596259-11-317f7079","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-f01e36e30010b5cf832c9fc80eb5e146","kind":"field_change","created_at":"2026-08-23T22:39:29.834506984Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596341-12-bf9443bb","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-3e24295d42f6d0d7f4d78a9e0f906daf","kind":"field_change","created_at":"2026-08-23T22:39:29.878271586Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596505-14-5b6c5494","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-7ea2725e048024e3bdcd313dcdc9f51e","kind":"field_change","created_at":"2026-08-23T22:39:29.920488311Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596587-15-fdd1dcbd","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-4afa382e87012778d88ef142bc3a7f24","kind":"field_change","created_at":"2026-08-23T22:39:29.966218413Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596676-16-d40037d5","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-0d31a3192b0d2d7730604e9075b8b1ec","kind":"field_change","created_at":"2026-08-23T22:39:30.011051192Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596831-18-366fdec1","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-eacf8c210b1b56df2d4565017660e5dd","kind":"field_change","created_at":"2026-08-23T22:39:30.053392332Z","actor":"Sam Catlow","issue_id":"archie-core-1787489596921-19-cf6351d9","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-1e53e4e25d7c160f193963bfd8820f4b","kind":"field_change","created_at":"2026-08-23T22:39:30.093631252Z","actor":"Sam Catlow","issue_id":"archie-core-1787489597001-20-4a13bb0b","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-371170472ddc09164504bbd82c05b255","kind":"field_change","created_at":"2026-08-23T22:39:30.136166949Z","actor":"Sam Catlow","issue_id":"archie-core-1787489597088-21-878229b4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-2ba179f5c4ba1631d80779a5fad8ca5b","kind":"field_change","created_at":"2026-08-23T22:39:30.186688742Z","actor":"Sam Catlow","issue_id":"archie-core-1787489597173-22-c7110160","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-3e5507c3aec51ab0a437b02ecffbf9c7","kind":"field_change","created_at":"2026-08-23T22:39:30.227542015Z","actor":"Sam Catlow","issue_id":"archie-core-1787489597262-23-f61d8b1b","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duplicate; work tracked under canonical epic"}}
|
||||
{"id":"int-f979ee8ee60a3c0adbf39a22a633672f","kind":"field_change","created_at":"2026-08-24T01:52:44.870831411Z","actor":"Sam Catlow","issue_id":"archie-core-dfck","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"SDK v0.1.22 provides one bounded forced-finish recovery; Archie opts in through InProcessRunner. Focused test, task check, module verification, and independent adversarial review passed."}}
|
||||
{"id":"int-6e8c42f1e69eedcd00a9d80344b6ba43","kind":"field_change","created_at":"2026-08-24T03:11:49.10707373Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Retry cleaning was implemented in 0522fb7 (reset + cleanUntracked, covered by TestPrepareRecoversFromADirtyWorktreeOnRetry). Remaining defect fixed in 037ee7c: SkipDir on a .git gitdir *file* aborted the whole walk, so cleaning silently no-opped for linked/adopted worktrees. Regression test TestCleanUntrackedHandlesGitdirFile."}}
|
||||
{"id":"int-454dbecf0b5c42387933d52043eb1467","kind":"field_change","created_at":"2026-08-24T03:29:04.998835814Z","actor":"Sam Catlow","issue_id":"archie-core-1786637496459-254-ed0462dd","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented in internal/domain/scheduling (branch feat/275-ticker-engine): configurable tick interval, parallel and sequential pools, overlap suppression, per-run timeout, bounded graceful shutdown. Job store, blueprints and delivery routing remain open in the epic."}}
|
||||
{"id":"int-42c12c17771c1ffb33c642f7ed979b5a","kind":"field_change","created_at":"2026-08-24T03:31:57.542869797Z","actor":"Sam Catlow","issue_id":"archie-core-q15y.1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}}
|
||||
{"id":"int-b6abc3db88593e4acbb1592f6030c6d4","kind":"field_change","created_at":"2026-08-24T03:49:21.308803458Z","actor":"Sam Catlow","issue_id":"archie-core-q15y.2","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}}
|
||||
{"id":"int-242dc6f04510849195c2ca038cd8fa77","kind":"field_change","created_at":"2026-08-24T04:21:08.061548146Z","actor":"Sam Catlow","issue_id":"archie-core-q15y.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Removed daemon in-process, subprocess, per-stage NATS, and shared-worker execution. Autonomous workflow loops now exist only in task-scoped archie-agent workers; mandatory boot metadata and exact task subjects fail closed. task check, new-code lint, and independent adversarial review are clean."}}
|
||||
{"id":"int-1e97f94b0fefd3184ada857dfca189e6","kind":"field_change","created_at":"2026-08-24T04:46:53.931228211Z","actor":"Sam Catlow","issue_id":"archie-core-ite6","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"subscribeAgentEvents now flushes its SUB frame before returning and cleans up on failure; regression coverage and full gate pass."}}
|
||||
{"id":"int-8edaedd8b418b3e8f072ae78ab2fb10d","kind":"field_change","created_at":"2026-08-24T04:46:55.023036661Z","actor":"Sam Catlow","issue_id":"archie-core-5bsf","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Runtime updater now snapshots and restores the configured managed worker Docker image; runtime-only and combined rollback regressions pass."}}
|
||||
{"id":"int-54344d1b04602ef10199dcdfbb5e0bd8","kind":"field_change","created_at":"2026-08-24T04:46:55.40908275Z","actor":"Sam Catlow","issue_id":"archie-core-q15y.4","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fresh/default deployment uses native archied, embedded NATS, and managed task containers; external NATS remains the documented advanced broker profile."}}
|
||||
{"id":"int-af5bde29ff8336b8ef204d395a2c1bf6","kind":"field_change","created_at":"2026-08-24T04:46:55.845209007Z","actor":"Sam Catlow","issue_id":"archie-core-q15y","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"All four execution-topology children are complete: embedded/external NATS now hand full tasks only to managed containers, with no host agent loop."}}
|
||||
{"id":"int-31d0709485e67c3896872eb134bb1129","kind":"field_change","created_at":"2026-08-24T05:19:34.093642376Z","actor":"Sam Catlow","issue_id":"archie-core-ite6","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Completed; reconciled with the already-closed GitHub issue."}}
|
||||
{"id":"int-776a5af38d02b14950152fe8829a3f48","kind":"field_change","created_at":"2026-08-24T05:19:34.146183867Z","actor":"Sam Catlow","issue_id":"archie-core-5bsf","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Completed; reconciled with the already-closed GitHub issue."}}
|
||||
{"id":"int-46674d25397d4bb87c4f75e87a2f5f51","kind":"field_change","created_at":"2026-08-24T06:58:28.955164993Z","actor":"Sam Catlow","issue_id":"archie-core-q15y.1","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented in 5c4b599 (feat(nats): expose embedded broker to managed workers); per-start token, Docker bridge binding, frozen worker env. Verified landed on main."}}
|
||||
{"id":"int-4aecc62b26a3df39b17f4682206ec89c","kind":"field_change","created_at":"2026-08-24T06:58:29.426080813Z","actor":"Sam Catlow","issue_id":"archie-core-q15y.2","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented in 7d69001 (fix(daemon): require full-task worker handoff); daemon.process parks instead of running locally. Verified: no workflow.Run in internal/daemon non-test code, enforced by daemon/architecture_test.go:75."}}
|
||||
{"id":"int-e4a1c857586c68f78bd3f5d6874d7dcc","kind":"field_change","created_at":"2026-08-24T06:58:29.896805082Z","actor":"Sam Catlow","issue_id":"archie-core-q15y.3","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented in 157e99b (refactor(agentexec): remove legacy execution paths); [agent] is decode-only. Verified: no SubprocessRunner/inprocess symbols in non-test code."}}
|
||||
{"id":"int-f1e577ee35b687a0617cdad26cb580c7","kind":"field_change","created_at":"2026-08-24T06:58:41.632146038Z","actor":"Sam Catlow","issue_id":"archie-core-q15y.4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented in c978f10 (feat(deployment): default to managed NATS workers). Verified: no agent.mode/inprocess remains in install.sh, deployments/*.toml or config.example.toml; deployment_contract_test.go added to enforce it."}}
|
||||
{"id":"int-56bcf976359c43a00dc3757fc89078cf","kind":"field_change","created_at":"2026-08-24T06:58:42.063215911Z","actor":"Sam Catlow","issue_id":"archie-core-q15y","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"All four children landed across 5c4b599, 7d69001, 157e99b, c978f10. Autonomous workflows now have exactly one production path: full-task core-NATS handoff to a task-scoped archie-agent container."}}
|
||||
{"id":"int-8edf22bd0458137fd91f3b80d4acb4af","kind":"field_change","created_at":"2026-08-24T06:59:21.301579884Z","actor":"Sam Catlow","issue_id":"archie-core-mzok","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Already fixed on main: session_store_sqlite_claimturn_race_test.go now runs the 100 trials serially (two stores racing one turn ID per trial) with bounded SQLITE_BUSY retries, instead of 200 concurrent claims. Verified: -count=3 passes."}}
|
||||
{"id":"int-971aed43b8a5636652250beff7c51699","kind":"field_change","created_at":"2026-08-24T06:59:22.444580557Z","actor":"Sam Catlow","issue_id":"archie-core-bia3","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Already fixed on main: BasePlatformAdapter has zero references repo-wide, adapter_capabilities.go + tests stand alone. Verified: go build ./... clean, gateway capability tests pass."}}
|
||||
{"id":"int-bd4e16b5b180296dfc959ceeb82e8ce5","kind":"field_change","created_at":"2026-08-24T06:59:35.171117421Z","actor":"Sam Catlow","issue_id":"archie-core-hqst","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Resolved on main: persistent_runner.go no longer imports encoding/json and TestApplicationOwnsNoTransportWireMechanics passes."}}
|
||||
{"id":"int-e986333daa22fff3786fb38b392c5b7c","kind":"field_change","created_at":"2026-08-24T06:59:57.951926691Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.1","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed on main: worktreerpc now exposes only Push, authorized by an opaque per-dispatch grant issued from the dispatched *store.Task (worktreerpc.go:71-83). Sandbox input no longer selects host path, repo or branch; ValidCoordinates rejects traversal. Package tests pass."}}
|
||||
{"id":"int-bc056d31eee686ce6433448b42fd29ea","kind":"field_change","created_at":"2026-08-24T06:59:58.40724543Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.2","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed on main: Manager.Dir base64url-encodes owner and repo as separate path components (worktree.go:66-70), so a-b/c and a/b-c no longer collide. legacyDir+migrateLegacy migrate old flattened dirs only on exact origin match. Package tests pass."}}
|
||||
{"id":"int-2247890b19ea11880354613831bb67e9","kind":"field_change","created_at":"2026-08-24T07:00:22.696171953Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed on main: prepared-worktree refresh now returns the resolveBase error instead of swallowing it (worktree.go:253-258, 'a missing base is configuration or repository drift and must fail closed'); resolveBase tries the qualified remote ref then origin/<base> and errors otherwise."}}
|
||||
{"id":"int-93f6e8c3fbaae2a327aab94b82c2df56","kind":"field_change","created_at":"2026-08-24T07:00:28.838440356Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.5","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed on main: patch() now errors with 'no common ancestor' when MergeBase returns no bases (worktree.go:498-501) instead of falling back to a direct tree diff, so Diff/ChangedFiles/ChangedLines all fail closed on unrelated histories."}}
|
||||
{"id":"int-fe81497a545158a0c954b4548631633f","kind":"field_change","created_at":"2026-08-24T07:12:05.178596666Z","actor":"Sam Catlow","issue_id":"archie-core-h019.1","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"One-page decision written at docs/prds/adversarial-self-review.md: reviewer runs in a second workspace (container or in-process) pointed at a .git-stripped snapshot of the reviewed commit, never the implementer's worktree; findings contract is workflow.ReviewFinding, owned by internal/domain/workflow, reported via a structured capture tool; a surviving error-level finding sets StatusParked (not WaitingHuman -- epic wording named two different states, this resolves which); model/effort reuse the existing Models[role] map and per-stage budget override, gated by a new opt-in Repo.ReviewEnabled so h019.4 doesn't gate every repo on an uncalibrated reviewer before h019.5 lands. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-42343a99009cf6873fce96a2c82ba389","kind":"field_change","created_at":"2026-08-24T07:12:06.369962622Z","actor":"Sam Catlow","issue_id":"archie-core-7d5u.5","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Investigated first: the dedup mechanism (TaskEnvelope.IdempotencyKey + PublishUnique + JetStream Nats-Msg-Id dedup) and the shared dispatch predicate were already fully wired by 7d5u.4 -- no double-dispatch code change was needed. Closed the two real gaps: (1) internal/infrastructure/eventbus/nats/dedup_test.go is a new regression test proving PublishUnique actually suppresses a duplicate publish on the same WorkQueuePolicy stream ARCHIE_TASKS uses in production; (2) internal/forge/webhook/receiver.go gained Status()/GET support tracking authenticated deliveries vs successful publishes separately, so a wedged or non-delivering receiver is observable rather than indistinguishable from an idle repo. AC's poll/webhook parity clause (disabling webhook still polls) is satisfied architecturally with no code change possible to violate it -- verified Cycle()/Run() never reference cfg.Forge.Intake anywhere in internal/daemon; only setupForgeWebhook in cmd/archied/bootstrap.go gates the webhook HTTP server. Adversarial review pass (fresh subagent, -race) found zero blocking issues; closed two minor coverage gaps it flagged. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-803c42454dcc93825d57fd64b06290c1","kind":"field_change","created_at":"2026-08-24T07:12:06.82962997Z","actor":"Sam Catlow","issue_id":"archie-core-1786637492559-106-5ea2315d","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented code-fence-aware Telegram message splitting with bounded continuation handling and regression coverage [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-fca467b0bda953484c17e18918362f38","kind":"field_change","created_at":"2026-08-24T07:12:07.207279124Z","actor":"Sam Catlow","issue_id":"archie-core-ippu","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: TurnRecord now persists tool-call activity alongside ResponseText; the completed-duplicate replay path replays it via stream.ToolCall before the text. Prior-reply fallback documented as deliberately text-only (crash race with no persisted tool record). Commit 86a9731, task check clean, adversarial review clean (0 findings). [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-ce49b4bfa7a9309c5e026b93ba263851","kind":"field_change","created_at":"2026-08-24T07:12:07.588050015Z","actor":"Sam Catlow","issue_id":"archie-core-1786637493205-131-a3dd2b53","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-5f3c3d77e64802ed75d947560e23cb81","kind":"field_change","created_at":"2026-08-24T07:12:08.005056434Z","actor":"Sam Catlow","issue_id":"archie-core-j8b4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented persistent session transcript, cross-session memory, and staged plugin storage [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-9ecea248febfdd7956009b66fe4aa150","kind":"field_change","created_at":"2026-08-24T07:12:08.400878511Z","actor":"Sam Catlow","issue_id":"archie-core-qk8m","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: MCP npm servers for per-task containers now reuse a persistent npm cache. Added mcp.NpmCacheEnv (shared with the daemon-side fix), an always-on archie-cache-mcp-npm Docker volume mounted at /data/cache/mcp-npm on every task container regardless of ecosystem, and wired it into internal/app/agentworker/mcp_providers.go's stdio transport construction. Adversarial review found zero surviving findings. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-74c9b16831b72e7c2a39ff730de4c107","kind":"field_change","created_at":"2026-08-24T07:12:08.802194791Z","actor":"Sam Catlow","issue_id":"archie-core-azbo","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Removed the unwired BasePlatformAdapter, SendResult, ChatInfo, and their test-only stub. CapabilitiesOf is absent from the current checkout/history. Gateway and worktree tests pass. task check passes all packages except the pre-existing tracked agentworker architecture failure archie-core-hqst. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-a97be73b9145b6d78b9f80e2b116bf0f","kind":"field_change","created_at":"2026-08-24T07:12:09.224403876Z","actor":"Sam Catlow","issue_id":"archie-core-1786637493329-136-49b39c78","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Media portion delivered: gateway.MediaSender + telegramMediaSender + TurnStream.Media wiring in Telegram's liveReply. Typing/edit/delete indicators from this issue's original scope are NOT done -- splitting them out if still wanted, since they're unrelated to the video-gen work that drove this. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-daf488dc4ef11bf278e406e5d65c4a48","kind":"field_change","created_at":"2026-08-24T07:12:09.625994864Z","actor":"Sam Catlow","issue_id":"archie-core-3ghy","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Shipped and verified: task check equivalent (fmt/vet/build/test/lint) is clean across every touched package, red-then-green throughout. See the issue description for what's in scope and what's explicitly deferred. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-2dac3657dabd2829e5a24e6c0e5bf671","kind":"field_change","created_at":"2026-08-24T07:12:10.060099361Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942540-18-9af78536","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Deprioritized: prompt-level fix landed in fba80e3 (archie-core-3jag/GH#524) covers the general overconfidence pattern. Not worth mechanical enforcement (postcondition checks, tool-result verification) unless this recurs — revisit with stronger prompting first if it does. [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-77e557b6a8cbb8b826dcf400ee419b39","kind":"field_change","created_at":"2026-08-24T07:12:10.478442214Z","actor":"Sam Catlow","issue_id":"archie-core-w35v","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: themed .wf-form input/select/textarea in workflows.css to match the dark theme. [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-cdec894a69ee94b7a0011cf0bb06683d","kind":"field_change","created_at":"2026-08-24T07:12:10.913658383Z","actor":"Sam Catlow","issue_id":"archie-core-1786751948782-3-837a8fd0.1","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: archie-agent's build is now stamped (installtype + agentworker.Version), and it reports both back to the daemon in every taskrun.Response. daemon.AgentStatus records the latest observation; daemonRunningVersions includes the agent component once one lands. Adversarial review clean (one nice-to-have comment added). [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-765118ce3cf8f020020fcd8ef76879e5","kind":"field_change","created_at":"2026-08-24T07:12:11.379239858Z","actor":"Sam Catlow","issue_id":"archie-core-1786751948782-3-837a8fd0.2","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: Component gained InstallType/Reference, populated via Service.Enrich from installtype.Type() (daemon), observed AgentStatus (agent), and [nats] config (third-party). Adversarial review clean (one lint-consistency nit fixed: use config.NATSMode* constants instead of raw strings). [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-4cf7ad8912f5fbf96dd4111ba46d9f9a","kind":"field_change","created_at":"2026-08-24T07:12:11.82615813Z","actor":"Sam Catlow","issue_id":"archie-core-1786751948782-3-837a8fd0.3","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: GET /api/version + Configuration-page 'Update status' card, sourced from the InstallType/Reference/RunningVersions plumbing landed in .1/.2. Adversarial review found one real bug (Installed=='' with Available set incorrectly returned update_available instead of unknown) and one test gap (present-but-empty running-version map entry) -- both fixed, tests added, all green. [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-24dfa19bb0c13eba84871d83d412520b","kind":"field_change","created_at":"2026-08-24T07:12:12.273422399Z","actor":"Sam Catlow","issue_id":"archie-core-dfck","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"SDK v0.1.22 provides one bounded forced-finish recovery; Archie opts in through InProcessRunner. Focused test, task check, module verification, and independent adversarial review passed. Re-verified 2026-08-24: the opt-in moved from the deleted InProcessRunner to agentexec.NewLoopRunner (loop_runner.go:106 CompletionForceFinish), which is what the archie-agent worker constructs; ai-sdk still v0.1.22. [Closure restored 2026-08-24: originally closed 2026-08-24, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]"}}
|
||||
{"id":"int-33653ae0f02479da575ee2b075218ac6","kind":"field_change","created_at":"2026-08-24T07:59:38.613969236Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.7","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}}
|
||||
{"id":"int-e5c0464ce6117a2013ccdccf67829c46","kind":"field_change","created_at":"2026-08-24T08:15:46.802569084Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.6","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: recordUpstream extracted from Push (worktree.go:465); a post-publication config failure is now a logged warning and Push returns success once the remote ref is published. Manager gained an optional Log field with a slog.Default() fallback. Verified by inspection rather than a red run -- the test uses the new Log field so it cannot compile against the pre-fix code. task check green; fresh adversarial review (independent, did not write the code) zero findings."}}
|
||||
{"id":"int-07bcd93041cf024404279b55497e4f4a","kind":"field_change","created_at":"2026-08-24T08:15:48.462601908Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.8","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: CommitAll now takes a live context and checks ctx.Err() before open, worktree, staging, status and commit (worktree.go:398-430), so a pre-cancelled context mutates neither index nor HEAD. Proven red against pre-fix code: 'CommitAll() error = nil, want context canceled' for both a cancelled context and an expired deadline. task check green; fresh adversarial review zero findings."}}
|
||||
{"id":"int-997fffb13822c36e05730e69110d7602","kind":"field_change","created_at":"2026-08-24T08:15:48.90789093Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw.9","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: precedence is now title-first via parseTitlePrefix with a labels fallback and 'feat' default; the strings.TrimSuffix(prefix, \"\") no-op is gone; the dead body parameter is removed from archieBranch and its call site (worktree.go:131); branchSlug's doc now says 60, matching the implementation. go fix later modernised parseTitlePrefix to strings.Cut -- verified equivalent (Cut splits on the first separator; ok mirrors idx != -1). Verified by inspection rather than a red run, since the signature change prevents compiling the tests against pre-fix code. task check green; fresh adversarial review zero findings."}}
|
||||
{"id":"int-01f64138504555374b1349cc30e94c40","kind":"field_change","created_at":"2026-08-24T08:15:59.810530521Z","actor":"Sam Catlow","issue_id":"archie-core-1ysw","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"All 9 children complete. The P0/P1 trust-boundary and correctness defects (.1 RPC task binding, .2 colliding directory keys, .3 untracked cleanup, .4 fail-closed base resolution, .5 three-dot merge-base semantics) were already fixed on main and reconciled 2026-08-24. The remaining four (.6 push result, .7 no-change worktree leak, .8 commit cancellation, .9 branch naming contract) were implemented this session, merged as 474c31d and its two merge commits, task check green, with an independent adversarial review reporting zero findings."}}
|
||||
{"id":"int-df896cababb907b14b094c56b928ebd3","kind":"field_change","created_at":"2026-08-24T09:15:55.715496686Z","actor":"Sam Catlow","issue_id":"archie-core-h019.2","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented: workflow.ReviewFinding + ReviewReport in internal/domain/workflow/review_findings.go, merged 53bb841. The domain owns the type; gate.Finding was used as a shape precedent only, not reused, so the review contract is not coupled to the Yaegi gate's evolution. Blocking requires Verdict==confirmed AND Level==error, so a PLAUSIBLE finding never blocks however severe it claims to be. ReviewStatus makes 'ran and found nothing' structurally distinct from 'never ran' -- Passed() is false for a zero-value report, and the distinction does not rest on nil-vs-empty-slice. JSON round-trip covered; Line 0 is preserved (no omitempty) for whole-file findings. Review found and fixed a duplicate package doc comment and a redundant ReviewBlocking/BlockingReviewFindings alias pair. task check green. Fresh adversarial review clean across 8 dimensions; I independently mutation-tested the blocking rule: dropping the verdict check fails 5 tests (incl. plausible_error_MUST_NOT_block) and dropping the level check fails 5 more, so the tests genuinely pin both halves."}}
|
||||
{"id":"int-bc45db099eb63b2e22f27449984fd770","kind":"field_change","created_at":"2026-08-24T15:42:47.277649102Z","actor":"Sam Catlow","issue_id":"archie-core-0dic","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}}
|
||||
{"id":"int-6ef69a7ebb781fb99529e52ef038cdaf","kind":"field_change","created_at":"2026-08-24T15:43:19.639842603Z","actor":"Sam Catlow","issue_id":"archie-core-absb","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"send_file tool plus upload-by-reader delivery; commit 9a45fbb"}}
|
||||
{"id":"int-fd47d92bec50df8b1766cccc3d17ca82","kind":"field_change","created_at":"2026-08-24T17:00:21.332713238Z","actor":"Sam Catlow","issue_id":"archie-core-b7f1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented UUIDv7 identities, replayable archived chat tool activity, and post-start update report delivery; full quality gate passes."}}
|
||||
{"id":"int-69455e46e4de1e58cef4cdc6a124ca5f","kind":"field_change","created_at":"2026-08-24T17:19:41.905294834Z","actor":"Sam Catlow","issue_id":"archie-core-4tye","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented, regression-tested, full task check passed, and adversarial review finding resolved."}}
|
||||
{"id":"int-084477087493b06c289d87dfc319c6d3","kind":"field_change","created_at":"2026-08-24T17:19:41.96078947Z","actor":"Sam Catlow","issue_id":"archie-core-y1hv","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented, regression-tested, full task check passed, and adversarial review finding resolved."}}
|
||||
{"id":"int-9de2b83189f32eec56dd588dd4b1c439","kind":"field_change","created_at":"2026-08-24T17:28:38.936618176Z","actor":"Sam Catlow","issue_id":"archie-core-15iq","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented with regression coverage, full task check passing, and adversarial review clean."}}
|
||||
{"id":"int-45a964f90a687ff51f5d7678683f2706","kind":"field_change","created_at":"2026-08-24T17:28:38.999458853Z","actor":"Sam Catlow","issue_id":"archie-core-473l","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented with regression coverage, full task check passing, and adversarial review clean."}}
|
||||
{"id":"int-208089f7a06402742d9c8765472ed479","kind":"field_change","created_at":"2026-08-24T17:55:34.430893806Z","actor":"Sam Catlow","issue_id":"archie-core-jy5m","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Task timelines now render stage/retry context; baseline and gate-cycle logs expose useful bounded failure output. task check and independent review pass."}}
|
||||
{"id":"int-196298a33f71370a0a0c538590985b53","kind":"field_change","created_at":"2026-08-24T19:48:32.993325535Z","actor":"Sam Catlow","issue_id":"archie-core-n5sr","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Provider usage is durable by stage, baseline repair is included, model-adaptive compaction is enabled without a token cap, and ai-sdk preserves partial/compaction usage. task check and fresh adversarial review pass."}}
|
||||
{"id":"int-574291f5bd917eaf7b78056b15abffcb","kind":"field_change","created_at":"2026-08-24T19:48:34.38833081Z","actor":"Sam Catlow","issue_id":"archie-core-nq0c","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Commit identity now crosses the task boundary, per-identity email defaults are derived when omitted, and the worker end-to-end test verifies author and committer. task check and fresh adversarial review pass."}}
|
||||
{"id":"int-b91d5f4013ec1fde90a34b440e87b986","kind":"field_change","created_at":"2026-08-24T19:48:34.825217514Z","actor":"Sam Catlow","issue_id":"archie-core-z0u8","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"The API now supplies canonical per-task GitHub or Gitea URLs and the dashboard consumes them directly. Regression coverage, task check, and fresh adversarial review pass."}}
|
||||
{"id":"int-77c23261cb5fd1c2881ff882de56d86e","kind":"field_change","created_at":"2026-08-25T15:05:23.948131293Z","actor":"Sam Catlow","issue_id":"archie-core-p1bl","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Shipped in 6a23f8d: logging resolves every non-nil error attribute through Error(), with custom unexported-field and typed-nil regression coverage; included in archied v1.18.0."}}
|
||||
{"id":"int-ff379eca588df2a11fc3bf5121a7cc18","kind":"field_change","created_at":"2026-08-25T15:05:25.362400545Z","actor":"Sam Catlow","issue_id":"archie-core-440c","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Shipped in 16f9456: explicitly configured trusted forwarded headers drive effective Origin validation, with direct/proxied/spoofed regression coverage; included in archied v1.18.0."}}
|
||||
{"id":"int-d61ab877d6ab666df299085a52ca1c75","kind":"field_change","created_at":"2026-08-25T16:02:24.011512716Z","actor":"Sam Catlow","issue_id":"archie-core-vq92","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"task_logs cursor pagination, level/time filters, and honest truncation reporting"}}
|
||||
{"id":"int-6578329d076c7da3806f4c446f2dfe20","kind":"field_change","created_at":"2026-08-27T14:31:41.48495579Z","actor":"Sam Catlow","issue_id":"archie-core-1786637489932-6-1f803e02","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Wired GET /api/curators (names, health, last-run, recent actions) backed by a new bounded in-memory activity tracker in internal/domain/curator, plus a Curators dashboard page at ui/src/curators/."}}
|
||||
{"id":"int-ca5043a35866779a1ff6969afe4b98d3","kind":"field_change","created_at":"2026-08-28T10:59:18.865497151Z","actor":"Sam Catlow","issue_id":"archie-core-1786637496320-249-be6d9a20.1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Slice 1 of cron/scheduling epic landed: per-profile JSON store with cross-process flock, merge-semantic Update, version-stamped schema, ErrCorruptFile on truncated files, ErrUnsupportedSchema on forward versions. Implements scheduling.JobSource so the ticker engine can poll it without knowing the file layout. Adversarial review applied: deep-copy Get/List, pool validation in Create/Update, ErrScheduleUnsupported on Once MarkRun, 0o600 file mode, SetEscapeHTML(false) for operator-readable files, fsync before rename for durability, ErrClosed sentinel after Close, real cross-process flock test via os/exec. task check green."}}
|
||||
{"id":"int-2cfa12d6d6ab2555475033ca3c3d4a48","kind":"field_change","created_at":"2026-08-31T10:03:46.34399459Z","actor":"Sam Catlow","issue_id":"archie-core-bas7","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Added missing test + CLAUDE.md reference to ARCHITECTURE.md#plugin-engine-rule-strict"}}
|
||||
{"id":"int-4ed850ca96fe030bea8ccc85ffb14dd6","kind":"field_change","created_at":"2026-08-31T10:04:10.364314672Z","actor":"Sam Catlow","issue_id":"archie-core-1sjk","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"go.mod already at 1.27.0 (supersedes 1.26.6 CVE fix); bumped both Dockerfiles from golang:1.26-trixie to golang:1.27-trixie to match"}}
|
||||
{"id":"int-1c8f871a9893894d6a38b38a8cdc4dc5","kind":"field_change","created_at":"2026-08-31T10:04:52.887508436Z","actor":"Sam Catlow","issue_id":"archie-core-2tqh","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Reconciled migration-decisions.md with actual tree: confirmed curator/mapping/scheduling as legitimate domains (were undocumented, not misplaced), documented that identity/agent/messaging/plugin are approved-but-unmaterialised targets rather than creating dead stub packages"}}
|
||||
{"id":"int-f073a26e120e051d468475af5b40944f","kind":"field_change","created_at":"2026-08-31T10:05:31.24577816Z","actor":"Sam Catlow","issue_id":"archie-core-zq4l","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Switched CI to actions/setup-go go-version-file: go.mod so CI's Go version is always sourced from go.mod directly, eliminating drift"}}
|
||||
{"id":"int-3efcffdcd23615693655eca568c69456","kind":"field_change","created_at":"2026-08-31T10:05:53.315558477Z","actor":"Sam Catlow","issue_id":"archie-core-0bvr","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Added 'task vuln' (govulncheck) to Taskfile, deliberately kept out of task check since it needs network access to the vuln DB; wired as a separate CI step in deploy.yml"}}
|
||||
{"id":"int-864ce794c14f56fd0c16c4502c964c4b","kind":"field_change","created_at":"2026-08-31T10:06:41.867659939Z","actor":"Sam Catlow","issue_id":"archie-core-tnsr","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"go.mod already on ai-sdk v0.1.30. Refactored pluginToolSet and scriptToolSet in internal/agentexec/loop_runner.go to use NewTypedTool instead of hand-written JSON Schema + manual unmarshal; tests pass"}}
|
||||
{"id":"int-63772b74965b7fe43a50198a54f568d8","kind":"field_change","created_at":"2026-08-31T10:09:58.63859751Z","actor":"Sam Catlow","issue_id":"archie-core-p3wt","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Duration and TaskEnvelope were already consistent by the time this was picked up; fixed the remaining recvcheck violation on Provenance (Paths/String moved to pointer receiver to match the mutating record() method). All Provenance uses are through addressable struct fields, so build/tests are unaffected. recvcheck now reports 0 issues."}}
|
||||
{"id":"int-9eeadba2e982ae4000e6dd37aaea420e","kind":"field_change","created_at":"2026-08-31T10:10:50.270527399Z","actor":"Sam Catlow","issue_id":"archie-core-d66k","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Added internal/gateway, internal/tools, internal/memory, internal/secret, internal/plugin, internal/skill to ARCHITECTURE.md Package Map with LOC and role descriptions"}}
|
||||
{"id":"int-f575951da73a5707c81493b368531413","kind":"field_change","created_at":"2026-08-31T10:12:25.271511127Z","actor":"Sam Catlow","issue_id":"archie-core-g1y3","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Resolved migration-decisions.md's open Session/Messaging decision: keep internal/gateway as-is rather than risk a big-bang rewrite of live session/compression/approval/branch logic. Materialised internal/domain/messaging with the already-settled canonical Message/Conversation/ToolCall/ToolResult types (composite Conversation identity, immutable MessageID, branch lineage), with tests. Actual gateway migration onto these types is tracked as sequenced follow-up bd issues (d9dv, 4hof, o4e4, h3w2, label messaging-migration) so each channel lands with its own verification."}}
|
||||
{"id":"int-d6e7e2aa2c469fd389151e0202b5a036","kind":"field_change","created_at":"2026-08-31T11:27:14.46134892Z","actor":"Sam Catlow","issue_id":"archie-core-kg1w","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Extracted the full cmd/archied wiring package into internal/app/archied (matching the sibling internal/app/agentworker pattern); cmd/archied/main.go is now 18 lines (codesearch-helper dispatch + call into archied.Run()). Fixed two architecture tests still hardcoded to the old cmd/archied path. task check passes clean."}}
|
||||
{"id":"int-d9b75b37f0500c88f598cd75d42bba9d","kind":"field_change","created_at":"2026-08-31T11:27:20.577217872Z","actor":"Sam Catlow","issue_id":"archie-core-k7y7","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Raised coverage: workintake 14.3%->94.6%, secret/enginehost 0%->100%, secret/secretextract 10%->100%, forge 36.1%->77.0%, natsrpc 28.3%->91.3%. Committed as bc5b355."}}
|
||||
{"id":"int-23a20b34ab857979d0935531ac8483b7","kind":"field_change","created_at":"2026-08-31T11:36:16.676339656Z","actor":"Sam Catlow","issue_id":"archie-core-agui","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"All 31 original findings (5 cyclop, 9 gocognit, 1 gocyclo, 2 nestif, plus incidental funlen) resolved via targeted extraction across tools/builtin, gateway, workflow, webui, telegram, cronstore, tomlwrite, agentexec. Remaining 6 lint findings (containedctx/errorlint/noctx/staticcheck) were never part of this bead's scope."}}
|
||||
{"id":"int-659ff8bb1ef5160f8bc3f1e3f31d3d75","kind":"field_change","created_at":"2026-08-31T11:51:41.85053027Z","actor":"Sam Catlow","issue_id":"archie-core-h019.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented as agent.Subagent inside the task-scoped archie-agent worker (internal/app/agentworker/review.go). Conversation isolation is structural (Subagent.Run only sends a prompt, never message history -- verified against a fake chat.Provider). Workspace isolation via new worktree.Manager.Snapshot (.git-free export of HEAD's tracked files into a scratch dir beside the task worktree). Reviewer's toolset is read-only (read/grep/find) rooted at the snapshot, never the worker's own toolset -- verified as a construction fact that the toolset contains no write/edit/shell tool and cannot read outside the snapshot dir. Findings captured via a typed record_finding tool appending to a slice the stage owns, surviving a Subagent.Run error when findings were already captured."}}
|
||||
{"id":"int-b0d4496e53ae09d1926495a2215fff13","kind":"field_change","created_at":"2026-08-31T11:51:43.090585774Z","actor":"Sam Catlow","issue_id":"archie-core-h019.4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"StageReview wired into the implement workflow between StageDiffCap and StageOpenPR. Fail-closed: not-run or a confirmed error-level finding parks (store.StatusParked) with findings in Detail; warn/plausible findings never block. Inert unless Repo.ReviewEnabled (new config field, default false); Models[\"reviewer\"] falls back to Models[\"builder\"]. task check clean, golangci-lint clean. Committed 8db8a17."}}
|
||||
{"id":"int-bdb049c55a0a716a843b41f25c644bd7","kind":"field_change","created_at":"2026-09-01T15:18:56.663403225Z","actor":"Sam Catlow","issue_id":"archie-core-atv2","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: stopRendering now marks the reply finalized, and appendFallbackLine sends a standalone follow-up message instead of writing into a dead render buffer. Covered by TestLiveReplyMediaFallbackAfterFinalizeSendsFollowUp."}}
|
||||
{"id":"int-79cc9ce98fc14750b24a9590b641f68c","kind":"field_change","created_at":"2026-09-01T15:30:08.83790169Z","actor":"Sam Catlow","issue_id":"archie-core-1786637500752-415-434e5bb9","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-6c8b1ec0ed98295ad0c7d27c65bd6696","kind":"field_change","created_at":"2026-09-01T15:55:33.214859138Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490069-11-e245c170","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Complete: internal/domain/memory/{contract,registrar,registry}.go stands up\nmemory as a conforming engine family, mirroring internal/domain/curator's\nsplit exactly per this issue's own notes.\n\nMemoryEngine (contract.go) embeds Lifecycle (Start/Health/Stop) and Store\n(Write/Query/List/Forget -- real operations, not identity metadata) plus\nName/Version/Manifest/Bind. Store is split out as its own embedded\ninterface so MemoryEngine stays under golangci-lint's interfacebloat\nthreshold, same mechanism as curator's embedded Lifecycle.\n\nRegistry (registry.go) owns Register/Get/Names/Start/Health/Stop with\nduplicate/nil-engine/panic-in-Bind rejection, per-engine Start failure\nisolation (one engine's failed Start does not block the others, and is\nreported via Health), ctx-bounded Stop, and reverse-registration-order\nshutdown -- all verified by registry_test.go, mirroring curator's test\nsuite. go test ./internal/domain/memory/... -race -count=1 is green;\ntask lint is 0 issues.\n\nRegistrar (registrar.go) carries EventSink and Clock -- the only host\nservices with anything to gate on today. No capability-filtering logic\nexists yet because no memory-specific host service is capability-gated\n(unlike curator's Tools/Skills), so Bind passes the host straight\nthrough; add filtering if/when a gated service appears.\n\nOne AC clause is not literally testable yet: internal/plugin/\narchitecture_test.go's TestEngineFamilyInspectionRejectsInvalidShapes\nonly scans inline fixture source, not the real package tree, so nothing\ncurrently asserts memory.MemoryEngine is \"recognised\" by it one way or\nthe other -- the shape matches curator's (which the fixture tests\nvalidate the pattern against), but there is no scan-the-repo test to\nliterally pass. Noting this so a future close of a sibling issue doesn't\nrepeat the earlier inaccurate claim that this test scans real packages\n(archie-core-1786637499933-386-83646cce's close reason cited a test name,\nTestEveryEngineInterfaceHasTypedCapabilityAndFamilyOwner, that does not\nexist in the repo -- likely stale even at the time it was written).\n\nNot done, and correctly still open as their own issues: engines that\nimplement this contract (the Honcho proof, archie-core-1786637492031),\nthe config surface to select one (archie-core-1786637490043), and\nbinding curators to an attached engine (archie-core-1786637499636)."}}
|
||||
{"id":"int-86bb44776b478e9f6df5c63941200607","kind":"field_change","created_at":"2026-09-01T16:44:27.441778447Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499480-370-223df308","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Complete: cfg.Memory.Engine now actually selects and starts an engine at\ndaemon boot, not just implements the contract in isolation.\n\ninternal/app/archied/bootstrap.go:setupMemoryEngine builds a\ndomain/memory.Registry, registers infraMemory.BuiltinEngine for\ncfg.Memory.Engine == \"builtin\" or \"\" (matching applyMemoryDefaults'\nresolution, so unconfigured and explicitly-builtin behave identically),\nstarts it, and stops it on shutdown -- rooted at workDir/memory-engine,\nseparate from the legacy provider's workDir/memory so the two can never\ncollide while both exist. Wired into Run() via setupMemoryAll\n(archie-core-1786637490043's cfg.Memory.Engine validation runs first at\nconfig load, so the switch's default case only guards drift between\nthat list and this one, not live operator input).\n\ninternal/memory/builtin is unchanged (verified: no diff, its tests pass\nunmodified) and internal/memory.Manager (the live system-prompt/tool-call\npath) does not read through this registry -- the two systems run in\nparallel by design, per archie-core-1786637490069-11-e245c170's explicit\nscoping. Converging them is future work, not part of this issue's AC.\n\ngo test ./... is green; task lint is 0 issues."}}
|
||||
{"id":"int-c7304b2101eb73c6404d8508da30e2be","kind":"field_change","created_at":"2026-09-01T16:44:37.765726853Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490043-10-711c450a","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Complete, all four AC clauses:\n\n- config.MemoryConfig.Engine field added with toml/yaml/json tags;\n Provider/ProviderConfig/SessionTTL also gained the toml tags they were\n missing (repo convention, config.toml is the primary format).\n- validateMemory (internal/infrastructure/configuration/validate.go)\n rejects an engine name outside memoryEngines with\n \"%w: memory.engine %q (want %s)\", the same named-constant-list +\n oneOf/list shape forge.type already uses. TestValidateMemoryNames\n TheValidSet pins the exact message.\n- applyMemoryDefaults resolves an absent engine to \"builtin\"\n (memoryEngineBuiltin), verified by\n TestApplyMemoryDefaultsFillsAbsentEngineWithBuiltin, and an explicit\n value is left alone (TestApplyMemoryDefaultsLeavesExplicitValuesAlone).\n- config.example.toml documents [memory] engine alongside the existing\n provider field, distinguishing the two mechanisms.\n\nSince closing this, archie-core-1786637499480 (ship builtin as default)\nlanded the bootstrap wiring that actually consumes cfg.Memory.Engine, so\nthe field is not just parsed and validated but live end to end."}}
|
||||
{"id":"int-432ac25baf4f85d1a9f04ff494d0bc62","kind":"field_change","created_at":"2026-09-01T16:47:57.576063469Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499636-376-2f94082e","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Complete, all three AC clauses:\n\n- A curator declares its memory engine via Manifest.MemoryEngine and\n receives it as a typed dependency: curator.Registrar.MemoryEngines\n (Get(name) (domainmemory.MemoryEngine, bool)), same trust model as\n ToolBuilder.Build(ctx, declared) -- the curator calls Get with its own\n declared name, not handed a pre-resolved instance. Registration\n enforces presence exactly like Tools/Skills: declared with no\n MemoryEngineSource on the host is rejected at Register\n (TestRegistryDeclaredCapabilitiesRequireHostServices' two new cases),\n and filter() clears the field from a curator's view when undeclared\n (TestRegistryBindFiltersToDeclaredCapabilities).\n- Swapping the configured engine changes where memories land with no\n curator code change: nothing about a curator names a concrete engine,\n only the string it declared, resolved fresh through whichever registry\n it was bound to.\n- A curator with no declared engine stays valid (pre-existing behavior,\n now covered by table cases) and can only ever be affected by a memory\n operation it structurally cannot attempt, since MemoryEngines is nil\n in its view.\n\nWired end to end: internal/app/archied/bootstrap.go:setupCurators passes\nb.memEngines (*domainmemory.Registry, set by setupMemoryAll which Run()\ncalls before setupCurators) straight in -- it already satisfies\nMemoryEngineSource with no adapter.\n\ngo test ./... is green; task lint is 0 issues."}}
|
||||
{"id":"int-8e36a6b86a595feaebaa50956eb01382","kind":"field_change","created_at":"2026-09-01T16:51:00.094507904Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499161-356-e424e40d.1","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed, but not as originally framed. Investigated wiring RegisterExternal\nfor real: there is no external MemoryProvider implementation anywhere in\nthe repo to construct and pass to it (only internal/memory/builtin.Provider\nexists) -- calling RegisterExternal would be dead plumbing to nothing, not\na fix.\n\nThe actual fix: configuration.validateMemory now rejects memory.provider\nbeing set at all, with a clear reason, instead of accepting it and doing\nnothing. Turns the silent no-op into a loud one. setupMemory's doc comment\nand config.example.toml updated to match; the now-pointless\nprovider_config example section removed.\n\ntoml struct tags (the other half of this bug) were already fixed in\narchie-core-1786637490043's commit.\n\nDrop the rejection once a real external provider (or the domain/memory\nengine family's Honcho proof, archie-core-1786637492031) gives the field\nan effect again.\n\nTestValidateMemoryRejectsProviderSetToAnything covers it. task check is\ngreen."}}
|
||||
{"id":"int-9633d649a25f789b25865683d74755f7","kind":"field_change","created_at":"2026-09-01T16:51:58.124722776Z","actor":"Sam Catlow","issue_id":"archie-core-1786637492031-86-0fcaccc0","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Deprioritized by Sam (2026-09-02): not a current priority. Re-open when there's actual appetite to build against a live Honcho instance -- the engine contract it would implement against (domain/memory.MemoryEngine) is done and stable, so this is unblocked whenever picked back up, not superseded by anything."}}
|
||||
{"id":"int-c7c4a97f5d0d3b21df35da16c9f6ac8e","kind":"field_change","created_at":"2026-09-01T16:58:46.750078973Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499206-358-54f29252","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Complete, all three AC clauses. Design decided first in\ndocs/prds/skill-curator.md (no settled design existed for what \"review,\nprune, improve\" means as concrete behavior): v1 is mechanical validation\nplus safe whitespace normalization only -- no LLM-authored rewrites, no\ndeletion. See the doc for the full \"why this scope, not more\" reasoning.\n\n- Registers and runs through curator.Registry with no curator-specific\n special-casing: uses the existing Register/Runtime path unchanged\n (TestRegistersAndRunsThroughTheRegistry).\n- Its changes are observable and attributable: every write is preceded\n by an Action naming what changed and why (skill.normalized), surfaced\n through the existing curator activity tracker\n (archie-core-1786637489932, already shipped) -- no new observability\n surface needed.\n- Operates within its declared tool set: Manifest.Tools is empty, and\n nothing in the implementation ever touches Registrar.Tools\n (TestManifestDeclaresOnlySkills).\n\ninternal/infrastructure/skillcurator/{store,skillcurator}.go implement\ncurator.SkillStore and curator.CuratorEngine. The store deliberately does\nnot delegate to internal/skill.Discover, which aborts its whole call on\nany one skill's parse failure -- wrong for \"review each skill\nindependently\" (TestPassReviewsEverySkillIndependently covers the\nregression this would otherwise cause). Wired into\ninternal/app/archied/bootstrap.go:setupCurators, rooted the same way\nloadWorkflows resolves skillsBase.\n\ntask check is green (full Go suite + dashboard tests)."}}
|
||||
{"id":"int-1a3b692dbe849f86296f99adc893c60d","kind":"field_change","created_at":"2026-09-01T17:09:13.072769525Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499114-354-e5b475b4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Complete, all four AC clauses. Design decided first in\ndocs/prds/session-memory-curator.md, most notably: Observation.Identity\nis the session ID, not a user/cross-session identity -- migration-\ndecisions.md#5's memory-scope mapping is still explicitly open and this\nissue has no business deciding it unilaterally.\n\n- Registers and runs through curator.Registry with no special-casing\n (TestRegistersAndRunsThroughTheRegistry).\n- Writes through the memory engine contract, never a concrete store:\n Registrar.MemoryEngines.Get(name).Write, same trust model every other\n curator capability uses.\n- Extraction runs off the hot path: the model call happens inside Pass,\n which the curator runtime already runs off a chat turn's own\n goroutine.\n- What it wrote and why is inspectable: one memory.extracted Action per\n session with a count, through the existing curator activity tracker.\n- Honours the trigger-accounting invariant: Manifest.OnInput = true\n wakes it via the existing WakeOnPrimaryInput wiring, which already\n excludes every curator-derived event kind -- no new code needed for\n that guarantee to hold here.\n\nWired end to end: internal/app/archied/bootstrap.go:setupCurators,\nadapters for gateway.SessionStore (internal/infrastructure/\nsessioncurator/adapter.go) and the shared ai-sdk runtime\n(curatorLLMRunner, main.go).\n\nCaught and fixed during implementation: a model-call failure and an\nunparseable model response were originally conflated into the same\nswallowed-error path, which would have hidden a real provider outage as\n\"nothing to extract.\" Split into two paths;\nTestPassPropagatesALLMFailure is the regression test.\n\ntask check is green (full Go suite + dashboard tests)."}}
|
||||
{"id":"int-dc014eccf7018b59bff0cad0a67c0d71","kind":"field_change","created_at":"2026-09-02T09:43:01.465107883Z","actor":"Sam Catlow","issue_id":"archie-core-s81k","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: FeedHandler.WithAttrs/WithGroup now propagate to the wrapped handler, matching SystemLogHandler's existing pattern. Added regression test covering both feed and persistent sink."}}
|
||||
{"id":"int-a5c77f65cfbdfbf7886427990324ebaf","kind":"field_change","created_at":"2026-09-02T10:20:48.185625795Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942147-2-47cd5bd1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Shipped docs/prds/image-capability-contract.md plus internal/domain/image (Provider contract, Registry — no Lifecycle, provider is call-scoped) and config.ImageConfig/validateImage. Provider-neutral, tested with fakes, hosted+local both gated by explicit enabled=true. Also linked all 7 orphaned epic children (found unlinked again, same pattern as the curator/memory epics)."}}
|
||||
{"id":"int-3f215b612652bd0c68bcfdc3b31045ee","kind":"field_change","created_at":"2026-09-02T10:44:37.703540458Z","actor":"Sam Catlow","issue_id":"archie-core-1786637498998-349-fe936acb","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Added a commented token_env placeholder under [chat.telegram] in config.example.toml, matching the style of the other optional fields."}}
|
||||
{"id":"int-b208d885831c58b7fda40ddf24f00162","kind":"field_change","created_at":"2026-09-02T10:47:00.970235578Z","actor":"Sam Catlow","issue_id":"archie-core-1786637501039-425-88078ff7","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"MarkRunning now fires for telegram/email/webhook via a gateway.Lifecycle{Starting,Running} callback threaded through Gateway.Start: email/webhook report Running after their listener actually binds (webhook moved off ListenAndServe's internal bind to explicit net.Listen so this is observable), telegram reports Running after StartWebhook launch (webhook mode) or after the first successful getUpdates response via a pollReadinessClient http.Client wrapper (long-poll mode). Restart re-reports Starting/Running each cycle. task check clean, race-clean on the new tests."}}
|
||||
{"id":"int-2917afbba8a05e15500b4db33121b0ff","kind":"field_change","created_at":"2026-09-02T11:02:36.594846937Z","actor":"Sam Catlow","issue_id":"archie-core-1787583419901-1-85796c0b","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Already implemented and in use: parked tasks expose Retry/Abandon/Reject — Abandon/Reject transition to terminal Won't-do and close the forge issue; terminal tasks then expose Archive (removes the row, keeps the durable audit event); Retry reopens parked work. Landed in de60802 (archive+retry controls) and 52bb018 (reject from every non-terminal state incl. parked); covered by TestLifecycleSpecificTaskActions, TestTaskListExposesLifecycleActions, TestArchiveRemovesOnlyOneTerminalTask."}}
|
||||
{"id":"int-b12fb3a2fb1adc55717d64001a7ad1f3","kind":"field_change","created_at":"2026-09-02T11:25:53.176448321Z","actor":"Sam Catlow","issue_id":"archie-core-95dj","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed via a new TaskContext.BaselineFixed flag: StageBaselineGate sets it when its own CommitAll reports a real committed change (implement.go:104-111). The build stage's OnResult only sets BuildNoChanges when its own diff is empty AND BaselineFixed is false (implement.go:177), so a baseline-only fix can no longer be masked as 'no changes'. StageCommitPush itself now calls CommitAll directly and pushes whenever either a new commit was made OR BaselineFixed is true (steps.go), instead of erroring on 'nothing to commit' when the real change already sits on the branch from the baseline-fix commit. Two new regression tests (TestStageCommitPushPushesBaselineFixEvenWithNothingNewToCommit, TestStageBaselineGateSetsBaselineFixedWhenItCommits) plus a guard test that the old empty-tree error still fires without a baseline fix. task check clean."}}
|
||||
{"id":"int-a86253d4f2c53b0b13bd9ffa133c2c3f","kind":"field_change","created_at":"2026-09-02T11:26:52.22913622Z","actor":"Sam Catlow","issue_id":"archie-core-n2pv","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Added ui/src/base/log-row.js (row rendering extracted out of logs.js, shared -- second consumer per CLAUDE.md), ui/src/tasks/task-logs.js (taskLogPanel handling loading/error/disabled/empty/populated states), api.taskLogs() in ui/src/base/api.js, and a collapsible 'Attempt log' section wired into each task's existing timeline drill-down in ui/src/tasks/tasks.js -- lazily fetched on first expand. New tests: ui/test/log-row.test.js, ui/test/task-logs.test.js. task check clean, 100/100 JS tests."}}
|
||||
{"id":"int-e152961d7c350a087c3eb890299c7e9b","kind":"field_change","created_at":"2026-09-02T11:28:49.497263922Z","actor":"Sam Catlow","issue_id":"archie-core-rwzo","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Added TaskContext.RunUsage + accumulateUsage (agent.go, implement.go's baseline-fix branch) and formatTokenUsage (workflow.go), wired into implement.go's and tdd.go's PR-body footers plus ui/src/tasks/timeline-event.js's agent_finish rendering (raw prompt replaced with computed fresh = prompt - cached). Added extractFailingGateOutput (workflow.go) trimming go test 'ok' package lines from StageBaselineGate's retry mission, degrading to unchanged output when no --- FAIL:/FAIL\\t marker survives the filter. 5 new Go tests, 1 updated JS test. task check clean, 100/100 JS tests."}}
|
||||
{"id":"int-83ee0a63ff1338a9859c8fd3dc60b627","kind":"field_change","created_at":"2026-09-02T11:39:59.803695594Z","actor":"Sam Catlow","issue_id":"archie-core-enfj","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented internal/domain/workflow/triage.go: a cheap classify-only-once AgentStage (still runs StagePrepareWorktree -- AgentStage requires tc.Dir to mount into the container, no cheaper primitive exists) that either closes a task needing no code change (reusing the CloseIssue/StatusMerged pattern feasibility.go's OnResult already established for the same ctx-less constraint) or sets tc.Task.Workflow and requeues under the chosen workflow (implement/tdd/feasibility, defaulting to implement for a missing/unrecognized choice). Route()'s fallback (workflow.go) now prefers reg[\"triage\"] over reg[\"implement\"] when registered, falling back unchanged when it isn't -- fully backward compatible. Registered in skillbuild.builtins(). 9 new tests (triage_test.go, routing_test.go) plus the design doc at docs/prds/dynamic-workflow-triage.md. task check clean."}}
|
||||
{"id":"int-b1d36e66b443aeb3688f5d2e2e909b3e","kind":"field_change","created_at":"2026-09-02T11:48:52.971694566Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490097-12-bf415ffb","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Wrapped SOUL/Persona in an XML-escaped, trust=data <soul> block rendered before the invariant tags; added TestBuildSystemPromptSoulCannotOverrideInvariants; documented the enforcement in identity.md"}}
|
||||
{"id":"int-da44a764eff8bbd77eaeb2c18f994f45","kind":"field_change","created_at":"2026-09-02T11:52:24.144007919Z","actor":"Sam Catlow","issue_id":"archie-core-z6wy","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed: sessioncurator now stamps Action.At from its clock; activityTracker.record backfills any zero Action.At from the pass timestamp as a defense in depth for engines with no clock (skillcurator)."}}
|
||||
{"id":"int-bd3f00e413d4746b2d8988a3202aaf73","kind":"field_change","created_at":"2026-09-02T12:05:39.669372244Z","actor":"Sam Catlow","issue_id":"archie-core-b6ew.1","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Added internal/webui/config_schema.go: ConfigFieldType/ConfigField/ConfigSection descriptor types and configFieldDescriptors(), hand-authoring key/label/type/editable/restart_required for every field ConfigView exposes today, grouped into the sections settings.js already renders. RestartRequired sourced from internal/app/archied/reload.go's reloadableFields/reloadableSubFields allowlist. Contract tests pin key completeness, structured-field non-editability, and locked-storage-field non-editability. Not yet wired into GET /api/config -- that's b6ew.2."}}
|
||||
{"id":"int-cae7b7971e3919de27f9b5812415646e","kind":"field_change","created_at":"2026-09-02T12:07:57.773566779Z","actor":"Sam Catlow","issue_id":"archie-core-b6ew.2","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"ConfigView gains a Schema []ConfigSection field, populated in handleConfig via buildConfigSchema(view), which attaches each request's Value/LockedReason/Overridden onto the static configFieldDescriptors() catalog. The flat ConfigView fields (Identity, Repositories, etc.) are untouched -- Schema is additive. Tests confirm schema values match the flat fields they derive from, locked reasons propagate, structured fields stay non-editable, and secrets never reach the schema block."}}
|
||||
{"id":"int-13c0a9fb52c803fedae5507cb56e4928","kind":"field_change","created_at":"2026-09-02T12:12:40.665810909Z","actor":"Sam Catlow","issue_id":"archie-core-b6ew.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"settings.js renders identity/budgets/storage/web cards generically from cfg.schema sections (schemaCards()), replacing identityCard/budgetsCard/storageCard/webCard/pullPolicyLabel -- label, type, description, editability, and options all come from the backend descriptor. config-row.js gained enum edit support (select from opts.options), an editable:false branch distinct from locked rows, and a hint tooltip carrying the field's description. Structured sections (repositories, models & providers) are unaffected -- still rendered by their existing bespoke functions, reserved for b6ew.4. Not visually verified in a live browser (needs a full daemon+forge+NATS stack); verified via unit tests mirroring the existing config-row.test.js patterns and Go contract tests."}}
|
||||
{"id":"int-54a1278a10429ca2bbd2958c3c820ec4","kind":"field_change","created_at":"2026-09-02T12:23:52.384633026Z","actor":"Sam Catlow","issue_id":"archie-core-b6ew.4","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Scoped to visibility, not full inline editing -- while implementing, found that the dashboard's PATCH /api/config path (overlay.Nest + configuration.ApplyOverlayValues) has no array-index support, so a per-element update to the Repos slice cannot be expressed as a dotted key today. That's real, separate scope, filed as archie-core-b6ew.6 rather than bolted on.\n\nShipped: RepoView.ReviewEnabled (previously absent from the API entirely, not just unrendered) alongside AllowConcurrent and MaxRetries; the repositories card now shows Concurrent/Max retries/Self-review columns as read-only pills, closing the concrete discoverability gap (Sam couldn't see allow_concurrent without an agent tracing Go source). config.example.toml documents review_enabled, which was undocumented before this. Go test pins ReviewEnabled reaching ConfigView for both a configured and a zero-value repo."}}
|
||||
{"id":"int-2dc0a43352da967d610967a60f856a55","kind":"field_change","created_at":"2026-09-02T12:26:27.530156155Z","actor":"Sam Catlow","issue_id":"archie-core-b6ew.5","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Most of this issue's assertions were already covered incrementally by tests added in .1-.4 (key/label/type completeness, structured/locked non-editability, secret-leak guard on the schema block, schema values matching their flat-field source). This issue adds the two pieces still missing: TestConfigFieldDescriptorsRestartRequiredIsDeliberate pins the exact RestartRequired value per key against the reload.go evidence documented in configFieldDescriptors' own comment, so a reclassification without checking reload.go fails loudly. ui/test/settings-schema.test.js renders settingsPage against a schema fixture containing a field settings.js has never heard of (proving the renderer needs no field-specific branch to show it correctly) and asserts, by reading settings.js's own source text, that none of the generically-rendered section's field keys appear literally in it -- the direct regression test for archie-core-b6ew.3's whole point."}}
|
||||
{"id":"int-37dd0495d785d0caa591b37b80a884a2","kind":"field_change","created_at":"2026-09-02T12:34:55.552403062Z","actor":"Sam Catlow","issue_id":"archie-core-b6ew.6","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Traced the mechanism before implementing: overlay.Nest/ApplyOverlayValues has no array-index support, but Repos is addressed as a WHOLE dotted key ('repos', no dot) whose value is the full slice -- so no changes to overlay/configuration packages were needed at all. Added PATCH /api/config/repos/{owner}/{name} (webui.Server.UpdateRepoField seam + handleConfigRepoUpdate), wired in archied/bootstrap.go's installUpdateRepoFieldHandler: reads the daemon's own live, untrimmed Repos (not webui.RepoView, which omits Preflight/TestGlob and would silently drop them on a naive round-trip), mutates the one matched repo's one field via the pure applyRepoFieldUpdate helper, and republishes through the existing UpdateConfig(ctx, {\"repos\": repos}) path unchanged -- zero duplicated validate/persist/publish logic.\n\nFrontend: config-row.js's row() gained an opts.save override so a caller can redirect where an edit persists; the repositories table renders an autosaving checkbox (allow_concurrent, review_enabled) and a save-on-blur/Enter text input (max_retries) via api.configRepoUpdate, reverting/erroring inline on failure rather than reloading the whole page mid-edit.\n\nGo tests cover the pure applyRepoFieldUpdate function directly (matched-repo-only mutation, untouched-field preservation including Preflight, type coercion, unknown repo/field rejection) and the webui handler (seam delegation, editable-field allowlist enforced before the seam is called, 503/400 mapping). JS tests cover the structural render (checkbox/input initial state) -- the save round trip itself isn't exercisable through the test shim (addEventListener is a no-op there), consistent with existing config-row.test.js coverage."}}
|
||||
{"id":"int-ee27bcc0456fcdb9c3aac318d4bb3af9","kind":"field_change","created_at":"2026-09-02T12:35:10.731464054Z","actor":"Sam Catlow","issue_id":"archie-core-b6ew","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"All six child issues shipped: hand-authored field descriptor catalog (.1), schema attached to GET /api/config (.2), generic scalar renderer replacing hardcoded settings.js rows (.3), repository field visibility incl. the previously-API-absent ReviewEnabled (.4), schema contract tests pinning restart-required deliberateness and generic-render proof (.5), and inline editing for the three per-repo fields via a dedicated PATCH /api/config/repos/{owner}/{name} seam (.6). The concrete complaint that started this (allow_concurrent invisible on the dashboard) is fully resolved: visible, editable, and backed by a schema the frontend no longer hardcodes."}}
|
||||
{"id":"int-bc9900db78e837a41bdab70e5c87a586","kind":"field_change","created_at":"2026-09-02T13:09:38.125673122Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.4","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}}
|
||||
{"id":"int-0a90781f3769536eb31f55216586ab7b","kind":"field_change","created_at":"2026-09-02T13:09:39.473142189Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.5","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}}
|
||||
{"id":"int-bb7a57fc8fd0ba049e510a72fb3be31c","kind":"field_change","created_at":"2026-09-02T13:55:46.837305526Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.7","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-02ff6d638b2b4c1d57c72cb943772cc5","kind":"field_change","created_at":"2026-09-02T14:24:01.016248519Z","actor":"Sam Catlow","issue_id":"archie-core-v9gv.1","extra":{"field":"status","new_value":"closed","old_value":"open"}}
|
||||
{"id":"int-1e0bb26c5c74b32f536c86752b696e17","kind":"field_change","created_at":"2026-09-02T14:24:02.393516241Z","actor":"Sam Catlow","issue_id":"archie-core-v9gv.2","extra":{"field":"status","new_value":"closed","old_value":"open"}}
|
||||
{"id":"int-421fa6d2e329722271b29c6cc06e8aed","kind":"field_change","created_at":"2026-09-02T14:24:02.790015963Z","actor":"Sam Catlow","issue_id":"archie-core-v9gv.3","extra":{"field":"status","new_value":"closed","old_value":"open"}}
|
||||
{"id":"int-3662b2644b20858f97cfe68e35970ee1","kind":"field_change","created_at":"2026-09-02T16:35:43.782983144Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.9","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"kindWorkflows YAML override shipped, task check green"}}
|
||||
{"id":"int-0522bb088937b3f0516dccfa59016dbc","kind":"field_change","created_at":"2026-09-02T16:46:13.808391215Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.10","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented and gate-verified as 93a5f3a (pushed to main)."}}
|
||||
{"id":"int-782836fd0b2fcbfe670ee2d3ce83eb5a","kind":"field_change","created_at":"2026-09-02T16:57:50.536391547Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.11","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented and gate-verified as 3e7fe00 (pushed to main). PlaybookDirs is a list per ticket correction; cross-source collision rule exercised by new load path."}}
|
||||
{"id":"int-c377e39e68d768f1d33fd07a0a5cc8b0","kind":"field_change","created_at":"2026-09-02T17:07:38.984329395Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.12","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented and gate-verified as 2c7c79e (pushed to main). cmd/archie-playbooks lint mode reuses daemon loaders; file-granular positions documented as known limitation."}}
|
||||
{"id":"int-bcf0faab845afec53d14f3a316340930","kind":"field_change","created_at":"2026-09-02T17:30:33.765888462Z","actor":"Sam Catlow","issue_id":"archie-core-e7bo","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed and gate-verified as e3a20f6 (pushed to main). wfextract directive now targets internal/domain/workflow; 'go generate ./...' completes repo-wide. All four extract surfaces regenerated; nil-guards re-applied on interface wrappers (documented IMPORTANT note restated in wfextract package doc). Previously-missing symbols proven reachable from interpreted code: wfextract (Forger/Reviewer/Trees/routing loaders) and pluginextract (Host/Module/Manifest/NewHost/HostAPIVersion) via new reachability tests; secretextract exports were current (nil-guard drift only). Red-then-green verified: fresh regen wipes guards -> guard tests panic -> re-apply -> pass. task check clean (113/113 UI, exit 0)."}}
|
||||
{"id":"int-9bc9541763af71ffbdb351604e477227","kind":"field_change","created_at":"2026-09-02T17:35:28.094046545Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.13","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented and gate-verified as d29c732 (pushed to main). ModuleRegistry (Register/Invoke, strict arg decode, yaegiutil panic recovery) + internal/domain/eda/module/log schema with generated logextract symbols; ModuleDir config wired in bootstrap.go with log-and-abort; examples/modules/log.go operator example proven through the real registry. Playbook YAML action dispatch deliberately deferred (data-flow Q1 unresolved) and recorded in module-position.md. task check clean (113/113 UI, exit 0)."}}
|
||||
{"id":"int-0ae0e3fbcad5c9cc45344d5f64b6abc5","kind":"field_change","created_at":"2026-09-02T18:01:29.431793769Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.14","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented and gate-verified as 33cdece (pushed to main). internal/domain/eda/expr: NewEnv (event+actions roots, DefaultCostLimit 100k), Compile (reject-at-load: syntax/unknown-root/type errors returned), Eval (panic-free, errors returned, ref.Val unwrapped to native). cel.dev/cel-go v0.32.0 direct dep, vetted per resolved doc (no re-vet). 9 tests pass, all verified against real CEL semantics (cost limits accrue on macros; == on missing key is false; unknown root rejected at compile). task check clean (113/113 UI)."}}
|
||||
{"id":"int-f10f375727370c967a2884fbc8e60b70","kind":"field_change","created_at":"2026-09-02T18:06:07.68242224Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.15","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented and gate-verified as 2c2b9b7 (pushed to main). internal/domain/eda/playbook: Load (reject-at-load: 2+ actions, non-workflow position, malformed, bad when compile all fail whole load) + Store.Dispatch (trigger match via workintake kind/labels, CEL when eval, named-workflow registry lookup -- same as Route()'s, no duplicated dispatch). EDAPlaybookDir config field (distinct from PlaybookDirs, documented), bootstrap load-and-abort. workflow.Route()/binding loaders untouched; their suites verified zero-regression. 11 tests + shipped example proving end-to-end; task check clean (113/113 UI). FOLLOW-UP TICKET NEEDED (not in this slice, per design): wire Store.Dispatch into production task intake (daemon.go/pollNATS/publishTask) so real forge-triggered tasks flow through the coordinator instead of only workflow.Route(); plus a separate linter/LSP integration ticket for the expr compile path."}}
|
||||
{"id":"int-7908617f987c5056730fd95c595c8d7d","kind":"field_change","created_at":"2026-09-02T18:17:08.363568118Z","actor":"Sam Catlow","issue_id":"archie-core-uhtz","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Investigated per design notes: intentional behavior, not a bug -- confirmed against existing test coverage (skillcurator_test.go's parse-failure-doesn't-abort-batch test). Documented with a scoped nolint explaining why, not a behavior change. Commit pushed to main."}}
|
||||
{"id":"int-ad28db17a92a281b51deb682190489b8","kind":"field_change","created_at":"2026-09-02T20:18:20.468900706Z","actor":"Sam Catlow","issue_id":"archie-core-zv2t","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed, tested (Playwright against a real isolated server), and pushed as commit 85761c4."}}
|
||||
{"id":"int-5dd30e1f77dff564088caa908bd53330","kind":"field_change","created_at":"2026-09-02T20:18:20.908890222Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.8","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Backend Owner/Repo fix (ac42f64) + full dashboard UI (85761c4, mirroring ui/src/mappings/) both landed. Full state machine (draft->edit->pending_approval->approve->armed->delete) verified end-to-end in a real browser. Also fixed a related bug found in the process (empty-secret-on-edit rejected, commit 51ca509)."}}
|
||||
{"id":"int-5f9484b3ee198a74559bebb85c7227da","kind":"field_change","created_at":"2026-09-02T20:20:15.450996359Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.6","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"All four items done: binding model + threat model (bindings.md, 41dffe3), ARCHITECTURE.md task-lifecycle addendum (edb90e1), operator walkthrough (this commit). Unblocked once t2db.8's UI landed."}}
|
||||
{"id":"int-833f71f832182c4e497cb3695d7b0943","kind":"field_change","created_at":"2026-09-02T20:25:30.487991213Z","actor":"Sam Catlow","issue_id":"archie-core-mlro","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Extracted to ui/src/base/pill.jsx, all 12 call sites updated (11 pre-existing + bindings). Verified via task test:ui (120/120) and real browser re-check across all pages given this touches the same rendering path as the earlier Preact regression fix. Commit 2abccf3."}}
|
||||
{"id":"int-1b49035689778e6ba250164f5761ca88","kind":"field_change","created_at":"2026-09-02T20:42:32.356058038Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.16","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Both cyclop/gocognit findings resolved via pure extraction; golangci-lint run ./... reports 0 issues; go test ./... and task test:ui pass unchanged; task check green."}}
|
||||
{"id":"int-632b5998e10e3eb8dfab5e44c132b945","kind":"field_change","created_at":"2026-09-02T20:48:07.710891177Z","actor":"Sam Catlow","issue_id":"archie-core-7d5u.6","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"ARCHITECTURE.md and plugins-and-extensions.md reconciled with shipped webhook intake and the 7d5u.1 decision; config.example.toml already documented the intake flag/default; CLAUDE.md gained the internal/forge/webhook trap. Commit 8b53dc3."}}
|
||||
{"id":"int-2ad57b7174de600220357961732784fe","kind":"field_change","created_at":"2026-09-02T20:49:56.069736209Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499814-382-b27575d6","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Stale as of 2026-08-08's 56-issue count; verified today golangci-lint run ./... reports 0 issues (same command Taskfile's lint target runs), thresholds unchanged (cyclop max-complexity 15, gocognit min-complexity 30 in .golangci.yml), no threshold loosening. All 21 remaining //nolint suppressions (nilerr x14, contextcheck x4, others) carry a documented reason in an adjacent comment. Acceptance criteria met."}}
|
||||
{"id":"int-cb5978db917dc01665cd1aa1b8dcef5e","kind":"field_change","created_at":"2026-09-02T20:50:07.413197403Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499664-377-c2818afd","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Verified 2026-09-03: golangci-lint run ./... reports 0 issues repo-wide (thresholds unchanged from 9298afd's config: cyclop 15, gocognit 30). The gate this epic's description called RED is green. Its last known child (Phase 5, the 56-finding remainder) closed for the same reason -- see archie-core-1786637499814-382-b27575d6."}}
|
||||
{"id":"int-f308fd1259b3570d6fe3c3ac585b7757","kind":"field_change","created_at":"2026-09-02T20:57:28.723473462Z","actor":"Sam Catlow","issue_id":"archie-core-1786637500926-421-7c63bcd3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed in ui/src/dashboard/dashboard.css: .dash-top > div now flexes and .card grows to fill it, scoped to the HEALTH row only. Verified via a static HTML repro using the real project CSS (Playwright, computed geometry before/after) -- card heights and bottom edges now match. task check green, ui/dist rebuilt. Commit a9a056c."}}
|
||||
{"id":"int-65c370a748af068c55f6a3046a8800b9","kind":"field_change","created_at":"2026-09-02T20:58:35.392948669Z","actor":"Sam Catlow","issue_id":"archie-core-1786637500900-420-335d8bbb","extra":{"field":"assignee","new_value":"Sam Catlow","old_value":"samcharles93"}}
|
||||
{"id":"int-a4557ae17965484c7b2ea98496f6817f","kind":"field_change","created_at":"2026-09-02T20:58:41.680037166Z","actor":"Sam Catlow","issue_id":"archie-core-1786637500900-420-335d8bbb","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Superseded by the [[identities]] feature, not fixed via the originally-requested per-repo-within-one-[[repos]]-list forge override. Verified: IdentityConfig (internal/config/config.go:549) gives each identity its own Forge + Repos list, bootstrap.go:820 builds a per-identity runner with its own forge client, and deployments/multi-forge-github-gitea.toml is a documented, supported profile for exactly the carina/tau scenario this bug describes (GitHub + Gitea from one daemon). The bug's own workaround note anticipated this: 'tau gets no automated dispatch...until this is fixed or it gets a separate identity' -- separate identity is now the supported path. A single identity still cannot mix forges within one flat [[repos]] list; reopen if that finer granularity is specifically wanted."}}
|
||||
{"id":"int-d5813fff6b635478862067006c1c3af0","kind":"field_change","created_at":"2026-09-03T10:16:04.825390136Z","actor":"Sam Catlow","issue_id":"archie-core-fwvf","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Resolved; GitHub #703 closed. Stale-open copy recovered from carina during machine sync."}}
|
||||
{"id":"int-6e074ba6345cbb2197c7873ca6bb0780","kind":"field_change","created_at":"2026-09-03T10:16:05.296283836Z","actor":"Sam Catlow","issue_id":"archie-core-n5fz","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Resolved by commit 89f48a5 (PR #711); GitHub #709 closed. Stale-open copy recovered from carina during machine sync."}}
|
||||
{"id":"int-871cbe9079c586a5d558d0d7fa8906c8","kind":"field_change","created_at":"2026-09-03T10:16:05.744041675Z","actor":"Sam Catlow","issue_id":"archie-core-w1d5","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Resolved by commit 5f2b253 (PR #712); GitHub #710 closed. Stale-open copy recovered from carina during machine sync."}}
|
||||
{"id":"int-c2c340c7837ed536800bf698bc7bb131","kind":"field_change","created_at":"2026-09-04T17:10:44.25920158Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.21","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implementation complete and gate-verified for its scope. Playbook gains ID (path-relative) + Version (sha256 content hash), populated in loadOne; DispatchInput gains TaskID string carrying TaskEnvelope.IdempotencyKey(), per evidence that the discovery point computes kind/labels before any store.Task row exists. Red-green verified; gofumpt/vet/build/golangci-lint clean for the package. NOTE: task check has 5 lint failures PRE-EXISTING at HEAD in unrelated files (bootstrap.go cyclop/nestif, install_script_test.go noctx, telegram_setup_test.go usetesting) -- not caused by this change. Forced close because the earlier blocked-by: t2db.17 dependency is inverted -- .17 is doc-only sign-off; these are its implementation prereqs, not gated on it."}}
|
||||
{"id":"int-2497b727383994c4c3054eec786c0cd3","kind":"field_change","created_at":"2026-09-04T17:10:44.384814761Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.22","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implementation complete and gate-verified for its scope. Playbook gains ID (path-relative) + Version (sha256 content hash), populated in loadOne; DispatchInput gains TaskID string carrying TaskEnvelope.IdempotencyKey(), per evidence that the discovery point computes kind/labels before any store.Task row exists. Red-green verified; gofumpt/vet/build/golangci-lint clean for the package. NOTE: task check has 5 lint failures PRE-EXISTING at HEAD in unrelated files (bootstrap.go cyclop/nestif, install_script_test.go noctx, telegram_setup_test.go usetesting) -- not caused by this change. Forced close because the earlier blocked-by: t2db.17 dependency is inverted -- .17 is doc-only sign-off; these are its implementation prereqs, not gated on it."}}
|
||||
{"id":"int-8c4db26b9679e95af26b89cd1632490e","kind":"field_change","created_at":"2026-09-05T07:10:42.605060915Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.17","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-f729139e76e6b0d4226fdff3d5362bb6","kind":"field_change","created_at":"2026-09-05T07:10:42.727150517Z","actor":"Sam Catlow","issue_id":"archie-core-t2db.18","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-26fc72a25e298652228db1f70cc0563d","kind":"field_change","created_at":"2026-09-05T07:10:42.847407876Z","actor":"Sam Catlow","issue_id":"archie-core-1786637496789-265-b052b772","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-3012b8f41c3c953c4f18dd4e2e76b0b3","kind":"field_change","created_at":"2026-09-05T07:10:42.905693647Z","actor":"Sam Catlow","issue_id":"archie-core-1786637496817-266-06b64a72","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-d5901488cf1c58c467da4dcf9344d189","kind":"field_change","created_at":"2026-09-05T07:10:42.964960294Z","actor":"Sam Catlow","issue_id":"archie-core-1786637496842-267-8b2984f9","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
{"id":"int-15517157ecb20b071f7d51d82c9fd729","kind":"field_change","created_at":"2026-09-05T07:10:43.024637142Z","actor":"Sam Catlow","issue_id":"archie-core-14cs","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}}
|
||||
@@ -1,671 +0,0 @@
|
||||
{"_type":"issue","id":"archie-core-zv2t","title":"CRITICAL: every JSX-based dashboard page rendered '[object Object]' instead of content","description":"Found and fixed 2026-09-03 while building the bindings dashboard UI (archie-core-t2db.8), via real browser verification per AGENTS.md's UI rule -- not caught by any existing test, since unit tests render components in isolation via @testing-library/preact and never exercise the actual router/mount integration path.\n\nEvery page registered in ui/src/main.jsx's routes table (dashboard, tasks, logs, captures, mappings, skills, workflows, memory, curators, channels, settings) returns a Preact VNode from its page function (e.g. dashboardPage() returns \u003cDashboardApp /\u003e), but main.jsx's router passed that VNode into ui/src/base/dom.jsx's mount()/append(), which only knows how to append real DOM Nodes or String()-ify everything else -- so every page's actual content became the literal text \"[object Object]\" in the browser. Confirmed via git show that this bug already existed in the committed ui/dist bundle before any change tonight -- served the pre-existing bundle in isolation via a throwaway webui.Server harness and reproduced the identical failure on the stock dashboard. This shipped in the tagged v1.20.0 release earlier this session (and likely earlier releases too, pending the recent Preact migration commits cf1bce4/e5abb62) -- SAM: worth deciding whether a patch release is warranted, this ticket does not decide that.","design":"Fixed in commit 85761c4: main.jsx's show() function now detects whether route.view()'s result is a real DOM Node (only the unused comingSoon()/soon:true fallback) or a Preact VNode (every real page today), and calls Preact's own render(vnode, outlet) for the latter instead of the generic mount() helper. mount() itself and its other 4 vanilla-DOM call sites (theme icon swap, app shell mount, chat drawer no-op) are untouched -- this was the minimal-blast-radius fix, not a rewrite of the rendering bridge.","acceptance_criteria":"Verified via Playwright against a real running server (not just source inspection): all 11 pre-existing pages plus the new bindings page render real content, zero occurrences of the literal string in any page's main content area. task check passes.","notes":"Closed on discovery -- already fixed, tested, and pushed in the same session that found it.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-02T20:18:11Z","created_by":"Sam Catlow","updated_at":"2026-09-02T20:18:20Z","closed_at":"2026-09-02T20:18:20Z","close_reason":"Fixed, tested (Playwright against a real isolated server), and pushed as commit 85761c4.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-2tqh","title":"P0: Reconcile domain packages - docs and tree have diverged","description":"internal/domain/ contains curator/, mapping/, scheduling/ which do NOT appear in migration-decisions.md's confirmed domain list (identity, agent, workflow, messaging, workintake, plugin).\n\nMeanwhile, confirmed domains (identity, agent, messaging, plugin) don't exist yet as packages.\n\nNeed to:\n- Audit actual domain packages in internal/domain/\n- Update migration-decisions.md to reflect reality\n- Decide: are curator/, mapping/, scheduling/ legitimate domains or should they be folded into confirmed domains?\n- Create stub packages for missing confirmed domains if needed\n\nBlocked by: nothing (but blocks clean migration progress)","status":"closed","priority":0,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:41:10Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:51Z","closed_at":"2026-08-31T10:04:53Z","close_reason":"Reconciled migration-decisions.md with actual tree: confirmed curator/mapping/scheduling as legitimate domains (were undocumented, not misplaced), documented that identity/agent/messaging/plugin are approved-but-unmaterialised targets rather than creating dead stub packages","external_ref":"https://github.com/samcharles93/archie-core/issues/651","dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-kg1w","title":"P0: Refactor cmd/archied/main.go - violates organisation.md wiring rule","description":"cmd/archied/main.go is 1085 lines of substantive wiring, directly violating organisation.md's rule: 'cmd/* MUST NOT contain substantive wiring'.\n\nThis is the migration docs' own stated next chunk: internal/app/{archied,agentworker} (not yet started).\n\nNeed to:\n- Extract wiring logic from cmd/archied/main.go\n- Create internal/app/archied/ package\n- Create internal/app/agentworker/ package\n- Move dependency injection and lifecycle management into app layer\n- cmd/archied/main.go should only contain CLI flag parsing, OS signal traps, and entry point routing\n\nBlocked by: nothing (but is foundational for migration work)","status":"closed","priority":0,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:41:00Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:51Z","closed_at":"2026-08-31T11:27:14Z","close_reason":"Extracted the full cmd/archied wiring package into internal/app/archied (matching the sibling internal/app/agentworker pattern); cmd/archied/main.go is now 18 lines (codesearch-helper dispatch + call into archied.Run()). Fixed two architecture tests still hardcoded to the old cmd/archied path. task check passes clean.","external_ref":"https://github.com/samcharles93/archie-core/issues/652","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-bas7","title":"P0: Fix failing test - CLAUDE.md missing ARCHITECTURE.md reference","description":"TestPluginEngineRuleIsCanonicalAndSharedByAgentInstructions in internal/plugin test is failing because CLAUDE.md is missing a required reference to ARCHITECTURE.md#plugin-engine-rule-strict.\n\nThis is a red build - needs immediate doc fix.\n\nNeed to:\n- Add the missing reference to CLAUDE.md\n- Verify test passes\n\nBlocked by: nothing","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-28T13:40:53Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:52Z","closed_at":"2026-08-31T10:03:46Z","close_reason":"Added missing test + CLAUDE.md reference to ARCHITECTURE.md#plugin-engine-rule-strict","external_ref":"https://github.com/samcharles93/archie-core/issues/653","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1sjk","title":"P0: Bump Go from 1.26.5 to 1.26.6+ to fix 6 stdlib CVEs","description":"govulncheck found 6 CVEs in stdlib packages fixed in Go 1.26.6:\n- html/template\n- crypto/tls (handshake flood)\n- net/http (H2 timeout)\n- encoding/asn1 (recursion DoS)\n- x/net/idna\n\nNeed to:\n1. Update go.mod directive from 1.26.5 → 1.26.6\n2. Update both Dockerfiles (archied and archie-agent) from 1.26.5 → 1.26.6\n3. Rebuild and verify\n\nBlocked by: nothing","status":"closed","priority":0,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:40:40Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:53Z","closed_at":"2026-08-31T10:04:10Z","close_reason":"go.mod already at 1.27.0 (supersedes 1.26.6 CVE fix); bumped both Dockerfiles from golang:1.26-trixie to golang:1.27-trixie to match","external_ref":"https://github.com/samcharles93/archie-core/issues/654","dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-n5sr","title":"Measure and reduce task-agent context amplification","description":"PR #635 consumed at least 1,286,449 tokens across baseline repair, analysis, repro, and fix, while the PR footer reported only 997,900. Do not impose a hard token stop: successful and failed tasks are evaluation evidence. Measure prompt/completion/cached usage by stage and iteration, include every agent stage in task totals, enable adaptive history compaction, and bound redundant tool-result replay so task completion remains the authority while efficiency becomes observable and improvable.","acceptance_criteria":"Task telemetry attributes prompt, completion, cached, total tokens and iterations by workflow stage; baseline-repair usage is included in task totals; task agents compact redundant accumulated history without imposing a token stop; successful and failed tasks remain comparable; regression coverage and quality gate pass.","notes":"Maintainer decision: max_tokens is not desired as a blocker. Optimize context economics and preserve outcomes as metrics.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:58:59Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:31Z","started_at":"2026-08-24T18:02:41Z","closed_at":"2026-08-24T19:48:33Z","close_reason":"Provider usage is durable by stage, baseline repair is included, model-adaptive compaction is enabled without a token cap, and ai-sdk preserves partial/compaction usage. task check and fresh adversarial review pass.","external_ref":"https://github.com/samcharles93/archie-core/issues/637","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-nq0c","title":"Preserve Git author identity in sandboxed task commits","description":"PR #635 contains three commits with empty author and committer names/emails despite configured bot_user and the documented GitHub noreply default. Trace and preserve commit identity across the daemon-worker boundary.","acceptance_criteria":"Sandboxed task commits carry configured/defaulted author and committer name/email; regression covers the live RPC/local commit composition; quality gate passes.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T17:58:58Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:32Z","closed_at":"2026-08-24T19:48:34Z","close_reason":"Commit identity now crosses the task boundary, per-identity email defaults are derived when omitted, and the worker end-to-end test verifies author and committer. task check and fresh adversarial review pass.","external_ref":"https://github.com/samcharles93/archie-core/issues/638","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-473l","title":"Reconcile task clone ownership after container commits","description":"Agent containers write Git objects as root into bind-mounted task clones, while ownership is currently repaired only before push. A stopped or failed workflow before push leaves unreadable objects and makes the next host-side worktree prepare fail instantly. Reconcile ownership after every CommitAll result as well as before push.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:24:57Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:33Z","started_at":"2026-08-24T17:25:30Z","closed_at":"2026-08-24T17:28:39Z","close_reason":"Implemented with regression coverage, full task check passing, and adversarial review clean.","external_ref":"https://github.com/samcharles93/archie-core/issues/639","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-15iq","title":"Make UUIDv7 session references distinguishable","description":"UUIDv7 session IDs created close together share their first eight characters, making displayed chat session references unusable and allowing /topic to select the wrong first prefix match. Surface a sufficiently distinguishing shorthand and resolve topic references unambiguously.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:20:49Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:33Z","started_at":"2026-08-24T17:20:53Z","closed_at":"2026-08-24T17:28:39Z","close_reason":"Implemented with regression coverage, full task check passing, and adversarial review clean.","external_ref":"https://github.com/samcharles93/archie-core/issues/640","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-4tye","title":"Install updates without requiring a source checkout","description":"Make the automatic updater fetch approved release source into an invocation-scoped temporary clone, build and install the binary from that source, and never require or mutate an operator or agent checkout.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:11:05Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:34Z","started_at":"2026-08-24T17:11:11Z","closed_at":"2026-08-24T17:19:42Z","close_reason":"Implemented, regression-tested, full task check passed, and adversarial review finding resolved.","external_ref":"https://github.com/samcharles93/archie-core/issues/641","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489595430-1-8f81afa3","title":"Security: an unauthenticated endpoint must not be able to run an agent","description":"P0 within this epic because the feature's own pitch is the threat model: a public intake surface whose output is an agent with tool access and a repo. Get this wrong and a webhook URL is remote code execution with extra steps.\n\nNon-negotiables to design:\n\n- Per-source authentication. A source registers with a secret (HMAC, as internal/channels/webhook already does per route) before its events can trigger anything. Capture-only for unknown senders is acceptable; triggering is not.\n- Human approval before a binding goes live. An operator authoring a binding is a deliberate act; an event arriving is not. Nothing should self-arm.\n- Rate and volume limits per source, so capture cannot be used to exhaust disk or drown the inspector.\n- Payload content is untrusted input flowing into an agent prompt. Treat prompt injection as expected, not exceptional -- the sender controls that text, and the agent has tools. Bound what a playbook-triggered workflow may do.\n- Captured payloads may contain secrets from the sending system. Decide retention, redaction and who can view them; internal/memory/scrubber may already have applicable prior art.\n\nArchie's own principle applies: environmental enforcement over prompt rules. 'The agent should ignore instructions in the payload' is not a control.","status":"closed","priority":0,"issue_type":"feature","created_at":"2026-08-23T12:22:08Z","updated_at":"2026-08-24T06:58:51Z","closed_at":"2026-08-24T06:58:51Z","external_ref":"https://github.com/samcharles93/archie-core/issues/564","source_system":"github:https://github.com/samcharles93/archie-core/issues/564:564","metadata":null,"dependencies":[{"issue_id":"archie-core-1787489595430-1-8f81afa3","depends_on_id":"archie-core-t2db.5","type":"supersedes","created_at":"2026-08-24T06:58:51Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-mzok","title":"Make ClaimTurn insert-race regression deterministic under CI","description":"GitHub deploy run 32587841233 failed after the gateway compile fix because TestClaimTurnConcurrentInsertRaceNeverReturnsAnError launched 200 concurrent SQLite claims and exhausted its immediate retry loop with SQLITE_BUSY. The test's stated target is the two-connection same-turn insert race, not unrelated global write-lock saturation.","acceptance_criteria":"The regression still races two independent stores over the same turn ID; unrelated cross-trial SQLite contention cannot exhaust retries; repeated focused runs, task check, and diff-scoped lint pass; fresh adversarial review has zero surviving findings.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-22T17:34:07Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:59:21Z","started_at":"2026-08-22T17:34:11Z","closed_at":"2026-08-24T06:59:21Z","close_reason":"Already fixed on main: session_store_sqlite_claimturn_race_test.go now runs the 100 trials serially (two stores racing one turn ID per trial) with bounded SQLITE_BUSY retries, instead of 200 concurrent claims. Verified: -count=3 passes.","external_ref":"https://github.com/samcharles93/archie-core/issues/587","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-bia3","title":"Fix merged gateway capability contract blocking GitHub deploy","description":"PR #560 removed the dead BasePlatformAdapter while PR #561 independently added adapter_capabilities.go and tests that still depend on it. Both branches passed alone, but merged main no longer compiles, so deploy.yml cannot publish the intended video-generation release.","acceptance_criteria":"internal/gateway compiles without BasePlatformAdapter; live Telegram media delivery and capability reporting remain covered; task check and lint pass; a fresh adversarial review has zero surviving findings.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-22T17:15:14Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:59:22Z","started_at":"2026-08-22T17:15:22Z","closed_at":"2026-08-24T06:59:22Z","close_reason":"Already fixed on main: BasePlatformAdapter has zero references repo-wide, adapter_capabilities.go + tests stand alone. Verified: go build ./... clean, gateway capability tests pass.","external_ref":"https://github.com/samcharles93/archie-core/issues/588","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.1","title":"Bind worktree RPC operations to the dispatched task","description":"The sandboxed agent can currently choose owner, repo, issue, base, and branch on worktree RPC requests. The daemon then performs host deletion and credentialed forge operations without correlating the request to the dispatched task or enforcing WorkDir containment.","acceptance_criteria":"Reject traversal and unconfigured or task-mismatched coordinates before any filesystem or forge side effect; derive or validate the permitted branch; regression tests fail on the old behavior and pass on the fix.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:43Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:59:58Z","started_at":"2026-08-22T11:02:03Z","closed_at":"2026-08-24T06:59:58Z","close_reason":"Fixed on main: worktreerpc now exposes only Push, authorized by an opaque per-dispatch grant issued from the dispatched *store.Task (worktreerpc.go:71-83). Sandbox input no longer selects host path, repo or branch; ValidCoordinates rejects traversal. Package tests pass.","external_ref":"https://github.com/samcharles93/archie-core/issues/589","metadata":null,"dependencies":[{"issue_id":"archie-core-1ysw.1","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:42Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw","title":"Repair internal/worktree correctness and trust-boundary defects","description":"Track the concrete worktree-package defects proven by the 2026-08-22 evidence-gated review. Child bugs cover RPC authority/path containment, repository-key isolation, retry/base/diff correctness, push lifecycle, terminal cleanup, cancellation, and branch naming. This epic groups implementation only; each child has its own observable acceptance criteria.","acceptance_criteria":"All child bugs are closed with red-green regression tests, scoped lint passes, and the repository quality gate is clean.","status":"closed","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:18Z","created_by":"Sam Catlow","updated_at":"2026-08-24T08:16:00Z","closed_at":"2026-08-24T08:16:00Z","close_reason":"All 9 children complete. The P0/P1 trust-boundary and correctness defects (.1 RPC task binding, .2 colliding directory keys, .3 untracked cleanup, .4 fail-closed base resolution, .5 three-dot merge-base semantics) were already fixed on main and reconciled 2026-08-24. The remaining four (.6 push result, .7 no-change worktree leak, .8 commit cancellation, .9 branch naming contract) were implemented this session, merged as 474c31d and its two merge commits, task check green, with an independent adversarial review reporting zero findings.","external_ref":"https://github.com/samcharles93/archie-core/issues/590","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.5","title":"Security: an unauthenticated endpoint must not be able to run an agent","description":"P0 within this epic because the feature's own pitch is the threat model: a public intake surface whose output is an agent with tool access and a repo. Get this wrong and a webhook URL is remote code execution with extra steps.\n\nNon-negotiables to design:\n\n- Per-source authentication. A source registers with a secret (HMAC, as internal/channels/webhook already does per route) before its events can trigger anything. Capture-only for unknown senders is acceptable; triggering is not.\n- Human approval before a binding goes live. An operator authoring a binding is a deliberate act; an event arriving is not. Nothing should self-arm.\n- Rate and volume limits per source, so capture cannot be used to exhaust disk or drown the inspector.\n- Payload content is untrusted input flowing into an agent prompt. Treat prompt injection as expected, not exceptional -- the sender controls that text, and the agent has tools. Bound what a playbook-triggered workflow may do.\n- Captured payloads may contain secrets from the sending system. Decide retention, redaction and who can view them; internal/memory/scrubber may already have applicable prior art.\n\nArchie's own principle applies: environmental enforcement over prompt rules. 'The agent should ignore instructions in the payload' is not a control.","acceptance_criteria":"An event from an unauthenticated source can be captured but cannot trigger a workflow; a new binding requires explicit human approval before it arms; per-source rate limits exist; the blast radius of a playbook-triggered workflow is bounded by code rather than by prompt text; retention and visibility of captured payloads is decided and documented.","notes":"2026-08-22: security design decided and documented in docs/prds/webhook-intake-security.md, covering all five non-negotiables from this bead's description:\n1. Per-source auth reuses internal/channels/webhook's existing HMAC-SHA256 scheme; capture accepts unsigned events (visible, marked unauthenticated), only authenticated events can ever match a binding.\n2. Bindings gain a draft -\u003e pending_approval -\u003e armed state machine; any edit to an armed binding drops it back to pending_approval so approval can't be bypassed by editing. Modeled on telegram's existing dangerousAction/pendingApproval flow (dangerous.go/approval.go).\n3. Per-source token-bucket rate limiting (precedent: pairing/store.go's MaxPendingPerPlatform); limit-exceeded is an observable 429, not a silent drop.\n4. Blast radius bounded by the SAME code-level controls every task already gets -- gate, diff_cap_lines, sandboxed container, worktree isolation -- no new relaxation for playbook-triggered work, and payload text is ordinary untrusted prompt input, never a trusted instruction.\n5. 7-day configurable retention on captured payloads; best-effort redaction reusing gateway/stream.go's sensitiveParameterKey heuristic before persisting; visibility gated by the same dashboard auth as every other webui surface.\n\nThis bead's code-level acceptance criteria (capture-can't-trigger, rate limits exist, blast-radius bounded, approval gate) cannot be implemented yet: they constrain t2db.1 (capture), 7d5u.3 (intake family) and t2db.4 (binding), none of which have landed. This document is the contract those beads build against -- do not build any of them without satisfying it. Leaving this bead in_progress rather than closing it; it closes when t2db.1/7d5u.3/t2db.4 land and demonstrably satisfy points 1-5, not before.","status":"closed","priority":0,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:45:46Z","created_by":"Sam Catlow","updated_at":"2026-09-02T13:09:39Z","started_at":"2026-08-21T14:51:26Z","closed_at":"2026-09-02T13:09:39Z","close_reason":"Closed","external_ref":"https://github.com/samcharles93/archie-core/issues/536","dependencies":[{"issue_id":"archie-core-t2db.5","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-08-21T23:45:45Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8cda.2","title":"Phase 0: In-process contract seams (modular monolith, no process split)","description":"First phase of the resolved extraction order (open question #1). Still a\nmodular monolith -- no new process, nothing listening on a real port.\nIntroduces, in-process, the seams that make later extraction a swap of\ntransport rather than a rewrite, per open question #3's resolved\nmechanism (multiplexed in-process is the migration default).\n\nScope:\n- A ChatContract interface owned by the Gateway, aligning\n Router/SessionStore/Turns/ModelManager/PersonaRegistry behind it, so\n internal/webui depends on the contract type rather than holding\n *gateway.Router, gateway.SessionStore, *gateway.Turns,\n gateway.ModelManager, and *gateway.PersonaRegistry directly\n (internal/webui/api_chat.go's current ChatService struct, lines 22-26).\n- The ServiceRegistry interface from the discovery research\n (Resolve(service string) []Endpoint; Watch(service string) \u003c-chan\n Event), landed as a real internal package\n (internal/servicediscovery/servicediscovery.go per the research doc's\n citation) -- network-only; it never returns an in-process shim (see\n question #3's resolution part 3).\n- The State Store's already-narrow interfaces (TaskStore, CaptureStore,\n MappingStore, BindingStore, WorkflowStore in\n internal/store/interface.go) ratified as the State Store contract\n surface -- no code change to the interfaces themselves, this is the\n authority decision plus wiring them as wire-safe contracts.\n- For the ChatContract specifically: a wire-safe Go interface (values and\n streams only, no callbacks like Gateway's LLMStreamResponder, no\n *sql.Tx, no leaked object identity), a local in-process adapter (real\n production adapter, not a test fake), a generated gRPC client adapter\n satisfying the same interface via a compile-time assertion (the `var _\n store.WorkflowStore = (*Client)(nil)` idiom, internal/storerpc/storerpc.go:136),\n and a per-contract conformance suite run against both adapters over\n bufconn (the runSessionStoreSuite idiom,\n internal/gateway/sessionstore_conformance_test.go:65).\n- Composition (internal/app wiring), not ServiceRegistry, picks\n mode = \"inproc\" | \"remote\" per service, defaulting to \"inproc\".\n\nDepends on the contract-definition-mechanism issue (buf/proto toolchain)\nsince ChatContract's .proto definition and generated Go land here.\n\nFull reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#1\n(Phase 0 section) and #3 (the six-part mechanism).","acceptance_criteria":"- proto/gateway/v1/ ChatContract .proto definition committed, generated\n Go landed at internal/contracts/gateway/v1/ via the proto toolchain\n from the contract-mechanism issue.\n- ChatContract Go interface defined, wire-safe (no callbacks, no *sql.Tx,\n no object identity leaks).\n- A local adapter satisfying ChatContract that wraps the existing\n Router/SessionStore/Turns/ModelManager/PersonaRegistry in-process, with\n zero serialization.\n- A generated gRPC client adapter satisfying the same ChatContract\n interface, with a compile-time `var _ ChatContract = (*Client)(nil)`\n assertion.\n- A bufconn-based conformance test suite exercising both adapters against\n the same behavioural assertions.\n- internal/webui's ChatService depends on the ChatContract interface type,\n not on gateway.Router/SessionStore/Turns/ModelManager/PersonaRegistry\n structs directly.\n- mode = \"inproc\" | \"remote\" config plumbed through composition wiring,\n defaulting to \"inproc\"; no cmd/archie-gateway binary and nothing\n listening on a real network port yet.\n- ServiceRegistry interface (Resolve/Watch) exists as a real Go interface\n in internal/servicediscovery, even if only a stub/no-op implementation\n backs it at this phase.\n- task check passes; no behavioural change to production traffic (still\n fully in-process).","status":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T06:05:30Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:05:30Z","dependencies":[{"issue_id":"archie-core-8cda.2","depends_on_id":"archie-core-8cda","type":"parent-child","created_at":"2026-09-05T06:05:30Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-8cda.2","depends_on_id":"archie-core-8cda.1","type":"blocks","created_at":"2026-09-05T06:06:59Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8cda.1","title":"Contract-definition mechanism: buf v2 + protoc-gen-go/grpc-go toolchain","description":"Groundwork for all service-decomposition contracts (resolved open\nquestion #2 in docs/prds/service-decomposition.md). Every later phase\n(starting with Phase 0's ChatContract seam) needs this toolchain in place\nbefore it can define a wire contract.\n\nDecision (already made, not open for redesign here): buf v2 driving\nprotoc-gen-go + protoc-gen-go-grpc, targeting grpc-go -- NOT connect-go,\nbecause connect-go's net/http-based client breaks the service-discovery\nresearch's gRPC resolver plumbing for K8s DNS and NATS-KV custom\nresolvers. google.golang.org/grpc becomes a direct dependency (today only\ngoogle.golang.org/protobuf is an indirect one, go.mod:59).\n\nLayout: one committed proto/\u003cservice\u003e/v1/ tree (one buf module, not\nper-service modules), directory name matching the canonical\nservice/registry/DNS/chart name. Generated Go is committed (not\nbuild-time generated) to internal/contracts/\u003cservice\u003e/v1/, produced via\nbuf's managed mode (go_package_prefix) + paths=source_relative, per\ndocs/architecture/dependencies-and-contracts.md:55's per-domain\nwire-contract ownership rule.\n\nVersioning: directory versioning (v1, v2, ...); a breaking change gets a\nnew vN directory, never an in-place edit. Enforced by\n`buf breaking --against '.git#branch=main,subdir=proto'`.\n\nFull reasoning, scratch-verified buf/connect-go toolchain results, and\nthe CI shallow-checkout gotcha: see\ndocs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#2","acceptance_criteria":"- buf v2 config (buf.yaml / buf.gen.yaml) committed at the proto/ tree\n root; protoc-gen-go and protoc-gen-go-grpc wired as buf plugins\n targeting grpc-go.\n- Empty proto/\u003cservice\u003e/v1/ tree scaffolded (at minimum a placeholder or\n the first real service's .proto once Phase 0 needs it) with the\n directory-versioning convention documented.\n- Generated Go lands at internal/contracts/\u003cservice\u003e/v1/ and is committed\n (gofumpt-clean, matching the \"generated assets are LAW\" precedent).\n- New `task proto:generate`, `task proto:lint`, `task proto:check` tasks\n in Taskfile.yml; proto:check regenerates then `git diff --exit-code --\n internal/contracts`.\n- `task proto:generate/lint/check` wired into `task check`, inserted\n after `go fix ./...` and before vet/lint/build.\n- The same proto:lint/proto:check steps (or their direct buf/git-diff\n equivalents) mirrored into .github/workflows/deploy.yml's Quality gate\n step, since CI does not invoke `task check` today -- with fetch-depth:0\n (or an explicit `git fetch origin main`) so `buf breaking --against`\n has a local main ref to diff against.\n- `buf breaking` demonstrably fails the gate on a deliberately introduced\n breaking change (deleted RPC, renamed/removed field) in a smoke test or\n manual verification note.","status":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T06:05:10Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:05:10Z","dependencies":[{"issue_id":"archie-core-8cda.1","depends_on_id":"archie-core-8cda","type":"parent-child","created_at":"2026-09-05T06:05:10Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8cda","title":"Service decomposition: archie-core modularization","description":"archie-core moves from one Go binary (archied) hosting every domain\nin-process to a set of independently deployable services, each exposing\nexactly one typed contract. Consumers depend on the contract; they never\nreach into another service's internal types, session state, or config.\ngRPC is the synchronous transport; NATS remains for asynchronous fan-out\n(status, telemetry) rather than being replaced.\n\nThis is a distribution decision, not a rewrite of Archie's domain model.\nThe six-domain split already approved in docs/architecture/index.md and\ndocs/architecture/organisation.md (Identity, Agent, Messaging, Workflow,\nWork Intake, Plugin) is unchanged; this epic is about how the processes\nrunning that domain logic get packaged, contracted, and discovered.\n\nTarget services (see the PRD's table): UI Service, Gateway Service,\nMessaging Service, Curator Service (optional), Scheduler Service,\nExecution Environment, Runner, State Store.\n\nAll five blocking open questions in the PRD are resolved as of\n2026-09-05: extraction order (Gateway first, then State Store, UI,\nMessaging, Execution/Runner/Scheduler, Curator -- preceded by a Phase 0\ncontract-seams step), contract-definition mechanism (buf v2 +\nprotoc-gen-go/grpc-go), in-process-vs-out-of-process migration mechanism\n(multiplexed in-process is the default, per-service wire-safe contract\ninterfaces with local + gRPC adapters), State Store's contract shape (one\nState Store service, single SQLite, narrow typed contracts, no physical\nper-service database), and Helm chart / Operator ownership (a library\nchart + a core-services chart + a Curator chart/Operator).\n\nFull decision record: docs/prds/service-decomposition.md\nFull resolution detail and reasoning for each question:\ndocs/inspiration/service-decomposition-open-questions-research-2026-09-05.md\n\nFiling this epic satisfies the PRD's \"file a beads epic\" completion\ncriterion only. It does NOT authorize implementation -- the PRD's\ncompletion criteria separately require the captain's explicit go-ahead\ngiven the scale of this change. No implementation work should start\nagainst the child issues below until that go-ahead is given.","status":"open","priority":1,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-09-05T06:04:50Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:04:50Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-w1d5","title":"Gateway-only release must not rebuild or publish archie-agent","description":"## Bug Description\n\nA gateway-only release (`archied v1.22.0`, runtime skipped) still runs the `Build and push archie-agent` job and pushes `ghcr.io/samcharles93/archie-agent:latest` with `RUNTIME_VERSION=dev` because no `archie/v1.22.0` tag exists. This violates the release process rule that an untouched component must not be rebuilt or published.\n\n## Evidence\n\n- Release target: `archied/v1.22.0` only; `archie-agent` was explicitly skipped.\n- Workflow: `.github/workflows/deploy.yml` unconditionally builds both images.\n- Version resolver uses `RUNTIME_VERSION=dev` when no runtime tag points at HEAD.\n- Tag workflow 33723604418 passed, but rebuilt/pushed the agent image anyway.\n\n## Expected Behavior\n\nA gateway-only release builds and publishes only the archied component. The existing agent image remains unchanged.\n\n## Acceptance Criteria\n\n- Make the deploy workflow component-aware: skip the agent build/push when no `archie/v*` release tag points at HEAD.\n- Preserve full dual-image builds when both component tags are present.\n- Add CI/workflow validation for gateway-only and dual-component releases.\n- Do not publish an agent image stamped `dev` from a gateway-only release.\n","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-03T06:40:43Z","created_by":"Sam Catlow","updated_at":"2026-09-03T10:16:06Z","closed_at":"2026-09-03T10:16:06Z","close_reason":"Resolved by commit 5f2b253 (PR #712); GitHub #710 closed. Stale-open copy recovered from carina during machine sync.","external_ref":"https://github.com/samcharles93/archie-core/issues/710","labels":["bug","ci","release"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-n5fz","title":"Migrate existing bindings table for owner and repo columns","description":"## Bug Description\n\nArchied v1.22.0 starts successfully against the existing production task database, but binding listing logs `SQL logic error: no such column: owner`. The database was created/migrated by an earlier release and its `bindings` table has no `owner` or `repo` columns, while current `internal/store/bindings.go` selects/inserts/updates both columns.\n\n## Steps to Reproduce\n\n1. Run archied v1.22.0 against an existing database upgraded from the previous release.\n2. Open the bindings dashboard or call the bindings listing path.\n3. Observe `list bindings failed: SQL logic error: no such column: owner`.\n\n## Expected Behavior\n\nExisting databases migrate forward without data loss, and binding listing/creation/update works after upgrade.\n\n## Actual Behavior\n\nThe daemon stays up, but binding listing fails because the migration does not add the owner/repo columns required by the current binding store.\n\n## Evidence\n\n- Release: archied v1.22.0\n- Production DB: `/home/sam/.local/share/archie/archie.db-tasks.sqlite`\n- `pragma user_version = 2`\n- Existing `bindings` table has columns through `updated_at`, but no `owner` or `repo`.\n- Current code in `internal/store/bindings.go` references `owner` and `repo`.\n\n## Acceptance Criteria\n\n- Add an idempotent migration for owner/repo columns with safe defaults.\n- Preserve existing bindings and make them readable after upgrade.\n- Add regression coverage starting from the pre-owner/repo schema.\n- Verify binding list/create/update paths against both fresh and upgraded databases.\n- Do not reset or delete the production database.\n","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-03T06:39:09Z","created_by":"Sam Catlow","updated_at":"2026-09-03T10:16:05Z","closed_at":"2026-09-03T10:16:05Z","close_reason":"Resolved by commit 89f48a5 (PR #711); GitHub #709 closed. Stale-open copy recovered from carina during machine sync.","external_ref":"https://github.com/samcharles93/archie-core/issues/709","labels":["bug","migration","release"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-fwvf","title":"v1.20.0 archied startup panic and schema-unsafe update rollback","description":"## Bug Description\n\nAfter `/update` installed `archied` v1.20.0, the service failed to start. The update watchdog reported `health_check: failed` and rolled the binary back to v1.19.10, but the v1.20.0 binary had already migrated the task database to schema version 2. The rollback binary then entered a restart loop because it only supports schema version 1.\n\nRestoring the matching v1.20.0 daemon did not recover the service: it panics during startup in `(*boot).connectNATS` at `bootstrap.go:366` while dereferencing `cfg.NATS.URL`.\n\n## Steps to Reproduce\n\n1. Run `/update` from the Telegram gateway, selecting archied v1.20.0.\n2. Observe the watchdog health check fail and rollback.\n3. Start the matching v1.20.0 binary against the existing config.\n\n## Expected Behavior\n\nThe released daemon starts successfully with the production config, or returns a clear configuration error. `/update` must not leave the installed binary and persisted task schema at incompatible versions.\n\n## Actual Behavior\n\nThe service is in a systemd restart loop. v1.19.10 reports `store: migrate: database schema version 2 is newer than supported version 1`; v1.20.0 panics with `runtime error: invalid memory address or nil pointer dereference` in `connectNATS` at `bootstrap.go:366`.\n\n## Evidence\n\n- Installed before recovery: `archied 1.19.10`, `archie-agent 1.19.9`\n- Update report: installed daemon/agent `1.20.0`, `health_check: failed`, `rolled_back: true`\n- Task DB: `/home/sam/.local/share/archie/archie.db-tasks.sqlite`, `PRAGMA user_version = 2`\n- v1.20.0 panic: `url := cfg.NATS.URL` in `internal/app/archied/bootstrap.go:366`\n- Current config contains `[nats] url = \"nats://172.19.0.1:4222\"`\n\n## Acceptance Criteria\n\n- Add a regression test covering startup with the production NATS configuration and nil/invalid NATS state.\n- Remove the nil dereference; startup must return a useful error or initialise the required NATS configuration.\n- Make update rollback schema-safe: either verify the candidate before migration, retain/restore compatible state, or prevent rollback to a binary that cannot read the candidate schema.\n- Exercise `/update` or an equivalent installer/restart path and verify `archied.service` reaches active, Telegram gateway starts, NATS connects, and `/version` reports the installed release.\n- Preserve the task database and existing tasks.\n\n## Environment\n\n- Host: carina.srv.catlow.cloud\n- OS: Debian/Linux 6.12.96+deb13-amd64\n- Service: systemd user unit `archied.service`\n- Update path: Telegram `/update`\n","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-03T04:19:21Z","created_by":"Sam Catlow","updated_at":"2026-09-03T10:16:05Z","closed_at":"2026-09-03T10:16:05Z","close_reason":"Resolved; GitHub #703 closed. Stale-open copy recovered from carina during machine sync.","external_ref":"https://github.com/samcharles93/archie-core/issues/703","labels":["bug","release","update"],"comments":[{"id":"01a06585-1d1b-76bf-833a-71ba15ab0d3d","issue_id":"archie-core-fwvf","author":"Sam Catlow","text":"## Investigation correction\n\nThe panic frame is `setupObservability`, not `connectNATS`. In the released/latest source, `setupObservability` assigns `b.d.Mappings = ms` while `b.d` is still nil; `buildDaemon` runs later in startup. The direct nil dereference is therefore the daemon wiring order, while the schema-unsafe rollback remains the separate update failure.\n\nThe implementation and regression test will cover both paths.","created_at":"2026-09-03T04:26:58Z"}],"dependency_count":0,"dependent_count":0,"comment_count":1}
|
||||
{"_type":"issue","id":"archie-core-t2db.18","title":"eda: resolve mid-playbook action failure semantics (execution-time gap 1)","description":"Design-investigation ticket, same shape as the idempotency one above -- produces a design-doc resolution, not implementation. Gates multi-action playbooks (t2db.15 is deliberately single-action to avoid needing this). docs/prds/eda-playbook-engine.md's 'Execution-time gap 1' has no default yet and explicitly says a default must be a stated decision, not something nobody chose.\n\nGrounded by a crew investigation pass (2026-09-03, not committed -- content folded in here): read event-sources-and-reactions.md's producer-only/no-veto/no-mutation language, existing internal/domain/workflow stage-failure conventions (does a failing stage stop/wrap/resume?), and the load-collision report shape (drop+log+report to caller) from t2db.9-.12 as the precedent for how a run outcome should be reported.","design":"Decide and write the resolution into eda-playbook-engine.md:\n1. On action N of M failing: stop-on-first-failure (matches this doc's existing anti-clever-recovery bias) vs continue-to-independent-later-actions vs rollback. State which, and why the alternatives were rejected -- don't just restate the doc's existing hedge.\n2. What 'rollback' means (likely: nothing, since a posted forge comment isn't revocable) -- state this explicitly rather than leaving it implied.\n3. Producer-only interaction: decide whether a playbook reacting to its own action's failure by running compensating actions is in scope -- state the boundary explicitly against event-sources-and-reactions.md's producer-only rule.\n4. Condition-failure vs action-failure: J3 (CEL condition eval error -\u003e false, skip, log, continue) is already decided for conditions specifically. State cleanly how this differs from an actual action failure.\n\nSTRONG REUSABLE PRECEDENT FOUND IN THIS CODEBASE (verified directly, 2026-09-03) -- read internal/domain/workflow/workflow.go:294-352 (Run/finish/park) before designing anything new. The existing workflow engine already answers a structurally identical question for its own stages, and the answer is precise, not just 'stop on failure':\n- A real stage error: stop immediately, set ParkReason (which stage, what error), call park() -- status becomes store.StatusParked, requiring human/retry intervention. This IS this codebase's existing 'stop-on-first-failure, log the outcome, report to caller' pattern -- a playbook run failure should almost certainly reuse the SAME park/report shape (or a directly analogous one) rather than inventing new run-outcome semantics.\n- Context cancellation (ctx.Err() != nil, e.g. daemon shutdown mid-stage) is explicitly NOT treated as a failure: the task is left running so existing crash-recovery requeues it; parking here 'would publish a false failure and require manual intervention.' A playbook coordinator dispatching a Module/Workflow action needs the SAME distinction -- a daemon-shutdown interruption mid-action must not be recorded as an action failure, or every restart during a dispatch would falsely mark playbooks as broken.\n- A workflow ending without an explicit terminal outcome is itself parked as 'workflow ended without an outcome (definition bug)' -- i.e. an engine-level invariant violation gets its own distinct, honestly-labeled outcome rather than being silently treated as success. Consider whether a playbook run has an analogous 'must end with X' invariant.\n\nThis means gap 1 may reduce to: 'reuse park()'s three-way distinction (real failure / shutdown interruption / definition-bug) for playbook runs' rather than a from-scratch design -- read the actual code before deciding whether that reduction actually holds or where a playbook run's shape genuinely differs (e.g. playbooks may not have a Store.Transition-shaped persistence target the way a store.Task does -- confirm what a playbook run's own state, if any, actually gets recorded to).","acceptance_criteria":"eda-playbook-engine.md's Execution-time gap 1 section is marked resolved with a stated default (not a list of candidates) and explicit reasoning against event-sources-and-reactions.md's producer-only rule. No code changes required for this ticket to close.","notes":"Proposed resolution drafted 2026-09-03 in docs/prds/eda-playbook-engine.md, commit 99eaa7a -- reuses workflow.Run's existing three-way stage-failure distinction. Explicitly marked 'awaiting Sam's sign-off,' not settled.","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T18:12:15Z","created_by":"Sam Catlow","updated_at":"2026-09-05T07:10:42Z","closed_at":"2026-09-05T07:10:42Z","close_reason":"Closed","dependencies":[{"issue_id":"archie-core-t2db.18","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T18:12:15Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.17","title":"eda: resolve idempotency keying for Module/Channel/Forge actions (execution-time gap 2)","description":"Design-investigation ticket (like the CEL question, archie-core-t2db resolution in eda-playbook-engine.md) -- produces a design-doc resolution, NOT implementation. This is the sharper of the two unresolved execution-time gaps named in docs/prds/eda-playbook-engine.md's 'Execution-time gaps' section: workflow-kind actions inherit idempotency for free via TaskEnvelope; channel/forge/module actions with real side effects have no keying scheme, so a redelivered trigger event (internal/eventbus is at-least-once PublishUnique) would double-fire a comment, a message, or a billed image generation.\n\nGrounded by a crew investigation pass (2026-09-03, further-investigation.md, not committed -- content folded into this ticket): read internal/eventbus's PublishUnique key computation and existing dedup surface, TaskEnvelope's idempotency key minting/consumption path, event-sources-and-reactions.md's decided contract (extend it, don't contradict it), and the CEL context surface in internal/domain/eda/expr (event/actions fields available for key derivation).","design":"Design-decide and write into eda-playbook-engine.md:\n1. Granularity: one idempotency key per trigger-event + playbook (whole run dedups) vs per-action key derived from the run key. The doc's stated bias is the former unless a specific action needs finer dedup -- turn that bias into a stated decision.\n2. Where the key lives: does a playbook run get its own envelope/context carrying the key, and how does it reach the target position's invocation (Module.Invoke, a future Channel/Forge call)?\n3. What 'dedup' does on redelivery: is the whole run skipped, or just the already-fired action? What gets recorded?\n\nSTRONG REUSABLE PRECEDENT FOUND IN THIS CODEBASE (verified directly, 2026-09-03) -- do not design a new ledger without reading this first: internal/store/bindings.go already implements exactly this shape for playbook bindings. binding_dispatches table, unique on (binding_id, capture_id), written via RecordDispatch's 'INSERT OR IGNORE' -- a duplicate insert returns the sentinel ErrAlreadyDispatched, which dispatchBindings (internal/daemon/daemon.go:479) treats as a normal 'another cycle raced us' outcome, not an error. This is a proven, tested, at-most-once dispatch guarantee across cycles AND daemon restarts, for the exact same kind of problem (don't re-fire a binding for a capture it already dispatched). The playbook-run idempotency key almost certainly should reuse this exact pattern: a new ledger table (or a generalization of binding_dispatches) keyed on (playbook_id, event_id) or (playbook_id, trigger_event_identity), written with the same INSERT OR IGNORE + sentinel-error convention. Read internal/store/bindings.go:29-61,351-378 and internal/daemon/daemon.go:479-514 before designing anything -- this may reduce gap 2 to 'apply the existing pattern to a new key shape' rather than new design.\n4. Key derivation: a CEL-reachable expression over event fields, or a stable hash of event-identity+playbook-id -- pick one and justify it against the expr package's actual context surface, and against how capture identity is derived today (check what 'capture_id' actually is -- likely a stable hash or row id from the same capture pipeline a playbook trigger would also read).","acceptance_criteria":"eda-playbook-engine.md's Execution-time gap 2 section is marked resolved with a stated decision (not a survey of options) covering granularity, key storage/lookup, redelivery behavior, and key derivation. Consistent with event-sources-and-reactions.md's existing idempotency contract -- explicitly states how it extends rather than contradicts it. No code changes required for this ticket to close.","notes":"Proposed resolution drafted 2026-09-03 in docs/prds/eda-playbook-engine.md, commit 99eaa7a -- reuses internal/store/bindings.go's binding_dispatches ledger shape. Explicitly marked 'awaiting Sam's sign-off,' not settled. Surfaced two concrete prerequisites while drafting: t2db.15's Playbook struct needs an ID/Version (doesn't have one), and DispatchInput needs a task identity threaded through (doesn't have one either) -- both stated honestly as blockers for implementation, not glossed over.","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T18:12:13Z","created_by":"Sam Catlow","updated_at":"2026-09-05T07:10:42Z","closed_at":"2026-09-05T07:10:42Z","close_reason":"Closed","dependencies":[{"issue_id":"archie-core-t2db.17","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T18:12:13Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":3,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-e7bo","title":"fix stale wfextract go:generate directive; audit pluginextract/secretextract drift","description":"Discovered 2026-09-03 while scoping archie-core-t2db.13 (Module position). Two separate, pre-existing issues, unrelated to the playbook engine work -- do not fix as a drive-by inside that ticket.\n\n1. internal/domain/workflow/wfextract/wfextract.go's //go:generate directive still targets 'github.com/samcharles93/archie-core/internal/workflow', a path that has not existed since the domain migration (7e896c9, 2026-08-07 - the package moved to internal/domain/workflow). The committed generated file was hand-patched at some point to import the new path, but the directive itself was never fixed. Net effect: 'go generate ./...' has been broken repo-wide (at least for wfextract) since that migration, silently, for anyone who hasn't tried running it.\n\n2. Running 'go generate ./...' anyway (to see what breaks) also produced real, substantive diffs in internal/plugin/pluginextract and internal/secret/secretextract's generated symbol tables -- new wrapper types (Host, Module) appearing that are NOT in the currently-committed, in-production symbol tables. This means the Yaegi plugin and secret-engine extension surfaces have been running against stale, incomplete generated symbol tables for an unknown period: interpreted plugin/secret-engine code may be unable to reference types it should have access to. This is a latent correctness gap with real blast radius on two extension surfaces, not cosmetic drift.","design":"Two-part fix, do not conflate:\n1. Fix wfextract's directive to point at internal/domain/workflow (matching what the generated file already imports). Verify 'go generate ./internal/domain/workflow/wfextract/...' now succeeds and produces output identical (or intentionally different, documented why) to what's committed.\n2. For pluginextract/secretextract: do NOT blindly regenerate-and-commit. First determine why they're stale (when did plugin.go/secret's Engine gain the types the fresh generation adds -- git log on internal/plugin/plugin.go and internal/secret's engine files vs. when the generated files were last touched) and whether any existing test exercises a Yaegi plugin/secret-engine referencing the missing types (if none does, that's itself a coverage gap worth noting). Regenerate, gofumpt, and add/confirm a test that would have caught the drift, before committing the regenerated symbol tables -- this is a correctness-sensitive change to two live extension surfaces and needs real verification, not a mechanical re-run.","acceptance_criteria":"'go generate ./...' completes without error across the whole repo. wfextract's directive matches its actual package path. pluginextract/secretextract regeneration (if done) is backed by a test demonstrating the previously-missing types are now reachable from interpreted code, and task check passes. No behavior change to existing plugins/secret engines that were already working (regression-tested, not assumed).","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-02T17:17:42Z","created_by":"Sam Catlow","updated_at":"2026-09-02T17:30:34Z","closed_at":"2026-09-02T17:30:34Z","close_reason":"Fixed and gate-verified as e3a20f6 (pushed to main). wfextract directive now targets internal/domain/workflow; 'go generate ./...' completes repo-wide. All four extract surfaces regenerated; nil-guards re-applied on interface wrappers (documented IMPORTANT note restated in wfextract package doc). Previously-missing symbols proven reachable from interpreted code: wfextract (Forger/Reviewer/Trees/routing loaders) and pluginextract (Host/Module/Manifest/NewHost/HostAPIVersion) via new reachability tests; secretextract exports were current (nil-guard drift only). Red-then-green verified: fresh regen wipes guards -\u003e guard tests panic -\u003e re-apply -\u003e pass. task check clean (113/113 UI, exit 0).","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-95dj","title":"StageCommitPush discards baseline-fix commits when build makes no changes","description":"Confirmed via carina production logs (task 6, chat-spawned synthetic test task, 2026-09-02). StageBaselineGate (internal/domain/workflow/implement.go:37) found the repo's gate red at the base commit, spent 405,004 tokens/14 iterations genuinely fixing two broken pre-existing tests, and committed the fix locally via tc.Trees.CommitAll (implement.go:104) -- verified passing. plan and build stages then correctly found nothing else to do for the (synthetic, content-free) task. StageCommitPush -\u003e closeNoChangesIssue (steps.go:56) decides 'no changes' purely from tc.BuildNoChanges, which the build AgentStage sets from its own len(res.Changes)==0 (implement.go:176) -- it has zero awareness that StageBaselineGate already committed real changes two stages earlier. Never pushed, never opened a PR; the entire worktree containing a real, gate-verified fix for genuinely broken tests was discarded when the task closed as 'merged: completed -- no changes required'.\n\nCost: 669,421 tokens burned to fix a real bug that then evaporated. This recurs: any task that hits the same red baseline pays the identical tax again since the fix never lands. Evidence a prior incident already happened: an orphaned 'fix: baseline gate repair' commit (e49f3cd) sits on a stale, unmerged branch (fix/441-archied-repos-entries-cant-span-more-than-one-forge) from an earlier occurrence.","design":"Fix direction: either (a) StageBaselineGate sets a flag /flips tc.BuildNoChanges appropriately when it commits, or (b) StageCommitPush's no-changes branch checks the worktree's actual diff against the base branch (tc.Trees, similar to StageDiffCap's ChangedLines) instead of trusting tc.BuildNoChanges alone. Prefer (a): cheaper, and keeps the diff-against-base check (which already exists for StageDiffCap) from being computed twice per task.","acceptance_criteria":"A task whose baseline-fix stage committed real changes, but whose plan/build stages found nothing further to do, still pushes and opens a PR carrying the baseline-fix commit -- it must never be silently discarded. tc.BuildNoChanges (or StageCommitPush's decision) accounts for what StageBaselineGate already committed, not just the build stage's own diff. Regression test reproduces the exact scenario (baseline-fix commits, build stage reports zero changes) and proves a PR opens. task check passes.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-09-02T11:20:48Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:02Z","started_at":"2026-09-02T11:20:51Z","closed_at":"2026-09-02T11:25:53Z","close_reason":"Fixed via a new TaskContext.BaselineFixed flag: StageBaselineGate sets it when its own CommitAll reports a real committed change (implement.go:104-111). The build stage's OnResult only sets BuildNoChanges when its own diff is empty AND BaselineFixed is false (implement.go:177), so a baseline-only fix can no longer be masked as 'no changes'. StageCommitPush itself now calls CommitAll directly and pushes whenever either a new commit was made OR BaselineFixed is true (steps.go), instead of erroring on 'nothing to commit' when the real change already sits on the branch from the baseline-fix commit. Two new regression tests (TestStageCommitPushPushesBaselineFixEvenWithNothingNewToCommit, TestStageBaselineGateSetsBaselineFixedWhenItCommits) plus a guard test that the old empty-tree error still fires without a baseline fix. task check clean.","external_ref":"https://github.com/samcharles93/archie-core/issues/682","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-s81k","title":"Preserve bound slog attributes in persistent log sinks","description":"PR #650 scopes daemon, Web UI, and curator loggers with slog.Logger.With. internal/logging.FeedHandler.WithAttrs retains those bound attributes for the live feed but does not pass them to the wrapped handler, while Handle forwards the bare slog.Record. As a result, component is present in live Web UI entries but absent from stderr and file JSON; after restart, historical component discovery and filtering cannot see those records. Fix bound-attribute propagation without breaking slog group semantics or duplicating attributes.","acceptance_criteria":"Bound attributes appear in both Feed entries and the wrapped JSON sink; component values survive file persistence and are discoverable and filterable through historical /api/logs reads; regression tests exercise logger.With for both live and persistent paths; task check passes.","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-02T09:37:55Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:54Z","closed_at":"2026-09-02T09:43:01Z","close_reason":"Fixed: FeedHandler.WithAttrs/WithGroup now propagate to the wrapped handler, matching SystemLogHandler's existing pattern. Added regression test covering both feed and persistent sink.","external_ref":"https://github.com/samcharles93/archie-core/issues/655","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-d66k","title":"P1: Update ARCHITECTURE.md Package Map with missing packages","description":"ARCHITECTURE.md's Package Map omits sizeable load-bearing packages:\n- internal/gateway: 18.7k LOC\n- internal/tools: 20.9k LOC\n- internal/memory: 7k LOC\n- secret/*\n- plugin/*\n- skill/*\n\nA contributor or agent reading the map would miss where most of the code actually lives.\n\nNeed to:\n- Audit ARCHITECTURE.md Package Map section\n- Add all missing packages with their responsibilities\n- Ensure consistency with actual package structure\n- Verify LOC counts are accurate\n\nBlocked by: nothing","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:10Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:55Z","closed_at":"2026-08-31T10:10:50Z","close_reason":"Added internal/gateway, internal/tools, internal/memory, internal/secret, internal/plugin, internal/skill to ARCHITECTURE.md Package Map with LOC and role descriptions","external_ref":"https://github.com/samcharles93/archie-core/issues/656","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-p3wt","title":"P1: Fix recvcheck - mixed pointer/value receivers","description":"recvcheck found mixed pointer/value receivers on:\n- Duration\n- TaskEnvelope\n- Provenance\n\nThis is a latent mutation-semantics bug - methods may not behave correctly if they expect to mutate the receiver.\n\nNeed to:\n- Audit all methods on Duration, TaskEnvelope, Provenance\n- Standardize to either all pointer receivers or all value receivers\n- Prefer pointer receivers for types that need mutation\n- Verify no behavior changes after fix\n\nBlocked by: nothing","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:07Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:55Z","closed_at":"2026-08-31T10:09:59Z","close_reason":"Duration and TaskEnvelope were already consistent by the time this was picked up; fixed the remaining recvcheck violation on Provenance (Paths/String moved to pointer receiver to match the mutating record() method). All Provenance uses are through addressable struct fields, so build/tests are unaffected. recvcheck now reports 0 issues.","external_ref":"https://github.com/samcharles93/archie-core/issues/657","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-agui","title":"P1: Fix 31 golangci-lint issues","description":"31 golangci-lint issues clustered as high cyclomatic/cognitive complexity in:\n- internal/tools/builtin/find.go\n- internal/tools/builtin/grep.go\n- internal/tools/builtin/shell.go\n- internal/gateway/go:dispatchLocal\n\nThese are real refactor candidates, not noise.\n\nNeed to:\n- Review each issue to understand the complexity\n- Refactor functions to reduce cyclomatic complexity\n- Break down large functions into smaller, focused ones\n- Re-run golangci-lint to verify fixes\n\nBlocked by: nothing","notes":"Fixed cyclop findings (applyEdits, grepFallback, grepDirFallback, serveReadContent, handleChatStream) and several gocognit/funlen findings (TDD, runFindGoFallback, makeGrepExecutor, makeShellExecutor). Remaining: richblocks.go markdownToBlocks/blocksToPlainText (gocognit), gateway.go dispatchLocal (gocyclo), agent.go Stage (gocognit 70), turn.go Run (gocognit 53), tomlwrite.go Apply (gocognit 82), cronstore store.go Update (gocognit) + nestif x2, toolset.go nestif. 22 of original 31 findings remain unaddressed -- keeping open.","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:04Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:56Z","closed_at":"2026-08-31T11:36:17Z","close_reason":"All 31 original findings (5 cyclop, 9 gocognit, 1 gocyclo, 2 nestif, plus incidental funlen) resolved via targeted extraction across tools/builtin, gateway, workflow, webui, telegram, cronstore, tomlwrite, agentexec. Remaining 6 lint findings (containedctx/errorlint/noctx/staticcheck) were never part of this bead's scope.","external_ref":"https://github.com/samcharles93/archie-core/issues/658","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-k7y7","title":"P1: Address coverage gaps in load-bearing packages","description":"Coverage gaps in critical packages:\n- domain/workintake: 14.3%\n- secret/enginehost: 0%\n- secret/secretextract: 10%\n- forge: 35.8%\n- natsrpc: 28.3%\n\nNeed to:\n- Analyze why coverage is low in these packages\n- Add tests for uncovered code paths\n- Prioritize based on risk/criticality\n- Aim for at least 60-70% coverage in load-bearing packages\n\nBlocked by: nothing","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:01Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:57Z","closed_at":"2026-08-31T11:27:21Z","close_reason":"Raised coverage: workintake 14.3%-\u003e94.6%, secret/enginehost 0%-\u003e100%, secret/secretextract 10%-\u003e100%, forge 36.1%-\u003e77.0%, natsrpc 28.3%-\u003e91.3%. Committed as bc5b355.","external_ref":"https://github.com/samcharles93/archie-core/issues/659","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-zq4l","title":"P1: Tighten CI go-version pinning","description":"CI's go-version is set to '1.26' (floating) while go.mod has exact 1.26.5. This loose coupling means CI could use 1.26.0-1.26.5 or newer minor versions, potentially missing bugs or compatibility issues.\n\nNeed to:\n- Pin CI go-version to exact match go.mod (currently 1.26.5, will be 1.26.6+ after P0 bump)\n- Consider using same variable/source of truth for both\n- Update CI configuration files\n\nBlocked by: Go version bump (archie-core-1sjk) for consistency","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:41:58Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:57Z","closed_at":"2026-08-31T10:05:31Z","close_reason":"Switched CI to actions/setup-go go-version-file: go.mod so CI's Go version is always sourced from go.mod directly, eliminating drift","external_ref":"https://github.com/samcharles93/archie-core/issues/660","dependencies":[{"issue_id":"archie-core-zq4l","depends_on_id":"archie-core-1sjk","type":"blocks","created_at":"2026-08-28T13:42:31Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-0bvr","title":"P1: Add govulncheck step to CI/Taskfile","description":"The 6 stdlib CVEs went undetected through normal task check because there's no govulncheck step anywhere in CI or Taskfile.\n\nNeed to:\n- Add govulncheck to Taskfile.yml (e.g., task vuln)\n- Consider adding to CI pipeline\n- Decide: should vuln check be part of task check or separate?\n- Document the new task\n\nBlocked by: nothing","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:41:54Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:58Z","closed_at":"2026-08-31T10:05:53Z","close_reason":"Added 'task vuln' (govulncheck) to Taskfile, deliberately kept out of task check since it needs network access to the vuln DB; wired as a separate CI step in deploy.yml","external_ref":"https://github.com/samcharles93/archie-core/issues/661","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-g1y3","title":"P1: Refactor internal/gateway/ - duplicate implementation risk with messaging domain","description":"internal/gateway/ contains session/compression/approval/branch logic which is the exact 'parallel gateway implementation' that migration-decisions.md says must be replaced by the not-yet-built messaging domain.\n\nThis is a live duplicate-implementation risk - gateway logic should migrate to domain/messaging.\n\nNeed to:\n- Analyze current gateway responsibilities\n- Create domain/messaging package structure\n- Migrate gateway logic incrementally to messaging domain\n- Update callers to use domain/messaging\n- Ensure no behavior changes during migration\n\nBlocked by: domain/messaging package not yet created","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:41:51Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:59Z","closed_at":"2026-08-31T10:12:25Z","close_reason":"Resolved migration-decisions.md's open Session/Messaging decision: keep internal/gateway as-is rather than risk a big-bang rewrite of live session/compression/approval/branch logic. Materialised internal/domain/messaging with the already-settled canonical Message/Conversation/ToolCall/ToolResult types (composite Conversation identity, immutable MessageID, branch lineage), with tests. Actual gateway migration onto these types is tracked as sequenced follow-up bd issues (d9dv, 4hof, o4e4, h3w2, label messaging-migration) so each channel lands with its own verification.","external_ref":"https://github.com/samcharles93/archie-core/issues/662","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tnsr","title":"P1: Bump ai-sdk from v0.1.29 to v0.1.30","description":"github.com/samcharles93/ai-sdk is pinned at v0.1.29, one release behind (v0.1.30 pushed today).\n\nMissing features available in v0.1.30:\n- NewTypedTool\n- GenerateTypedObject\n- errx.ProviderError\n- RetryConfig.OnAttempt\n\nConcrete usage sites in internal/agentexec/loop_runner.go:\n- pluginToolSet: hand-writes JSON Schema + manual unmarshal\n- scriptToolSet: hand-writes JSON Schema + manual unmarshal\n\nThese are clean NewTypedTool[In] candidates once bumped.\n\nNeed to:\n- Update go.mod to require ai-sdk v0.1.30\n- Run go mod tidy\n- Refactor pluginToolSet and scriptToolSet to use NewTypedTool\n- Verify no breaking changes\n\nBlocked by: nothing","status":"closed","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:41:43Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:48:59Z","closed_at":"2026-08-31T10:06:42Z","close_reason":"go.mod already on ai-sdk v0.1.30. Refactored pluginToolSet and scriptToolSet in internal/agentexec/loop_runner.go to use NewTypedTool instead of hand-written JSON Schema + manual unmarshal; tests pass","external_ref":"https://github.com/samcharles93/archie-core/issues/663","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-z0u8","title":"Fix dashboard PR links to target the pull request","description":"The task dashboard Open PR action builds GitHub /pulls/\u003cnumber\u003e, which GitHub interprets as the pull-request listing and a numeric author filter. Link directly to /pull/\u003cnumber\u003e.","acceptance_criteria":"Open PR links use the forge's direct pull-request URL shape; a regression test fails against the plural route and passes after the fix; quality gate passes.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:57:39Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:35Z","started_at":"2026-08-24T17:57:46Z","closed_at":"2026-08-24T19:48:35Z","close_reason":"The API now supplies canonical per-task GitHub or Gitea URLs and the dashboard consumes them directly. Regression coverage, task check, and fresh adversarial review pass.","external_ref":"https://github.com/samcharles93/archie-core/issues/642","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-jy5m","title":"Make task timeline events operationally informative","description":"Task timelines currently render generic stage_start/stage_finish entries with no stage name or outcome, and task_retried entries add little beyond the event kind. Surface the existing event stage, workflow, detail, and relevant structured data so operators can understand what happened without opening raw logs.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:39:51Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:36Z","started_at":"2026-08-24T17:39:57Z","closed_at":"2026-08-24T17:55:34Z","close_reason":"Task timelines now render stage/retry context; baseline and gate-cycle logs expose useful bounded failure output. task check and independent review pass.","external_ref":"https://github.com/samcharles93/archie-core/issues/643","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-y1hv","title":"Relay dashboard update completion through Telegram","description":"Integrate the existing Carina-side behavior so dashboard-initiated updates can deliver their post-restart watchdog result to an authorized Telegram recipient, while retaining the web UI report path fallback.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:18:30Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:36Z","started_at":"2026-08-24T17:18:35Z","closed_at":"2026-08-24T17:19:42Z","close_reason":"Implemented, regression-tested, full task check passed, and adversarial review finding resolved.","external_ref":"https://github.com/samcharles93/archie-core/issues/644","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b7f1","title":"Fix Web UI session UUID compatibility and update-status synchronization","description":"The production Web UI crashes when crypto.randomUUID is unavailable, preventing chat session creation. Review and fix UUID generation compatibility plus the recovered Web UI/Telegram update-status synchronization issue, with regression tests and production-path verification.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T16:50:12Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:37Z","started_at":"2026-08-24T16:50:18Z","closed_at":"2026-08-24T17:00:21Z","close_reason":"Implemented UUIDv7 identities, replayable archived chat tool activity, and post-start update report delivery; full quality gate passes.","external_ref":"https://github.com/samcharles93/archie-core/issues/645","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-vq92","title":"task_logs truncates at 50KB with no pagination, so full logs are unreachable","description":"The task_logs chat tool caps its response at 50 KB and offers no way to fetch the rest. An operator asking the agent to retrieve or archive a task's logs gets a silently clipped window, and the agent has no mechanism to page past it. Observed 2026-08-24: asked to save a full transcript and agent logs, the agent could only produce a partial archive and had to document the truncation as a limitation rather than satisfy the request.\n\nThe failure compounds with archie-core-p1bl (errors logging as `{}`): a truncated log of uninformative errors leaves an operator with nothing at all, precisely when a task is stuck.\n\n## What is needed\n\nTruncation itself is legitimate -- a tool result must be bounded, and unbounded log text would blow the model's context. The defect is that truncation is TERMINAL: there is no continuation, no offset/cursor, no way to narrow the window, and the caller cannot tell how much was lost.\n\nEstablish first where the cap is applied (the task_logs tool in internal/gateway/task_tools.go and whatever log reader it calls in internal/logging -- note internal/logging owns the on-disk format end to end and internal/webui parses nothing, per CLAUDE.md, so the reader is the right place for range support).\n\nDesign points to decide:\n- A cursor or offset so successive calls walk the whole log, rather than always returning the same head or tail.\n- Filters that make bounded retrieval useful rather than merely possible: by level (errors only), by time range, by stage.\n- The response must state explicitly that it was truncated and how much remains, so the agent can report honestly instead of implying completeness.\n- Consider whether bulk retrieval belongs in a tool result at all, or whether the right answer for \"save the full logs\" is to write the file and deliver it via the new send_file path (archie-core-absb), keeping the tool result small.\n\n## Acceptance Criteria\n\nAn operator can obtain a task's complete logs through the agent, by paging or by file delivery; a truncated response says so and reports what remains rather than ending silently; level and time-range filtering exist so a bounded call can still answer a specific question; the cap remains enforced so no single response can exhaust the model's context; tests cover a log larger than the cap and assert that repeated calls retrieve all of it without gaps or duplication.\n","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:15Z","created_by":"Sam Catlow","updated_at":"2026-08-25T16:04:57Z","started_at":"2026-08-25T15:03:46Z","closed_at":"2026-08-25T16:02:24Z","close_reason":"task_logs cursor pagination, level/time filters, and honest truncation reporting","external_ref":"https://github.com/samcharles93/archie-core/issues/625","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-p1bl","title":"Task logs serialise errors to an empty object, destroying diagnostics","description":"Error values in task logs sometimes render as an empty JSON object, so the one field that says WHY something failed carries no information. Observed in production task logs 2026-08-24, in the same stream:\n\n {\"time\":\"...\",\"level\":\"ERROR\",\"message\":\"handle failed\",\"fields\":{\"err\":{}}}\n {\"time\":\"...\",\"level\":\"ERROR\",\"message\":\"handle failed\",\"fields\":{\"err\":\"stage re…\"}}\n\nSame message, same field, two different encodings -- one useful, one useless. The empty-object form is what an operator hits when diagnosing a stuck task, which is exactly when the log is the only evidence available.\n\n## Likely mechanism (to be confirmed, not assumed)\n\n`{}` is what encoding/json produces for a struct with no exported fields. A custom error type (a struct implementing `error` via a value or pointer receiver, with all fields unexported) marshals to `{}` rather than to its Error() string, because encoding/json does not consult the error interface. Errors that happen to be `*errors.errorString` or `fmt.Errorf` results go through a different path and survive as text.\n\nStart at internal/logging (attrs.go and its tests already reference a \"handle failed\" record, so the attribute handling is there) and establish where an `error` attribute is converted for the JSONL sink. The fix is to render errors through their Error() string -- and, where the error carries structured context worth keeping, to do so ADDITIONALLY rather than instead.\n\n## Why P1\n\nSam's words: \"LOGGING! ... this is another critical requirement.\" Diagnosis of every other defect depends on it. Two separate investigations this week were slowed by log output that recorded that something failed without recording what.\n\nNote this compounds archie-core-1ysw-era debugging and the parked-task investigation: an operator seeing `{\"err\":{}}` has strictly less information than one seeing no log line at all, because the empty object implies the error was captured.\n\n## Steps to Reproduce\n\n1. Arrange for a code path that logs a custom error type (unexported fields) as an `err` attribute.\n2. Read the task's JSONL log via the dashboard, /api logs, or the task_logs tool.\n3. Observe `\"err\":{}` where the message should be.\n4. Compare with a path that logs a fmt.Errorf value and observe `\"err\":\"...\"` in the same file.\n\n## Acceptance Criteria\n\nEvery error logged as an attribute renders its Error() text in the JSONL sink regardless of the concrete error type; a custom error type with only unexported fields is covered by a test asserting the message survives; structured context on an error is preserved in addition to, never instead of, the message; a regression test fails against the current encoder; no log line can report an error as an empty object.\n","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T15:47:44Z","created_by":"Sam Catlow","updated_at":"2026-08-25T15:05:24Z","closed_at":"2026-08-25T15:05:24Z","close_reason":"Shipped in 6a23f8d: logging resolves every non-nil error attribute through Error(), with custom unexported-field and typed-nil regression coverage; included in archied v1.18.0.","external_ref":"https://github.com/samcharles93/archie-core/issues/626","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-440c","title":"Dashboard mutations 403 behind a TLS-terminating reverse proxy: Origin check ignores X-Forwarded-Proto","description":"Every operator action from the dashboard -- Stop, Cancel, Retry, Approve, Reject, Abandon, Archive -- fails with HTTP 403 in the production deployment. Observed 2026-08-24: `POST https://archie.catlow.cloud/api/tasks/3/action` returned 403 in 7ms with a 30-byte body. This left the operator with no way to stop a running task from the web UI at all.\n\n## Root cause\n\n`authorizeTaskMutation` (internal/webui/api_tasks.go:197-221) derives the expected Origin scheme from the daemon's OWN connection:\n\n wantScheme := \"http\"\n if r.TLS != nil {\n wantScheme = \"https\"\n }\n ...\n if ... || !strings.EqualFold(u.Scheme, wantScheme) || !strings.EqualFold(u.Host, r.Host) {\n http.Error(w, \"cross-origin mutation refused\", http.StatusForbidden)\n\narchied runs behind a reverse proxy that terminates TLS (confirmed: archie.catlow.cloud redirects to auth.catlow.cloud for forward auth, and the request was HTTP/2 to the proxy). The daemon therefore receives a PLAIN HTTP connection, so `r.TLS == nil` and `wantScheme == \"http\"`, while the browser correctly sends `Origin: https://archie.catlow.cloud`. Scheme mismatch -\u003e 403 on every mutation.\n\n`X-Forwarded-Proto` is never consulted anywhere in the codebase (`grep -rn 'X-Forwarded' internal/webui/ internal/config/` returns nothing).\n\n## Evidence the body confirms which branch fired\n\nThere are exactly two 403 paths in this handler. Their response bodies differ in length:\n- \"missing CSRF header\\n\" = 20 bytes\n- \"cross-origin mutation refused\\n\" = 30 bytes\n\nThe observed response was 30 B, so the Origin comparison is what rejected it, NOT the CSRF header. The dashboard is sending X-Archie-CSRF correctly.\n\n## Why this is P1\n\nIt is a total loss of the operator control surface in the supported deployment shape. It also removes the documented remedy for other faults: archie-core-0dic leaves a stopped task's row reading `running`, and `Parked`'s retry action is the stated recovery for a review that fails closed (docs/prds/adversarial-self-review.md section 4) -- both assume dashboard actions work.\n\nNote the deployment model is explicitly plural (CLAUDE.md \"Deployment model\": several supported shapes, systemd is not required), so \"runs behind a proxy\" is a first-class configuration, not an edge case.\n\n## Steps to Reproduce\n\n1. Serve archied behind any TLS-terminating reverse proxy (nginx, Caddy, Traefik, or a forward-auth proxy such as Authelia), with the daemon listening on plain HTTP.\n2. Load the dashboard over https and press Stop on a running task.\n3. Observe `POST /api/tasks/\u003cid\u003e/action` -\u003e 403, body \"cross-origin mutation refused\".\n4. The same build works when reached directly over http, or over https terminated by the daemon itself, which is why this does not reproduce in local development.\n\n## Acceptance Criteria\n\nDashboard mutations succeed when archied is behind a TLS-terminating reverse proxy; the effective scheme is derived from X-Forwarded-Proto (and the effective host from X-Forwarded-Host where applicable) ONLY when the request arrives from a trusted proxy, configured explicitly -- an unconditional trust of these headers would let any client forge the Origin check and defeat the CSRF protection this function exists to provide; direct (non-proxied) deployments keep their current strict behaviour; tests cover proxied-https, direct-http, direct-https, and a spoofed X-Forwarded-Proto from an untrusted source; the config surface and its default are documented in config.example.toml and the deployment profiles.\n","notes":"CONFIRMED LIVE against production 2026-08-25 via Playwright, signed in as the operator.\n\nReproduced the dashboard's own Stop request from the loaded page:\n\n fetch('/api/tasks/3/action', {method:'POST',\n headers:{'X-Archie-CSRF':'1','Content-Type':'application/json'},\n body:'{\"action\":\"stop\"}'})\n\nResult: status 403, body exactly \"cross-origin mutation refused\\n\" (30 bytes), with location.origin = https://archie.catlow.cloud and location.protocol = https:.\n\nThis settles which of the two 403 branches fires. The request carried a correct X-Archie-CSRF header and same-origin credentials, so it passed the CSRF check and was rejected by the Origin comparison in authorizeTaskMutation. Combined with the deployment shape (archie.catlow.cloud 302s to auth.catlow.cloud for forward auth, so TLS terminates at the proxy and the daemon sees plain HTTP), the scheme comparison is the failing term: browser Origin scheme 'https' vs the daemon's computed wantScheme 'http' from r.TLS == nil.\n\nThe dashboard confirms the operator impact at the same time: the header reads '1 running' and task #3 is still listed as running (that stale row is archie-core-0dic, a separate defect). So in production the Line truncated
|
||||
{"_type":"issue","id":"archie-core-0dic","title":"Stopped tasks stay 'running' forever: terminal writes ride the cancelled context","description":"/stop reports success and genuinely does stop the container, but the task row is never updated, so the dashboard, /status and task_list all show the task as running indefinitely. Observed 2026-08-24: task #3 was stopped and was still displayed as running the following day.\n\n## Root cause\n\n`Daemon.runViaAgent` (internal/daemon/daemon.go:1010-1100) writes its terminal state with the SAME context that was just cancelled, and discards the result:\n\n reply, err := d.requestTaskRun(ctx, task.ID, data) // returns ctx.Err() on /stop\n if err != nil {\n _ = d.Store.Transition(ctx, task.ID, store.StatusRunning, store.StatusParked, \"taskrun request failed: \"+err.Error())\n\n`store.Transition` writes through `tx.ExecContext(ctx, ...)` (internal/store/store.go:358-365), so on a cancelled context the write fails immediately and the `_ =` throws the error away. The row stays `running` with nothing left to correct it.\n\nThere are SIX such writes in runViaAgent (grant unavailable, grant failed, encode failed, request failed, decode failed, run failed). Every one is unreachable in exactly the situation it exists for -- cancellation -- because cancellation is what invalidates the context it writes with.\n\n`cleanupTerminalTaskWorktree` (daemon.go:897) has the same defect: it re-reads via `d.Store.TaskByID(ctx, ...)` and returns early on error, so a cancelled task also skips worktree cleanup.\n\n## Why the container is NOT the problem\n\n`Pool.Release` already gets this right and is the precedent for the fix: it detaches deliberately with `context.WithTimeout(context.WithoutCancel(ctx), 10*time.Second)` and documents why -- \"the most important reason a task is on its way out is that it was cancelled... Teardown is cleanup, so it gets its own deadline rather than inheriting the caller's cancellation.\" So teardown works; only state recording is broken.\n\n## Contributing factor\n\n`StoreTaskController.StopRunning` (internal/gateway/tasks.go:227) deliberately writes no terminal state, documented as \"A stopped task unwinds through its own error paths and lands wherever that leaves it, usually parked\". That assumption is now false: the unwind path cannot record anything, so nothing lands. Note `CancelChatTask` (the /cancel path) DOES write state explicitly and is unaffected.\n\n## Steps to Reproduce\n\n1. Start an autonomous task so it reaches `running` with a live archie-agent container.\n2. Issue `/stop` from chat (or Stop from the dashboard).\n3. Observe the container is stopped and removed by Pool.Release.\n4. Observe the task row is still `status = running` in the store, in `task_list`, in `/status` and on the dashboard.\n5. Wait: nothing ever corrects it. Only a daemon restart re-queues it, via the crash-recovery path that re-queues tasks left `running`.\n\n## Acceptance Criteria\n\nTerminal state writes on the cancellation path use a context that survives cancellation (`context.WithoutCancel`, with its own timeout, mirroring Pool.Release); their errors are logged rather than discarded; a stopped task reaches a terminal state observable in the store, task_list and the dashboard without a daemon restart; cleanupTerminalTaskWorktree also runs for a cancelled task; a regression test cancels a task mid-run and asserts the row is no longer `running`, and fails against the current code.\n","notes":"Timeline correction: the task was observed still 'running' roughly ONE HOUR after /stop, not a day (an earlier note said a day; that was inferred wrongly from a date rollover). An hour is if anything stronger evidence, since no plausible refresh interval covers it.\n\nChronology correction: the agent's pre-/stop task_list reading 'still marked running' is NOT evidence of this bug -- nothing had stopped the task at that point, so it was reporting correctly. The genuine evidence is (a) the row still 'running' an hour after /stop, and (b) the code path itself, which predicts exactly that and was found by reading runViaAgent rather than from the transcript.\n\nScope note: this bug explains a stale ROW only. It does not explain a still-live container, because container.Pool.Release deliberately detaches from the cancelled context and does tear down. If a container is ever found alive after /stop, that is a SEPARATE defect, not this one.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T15:22:19Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:13Z","started_at":"2026-08-24T15:31:34Z","closed_at":"2026-08-24T15:42:47Z","close_reason":"Closed","external_ref":"https://github.com/samcharles93/archie-core/issues/628","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-ite6","title":"Flush daemon task-event subscription before accepting worker events","description":"cmd/archied.subscribeAgentEvents registers a core-NATS wildcard subscription but returns before flushing the SUB frame. A task worker can publish immediately and lose its first event; TestSubscribeAgentEventsDropsUnparseableMessages exposes the race under full-suite load.","acceptance_criteria":"subscribeAgentEvents flushes the NATS connection before returning; flush failure unsubscribes the just-created subscription; a regression test proves a publisher can deliver immediately after subscription setup.","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T04:39:22Z","created_by":"Sam Catlow","updated_at":"2026-08-24T05:19:34Z","started_at":"2026-08-24T04:39:24Z","closed_at":"2026-08-24T05:19:34Z","close_reason":"Completed; reconciled with the already-closed GitHub issue.","external_ref":"https://github.com/samcharles93/archie-core/issues/616","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-q15y.3","title":"Remove legacy inprocess subprocess and single-stage agent execution","description":"The configuration and worker still expose daemon inprocess, per-stage subprocess, and single-stage NATS execution paths. Remove those production choices and keep the agent-loop runner owned only by the full-task archie-agent worker.","acceptance_criteria":"agent.mode no longer selects inprocess/subprocess/nats production behavior; cmd/archied and internal/daemon cannot construct an agent loop runner; legacy SubprocessRunner and single-stage worker paths are deleted or proven test-only; architecture tests enforce worker-only ownership.","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T03:03:38Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:58:30Z","started_at":"2026-08-24T03:49:36Z","closed_at":"2026-08-24T06:58:30Z","close_reason":"Implemented in 157e99b (refactor(agentexec): remove legacy execution paths); [agent] is decode-only. Verified: no SubprocessRunner/inprocess symbols in non-test code.","external_ref":"https://github.com/samcharles93/archie-core/issues/617","metadata":null,"dependencies":[{"issue_id":"archie-core-q15y.3","depends_on_id":"archie-core-q15y","type":"parent-child","created_at":"2026-08-24T03:03:38Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-q15y.3","depends_on_id":"archie-core-q15y.2","type":"blocks","created_at":"2026-08-24T03:03:52Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-q15y.2","title":"Use full-task NATS handoff for every autonomous workflow","description":"daemon.process currently runs workflow.Run locally unless a container pool exists, and NATS mode without containers uses per-stage requests. Make full-task taskrun request/reply the only production workflow path for both embedded and external brokers.","acceptance_criteria":"daemon.process never calls workflow.Run; every workflow task is sent once through the taskrun subject to a dedicated managed worker; task state/RPC/event behavior remains correct; regression tests fail against the old local branch.","notes":"Implemented full-task-only autonomous dispatch: archied parks before worktree access when the managed container pool or task transport is unavailable, acquires exactly one task-scoped worker, and sends exactly one full-task request. Removed daemon-local workflow execution state and persisted daemon-side park details atomically as Task.ParkReason. task check passes; scoped lint is clean; fresh adversarial re-review has zero findings.","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T03:03:37Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:58:29Z","started_at":"2026-08-24T03:32:18Z","closed_at":"2026-08-24T06:58:29Z","close_reason":"Implemented in 7d69001 (fix(daemon): require full-task worker handoff); daemon.process parks instead of running locally. Verified: no workflow.Run in internal/daemon non-test code, enforced by daemon/architecture_test.go:75.","external_ref":"https://github.com/samcharles93/archie-core/issues/618","metadata":null,"dependencies":[{"issue_id":"archie-core-q15y.2","depends_on_id":"archie-core-q15y","type":"parent-child","created_at":"2026-08-24T03:03:37Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-q15y.2","depends_on_id":"archie-core-q15y.1","type":"blocks","created_at":"2026-08-24T03:03:51Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":2,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-q15y.1","title":"Expose embedded NATS securely to managed task containers","description":"Embedded NATS currently binds unauthenticated loopback, so task containers cannot use it. Give the daemon and task containers distinct reachable URLs for the same embedded listener, require generated per-start credentials, and wire Docker host/network reachability without exposing credentials in logs or config files.","acceptance_criteria":"Native archied can connect to embedded JetStream; managed agent containers can connect to the same listener; all connections require a cryptographically generated token; the listener is not exposed on ordinary LAN interfaces; lifecycle and container environment tests pass.","notes":"Implemented authenticated embedded NATS reachability for native archied plus managed Docker workers. Embedded NATS now generates a crypto token per start, binds the resolved local Docker bridge gateway when a pool is available, and freezes URL/token into worker env. Added bridge validation, cleanup ordering, config acceptance/guardrails, Docker-create seam tests, lifecycle/auth tests, and amended the architecture decision. task check passed; focused race passed; new-code lint 0; fresh adversarial re-review 0 findings.","status":"closed","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T03:03:36Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:58:29Z","started_at":"2026-08-24T03:03:54Z","closed_at":"2026-08-24T06:58:29Z","close_reason":"Implemented in 5c4b599 (feat(nats): expose embedded broker to managed workers); per-start token, Docker bridge binding, frozen worker env. Verified landed on main.","external_ref":"https://github.com/samcharles93/archie-core/issues/619","metadata":null,"dependencies":[{"issue_id":"archie-core-q15y.1","depends_on_id":"archie-core-q15y","type":"parent-child","created_at":"2026-08-24T03:03:36Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":2,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-q15y","title":"Make NATS the sole autonomous workflow execution path","description":"Keep archied native on the host (systemd in the operator deployment) so interactive chat retains operator-authorized server access. Autonomous durable workflows must never execute their agent loop inside archied: embedded and external NATS both hand the complete task to a task-scoped archie-agent container.","design":"One execution architecture, two broker deployments. archied owns orchestration, state, forge credentials, worktree preparation, and optionally the embedded broker. A task-scoped archie-agent container owns the complete workflow and model/tool loop. Embedded NATS is authenticated and reachable only through the managed Docker host/network boundary; external NATS preserves current behavior.","acceptance_criteria":"No production configuration runs workflow.Run or agentloop in archied; embedded and external NATS use the same full-task container handoff; host-native chat authority is unchanged; installer and supported deployment profiles select the new topology.","status":"closed","priority":1,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-24T01:56:43Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:58:42Z","started_at":"2026-08-24T01:56:52Z","closed_at":"2026-08-24T06:58:42Z","close_reason":"All four children landed across 5c4b599, 7d69001, 157e99b, c978f10. Autonomous workflows now have exactly one production path: full-task core-NATS handoff to a task-scoped archie-agent container.","external_ref":"https://github.com/samcharles93/archie-core/issues/620","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-462t","title":"Fix component-aware /update installation","description":"The approved update snapshot is discarded before CommandInstaller, causing scripts/archie-update-install to build, back up, install, and rebuild both components even for gateway-only releases. Implement component-specific plans and runtime release stamping.","design":"Flow the freshly revalidated approved Snapshot into the installer contract. CommandInstaller exports explicit requested versions. The shell adapter treats those variables as the complete plan and records only affected components in rollback/report metadata.","acceptance_criteria":"Gateway-only, runtime-only, both, and no-op harness cases pass; only selected components are fetched/built/backed up/installed; image builds only for runtime with an explicit non-dev release stamp; rollback/report metadata stays correct; task check passes.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-23T15:56:26Z","created_by":"Sam Catlow","updated_at":"2026-08-23T16:18:38Z","started_at":"2026-08-23T15:56:27Z","closed_at":"2026-08-23T16:18:38Z","close_reason":"Implemented and verified in commit 881bba2; linked GitHub issue #606.","external_ref":"https://github.com/samcharles93/archie-core/issues/606","labels":["bug","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tzzn","title":"Fix Telegram tool progress and project context UX","description":"Investigate and fix Telegram tool-call rendering so progress is compact, cleaned, bounded, and failure-aware without raw schema placeholders; ensure chat/task tool context roots at the actual configured project/worktree; add regression tests for rendering, truncation/offload, context root, and failures; run gates and deploy runtime changes.","acceptance_criteria":"Telegram progress is readable and Telegram-safe; oversized tool output is bounded or offloaded; task tools use the task worktree rather than unrelated home paths; malformed shell/input failures remain visible; targeted and full checks pass.","notes":"GitHub #604 reopened after PR #605. Building integration regression at the chat-stream → Telegram Bot API seam; tool-output budget is character/result-volume only, never token based.\nPR #608 (5d45633) on fix/604-telegram-tool-output-pipeline. Waiting on live Telegram verification after deploy; do not close until Sam confirms.","status":"in_progress","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-23T15:31:31Z","created_by":"Sam Catlow","updated_at":"2026-08-23T16:40:48Z","started_at":"2026-08-23T15:31:34Z","external_ref":"gh-604","comments":[{"id":"01a02f67-ae94-7c6b-95b2-2cfc761cbffc","issue_id":"archie-core-tzzn","author":"Sam Catlow","text":"Reopened after live deployment evidence: full source files and module-cache results are still exposed, output is quoted/escaped, repeated turn-budget failures continue, searches wander outside the active project, and failed shell probes remain noisy. The bounded wrapper alone did not meet acceptance criteria.","created_at":"2026-08-23T16:15:19Z"},{"id":"01a02f68-fdc9-7186-b054-6dd9ad18c576","issue_id":"archie-core-tzzn","author":"Sam Catlow","text":"Architecture correction from Sam: turn continuation must never be token-count based. The observed 200000-char failure is the aggregate tool-result character/output-volume cap. Fix via spill/offload/summarization and suppression of repeated oversized results; do not add token-based stopping.","created_at":"2026-08-23T16:16:45Z"},{"id":"01a02f7e-fcec-7d88-a36b-29bfbf9c161c","issue_id":"archie-core-tzzn","author":"Sam Catlow","text":"PR #608 opened at 5d45633. Telegram integration regression + turn-cap removal + workspace-only discovery. task check passed. Not deployed; live Telegram confirmation still needed.","created_at":"2026-08-23T16:40:47Z"}],"dependency_count":0,"dependent_count":0,"comment_count":3}
|
||||
{"_type":"issue","id":"archie-core-1787489596754-17-3b1639d9","title":"[EPIC] Adversarial self-review before archie opens a PR","description":"Archie enforces gates on every PR it opens, but it does not run the adversarial review CLAUDE.md makes mandatory for every change in this repo: a fresh reviewer that did not write the code, told to assume every line is wrong, working a defined checklist, where a surviving finding blocks the work. It is the one discipline the project requires of its contributors and exempts itself from.\n\nWhy it matters, with evidence rather than assertion: on 2026-08-20/21 the update-verification change (PR #530) passed task check at every checkpoint -- exit 0, golangci-lint 0 issues, gofumpt clean -- and three adversarial passes still found six real defects, two of them blocking. A 'dev' version placeholder would have reported healthy updates as failures, and an 'unknown' install claim was still being worded as confirmed success. The gates were green throughout and would have stayed green. This is CLAUDE.md's own recorded lesson: tests catch behaviour that breaks, not behaviour that quietly starts meaning something else.\n\nArchie is unusually well placed to do this. It already runs each task in an isolated container and worktree, so it can spawn a reviewer that genuinely never saw the implementation -- not a second opinion from the same context pretending to be fresh, which is the failure mode of every single-context tool. The isolation boundary built for safety is what makes honest self-review possible.\n\nWhat the operator gets: a PR that arrives with a findings section -- what was checked, what was found, what was fixed, what survived. A surviving finding parks the task as waiting_human instead of opening a PR that looks ready and is not. Review shifts from hunting for bugs to adjudicating findings.\n\nThe risk that kills the feature is a reviewer that cries wolf. Findings must be adversarially confirmed before they surface, and the reviewer must be able to report zero findings on properties it checked and cleared. Calibration is the feature, not the finding count.","status":"closed","priority":1,"issue_type":"epic","created_at":"2026-08-23T12:22:20Z","updated_at":"2026-08-23T22:37:28Z","closed_at":"2026-08-23T22:37:28Z","close_reason":"Duplicate epic; canonical versions are archie-core-t2db (#541), archie-core-7d5u (#547), and archie-core-h019 (#552) with proper work breakdown","external_ref":"https://github.com/samcharles93/archie-core/issues/580","source_system":"github:https://github.com/samcharles93/archie-core/issues/580:580","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596587-15-fdd1dcbd","title":"Findings contract: a structured review result the workflow can act on","description":"The reviewer's output must be data the workflow can branch on, not prose a human has to read to find out whether the PR is safe to open. Prose is what makes a review advisory; structure is what lets a finding block.\n\nDefine the finding type in the workflow domain (the domain declares the contract it needs; it never names who implements it). At minimum a finding carries: file and line, a one-sentence defect, a concrete failure scenario (inputs/state -\u003e wrong output), a verdict distinguishing CONFIRMED from PLAUSIBLE, and a disposition once acted on (fixed / skipped / no_change_needed).\n\nThe CONFIRMED/PLAUSIBLE split is load-bearing and must not be collapsed into a single boolean: only confirmed findings may block, or the feature degrades into crying wolf and the operator learns to skim past it.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:19Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/579","source_system":"github:https://github.com/samcharles93/archie-core/issues/579:579","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596676-16-d40037d5","title":"Design: adversarial self-review stage (one-page decision in docs/prds/)","description":"No settled design exists for this in docs/architecture/, so under the scope-discipline rule merged as PR #533 the design comes first -- briefly and decisively -- and is not finished until a diff follows it.\n\nDecide and record, in one page under docs/prds/: where the reviewer runs (reuse the per-task container pool, or a separate short-lived container); what it is given (diff plus originating issue, and explicitly what it must NOT be given); the findings contract and who owns the type; what a surviving finding does to the task lifecycle; and how the reviewer's model/effort is configured.\n\nConstraints from the repo that the design must respect: dependency direction is cmd -\u003e app -\u003e {domain, infrastructure}, so the reviewer contract belongs to the workflow domain and the execution to infrastructure/app. Agent execution is a data boundary. The model never runs git. Prefer environmental enforcement over prompt rules -- 'the reviewer cannot see the implementation' must be a property of how it is launched, not an instruction in its prompt.\n\nDo not write an architecture document, migration plan or review campaign. One page that decides.","status":"closed","priority":1,"issue_type":"decision","created_at":"2026-08-23T12:22:19Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/578","source_system":"github:https://github.com/samcharles93/archie-core/issues/578:578","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596505-14-5b6c5494","title":"Wire review as an implement-workflow stage: after gates, before PR open","description":"Sequence matters. The review runs after gates pass -- there is no point reviewing code that does not build or test -- and before the PR is opened, because the point is to not spend the operator's attention on a PR that is not ready.\n\nA surviving CONFIRMED finding must not open a PR. It parks the task as waiting_human with the findings attached, which is the existing lifecycle state for 'a human needs to look at this' and needs no new state. Per CLAUDE.md, a finding that survives blocks closing the work; it does not get waved through.\n\nScope to the implement workflow first. Routing to tdd/bootstrap/feasibility is a later decision -- feasibility in particular produces a document rather than a diff, so 'review the diff' may not even apply.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:18Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/577","source_system":"github:https://github.com/samcharles93/archie-core/issues/577:577","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596341-12-bf9443bb","title":"Reviewer runs in a context that provably never saw the implementation","description":"This is the whole feature. A reviewer that shares the implementer's context is a second opinion from the same mind, and it will rationalise the same mistakes -- which is exactly the failure mode CLAUDE.md's 'never self-certified by the implementer' rule exists to prevent.\n\nArchie already has the machinery: each task runs in an isolated container against its own worktree. Launch the reviewer the same way, seeded only with the diff and the originating issue. It must not receive the implementer's conversation, its notes, its reasoning, or its own claims about what it did.\n\nPer 'environmental enforcement over prompt rules', isolation must be a property of construction, not a sentence in the prompt. The agent cannot talk its way out of a context it was never given. Assert it in a test rather than assuming it: a test that would fail if implementer context were threaded through.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:17Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/576","source_system":"github:https://github.com/samcharles93/archie-core/issues/576:576","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596426-13-e24a2c83","title":"[EPIC] Event sources and typed reactions: archie as an extensible platform","description":"Goal: let archie react to things happening -- forge activity, inbound callers, schedules -- and let extensions hook those reactions, without a generic untyped event bus.\n\nTwo findings shape this, both verified in the tree on 2026-08-21.\n\n1. ARCHIE HAS TWO EVENT NEEDS AND ONE BUS. internal/events is documented as 'archied's in-process observability stream' with 'bounded per-subscriber buffers that DROP on overflow, so a stalled dashboard connection can never apply backpressure to the task engine'. Publish is fire-and-forget; subscribers get a read-only channel and cannot influence anything. Correct for the dashboard, wrong for reactions: a hook that silently misses events under load and cannot affect an outcome is worse than no hook, because it looks like it ran. Reactions need at-least-once delivery and the ability to change what happens. Do not bolt reactions onto events.Bus.\n\n2. THE OBVIOUS DESIGN IS PROHIBITED, DELIBERATELY. The tau model this is drawn from dispatches generically: DispatchEvent(ctx, eventName string, sessionID, ...) to out-of-process gRPC plugins. archie's approved foundation (docs/architecture/plugins-and-extensions.md) forbids that shape -- the generic plugin contract stays metadata-only and MUST NOT expose untyped hooks. plugin.Plugin is Name()/Version() only, enforced by internal/plugin/architecture_test.go and by the plugin engine rule in ARCHITECTURE.md. tau already carries the scar the rule avoids: TestUnload_DoesNotWaitForInFlightDispatch exists because a stuck plugin blocked plugin unload.\n\nThe reconciliation, and why this is an epic rather than a feature: separate INBOUND (callers push work in -- forge webhook, chat webhook, cron, channel) from REACTION (extensions respond to something that happened). Inbound becomes a typed source/intake capability family with an owning registry. Reactions become typed capability families owned by the domain whose semantics they affect. 'Webhooks aligned to types of callers' is exactly the typed-family model applied to intake: the instinct is right, the generic bus is what has to go.\n\nNear-term payoff: archie reacts to an issue being labelled the moment it happens, instead of up to poll_interval later.","status":"closed","priority":1,"issue_type":"epic","created_at":"2026-08-23T12:22:17Z","updated_at":"2026-08-23T22:37:28Z","closed_at":"2026-08-23T22:37:28Z","close_reason":"Duplicate epic; canonical versions are archie-core-t2db (#541), archie-core-7d5u (#547), and archie-core-h019 (#552) with proper work breakdown","external_ref":"https://github.com/samcharles93/archie-core/issues/575","source_system":"github:https://github.com/samcharles93/archie-core/issues/575:575","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596259-11-317f7079","title":"Shared webhook mechanics: HMAC verification, per-source rate limiting, payload redaction","description":"NARROWED 2026-08-22 from this bead's prior scope, which bundled capture-storage and an approval state machine into a single 'shared mechanics' package. On reflection those are not genuinely shared yet:\n\n- Capture STORAGE is t2db.1's job -- it depends on the NATS-vs-SQLite decision 7d5u.2 owns, and building a storage engine here would either duplicate or contradict that. This package may be USED by t2db.1's capture path, but does not own persistence.\n- The draft/pending_approval/armed state machine belongs to the entity that has that state -- t2db.4's binding -- not a generic package. There is exactly one consumer (bindings) today; per 'extract into a shared primitive on the second real consumer, never in anticipation of one,' building it here now would be speculative.\n\nWhat remains, and is genuinely storage-agnostic and reusable by any inbound HTTP source regardless of what consumes it:\n\n1. HMAC-SHA256 verification -- generalize internal/channels/webhook/webhook.go's existing unexported validateHMAC into an exported function here, and have that package call into it instead of keeping its own copy. One implementation of signature checking, not two that can drift.\n2. Per-source rate limiting -- a token bucket keyed by source ID (not global), so one noisy sender cannot exhaust another's budget. Limit-exceeded is an observable rejection, not a silent drop, per t2db.5's decision.\n3. Payload redaction -- generalize internal/gateway/stream.go's unexported sensitiveParameterKey/redactToolParameters heuristic (matches token/secret/password/passwd/api_key/apikey/authorization/credential/cookie/private_key against normalized JSON keys) into a reusable, storage-agnostic transform any capture path can apply before persisting.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:16Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/574","source_system":"github:https://github.com/samcharles93/archie-core/issues/574:574","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596182-10-d1e59e32","title":"Reaction delivery via embedded NATS, no external server required","description":"Reactions need at-least-once delivery distinct from the lossy events.Bus (see epic description). The delivery mechanism is NATS -- that part is settled, not a design question. What's open is deployment shape.\n\nVERIFIED 2026-08-22: config.NATSConfig.URL empty currently means 'no NATS, use SQLite ClaimNext' (internal/config/config.go:573-582). That fallback was designed for task distribution working without a broker at all. It was never meant to generalise to 'archie has no NATS' as a permanent architectural stance -- the intended second deployment shape alongside an external NATS server was always NATS EMBEDDED (in-process), not a different eventbus.\n\ngithub.com/nats-io/nats-server/v2 is already a direct dependency and is proven to work in this codebase: internal/infrastructure/agenttransport/nats/transport_test.go and others already start a real embedded server via nats-server/v2/test for tests. It has just never been wired into production startup -- cmd/archied only knows 'external URL configured' vs 'fall back to SQLite'. No new library, no new bus, no architectural gap to design around: this is 'wire the dependency we already have and already test against into the daemon's own startup path.'\n\nDesign questions that remain, now correctly scoped: does an embedded NATS instance replace the SQLite fallback outright for single-process deployments, or run alongside it; what config controls embedded vs external vs disabled; does the daemon own the embedded server's lifecycle the same way it owns everything else (start/stop paired with daemon start/stop, per the shutdown-ordering rules in ARCHITECTURE.md).","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:15Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/573","source_system":"github:https://github.com/samcharles93/archie-core/issues/573:573","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596025-8-afa6f721","title":"Design: event sources, reaction delivery, and how extensions hook them","description":"No settled design covers this. docs/architecture/plugins-and-extensions.md settles the PLUGIN FRAMEWORK (metadata-only contract, typed capability families, owning registries) but says nothing about event sources, reaction delivery, or intake. Under the scope-discipline rule merged as PR #533, that means design first -- one page, decisive -- then a diff.\n\nDecide and record in docs/prds/:\n\n1. THE HEADLINE QUESTION, which changes everything downstream: do extensions react in-process through typed capability families (what the approved rule mandates), or out-of-process like tau's generic DispatchEvent? If out-of-process generic dispatch is genuinely wanted, docs/architecture/plugins-and-extensions.md is an APPROVED document and must be amended first -- CLAUDE.md's organisation rule is explicit that you change the doc before the rule it states. Do not quietly work around it.\n\n2. Reaction delivery. events.Bus drops on overflow by design and must stay that way for the dashboard. Decide whether reactions get a second in-process bus with at-least-once delivery, or ride the existing NATS eventbus (internal/infrastructure/eventbus), which already has durable semantics and the work-queue traps documented in CLAUDE.md.\n\n3. Whether a reaction may INFLUENCE an outcome (veto, mutate, add work) or only observe. This is the difference between a hook and a subscriber, and it determines whether ordering and failure semantics matter. If a reaction can block, decide what a slow or crashed extension does -- tau's answer was a dispatch timeout, and it still deadlocked unload once.\n\n4. The typed source/intake family: its interface, its owning registry, and how a source declares what it produces.\n\nRespect dependency direction: cmd -\u003e app -\u003e {domain, infrastructure}. A domain declares the contract; app wires implementations. Cross-cutting packages may be imported by any layer and import none.","status":"closed","priority":1,"issue_type":"decision","created_at":"2026-08-23T12:22:14Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/572","source_system":"github:https://github.com/samcharles93/archie-core/issues/572:572","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596102-9-3ec24fcd","title":"Idempotency and poll/webhook parity: never double-dispatch, never lose work","description":"Webhooks deliver at-least-once, out of order, and sometimes not at all. Polling is the opposite: slow but eventually consistent. Running both (intake='both') is the honest production configuration, and it is also where the two failure modes meet.\n\nTwo things must hold. A single issue event must not start two tasks because the webhook and the next poll both saw it. And a webhook outage must not silently stop work -- if the receiver is wedged or the ingress is down, polling has to pick the work up, which is the entire argument for keeping it.\n\nNote archie-core-...-286 (WebhookAdapter: idempotency cache) already exists for the chat adapter. Decide whether that mechanism generalises to intake or whether forge dispatch needs its own key; do not build a second one by accident.\n\nThe silent-failure shape to design against is the one this codebase keeps hitting: a path that looks like it is working because nothing errors. A webhook receiver that has silently stopped delivering looks identical to a repo with no activity.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:14Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/571","source_system":"github:https://github.com/samcharles93/archie-core/issues/571:571","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489595942-7-3ec33776","title":"GitHub forge webhook receiver behind a feature flag","description":"The concrete autonomy win: react to an issue being assigned or labelled the moment it happens, instead of up to poll_interval (default 60s) later.\n\nVerified absent on 2026-08-21: internal/forge/ and internal/daemon/ contain zero webhook references, and no bead tracked forge-event intake before this epic. internal/channels/webhook exists but is a CHAT channel -- it routes inbound text through gateway.Router for LLM processing, a peer of Telegram and email. It is not forge intake and should not be bent into it.\n\nShip as a source in the typed intake family, off by default: [forge] intake = 'poll' (default) | 'webhook' | 'both'. Verify GitHub's HMAC signature. Reuse the label/assignee dispatch predicate the poller already uses -- do NOT reimplement it, since it just took a fix (3209a1f, refusing to poll on an empty label match) and two implementations will drift.\n\nDeployment reality from CLAUDE.md: archied may run on a host, in a container, or behind no public ingress at all. A webhook receiver that assumes a reachable public URL will not fit every profile, which is exactly why polling has to remain a first-class option rather than a legacy fallback.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:13Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/570","source_system":"github:https://github.com/samcharles93/archie-core/issues/570:570","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489595853-6-50e11603","title":"[EPIC] Event capture and no-code playbooks: turn any inbound webhook into an agentic workflow","description":"The pitch, in the operator's words: point any app's outgoing webhook at archie, open archie, SEE the event that just arrived with its real payload, map the fields you care about, bind them to an agentic workflow, save. No code change, no redeploy, no restart. Adding a new integration stops being a development task.\n\nWhy this is different from n8n or Power Automate rather than a copy of them: their terminal node is a deterministic connector. Archie's is an AGENT with a repo, a worktree, tools and a gate. 'When Sentry reports a new issue in this project, open a PR that fixes it' is one binding here and an entire product elsewhere.\n\nThe design insight that makes it buildable: you cannot write a payload mapper against a payload you have not seen. Schema-by-example requires real recent events to map against, which means archie must CAPTURE events it does not yet understand -- including ones with no binding at all -- and retain them long enough to design against. That is also the strongest argument for putting inbound events on NATS JetStream rather than the lossy in-process bus: durable, replayable, retention-bounded, and already deployed. The capture requirement and the transport choice are the same decision.\n\nSequence: capture unrecognised events -\u003e inspect real payloads in the UI -\u003e map fields by example -\u003e bind matcher+mapping to a workflow -\u003e the next matching event runs it.\n\nThis is a public, unauthenticated-by-default intake surface whose output is an agent with tool access. Security is not a later hardening pass; it is a first-class child of this epic.","status":"closed","priority":1,"issue_type":"epic","created_at":"2026-08-23T12:22:12Z","updated_at":"2026-08-23T22:37:28Z","closed_at":"2026-08-23T22:37:28Z","close_reason":"Duplicate epic; canonical versions are archie-core-t2db (#541), archie-core-7d5u (#547), and archie-core-h019 (#552) with proper work breakdown","external_ref":"https://github.com/samcharles93/archie-core/issues/569","source_system":"github:https://github.com/samcharles93/archie-core/issues/569:569","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489595684-4-92ed3d8c","title":"Map payload fields by example, from a real captured event","description":"Pick a captured event, click through its payload, and bind JSON paths to named fields the workflow will receive. Schema by example, not schema by specification.\n\nThe hard part is not the happy path, it is drift. A mapping authored against one payload will eventually meet a payload where the path is missing, null, or a different type -- the sending app shipped a change nobody told you about. That must fail LOUDLY and land somewhere the operator sees, not silently pass an empty string into an agent prompt. An agent handed a blank field will confabulate around it, which turns a schema change into an agent doing confident nonsense in a repo.\n\nSupport a preview: given this mapping and this captured event, show exactly what the workflow would receive. Never ship a mapping the operator has not seen resolve against real data.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:11Z","updated_at":"2026-08-24T06:58:50Z","closed_at":"2026-08-24T06:58:50Z","external_ref":"https://github.com/samcharles93/archie-core/issues/568","source_system":"github:https://github.com/samcharles93/archie-core/issues/568:568","metadata":null,"dependencies":[{"issue_id":"archie-core-1787489595684-4-92ed3d8c","depends_on_id":"archie-core-t2db.3","type":"supersedes","created_at":"2026-08-24T06:58:50Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489595777-5-bc238550","title":"Event inspector: see real inbound payloads in the dashboard","description":"The operator-facing half of capture. A live view of recent inbound events: source, arrival time, and the actual payload, pretty-printed and explorable.\n\nThis is the screen that makes the feature feel like magic: you hit 'send test webhook' in the other app, alt-tab to archie, and the event is sitting there. Latency from arrival to visible matters more than it looks -- it is the difference between a design loop and a guessing game.\n\nShow unbound events prominently. An event nothing is listening to is not noise here, it is the queue of integrations waiting to be built.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:11Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/567","source_system":"github:https://github.com/samcharles93/archie-core/issues/567:567","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489595596-3-e2c56185","title":"Capture inbound events archie does not yet understand","description":"The precondition for everything else. Today an unrecognised inbound request is rejected; for schema-by-example it must be RECORDED, because you cannot map a payload you have never seen.\n\nAccept, store and retain inbound events with no binding: raw body, headers, source, arrival time, and the identity that sent it. Retention must be bounded -- an open capture endpoint is an unbounded disk write, and this is exactly the kind of surface an attacker fills.\n\nStrong argument for NATS JetStream as the store rather than the in-process events.Bus: durable, replayable, retention-bounded natively, already deployed. Note the constraint though -- internal/infrastructure/eventbus/nats/doc.go states 'when no NATS URL is configured the daemon uses its local SQLite claim flow instead; nothing here is required for single-process operation'. NATS is currently OPTIONAL. Decide deliberately whether capture requires it (making this feature unavailable in single-process deployments) or degrades to SQLite, and record which -- do not let it become a hard dependency by accident.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:10Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/566","source_system":"github:https://github.com/samcharles93/archie-core/issues/566:566","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489595508-2-98c4b849","title":"Playbook binding: matcher + mapping + workflow, editable at runtime","description":"The object that ties it together. A binding is: a matcher (which inbound events does this apply to), a mapping (which fields the workflow receives), and a target agentic workflow.\n\nRuntime-editable is the whole point -- creating or changing a binding must not require a redeploy or a daemon restart. That has real consequences the design must face:\n\n- Bindings are persisted state, not config. They live in the store, not config.toml, because operators create them from the UI while the daemon runs.\n- They need versioning. A binding that starts a task should record WHICH version ran, or a later edit makes historical task provenance a lie.\n- Matcher ambiguity needs a defined resolution: two bindings matching one event either both run, or the more specific wins, or it is an error. Pick one and say so.\n- A binding referencing a workflow that no longer exists must fail visibly at bind time, not at 3am when the event arrives.","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-23T12:22:09Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/565","source_system":"github:https://github.com/samcharles93/archie-core/issues/565:565","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.3","title":"Clean abandoned untracked files on retry","description":"Prepare refresh hard-resets tracked files but retains untracked files; CommitAll later stages and publishes them during the next attempt.","acceptance_criteria":"A regression test proves an untracked file left by an interrupted attempt is absent after retry and cannot appear in ChangedFiles or the next commit; deliberate .git control files remain intact.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:44Z","created_by":"Sam Catlow","updated_at":"2026-08-24T03:11:49Z","started_at":"2026-08-22T11:47:47Z","closed_at":"2026-08-24T03:11:49Z","close_reason":"Retry cleaning was implemented in 0522fb7 (reset + cleanUntracked, covered by TestPrepareRecoversFromADirtyWorktreeOnRetry). Remaining defect fixed in 037ee7c: SkipDir on a .git gitdir *file* aborted the whole walk, so cleaning silently no-opped for linked/adopted worktrees. Regression test TestCleanUntrackedHandlesGitdirFile.","external_ref":"https://github.com/samcharles93/archie-core/issues/591","metadata":null,"dependencies":[{"issue_id":"archie-core-1ysw.3","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:44Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.2","title":"Make worktree directory keys collision-free","description":"Manager.Dir flattens owner and repo with a hyphen, so distinct repositories such as a-b/c and a/b-c share a task directory for equal issue numbers.","acceptance_criteria":"Distinct owner/repo tuples always map to distinct contained paths; sequential and concurrent collision regressions cannot reuse, delete, reset, or push the other repository's clone.","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:43Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:59:58Z","started_at":"2026-08-22T11:44:35Z","closed_at":"2026-08-24T06:59:58Z","close_reason":"Fixed on main: Manager.Dir base64url-encodes owner and repo as separate path components (worktree.go:66-70), so a-b/c and a/b-c no longer collide. legacyDir+migrateLegacy migrate old flattened dirs only on exact origin match. Package tests pass.","external_ref":"https://github.com/samcharles93/archie-core/issues/592","metadata":null,"dependencies":[{"issue_id":"archie-core-1ysw.2","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:43Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.4","title":"Playbook binding: matcher + mapping + workflow, editable at runtime","description":"The object that ties it together. A binding is: a matcher (which inbound events does this apply to), a mapping (which fields the workflow receives), and a target agentic workflow.\n\nRuntime-editable is the whole point -- creating or changing a binding must not require a redeploy or a daemon restart. That has real consequences the design must face:\n\n- Bindings are persisted state, not config. They live in the store, not config.toml, because operators create them from the UI while the daemon runs.\n- They need versioning. A binding that starts a task should record WHICH version ran, or a later edit makes historical task provenance a lie.\n- Matcher ambiguity needs a defined resolution: two bindings matching one event either both run, or the more specific wins, or it is an error. Pick one and say so.\n- A binding referencing a workflow that no longer exists must fail visibly at bind time, not at 3am when the event arrives.","acceptance_criteria":"A binding can be created, edited and disabled from the UI while the daemon runs; a task records the binding version that started it; overlapping matchers resolve by a defined and documented rule; a binding naming a missing workflow is rejected when saved.","notes":"2026-08-22: the draft -\u003e pending_approval -\u003e armed state machine from t2db.5's decision belongs to the binding entity this bead defines, not to a shared package -- 7d5u.3 was narrowed to exclude it since there is exactly one consumer today. Implement the state transitions here.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:45:45Z","created_by":"Sam Catlow","updated_at":"2026-09-02T13:09:38Z","started_at":"2026-09-02T12:22:48Z","closed_at":"2026-09-02T13:09:38Z","close_reason":"Closed","external_ref":"https://github.com/samcharles93/archie-core/issues/537","dependencies":[{"issue_id":"archie-core-t2db.4","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-08-21T23:45:45Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.4","depends_on_id":"archie-core-t2db.3","type":"blocks","created_at":"2026-08-21T23:45:53Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.4","depends_on_id":"archie-core-t2db.5","type":"blocks","created_at":"2026-08-21T23:45:53Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.1","title":"Capture inbound events archie does not yet understand","description":"The precondition for everything else. Today an unrecognised inbound request is rejected; for schema-by-example it must be RECORDED, because you cannot map a payload you have never seen.\n\nAccept, store and retain inbound events with no binding: raw body, headers, source, arrival time, and the identity that sent it. Retention must be bounded -- an open capture endpoint is an unbounded disk write, and this is exactly the kind of surface an attacker fills.\n\nStrong argument for NATS JetStream as the store rather than the in-process events.Bus: durable, replayable, retention-bounded natively, already deployed. Note the constraint though -- internal/infrastructure/eventbus/nats/doc.go states 'when no NATS URL is configured the daemon uses its local SQLite claim flow instead; nothing here is required for single-process operation'. NATS is currently OPTIONAL. Decide deliberately whether capture requires it (making this feature unavailable in single-process deployments) or degrades to SQLite, and record which -- do not let it become a hard dependency by accident.","acceptance_criteria":"An unbound webhook POST is captured and visible rather than rejected; capture is retention-bounded with a documented limit; the single-process (no NATS) behaviour is a deliberate, recorded decision; capture cannot exhaust disk.","notes":"2026-08-22: capture-storage ownership confirmed here (not in 7d5u.3, which was narrowed to storage-agnostic HMAC/rate-limit/redaction mechanics only). This bead's capture path should call webhookguard's redaction before persisting and its rate limiter at the HTTP boundary, but owns its own storage engine and the NATS-vs-SQLite decision.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:45:18Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:03Z","started_at":"2026-08-21T16:18:24Z","closed_at":"2026-08-21T18:51:09Z","close_reason":"Built capture storage + endpoint: docs/prds/event-capture-storage.md decides SQLite over NATS JetStream (NATS not unconditionally available pre-7d5u.2, capture's single-writer/single-reader access pattern doesn't need JetStream fan-out/replay). internal/store/captures.go adds captured_events table + InsertCapture (prune-on-write by retention age and row count) + ListCaptures. internal/webui/api_capture.go adds POST /webhooks/capture/{source}, unauthenticated (bypasses requireToken like /healthz), applying webhookguard redaction before persisting and a per-remote-address rate limit + hard body-size cap before that. New [capture] config section with documented defaults. Adversarial self-review (the usual fresh subagent pass hit a session API limit mid-run, so this was a manual re-read with the same checklist) caught and fixed three real bugs before landing: (1) body-size cap silently unenforced when unset -- added a hardcoded fallback floor since it's the only bound on a SINGLE payload's size; (2) rate limiter was keyed by the request's own unregistered source path segment, violating webhookguard.RateLimiter's documented bounded-key-space assumption -- an attacker could rotate the segment to bypass the limit and grow the bucket map unbounded; rekeyed to remote address; (3) retention prune used time.RFC3339Nano, whose variable-width trimmed fractional seconds break lexicographic string comparison in `WHERE received_at \u003c ?` (an exact-second timestamp can sort after a later fractional one) -- switched to fixed-width RFC3339. All three have regression tests verified to fail against the pre-fix code. task check clean, golangci-lint zero new findings repo-wide.","external_ref":"https://github.com/samcharles93/archie-core/issues/538","dependencies":[{"issue_id":"archie-core-t2db.1","depends_on_id":"archie-core-7d5u.4","type":"relates-to","created_at":"2026-08-22T01:01:02Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.1","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-08-21T23:45:17Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":2,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.2","title":"Event inspector: see real inbound payloads in the dashboard","description":"The operator-facing half of capture. A live view of recent inbound events: source, arrival time, and the actual payload, pretty-printed and explorable.\n\nThis is the screen that makes the feature feel like magic: you hit 'send test webhook' in the other app, alt-tab to archie, and the event is sitting there. Latency from arrival to visible matters more than it looks -- it is the difference between a design loop and a guessing game.\n\nShow unbound events prominently. An event nothing is listening to is not noise here, it is the queue of integrations waiting to be built.","acceptance_criteria":"Recent inbound events are listed with source, time and full payload; unbound events are distinguishable from bound ones; a newly arrived event appears without a manual refresh; payloads are explorable rather than a wall of text.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:45:18Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:04Z","started_at":"2026-08-21T18:57:52Z","closed_at":"2026-08-21T19:17:03Z","close_reason":"GET /api/captures (token-gated, memory/skills-style enabled:false-not-an-error when Captures is nil) plus a new /captures dashboard page: recent captures newest-first, expandable per-row to explore redacted payload/headers pretty-printed. Live updates reuse the existing operator-activity event pipeline (Server.emit -\u003e Events.Publish -\u003e the /events SSE stream) as an invalidation signal, refetching the list rather than merging partial event data. Every row shows an 'Unbound' pill today since no binding model exists yet (t2db.4 wires the real distinction). Frontend follows the tasks/task-row.js precedent: row rendering split into capture-row.js for unit testing without the page's fetch/SSE wiring. Adversarial review (fresh subagent, full pass) found one real severe bug before merge: the live SSE event was embedding the full (up to 256KiB) redacted body/headers into the events table, which has no retention/row-count prune anywhere in the codebase -- silently defeating t2db.1's disk-bound guarantee for an unauthenticated, only-rate-limited endpoint. Fixed: the live event now carries just {id, source} as a pure invalidation signal; the dashboard refetches the authoritative list. Two smaller findings (untested Data[\"id\"] field the frontend's dedup depended on; a received_at precision mismatch between live and REST-fetched copies) were resolved as a side effect of that fix. task check clean, golangci-lint zero new findings.","external_ref":"https://github.com/samcharles93/archie-core/issues/539","dependencies":[{"issue_id":"archie-core-t2db.2","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-08-21T23:45:17Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.2","depends_on_id":"archie-core-t2db.1","type":"blocks","created_at":"2026-08-21T23:45:53Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.3","title":"Map payload fields by example, from a real captured event","description":"Pick a captured event, click through its payload, and bind JSON paths to named fields the workflow will receive. Schema by example, not schema by specification.\n\nThe hard part is not the happy path, it is drift. A mapping authored against one payload will eventually meet a payload where the path is missing, null, or a different type -- the sending app shipped a change nobody told you about. That must fail LOUDLY and land somewhere the operator sees, not silently pass an empty string into an agent prompt. An agent handed a blank field will confabulate around it, which turns a schema change into an agent doing confident nonsense in a repo.\n\nSupport a preview: given this mapping and this captured event, show exactly what the workflow would receive. Never ship a mapping the operator has not seen resolve against real data.","acceptance_criteria":"Fields are mappable from a captured payload without writing code; a mapping preview resolves against a real event before saving; a missing, null or type-changed path at runtime produces a visible failure rather than an empty value; the failure names the path and the event.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:45:18Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:05Z","started_at":"2026-08-22T08:39:40Z","closed_at":"2026-08-22T09:01:53Z","close_reason":"Payload field mapping: domain (internal/domain/mapping), SQLite store (internal/store/mappings.go), HTTP API (internal/webui/api_mapping.go), and dashboard editor (ui/src/mappings) shipped. PRD at docs/prds/payload-field-mapping.md. task check green; adversarial review found 4 issues (stale preview after rename, duplicate field names, hardcoded capture scan window, malformed path silently reinterpreted), all fixed and re-verified.","external_ref":"https://github.com/samcharles93/archie-core/issues/540","dependencies":[{"issue_id":"archie-core-t2db.3","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-08-21T23:45:18Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.3","depends_on_id":"archie-core-t2db.1","type":"blocks","created_at":"2026-08-21T23:45:53Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db","title":"[EPIC] Event capture and no-code playbooks: turn any inbound webhook into an agentic workflow","description":"The pitch, in the operator's words: point any app's outgoing webhook at archie, open archie, SEE the event that just arrived with its real payload, map the fields you care about, bind them to an agentic workflow, save. No code change, no redeploy, no restart. Adding a new integration stops being a development task.\n\nWhy this is different from n8n or Power Automate rather than a copy of them: their terminal node is a deterministic connector. Archie's is an AGENT with a repo, a worktree, tools and a gate. 'When Sentry reports a new issue in this project, open a PR that fixes it' is one binding here and an entire product elsewhere.\n\nThe design insight that makes it buildable: you cannot write a payload mapper against a payload you have not seen. Schema-by-example requires real recent events to map against, which means archie must CAPTURE events it does not yet understand -- including ones with no binding at all -- and retain them long enough to design against. That is also the strongest argument for putting inbound events on NATS JetStream rather than the lossy in-process bus: durable, replayable, retention-bounded, and already deployed. The capture requirement and the transport choice are the same decision.\n\nSequence: capture unrecognised events -\u003e inspect real payloads in the UI -\u003e map fields by example -\u003e bind matcher+mapping to a workflow -\u003e the next matching event runs it.\n\nThis is a public, unauthenticated-by-default intake surface whose output is an agent with tool access. Security is not a later hardening pass; it is a first-class child of this epic.","acceptance_criteria":"An operator can point a new external webhook at archie, see its payload in the UI without writing code, map fields, bind it to a workflow, and have the next matching event run that workflow -- with no redeploy and no daemon restart. A binding cannot go live without explicit human approval.","status":"open","priority":1,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-21T13:44:56Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:06Z","external_ref":"https://github.com/samcharles93/archie-core/issues/541","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-7d5u.4","title":"GitHub forge webhook receiver behind a feature flag","description":"The concrete autonomy win: react to an issue being assigned or labelled the moment it happens, instead of up to poll_interval (default 60s) later.\n\nVerified absent on 2026-08-21: internal/forge/ and internal/daemon/ contain zero webhook references, and no bead tracked forge-event intake before this epic. internal/channels/webhook exists but is a CHAT channel -- it routes inbound text through gateway.Router for LLM processing, a peer of Telegram and email. It is not forge intake and should not be bent into it.\n\nShip as a source in the typed intake family, off by default: [forge] intake = 'poll' (default) | 'webhook' | 'both'. Verify GitHub's HMAC signature. Reuse the label/assignee dispatch predicate the poller already uses -- do NOT reimplement it, since it just took a fix (3209a1f, refusing to poll on an empty label match) and two implementations will drift.\n\nDeployment reality from CLAUDE.md: archied may run on a host, in a container, or behind no public ingress at all. A webhook receiver that assumes a reachable public URL will not fit every profile, which is exactly why polling has to remain a first-class option rather than a legacy fallback.","acceptance_criteria":"With intake='webhook', a labelled issue starts a task without waiting for the poll interval; an invalid HMAC is rejected and logged; intake='poll' behaves exactly as today; the dispatch predicate is shared with the poller, not duplicated; the flag defaults to poll.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:26:52Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:07Z","started_at":"2026-08-22T08:43:35Z","closed_at":"2026-08-22T09:21:16Z","close_reason":"GitHub webhook receiver shipped: [forge] intake=poll|webhook|both, shared MatchesDispatch predicate (case-insensitive assignee, case-sensitive label) consumed by poller and receiver, HMAC-verified, publishes via shared PublishTask. Adversarial self-review found and fixed 3 real defects (boot-crashing secret-resolve hard-fail under intake=both, assignee case-sensitivity mismatch vs GitHub's own filter, silent multi-identity misdispatch) before landing. task check + lint clean. Committed 41e43dc.","external_ref":"https://github.com/samcharles93/archie-core/issues/542","dependencies":[{"issue_id":"archie-core-7d5u.4","depends_on_id":"archie-core-7d5u","type":"parent-child","created_at":"2026-08-21T23:26:51Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.4","depends_on_id":"archie-core-7d5u.1","type":"blocks","created_at":"2026-08-21T23:26:58Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.4","depends_on_id":"archie-core-7d5u.3","type":"blocks","created_at":"2026-08-21T23:26:58Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.4","depends_on_id":"archie-core-t2db.1","type":"relates-to","created_at":"2026-08-22T01:01:02Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":2,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-7d5u.5","title":"Idempotency and poll/webhook parity: never double-dispatch, never lose work","description":"Webhooks deliver at-least-once, out of order, and sometimes not at all. Polling is the opposite: slow but eventually consistent. Running both (intake='both') is the honest production configuration, and it is also where the two failure modes meet.\n\nTwo things must hold. A single issue event must not start two tasks because the webhook and the next poll both saw it. And a webhook outage must not silently stop work -- if the receiver is wedged or the ingress is down, polling has to pick the work up, which is the entire argument for keeping it.\n\nNote archie-core-...-286 (WebhookAdapter: idempotency cache) already exists for the chat adapter. Decide whether that mechanism generalises to intake or whether forge dispatch needs its own key; do not build a second one by accident.\n\nThe silent-failure shape to design against is the one this codebase keeps hitting: a path that looks like it is working because nothing errors. A webhook receiver that has silently stopped delivering looks identical to a repo with no activity.","acceptance_criteria":"A duplicate delivery of the same forge event starts exactly one task; with intake='both', disabling the webhook path still results in the work being picked up by polling; a wedged or non-delivering webhook receiver is observable rather than indistinguishable from an idle repo.","status":"closed","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-21T13:26:52Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:06Z","started_at":"2026-08-22T09:30:20Z","closed_at":"2026-08-24T07:12:06Z","close_reason":"Investigated first: the dedup mechanism (TaskEnvelope.IdempotencyKey + PublishUnique + JetStream Nats-Msg-Id dedup) and the shared dispatch predicate were already fully wired by 7d5u.4 -- no double-dispatch code change was needed. Closed the two real gaps: (1) internal/infrastructure/eventbus/nats/dedup_test.go is a new regression test proving PublishUnique actually suppresses a duplicate publish on the same WorkQueuePolicy stream ARCHIE_TASKS uses in production; (2) internal/forge/webhook/receiver.go gained Status()/GET support tracking authenticated deliveries vs successful publishes separately, so a wedged or non-delivering receiver is observable rather than indistinguishable from an idle repo. AC's poll/webhook parity clause (disabling webhook still polls) is satisfied architecturally with no code change possible to violate it -- verified Cycle()/Run() never reference cfg.Forge.Intake anywhere in internal/daemon; only setupForgeWebhook in cmd/archied/bootstrap.go gates the webhook HTTP server. Adversarial review pass (fresh subagent, -race) found zero blocking issues; closed two minor coverage gaps it flagged. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/543","metadata":null,"dependencies":[{"issue_id":"archie-core-7d5u.5","depends_on_id":"archie-core-1786637497328-286-9c985f28","type":"relates-to","created_at":"2026-08-21T23:27:06Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.5","depends_on_id":"archie-core-7d5u","type":"parent-child","created_at":"2026-08-21T23:26:51Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.5","depends_on_id":"archie-core-7d5u.1","type":"blocks","created_at":"2026-08-21T23:26:58Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.5","depends_on_id":"archie-core-7d5u.4","type":"blocks","created_at":"2026-08-21T23:26:58Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-7d5u.1","title":"Design: event sources, reaction delivery, and how extensions hook them","description":"No settled design covers this. docs/architecture/plugins-and-extensions.md settles the PLUGIN FRAMEWORK (metadata-only contract, typed capability families, owning registries) but says nothing about event sources, reaction delivery, or intake. Under the scope-discipline rule merged as PR #533, that means design first -- one page, decisive -- then a diff.\n\nDecide and record in docs/prds/:\n\n1. THE HEADLINE QUESTION, which changes everything downstream: do extensions react in-process through typed capability families (what the approved rule mandates), or out-of-process like tau's generic DispatchEvent? If out-of-process generic dispatch is genuinely wanted, docs/architecture/plugins-and-extensions.md is an APPROVED document and must be amended first -- CLAUDE.md's organisation rule is explicit that you change the doc before the rule it states. Do not quietly work around it.\n\n2. Reaction delivery. events.Bus drops on overflow by design and must stay that way for the dashboard. Decide whether reactions get a second in-process bus with at-least-once delivery, or ride the existing NATS eventbus (internal/infrastructure/eventbus), which already has durable semantics and the work-queue traps documented in CLAUDE.md.\n\n3. Whether a reaction may INFLUENCE an outcome (veto, mutate, add work) or only observe. This is the difference between a hook and a subscriber, and it determines whether ordering and failure semantics matter. If a reaction can block, decide what a slow or crashed extension does -- tau's answer was a dispatch timeout, and it still deadlocked unload once.\n\n4. The typed source/intake family: its interface, its owning registry, and how a source declares what it produces.\n\nRespect dependency direction: cmd -\u003e app -\u003e {domain, infrastructure}. A domain declares the contract; app wires implementations. Cross-cutting packages may be imported by any layer and import none.","acceptance_criteria":"A one-page decision in docs/prds/ answering all four questions, naming the packages it will touch, and stating explicitly whether plugins-and-extensions.md needs amending. It decides rather than surveys.","notes":"CORRECTION 2026-08-22 (second): decision question 2 in this bead's description asked whether reactions get a second in-process bus or ride the existing NATS eventbus. That framing is wrong -- there is no 'or'. NATS is the settled transport; the only open axis is external-server vs embedded, not NATS vs something else. Do not design a second bus. See archie-core-7d5u and archie-core-7d5u.2 for the corrected framing and the verified state of github.com/nats-io/nats-server/v2 as an already-present, test-proven, production-unwired dependency.","status":"closed","priority":1,"issue_type":"decision","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:26:26Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:09Z","started_at":"2026-08-21T14:56:21Z","closed_at":"2026-08-21T15:00:55Z","close_reason":"Decided and documented in docs/prds/event-sources-and-reactions.md, satisfying this bead's own acceptance criterion (a one-page decision naming the packages it touches and stating whether plugins-and-extensions.md needs amending -- it does not).\n\nAnswers: (1) in-process typed families, no out-of-process dispatch -- archie has no existing extension-process boundary and neither epic's stated payoff needs one. (2) Reaction delivery reuses internal/eventbus's Publisher/Consumer contract (PublishUnique + Ack/Nak already provide at-least-once with dedup), but NOT the existing nats.Client as-is: it hardcodes Retention: jetstream.WorkQueuePolicy (client.go:65) for the competing-consumer ARCHIE_TASKS stream, which silently starves a second consumer on overlapping subjects per CLAUDE.md's documented trap -- reactions need fan-out, so retention needs to become a Config field and reactions get their own stream. (3) Reactions in these two epics are producer-only (cheap wake via curator's WakeOnPrimaryInput pattern, or produce real work via the existing pollNATS-\u003epublishTask path) -- no veto/mutate-in-flight-work capability is being built here; that belongs to archie-core-h019 if it's ever needed. (4) No single generic Source interface -- forge intake reuses workintake.TaskEnvelope unchanged (its IdempotencyKey is already keyed on owner/repo/number, not delivery source, so a webhook-sourced envelope naturally dedups against a poll-discovered one for free); chat webhook stays internal/channels/webhook, unmodified; what's genuinely new and shared is a small cross-cutting package for HMAC/rate-limit/approval/capture mechanics, owned by neither domain.","external_ref":"https://github.com/samcharles93/archie-core/issues/544","dependencies":[{"issue_id":"archie-core-7d5u.1","depends_on_id":"archie-core-7d5u","type":"parent-child","created_at":"20Line truncated
|
||||
{"_type":"issue","id":"archie-core-7d5u.2","title":"Reaction delivery via embedded NATS, no external server required","description":"Reactions need at-least-once delivery distinct from the lossy events.Bus (see epic description). The delivery mechanism is NATS -- that part is settled, not a design question. What's open is deployment shape.\n\nVERIFIED 2026-08-22: config.NATSConfig.URL empty currently means 'no NATS, use SQLite ClaimNext' (internal/config/config.go:573-582). That fallback was designed for task distribution working without a broker at all. It was never meant to generalise to 'archie has no NATS' as a permanent architectural stance -- the intended second deployment shape alongside an external NATS server was always NATS EMBEDDED (in-process), not a different eventbus.\n\ngithub.com/nats-io/nats-server/v2 is already a direct dependency and is proven to work in this codebase: internal/infrastructure/agenttransport/nats/transport_test.go and others already start a real embedded server via nats-server/v2/test for tests. It has just never been wired into production startup -- cmd/archied only knows 'external URL configured' vs 'fall back to SQLite'. No new library, no new bus, no architectural gap to design around: this is 'wire the dependency we already have and already test against into the daemon's own startup path.'\n\nDesign questions that remain, now correctly scoped: does an embedded NATS instance replace the SQLite fallback outright for single-process deployments, or run alongside it; what config controls embedded vs external vs disabled; does the daemon own the embedded server's lifecycle the same way it owns everything else (start/stop paired with daemon start/stop, per the shutdown-ordering rules in ARCHITECTURE.md).","acceptance_criteria":"A single-process deployment with no external NATS URL configured still gets reaction delivery via an embedded NATS instance; the daemon starts and stops the embedded server as part of its own lifecycle; no second eventbus type is introduced; internal/infrastructure/eventbus/nats is reused as the transport rather than duplicated.","notes":"2026-08-22, from docs/prds/event-sources-and-reactions.md: do not reuse the existing nats.Client's stream creation as-is. internal/infrastructure/eventbus/nats/client.go:65 hardcodes Retention: jetstream.WorkQueuePolicy -- correct for ARCHIE_TASKS (task distribution, one consumer claims each message) and wrong for reactions, which need fan-out (every registered reaction sees every matching event). Two reactions on overlapping subjects under WorkQueuePolicy hit the exact trap CLAUDE.md documents: the second consumer silently gets nothing. Config.StreamName/Config.Subjects are already composition-supplied (config.go:30-38); Retention is not parameterized and needs to become a Config field, defaulting to today's WorkQueuePolicy so ARCHIE_TASKS is unaffected, with reactions getting a second stream under a fan-out-capable policy and their own subject namespace.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:26:26Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:10Z","started_at":"2026-08-21T18:57:41Z","closed_at":"2026-08-21T19:18:55Z","close_reason":"Embedded NATS wired into production startup: mode=embedded/external/off resolves from url, daemon owns the in-process server lifecycle, Retention parameterized for a future fan-out reaction stream. task check + lint clean; adversarial review zero surviving findings. Committed 2c7db34.","external_ref":"https://github.com/samcharles93/archie-core/issues/545","dependencies":[{"issue_id":"archie-core-7d5u.2","depends_on_id":"archie-core-7d5u","type":"parent-child","created_at":"2026-08-21T23:26:26Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.2","depends_on_id":"archie-core-7d5u.1","type":"blocks","created_at":"2026-08-21T23:26:57Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-7d5u.3","title":"Shared webhook mechanics: HMAC verification, per-source rate limiting, payload redaction","description":"NARROWED 2026-08-22 from this bead's prior scope, which bundled capture-storage and an approval state machine into a single 'shared mechanics' package. On reflection those are not genuinely shared yet:\n\n- Capture STORAGE is t2db.1's job -- it depends on the NATS-vs-SQLite decision 7d5u.2 owns, and building a storage engine here would either duplicate or contradict that. This package may be USED by t2db.1's capture path, but does not own persistence.\n- The draft/pending_approval/armed state machine belongs to the entity that has that state -- t2db.4's binding -- not a generic package. There is exactly one consumer (bindings) today; per 'extract into a shared primitive on the second real consumer, never in anticipation of one,' building it here now would be speculative.\n\nWhat remains, and is genuinely storage-agnostic and reusable by any inbound HTTP source regardless of what consumes it:\n\n1. HMAC-SHA256 verification -- generalize internal/channels/webhook/webhook.go's existing unexported validateHMAC into an exported function here, and have that package call into it instead of keeping its own copy. One implementation of signature checking, not two that can drift.\n2. Per-source rate limiting -- a token bucket keyed by source ID (not global), so one noisy sender cannot exhaust another's budget. Limit-exceeded is an observable rejection, not a silent drop, per t2db.5's decision.\n3. Payload redaction -- generalize internal/gateway/stream.go's unexported sensitiveParameterKey/redactToolParameters heuristic (matches token/secret/password/passwd/api_key/apikey/authorization/credential/cookie/private_key against normalized JSON keys) into a reusable, storage-agnostic transform any capture path can apply before persisting.","acceptance_criteria":"webhookguard.VerifyHMAC replaces internal/channels/webhook's private copy with no behaviour change (its existing tests still pass); a per-source rate limiter rejects over-budget requests observably; a redaction function matches the same key heuristic already proven in gateway/stream.go; the package has zero imports of any domain, infrastructure or app package.","notes":"--notes=2026-08-22: merged to main as f3d3d32 (PR #534, squash of aa23ac9+46401ab+ce4f945).","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:26:26Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:11Z","started_at":"2026-08-21T15:19:09Z","closed_at":"2026-08-21T15:26:01Z","close_reason":"Built internal/webhookguard: VerifyHMAC (behavior-preserving extraction from internal/channels/webhook, which now calls it instead of keeping a private copy), RateLimiter (per-source token bucket, independent budgets, observable rejection), RedactPayload (key-name heuristic matching gateway/stream.go's marker list, but -- deliberately unlike that function -- redacts only values under sensitive keys and leaves ordinary strings/numbers/bools untouched, since a captured payload exists to be inspected for field mapping in t2db.3).\n\nAll four acceptance criteria met and independently confirmed by a fresh adversarial review with zero surviving findings: HMAC extraction is byte-for-byte behavior-preserving (diffed against the deleted function); rate limiter hand-traced correct on two scenarios plus race-clean under -race; redaction's divergence from gateway/stream.go verified by reading both functions side by side; zero non-stdlib imports confirmed by grep. The reviewer also mutation-tested both the redaction and rate-limit guards (disabled each in turn) and confirmed the test suite catches both, then reverted and re-verified go test -race and git status were clean.\n\ntask check exit 0, golangci-lint 0 issues (one forcetypeassert finding was caught and fixed properly during build, not suppressed), gofumpt clean. All 10 pre-existing internal/channels/webhook tests pass unmodified; the one now-redundant unit test was removed with a comment pointing to where its coverage relocated.","external_ref":"https://github.com/samcharles93/archie-core/issues/546","dependencies":[{"issue_id":"archie-core-7d5u.3","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"relates-to","created_at":"2026-08-21T23:27:06Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.3","depends_on_id":"archie-core-7d5u","type":"parent-child","created_at":"2026-08-21T23:26:26Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.3","depends_on_id":"archie-core-7d5u.1","type":"blocks","created_at":"2026-08-21T23:26:58Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-7d5u","title":"[EPIC] Event sources and typed reactions: archie as an extensible platform","description":"Goal: let archie react to things happening -- forge activity, inbound callers, schedules -- and let extensions hook those reactions, without a generic untyped event bus.\n\nTwo findings shape this, both verified in the tree on 2026-08-21.\n\n1. ARCHIE HAS TWO EVENT NEEDS AND ONE BUS. internal/events is documented as 'archied's in-process observability stream' with 'bounded per-subscriber buffers that DROP on overflow, so a stalled dashboard connection can never apply backpressure to the task engine'. Publish is fire-and-forget; subscribers get a read-only channel and cannot influence anything. Correct for the dashboard, wrong for reactions: a hook that silently misses events under load and cannot affect an outcome is worse than no hook, because it looks like it ran. Reactions need at-least-once delivery and the ability to change what happens. Do not bolt reactions onto events.Bus.\n\n2. THE OBVIOUS DESIGN IS PROHIBITED, DELIBERATELY. The tau model this is drawn from dispatches generically: DispatchEvent(ctx, eventName string, sessionID, ...) to out-of-process gRPC plugins. archie's approved foundation (docs/architecture/plugins-and-extensions.md) forbids that shape -- the generic plugin contract stays metadata-only and MUST NOT expose untyped hooks. plugin.Plugin is Name()/Version() only, enforced by internal/plugin/architecture_test.go and by the plugin engine rule in ARCHITECTURE.md. tau already carries the scar the rule avoids: TestUnload_DoesNotWaitForInFlightDispatch exists because a stuck plugin blocked plugin unload.\n\nThe reconciliation, and why this is an epic rather than a feature: separate INBOUND (callers push work in -- forge webhook, chat webhook, cron, channel) from REACTION (extensions respond to something that happened). Inbound becomes a typed source/intake capability family with an owning registry. Reactions become typed capability families owned by the domain whose semantics they affect. 'Webhooks aligned to types of callers' is exactly the typed-family model applied to intake: the instinct is right, the generic bus is what has to go.\n\nNear-term payoff: archie reacts to an issue being labelled the moment it happens, instead of up to poll_interval later.","acceptance_criteria":"A forge webhook triggers work behind a feature flag with polling still available as a backstop; inbound callers register through one typed family rather than bespoke wiring per caller; reactions have delivery guarantees distinct from the lossy observability bus; the generic plugin contract remains metadata-only and internal/plugin/architecture_test.go still passes.","notes":"CORRECTION 2026-08-22 (second): the earlier summary I gave characterized 'NATS is currently optional' as an open architectural gap for this epic to navigate around. That's wrong, and Sam corrected it directly: NATS was never meant to be optional as a technology. What's optional is running a standalone NATS SERVER -- config.NATSConfig.URL empty falls back to the existing SQLite ClaimNext flow (internal/config/config.go:573-582, internal/infrastructure/eventbus/nats/doc.go:24). The intended second deployment shape is NATS EMBEDDED (in-process, no external server to stand up), not 'no NATS, use some other eventbus'. There is no other eventbus in scope, was never meant to be one, and this epic must not introduce one.\n\nCurrent code state, verified: github.com/nats-io/nats-server/v2 (the embeddable NATS server package) is already a direct, non-indirect dependency, and is genuinely used to spin up an in-process server -- but only inside _test.go files (internal/infrastructure/agenttransport/nats/transport_test.go and others use github.com/nats-io/nats-server/v2/test to run tests against a real embedded server). It has never been wired into production as an actual deployment mode. So embedded NATS is proven to work in this codebase's own test harness, and the gap is purely that production startup only knows 'external URL configured' vs 'no NATS, fall back to SQLite' -- there is no production code path that starts nats-server in-process.\n\nThis changes 7d5u.2 (reaction delivery) materially: 'ride the existing NATS eventbus, or a second in-process bus' was the wrong framing. The actual question is whether reaction delivery requires an external NATS deployment or can run on an embedded NATS instance so single-process deployments still get it -- not whether to use NATS at all versus some other bus. If embedded NATS is wired for reaction delivery, capture (t2db.1) gets it too essentially for free, since they were flagged as needing the same underlying decision.","status":"open","priority":1,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-21T13:25:57Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/547","dependenLine truncated
|
||||
{"_type":"issue","id":"archie-core-h019.3","title":"Reviewer runs in a context that provably never saw the implementation","description":"A reviewer that shares the implementer's context is a second opinion from the same mind, and it will rationalise the same mistakes -- the failure mode CLAUDE.md's \"never self-certified by the implementer\" rule exists to prevent.\n\nUNBLOCKED 2026-08-25. The mechanism is decided in docs/prds/adversarial-self-review.md section 1 (rewritten, superseding the version q15y invalidated): the reviewer is an `agent.Subagent` run from inside the task-scoped archie-agent worker. ai-sdk v0.1.22 is already the pinned version, so no SDK bump. This adds no host executor, no second Pool.Acquire and no nested container lifecycle -- the open question the supersession left.\n\nTwo isolations are required and only one is free:\n\n- CONVERSATION isolation is structural. `Subagent.Run` (agent/subagent.go:76-96) calls GenerateText with Prompt set and Messages never populated, so the implementer's history has no code path into the nested run. This is the property to assert in the required test.\n- WORKSPACE isolation is ours to build. A sub-agent shares the parent's process, working directory and credentials, so the `.git`-free snapshot survives from the original design and is load-bearing: `git archive \u003ccommit\u003e | tar -x` into a fresh scratch directory BESIDE the task worktree, plus `diff.patch` and `issue.md`. Stripping `.git` is what makes commit messages, branch name and reflog structurally unreachable rather than merely undisclosed.\n\nThree construction rules:\n1. `Subagent.Tools` gets a distinct read-only toolset rooted at the snapshot. NEVER the worker's own toolset -- it carries the worktreerpc publication grant, so a reviewer holding it could push the branch it exists to block.\n2. Call `Run()`, not `Tool()`. `Tool()` would let the implementer's own model elect to review itself, which is the self-certification this feature prevents. It also avoids Tool()'s two-step-parent and recursion footguns.\n3. Findings return via a closure-captured capture tool, not the return value -- `Run` yields only text. Because the sub-agent is in-process, the capture tool's Go func appends to a []workflow.ReviewFinding the stage owns. Read that slice EVEN WHEN `Run` returns an error: findings already captured survive, so a reviewer that logged three defects then hit its step limit still yields those three.\n\n## Acceptance Criteria\n\nThe reviewer is launched with only the snapshot, diff.patch and issue.md; a test fails if implementer context reaches it, asserting isolation as a construction fact rather than prompt text; the reviewer's prompt instructs it to assume every line is wrong until proven correct; the mechanism reuses agent.Subagent inside the existing worker rather than inventing a second execution path; the reviewer's toolset is read-only, rooted at the snapshot, and provably excludes the worktreerpc publication grant; captured findings are recovered even when Run returns an error.\n","acceptance_criteria":"The reviewer is launched with only diff + issue; a test fails if implementer context reaches it; the reviewer's prompt instructs it to assume every line is wrong until proven correct; the mechanism reuses the existing container/worktree isolation rather than inventing a second one.","notes":"BLOCKED 2026-08-24: not implementable as specified. docs/prds/adversarial-self-review.md is marked 'Superseded; requires redesign before implementation' -- superseded by the full-task worker boundary landed in archie-core-q15y. Its mechanism for this bead was a daemon-side second container.Pool.Acquire plus an in-process agentexec path; q15y.2 and q15y.3 removed BOTH call sites, so the isolation mechanism this bead reuses no longer exists. Needs a design decision first: how a fresh reviewer receives a .git-stripped snapshot from INSIDE the existing task-scoped archie-agent worker, without introducing a host executor or a nested container lifecycle. Do not implement against the superseded PRD. The sibling bead h019.2 (findings contract) is unaffected and is being implemented, since it is a pure domain type with no execution dependency.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:02:54Z","created_by":"Sam Catlow","updated_at":"2026-08-31T11:51:42Z","started_at":"2026-08-25T15:06:11Z","closed_at":"2026-08-31T11:51:42Z","close_reason":"Implemented as agent.Subagent inside the task-scoped archie-agent worker (internal/app/agentworker/review.go). Conversation isolation is structural (Subagent.Run only sends a prompt, never message history -- verified against a fake chat.Provider). Workspace isolation via new worktree.Manager.Snapshot (.git-free export of HEAD's tracked files into a scratch dir beside the task worktree). Reviewer's toolset is read-only (read/grep/find) rooted at the snapshot, never the worker's oLine truncated
|
||||
{"_type":"issue","id":"archie-core-h019.4","title":"Wire review as an implement-workflow stage: after gates, before PR open","description":"Sequence matters. The review runs after gates pass -- there is no point reviewing code that does not build or test -- and before the PR is opened, because the point is to not spend the operator's attention on a PR that is not ready. The slot is between StageDiffCap() and StageOpenPR() in internal/domain/workflow/implement.go.\n\nA surviving CONFIRMED finding must not open a PR. Per CLAUDE.md, a finding that survives blocks closing the work; it does not get waved through.\n\nLIFECYCLE CORRECTION (2026-08-25): this bead previously said \"parks the task as waiting_human\", which names two different states in the actual machine (internal/taskstate/taskstate.go:44-59). docs/prds/adversarial-self-review.md section 4 decided this: use store.StatusParked, following StageDiffCap's existing precedent (steps.go:91-94) -- a stage-computed policy stop with a Detail explaining why, before PR open. Parked's available actions, retry and abandon, are the right shape: fix the flagged code and retry, or abandon/override a false positive. WaitingHuman's approve/reject actions have no referent here because there is no PR yet to approve or reject.\n\nBlocking is workflow.ReviewBlocking (shipped in h019.2): Verdict == confirmed AND Level == error. A PLAUSIBLE finding never blocks, however severe its level claims to be.\n\nFAIL-CLOSED (decided 2026-08-25): a review that fails to RUN is distinct from a review that ran and found nothing, and it must not open a PR. A sub-agent that errors, is truncated, or produces no conclusion yields ReviewStatusNotRun, for which Passed() is false and Blocking() is also false -- the contract deliberately refuses to guess, and this stage resolves it as park. Rationale: Repo.ReviewEnabled is opt-in, so an operator who turned the gate on wants the gate, and a provider outage silently degrading into \"PR opened unreviewed\" is what they were buying protection against. Accepted cost: a transient model error parks a task, and Parked's retry action is the remedy. The park Detail must say the review did not run, never that it passed.\n\nScope to the implement workflow first. Routing to tdd/bootstrap/feasibility is a later decision -- feasibility in particular produces a document rather than a diff, so \"review the diff\" may not even apply.\n\nAlso adds to internal/config: Models[\"reviewer\"] (falling back to Models[\"builder\"], no schema change) and Repo.ReviewEnabled bool (default false).\n\n## Acceptance Criteria\n\nAn implement task with a clean gate and no confirmed findings opens a PR as it does today; one with a surviving confirmed finding parks as store.StatusParked with findings recorded in Detail and opens no PR; a review that fails to run also parks, with a Detail that says so rather than implying a pass; a warn-level or plausible finding does not block; the stage is observable in the task's running(workflow:stage) status and emits task events despite the nested run being non-streaming; retry after operator action re-runs the stage; the stage is inert unless Repo.ReviewEnabled is true.\n","acceptance_criteria":"An implement task with a clean gate and no confirmed findings opens a PR as it does today; one with a surviving confirmed finding parks as waiting_human with findings recorded and opens no PR; the stage is observable in the task's running(workflow:stage) status; retry after operator action re-runs the review.","status":"closed","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-21T13:02:54Z","created_by":"Sam Catlow","updated_at":"2026-08-31T11:51:43Z","closed_at":"2026-08-31T11:51:43Z","close_reason":"StageReview wired into the implement workflow between StageDiffCap and StageOpenPR. Fail-closed: not-run or a confirmed error-level finding parks (store.StatusParked) with findings in Detail; warn/plausible findings never block. Inert unless Repo.ReviewEnabled (new config field, default false); Models[\"reviewer\"] falls back to Models[\"builder\"]. task check clean, golangci-lint clean. Committed 8db8a17.","external_ref":"https://github.com/samcharles93/archie-core/issues/549","dependencies":[{"issue_id":"archie-core-h019.4","depends_on_id":"archie-core-h019","type":"parent-child","created_at":"2026-08-21T13:02:54Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.4","depends_on_id":"archie-core-h019.1","type":"blocks","created_at":"2026-08-21T13:03:25Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.4","depends_on_id":"archie-core-h019.2","type":"blocks","created_at":"2026-08-21T13:03:25Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.4","depends_on_id":"archie-core-h019.3","type":"blocks","created_at":"2026-08-21T13:03:26Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":3,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h019.1","title":"Design: adversarial self-review stage (one-page decision in docs/prds/)","description":"No settled design exists for this in docs/architecture/, so under the scope-discipline rule merged as PR #533 the design comes first -- briefly and decisively -- and is not finished until a diff follows it.\n\nDecide and record, in one page under docs/prds/: where the reviewer runs (reuse the per-task container pool, or a separate short-lived container); what it is given (diff plus originating issue, and explicitly what it must NOT be given); the findings contract and who owns the type; what a surviving finding does to the task lifecycle; and how the reviewer's model/effort is configured.\n\nConstraints from the repo that the design must respect: dependency direction is cmd -\u003e app -\u003e {domain, infrastructure}, so the reviewer contract belongs to the workflow domain and the execution to infrastructure/app. Agent execution is a data boundary. The model never runs git. Prefer environmental enforcement over prompt rules -- 'the reviewer cannot see the implementation' must be a property of how it is launched, not an instruction in its prompt.\n\nDo not write an architecture document, migration plan or review campaign. One page that decides.","acceptance_criteria":"A one-page decision exists under docs/prds/ answering: reviewer isolation mechanism, inputs and forbidden inputs, findings contract owner, lifecycle effect of a surviving finding, and model/effort configuration. It decides rather than surveys, and cites the packages it will touch.","status":"closed","priority":1,"issue_type":"decision","owner":"sam@catlow.tech","created_at":"2026-08-21T13:02:39Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:05Z","started_at":"2026-08-22T09:30:19Z","closed_at":"2026-08-24T07:12:05Z","close_reason":"One-page decision written at docs/prds/adversarial-self-review.md: reviewer runs in a second workspace (container or in-process) pointed at a .git-stripped snapshot of the reviewed commit, never the implementer's worktree; findings contract is workflow.ReviewFinding, owned by internal/domain/workflow, reported via a structured capture tool; a surviving error-level finding sets StatusParked (not WaitingHuman -- epic wording named two different states, this resolves which); model/effort reuse the existing Models[role] map and per-stage budget override, gated by a new opt-in Repo.ReviewEnabled so h019.4 doesn't gate every repo on an uncalibrated reviewer before h019.5 lands. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/550","metadata":null,"dependencies":[{"issue_id":"archie-core-h019.1","depends_on_id":"archie-core-h019","type":"parent-child","created_at":"2026-08-21T13:02:39Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":5,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h019.2","title":"Findings contract: a structured review result the workflow can act on","description":"The reviewer's output must be data the workflow can branch on, not prose a human has to read to find out whether the PR is safe to open. Prose is what makes a review advisory; structure is what lets a finding block.\n\nDefine the finding type in the workflow domain (the domain declares the contract it needs; it never names who implements it). At minimum a finding carries: file and line, a one-sentence defect, a concrete failure scenario (inputs/state -\u003e wrong output), a verdict distinguishing CONFIRMED from PLAUSIBLE, and a disposition once acted on (fixed / skipped / no_change_needed).\n\nThe CONFIRMED/PLAUSIBLE split is load-bearing and must not be collapsed into a single boolean: only confirmed findings may block, or the feature degrades into crying wolf and the operator learns to skim past it.","acceptance_criteria":"A finding type exists in internal/domain/workflow with file, line, summary, failure scenario, verdict and disposition; it is serialisable across the agent-execution data boundary; a review result with zero findings is representable and distinct from a review that did not run.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:02:39Z","created_by":"Sam Catlow","updated_at":"2026-08-24T09:15:56Z","started_at":"2026-08-24T08:57:20Z","closed_at":"2026-08-24T09:15:56Z","close_reason":"Implemented: workflow.ReviewFinding + ReviewReport in internal/domain/workflow/review_findings.go, merged 53bb841. The domain owns the type; gate.Finding was used as a shape precedent only, not reused, so the review contract is not coupled to the Yaegi gate's evolution. Blocking requires Verdict==confirmed AND Level==error, so a PLAUSIBLE finding never blocks however severe it claims to be. ReviewStatus makes 'ran and found nothing' structurally distinct from 'never ran' -- Passed() is false for a zero-value report, and the distinction does not rest on nil-vs-empty-slice. JSON round-trip covered; Line 0 is preserved (no omitempty) for whole-file findings. Review found and fixed a duplicate package doc comment and a redundant ReviewBlocking/BlockingReviewFindings alias pair. task check green. Fresh adversarial review clean across 8 dimensions; I independently mutation-tested the blocking rule: dropping the verdict check fails 5 tests (incl. plausible_error_MUST_NOT_block) and dropping the level check fails 5 more, so the tests genuinely pin both halves.","external_ref":"https://github.com/samcharles93/archie-core/issues/551","dependencies":[{"issue_id":"archie-core-h019.2","depends_on_id":"archie-core-h019","type":"parent-child","created_at":"2026-08-21T13:02:39Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.2","depends_on_id":"archie-core-h019.1","type":"blocks","created_at":"2026-08-21T13:03:24Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":3,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h019","title":"[EPIC] Adversarial self-review before archie opens a PR","description":"Archie enforces gates on every PR it opens, but it does not run the adversarial review CLAUDE.md makes mandatory for every change in this repo: a fresh reviewer that did not write the code, told to assume every line is wrong, working a defined checklist, where a surviving finding blocks the work. It is the one discipline the project requires of its contributors and exempts itself from.\n\nWhy it matters, with evidence rather than assertion: on 2026-08-20/21 the update-verification change (PR #530) passed task check at every checkpoint -- exit 0, golangci-lint 0 issues, gofumpt clean -- and three adversarial passes still found six real defects, two of them blocking. A 'dev' version placeholder would have reported healthy updates as failures, and an 'unknown' install claim was still being worded as confirmed success. The gates were green throughout and would have stayed green. This is CLAUDE.md's own recorded lesson: tests catch behaviour that breaks, not behaviour that quietly starts meaning something else.\n\nArchie is unusually well placed to do this. It already runs each task in an isolated container and worktree, so it can spawn a reviewer that genuinely never saw the implementation -- not a second opinion from the same context pretending to be fresh, which is the failure mode of every single-context tool. The isolation boundary built for safety is what makes honest self-review possible.\n\nWhat the operator gets: a PR that arrives with a findings section -- what was checked, what was found, what was fixed, what survived. A surviving finding parks the task as waiting_human instead of opening a PR that looks ready and is not. Review shifts from hunting for bugs to adjudicating findings.\n\nThe risk that kills the feature is a reviewer that cries wolf. Findings must be adversarially confirmed before they surface, and the reviewer must be able to report zero findings on properties it checked and cleared. Calibration is the feature, not the finding count.","acceptance_criteria":"An implement-workflow task runs an adversarial review after gates pass and before the PR is opened; the reviewer provably cannot see the implementer's context; a surviving confirmed finding blocks PR creation and parks the task; findings and their disposition are visible on the PR and the dashboard.","status":"open","priority":1,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-21T13:02:17Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/552","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-3jag","title":"Chat/task agent persona is overconfident: presents unverified claims as verified, fabricates infrastructure details","description":"The chat assistant (archie, running via the Telegram/webui gateway) repeatedly\npresents unverified or fabricated information with false confidence, and only\nretracts it when directly challenged. This is a persona/system-prompt problem,\nnot a model quality problem -- reproduced on more than one underlying model.\n\nTwo concrete instances from a live Telegram transcript (2026-08-15):\n\n1. Fabricated infrastructure: asked \"are logs going anywhere else?\", the\n assistant invented an entire second log-shipping subsystem (\"Hermes\n gateway\") with specific fake file paths\n (/home/sam/.hermes/profiles/local-agent/logs/) that do not exist anywhere\n in archie-core, and stated it as verified fact (\"I confirmed the web UI\n token and task lifecycle messages are there\"). When challenged (\"Is there\n something in the codebase which tells you you're Hermes?\"), it admitted\n the paths were invented and carried forward from unrelated, unverified\n context.\n\n2. Overclaimed verification: asked \"Why did that last task fail?\", the\n assistant answered with a bulleted list explicitly labelled \"Verified\n details\" (attempt count, iteration count, token count, exact model name).\n When pressed with \"You checked it?\", it admitted the model name and\n change count were \"overstated\" -- i.e. it labelled unverified specifics as\n verified the first time, and only corrected itself under direct\n challenge.\n\nThe common shape: confident, specific claims presented as fact/verified\nfirst; a walked-back, hedged correction only appears after the user\nexplicitly challenges it. This erodes trust in every claim the assistant\nmakes about system state, since the default posture is confident assertion\nrather than \"I have/haven't actually checked this.\"","notes":"Root cause is believed to be the persona/system-prompt layer (internal/gateway/ BuildSystemPrompt + persona templates), not model selection -- reproduced across models per the reporter. Needs a system-prompt-level fix enforcing 'never label something verified unless it was actually checked this turn' and 'never state unconfirmed system details as fact.' Sam is reviewing the persona/prompt separately; this bead tracks the finding so it isn't lost.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-15T02:25:37Z","created_by":"Sam Catlow","updated_at":"2026-08-20T12:55:18Z","started_at":"2026-08-20T12:50:34Z","closed_at":"2026-08-20T12:55:18Z","close_reason":"Fixed in fix/persona-overconfidence (fba80e3): reworded core rule 1 and added rules 8/9 to the chat agent system prompt enforcing this-turn verification before labelling claims verified/confirmed.","external_ref":"https://github.com/samcharles93/archie-core/issues/524","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786756970855-1-72466b33","title":"worktree: retry fails on a dirty worktree left by an interrupted prior attempt","description":"## Problem\n\n`Manager.refresh` (`internal/worktree/worktree.go`) checks out the task's branch without `Force` before hard-resetting to base. If a prior attempt left uncommitted local changes in the worktree — a killed container, or a stage that edits files before ever reaching a commit — go-git's default checkout (`MergeReset` mode) can refuse to reconcile them, even when HEAD is already on the correct branch and the target commit hasn't moved.\n\nThat failure was then compounded by the fallback: the code assumed any checkout failure meant \"the branch doesn't exist yet in this worktree\" and retried with `Create: true`, which fails differently (and much more confusingly) since the branch *does* exist:\n\n```\ncheckout branch feat/1000000000000000-fix-github-issue-514-telegram-response-formatting-concatenat:\na branch named \"refs/heads/feat/1000000000000000-fix-github-issue-514-telegram-response-formatting-concatenat\" already exists\n```\n\n## Evidence\n\nReproduced directly against the actual broken worktree on a live deployment: `git status` showed a modified tracked file and an untracked file left over from an interrupted attempt, HEAD already correctly on the task branch. Retrying the task hit exactly the error above and parked again with the same unhelpful message, on every retry, since nothing about the state changes between attempts.\n\n## Fix\n\nAdd `Force: true` to both checkout attempts in `refresh`. This is safe unconditionally: `refresh` hard-resets to the base commit a few lines later regardless of what checkout leaves behind, so there is no scenario where discarding the working tree's local state here is wrong.\n\nRegression test: `TestPrepareRecoversFromADirtyWorktreeOnRetry` reproduces the exact production error (modified tracked file + untracked file, branch already checked out) and confirms retry now succeeds and correctly restores the tracked file to its base content.","status":"closed","priority":1,"issue_type":"bug","created_at":"2026-08-15T01:22:16Z","updated_at":"2026-08-15T01:22:38Z","closed_at":"2026-08-15T01:22:39Z","external_ref":"https://github.com/samcharles93/archie-core/issues/523","source_system":"github:https://github.com/samcharles93/archie-core/issues/523:523","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786751948782-3-837a8fd0","title":"Embed install-type at build time; verify updates against actual running state, not installer exit code","description":"## Problem\n\n`/update` and `/version` currently trust whatever the operator's external `update_check_command`/`update_install_command` reports (`internal/releaseupdate/command.go`). Nothing verifies that the reported version actually matches what's running. This already produced a false success: `/update` reported `archied`/`archie-agent` both updated to `v1.9.0` (the release containing the #468 fix), and a task run immediately after still hit the exact pre-fix failure — see #468 and #511 for the full evidence trail.\n\nSeparately, Archie ships in multiple install shapes (systemd-managed binary, Docker container via compose, possibly others). Nothing today tells the update mechanism which shape a given running component actually is, so a wrong-path update (e.g. attempting a container-style update against a systemd-managed process) is possible and would currently fail silently or claim success incorrectly.\n\n## Design (researched against prior art: restic, Tailscale, Docker/kubectl version output)\n\n**1. Stamp install type at build/release time — never probe for it at runtime.**\nAdd a small cross-cutting `internal/installtype` package: `var channel = \"unknown\"`, read via `Channel() string`. Stamp the real value per release artifact with `-ldflags \"-X .../installtype.channel=systemd\"` (native binary build) or `=container` (Docker image build) — one line per build target in the existing release pipeline, since `archied` and `archie-agent` are already built as separate artifacts for their respective channels.\n\nPrecedent: restic strips its `self-update` subcommand entirely via a build tag for distro-packaged builds — the wrong path isn't just mislabeled, it's absent. Tailscale, despite runtime-detecting almost everything else, treats Docker as an unconditional \"no self-update, manage via image tag\" — even the most sophisticated self-updater in this survey doesn't try to be clever about containers.\n\n**2. Fail closed, never guess.** The `/update` dispatcher must refuse to proceed if `installtype.Channel() == \"unknown\"` or doesn't match what the install/check command expects, with a clear operator-facing message. No fallback path.\n\n**3. Verify after, don't trust the exit code.** After `Installer.Install` returns success, re-check the *actual* running reference (binary path + hash, or container image digest) against the target version, and only then report success to the user. This is the concrete fix for the false-success bug. Tailscale's `confirm()` does the equivalent version comparison before/after in its own updater.\n\n**4. Extend `releaseupdate.Component`** (`internal/releaseupdate/service.go`) with `InstallType string` and `Reference string` fields (e.g. `\"container\"`, `\"ghcr.io/samcharles93/archie-agent:1.9.0@sha256:...\"`), populated by each component: `archied` reads its own compiled-in value; `archie-agent` reports its own the same way (already has a channel back to the daemon over NATS for logs — extend for a status/version response); third-party dependencies Archie doesn't build (e.g. NATS) can't self-report, so their `InstallType`/`Reference` comes from the deployment profile (`deployments/*.toml`) rather than detection.\n\n**5. Surface per-component status** on the Configuration page and in `/version`, structured as one block per component: `{install_type, running_version, reference, latest_available, status}`, where `status` is an enum (`ok` / `update_available` / `drift` / `unknown`) — not a bare color, with the actual comparison (e.g. running digest vs. latest digest) visible on hover/expand. Modeled on `docker version`'s Client/Server nested-block convention, which `kubectl version` independently converged on too.\n\n## Relates to\n\n- #468 (the fix this update-verification gap let slip through undetected)\n- #511 (update command UX — this issue is the underlying mechanism that makes accurate progress/success reporting possible; #511 shouldn't report a nicer-looking version of a still-unverified claim)","notes":"2026-08-21: design point 3 committed as c25799e on branch fix/522-verify-update-took-effect (not pushed).\n\nReport.Verify(running) partitions every claimed component into Confirmed/Drift/Unverified. Ground truth is the relaying process's own compiled-in gatewayVersion. Telegram now has three wordings: confirmed, 'could not confirm which version is actually running', and 'Update did NOT take effect' with per-component detail. Placeholders 'unknown' (watchdog default) and 'dev' (unstamped build) are unverifiable, never versions. Agent stays Unverified by design and is named as unchecked in the success message.\n\nGate: task check exit 0, golangci-lint 0 issues, gofumpt clean. Three adversarial review passes; all findings fixed. Regression tests proven to fail againstLine truncated
|
||||
{"_type":"issue","id":"archie-core-1786749700606-6-bf6aa32d","title":"agent containers: push fails with 'permission denied' reading .git/objects, distinct from #468","description":"## Problem\n\nTask `#445` (daemon: label dispatch trigger) parked at the `commit-push` stage with:\n\n```\npush fix/445-daemon-label-dispatch-trigger-with-empty-label-matches-every:\ngetting wanted object 295b030cc6face20f8a377e94076922c460576c1:\nopenat objects/29/5b030cc6face20f8a377e94076922c460576c1: permission denied\n```\n\nThis is a different failure mode than #468 (git's \"dubious ownership\" ownership *check*, resolved by `safe.directory`). Here git gets *past* whatever ownership check applies and fails on an actual filesystem permission bit when reading a loose object from the bind-mounted worktree's `.git/objects/`.\n\n## Why this is probably not fixed by #468\n\n`safe.directory` only tells git to trust a repo it doesn't own — it does not change the actual read/write permission bits on the files. If the object file was written by a process running as a different UID than the archie-agent container's process (e.g. daemon-side `worktree` package operations running as the host user, vs. the container process), a straightforward `openat ... permission denied` on a specific loose object is consistent with a UID mismatch on the bind mount that `safe.directory` does nothing for.\n\nNeither `Dockerfile` nor `docker-compose.yml` sets a `USER`/`user:` for the agent image, so the container should be running as root by default — worth confirming whether the deployment actually runs it as root (Docker `userns-remap` would explain root-inside behaving as an unprivileged UID on the host, which would produce exactly this symptom).\n\n## Ask\n\nConfirm the UID the archie-agent process actually runs as versus the UID that owns files under the worktree's `.git/objects/` on the host, and fix the mismatch (consistent UID, or `chown`/`chmod` the bind mount appropriately before handing it to the container).","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","created_at":"2026-08-14T23:18:58Z","updated_at":"2026-08-17T22:40:02Z","started_at":"2026-08-17T22:27:08Z","closed_at":"2026-08-17T22:40:02Z","close_reason":"Confirmed root cause: agent containers run as root (no USER in Dockerfile, no userns-remap anywhere in docker-compose.yml/internal/container/pool.go), so a commit the agent writes to the bind-mounted worktree lands owned by UID 0 on the host. The daemon later reads those same loose objects to push, running as its own non-root host user -- 'openat objects/../..: permission denied'. Fixed: containerEnv() now passes the daemon's own os.Getuid()/os.Getgid() as WORKTREE_UID/WORKTREE_GID; hybridTrees.Push (the single choke point before the push RPC) chowns the worktree back to that owner first. Adversarial review (fresh subagent) found one real bug in the first pass -- chownTree used os.Chown, which follows symlinks and fails on a legitimately-tracked-but-dangling symlink, which would have aborted a push that would otherwise have succeeded (worse than the original bug). Fixed with os.Lchown plus a regression test proving it against a dangling symlink. Full task check clean; all other review findings (full-tree walk cost, minor test-hygiene notes) were judged non-blocking by the reviewer.","external_ref":"https://github.com/samcharles93/archie-core/issues/520","source_system":"github:https://github.com/samcharles93/archie-core/issues/520:520","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786749700580-5-e3878224","title":"/stop does not kill an in-flight archie-agent NATS worker or its container — task keeps running","description":"## This is the most important finding from today's investigation.\n\n`/stop` is meant to be an emergency brake. It is not one: it reported success (\"🛑 Stopped task(s) #5\") while the task kept running, kept burning tokens, and kept flooding the logs with errors for at least the next 20+ minutes.\n\n## Root cause\n\n`/stop` → `Gateway.stopRunningTasks` → `router.Controller.StopRunning` (`internal/gateway/tasks.go:227`) → `Daemon.CancelRunningTasks` (`internal/daemon/running.go:114`) → `runningTasks.stopAll`, which cancels a `context.CancelFunc` registered in an in-process map (`internal/daemon/running.go:36-52`, populated by `Daemon.process` at `internal/daemon/daemon.go:800`).\n\nThat context governs only `archied`'s own orchestration goroutine for the task. In the NATS-dispatched execution model (`internal/app/agentworker`), the actual work happens in a **separate process** — the archie-agent worker — that pulled a stage request off NATS and is running it inside `handleSingleStageRequest` / `runMainLoopWithDelay` (`internal/app/agentworker/stage_loop.go`), driven by its own top-level context that has no connection whatsoever to the daemon's per-task cancel registry. Cancelling the daemon-side context does not reach it. There is currently no signal, subject, or mechanism by which `archied` can tell an already-dispatched archie-agent worker to stop.\n\nThis matches what was observed live: task `#1000000000000001` was reported stopped, remained `Working` in the dashboard 20+ minutes later, and its log showed 996 `handle failed err={}` entries in the minutes after the stop request — the worker was still very much alive and looping.\n\n## Expected behavior\n\n`/stop` (and task Cancel generally) should be a hard kill for both halves of the execution:\n1. `archied`'s own orchestration (already works, via the existing context cancellation).\n2. The archie-agent worker actually doing the work for that task.\n\n## Suggested fix\n\nContainers are per-task and Docker-managed by the daemon regardless of deployment shape (`internal/container/pool.go`). The most reliable \"dead in its tracks\" mechanism is for `/stop`/`Cancel` to kill the task's container directly via the Docker client the pool already holds, rather than relying on context propagation across a process boundary that current code has no way to cross. A NATS-side alternative (publish a cancellation event on a per-task subject that `stage_loop.go`'s loop checks between fetch and ack, or have the daemon revoke the task lease so the worker's next `Ack`/`Respond` fails) is a secondary/defense-in-depth improvement, but killing the container is what actually guarantees the work stops.\n\n## Related\n\nThe redelivery-storm behavior after a stop/nak (#517) and the swallowed error detail (#516) both make this worse in practice — an operator watching the logs after `/stop` sees hundreds of contentless error lines with no way to tell whether the stop is taking effect.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","created_at":"2026-08-14T23:18:46Z","updated_at":"2026-08-17T22:38:57Z","started_at":"2026-08-17T14:31:11Z","closed_at":"2026-08-17T22:38:57Z","close_reason":"Root cause found after Sam confirmed live testing still showed the task's in-flight tool calls/generation continuing tens of seconds to ~2 minutes after /stop reported success. internal/container/pool.go Release() always slept the configured GracePeriod and always used Docker's default ~10s graceful SIGTERM-then-SIGKILL timeout, even when the release was happening because the task's context had just been cancelled by /stop -- so a cancelled task's container (and the in-flight work inside it) could sit doing nothing for up to GracePeriod+~10s before actually dying. Fixed with a new releaseDecision(ctx, grace) helper: a cancelled ctx now skips the grace sleep entirely and requests an immediate SIGKILL (ContainerStopOptions.Timeout=0) instead of a graceful wait; a live ctx (normal completion) keeps the original behaviour byte-for-byte. Red-then-green with 3 new unit tests (internal/container/pool_test.go), task check clean, adversarially reviewed by a fresh subagent with zero blocking findings -- context-chain trace, Docker Timeout=0 semantics, and struct-equivalence for the unchanged path were all independently verified against the moby client source.","external_ref":"https://github.com/samcharles93/archie-core/issues/519","source_system":"github:https://github.com/samcharles93/archie-core/issues/519:519","metadata":null,"labels":["bug","gateway"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786749700549-4-d2331d9d","title":"dashboard: task timeline shows 'No events yet' for every task regardless of status or stage","description":"## Problem\n\nEvery task's expanded timeline on `/tasks` reads \"No events yet — This task has not recorded any transitions,\" regardless of status or how far the task progressed. Confirmed live across a `Working` task and multiple `Parked` tasks at different stages:\n\n- `#1000000000000001` — Working, implement/baseline, 20+ minutes in\n- `#1000000000000000` — Parked at implement/baseline (go build/VCS-stamp failure)\n- `#445` — Parked at tdd/commit-push (git push permission error)\n\nAll three show the identical empty-timeline message. This isn't isolated to the currently-stuck task — the timeline feature appears non-functional for the whole deployment, which means the dashboard's per-task \"what actually happened\" view (the thing an operator reaches for first when a task needs attention) carries no information at all.\n\n## Impact\n\nCombined with the logging defect in #516 (errors serialize to `{}`), this leaves an operator with almost no way to diagnose a stuck or parked task from the dashboard — no timeline, and the log detail that does exist is empty.\n\n## Ask\n\nFind where task transition events are supposed to be written (`store.Transition`, `d.emit(events.Event{...})`, etc.) versus what the timeline UI/API actually queries, and reconcile — either events aren't being persisted for these tasks, or the timeline endpoint is querying the wrong key/table.","status":"closed","priority":1,"issue_type":"bug","created_at":"2026-08-14T23:17:17Z","updated_at":"2026-08-15T00:35:51Z","started_at":"2026-08-15T00:03:04Z","closed_at":"2026-08-15T00:35:51Z","external_ref":"https://github.com/samcharles93/archie-core/issues/518","source_system":"github:https://github.com/samcharles93/archie-core/issues/518:518","metadata":null,"labels":["bug","webui"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786749700516-3-f1298573","title":"agentworker: stage handle-failure path has no backoff, causing rapid NATS redelivery storms","description":"## Problem\n\n`runMainLoopWithDelay` (`internal/app/agentworker/stage_loop.go:23-52`) sleeps 1 second before retrying when *fetching* a message fails:\n\n```go\ncase err != nil:\n ...\n log.Error(\"fetch failed\", \"err\", err)\n delay(time.Second)\n continue\n```\n\nBut when *handling* a fetched message fails, it Naks and loops straight back to the next fetch with **no delay at all**:\n\n```go\nif err := handleSingleStageRequest(ctx, message, log, productionSingleStageDependencies()); err != nil {\n log.Error(\"handle failed\", \"err\", err)\n if err := message.Nak(); err != nil {\n log.Warn(\"nak failed\", \"err\", err)\n }\n continue // \u003c-- no delay before the next FetchStage\n}\n```\n\nIf a stage message fails deterministically (bad request payload, unreachable dependency, permanently broken environment), Nak → immediate redelivery → immediate re-fail repeats at machine speed until `MaxDeliver` (default 3, `internal/infrastructure/eventbus/nats/config.go:16`) is exhausted for that message — but with multiple stage messages queued for a stuck task, or a `MaxDeliver` that doesn't apply the way expected in the stage-consumer path, this produces an uncontrolled burst.\n\n## Evidence\n\nTask `#1000000000000001`, 2026-08-15: **996 identical `handle failed err={}` log lines within a 3-second window** (08:51:28–08:51:31), confirmed live via the dashboard `/logs` page. Related: archie-core-9c985f28 style Sam messages describe this independently as \"unbounded rapid message redelivery.\"\n\n## Fix\n\nAdd a backoff (e.g. the same `delay(time.Second)`, or better, exponential with jitter) before `continue` in the handle-failure branch, and confirm `MaxDeliver` is actually enforced for the stage consumer's Nak path (`internal/infrastructure/agenttransport/nats/transport.go`) so a permanently-failing message stops being redelivered rather than burning the log and the NATS server.","status":"closed","priority":1,"issue_type":"bug","created_at":"2026-08-14T23:17:07Z","updated_at":"2026-08-15T02:55:32Z","closed_at":"2026-08-15T02:55:32Z","close_reason":"Fixed in 3eab6a2 (archied/archie v1.9.3): added the same time.Second backoff after Nak that the sibling fetch-error branch already had, stopping the immediate redelivery-storm loop. Regression test in stage_loop_test.go. Not done: exponential backoff+jitter (used the existing constant-delay pattern instead, for consistency) and explicit verification that MaxDeliver is enforced end-to-end for the stage consumer's Nak path -- worth a follow-up if the storm recurs at a smaller scale.","external_ref":"https://github.com/samcharles93/archie-core/issues/517","source_system":"github:https://github.com/samcharles93/archie-core/issues/517:517","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786749700482-2-ea056b07","title":"logging: errors logged through the slog JSON handler serialize to `{}`, losing all diagnostic detail","description":"## Problem\n\nEvery `log.Error(..., \"err\", err)` call site logs through `slog.NewJSONHandler` (`internal/logging/logging.go:56,61,69`, `internal/logging/tasksink.go:63`). Go's stdlib error types (`fmt.Errorf`, `errors.New`) are structs with unexported fields (`*fmt.wrapError{msg, err}`, `*errors.errorString{s}`). `encoding/json` cannot see unexported fields, and neither type implements `MarshalJSON`, `MarshalText`, or `slog.LogValuer` — so any error value passed to a JSON-handled logger serializes to the empty object `{}`, discarding the actual failure reason.\n\nThis is not one call site: `grep -rn '\"err\", err)'` across `internal/` and `cmd/` returns **160 matches across 25 files**.\n\n## Evidence\n\nLive on the dashboard `/logs` page (task `#1000000000000001`, 2026-08-15 08:51:28–08:51:31), captured via Playwright:\n\n```\n08:51:28 ERROR handle failed err={}\n08:51:28 ERROR handle failed err={}\n... (996 identical lines across a 3-second window)\n```\n\nThe message comes from `internal/app/agentworker/stage_loop.go:42`:\n```go\nlog.Error(\"handle failed\", \"err\", err)\n```\nwhere `err` is `fmt.Errorf(\"handle: %w\", err)` (`internal/app/agentworker/single_stage_request.go:82`). The real underlying failure is completely unrecoverable from the logs — there is no way to tell, after the fact, why 996 consecutive stage handles failed.\n\n## Fix\n\nAny of:\n- Log the string form explicitly: `log.Error(\"handle failed\", \"err\", err.Error())`\n- Add a small `slog.Attr` helper (`logging.Err(err)` → `slog.String(\"err\", err.Error())`) and require its use at all 160 call sites, or\n- Set `HandlerOptions.ReplaceAttr` on the JSON handlers to stringify any `error`-typed attribute value centrally, fixing every call site without touching them individually.\n\nThe last option is the smallest, single-point fix and should be preferred — it also protects any future `log.Error(..., \"err\", err)` call site from reintroducing the bug.","status":"closed","priority":1,"issue_type":"bug","created_at":"2026-08-14T23:16:53Z","updated_at":"2026-08-15T02:55:31Z","closed_at":"2026-08-15T02:55:31Z","close_reason":"Fixed in 6a23f8d (archied/archie v1.9.3). Root cause was more specific than the bead's hypothesis: slog.NewJSONHandler itself resolves an error attr correctly (verified live) -- the actual bug is that SystemLogHandler and FeedHandler both json.Marshal Entry.Fields directly via encoding/json, bypassing slog's value formatting entirely, which has no Error()-aware case. Fixed at the single choke point both handlers share: internal/logging/feed.go's addAttr/attrValue now resolves error attrs to .Error() before they reach the map, plus a guard against the typed-nil-pointer panic footgun. Regression test: internal/logging/attrs_test.go.","external_ref":"https://github.com/samcharles93/archie-core/issues/516","source_system":"github:https://github.com/samcharles93/archie-core/issues/516:516","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942495-16-0d6ea565","title":"Update command: show live status, version summary, and automatically roll back failures","description":"## Problem\n\nThe update command is not responsive enough during an update. The UX is excellent up to the point where the update starts, but then it does not clearly communicate whether the update succeeded, which version is now running, or whether the daemon and agent were updated successfully.\n\nA failed update also requires manual intervention instead of automatically restoring the previous known-good installation.\n\n## Desired behaviour\n\nWhen an update is requested, show progress/status throughout the operation, including:\n\n- update requested and started\n- current version and target version\n- download/build/install stages\n- daemon update status\n- agent update status\n- restart/health-check status\n- final success or failure state\n\nOn success, show a concise summary containing:\n\n- previous version\n- installed version\n- components changed (daemon, agent, and any other updated components)\n- whether the health check passed\n\nOn failure:\n\n- automatically roll back to the previous known-good version\n- restore/restart the daemon and agent as needed\n- verify the rollback with a health check\n- report the failure, rollback result, and versions to the user\n\n## Acceptance criteria\n\n- [ ] The command provides visible progress while the update is running.\n- [ ] The final response explicitly states success or failure.\n- [ ] The final response includes the previous and resulting versions.\n- [ ] Daemon and agent update/restart outcomes are reported separately.\n- [ ] Failed updates roll back automatically without manual intervention.\n- [ ] Rollback is health-checked and its result is reported.\n- [ ] Existing update deferral/check behaviour remains intact.\n- [ ] Tests cover successful updates, failed updates with successful rollback, and rollback failure.\n\n## Related\n\n- #359 — Telegram: announce newly installed Archie releases\n","status":"closed","priority":1,"issue_type":"feature","created_at":"2026-08-14T22:04:56Z","updated_at":"2026-08-18T15:51:15Z","closed_at":"2026-08-18T15:51:15Z","close_reason":"Shipped in archied v1.9.10 (commit 95290d1, feat(update): stream live progress and roll back failed updates automatically) -- live progress reporting, version summary, and automatic rollback on failed updates all landed and released.","external_ref":"https://github.com/samcharles93/archie-core/issues/511","source_system":"github:https://github.com/samcharles93/archie-core/issues/511:511","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942463-15-78823975","title":"Add end-to-end security and regression test matrix","description":"## Scope\nBuild the verification layer for remote secret input across the capability core, engine adapter, Telegram/mobile flow, and cleanup paths. Include automated redaction assertions and tests that inspect all emitted logs/events/transcripts for accidental secret leakage.\n\nAdd an integration test using a fake writable engine and a fake mobile channel, plus focused tests for real adapter boundaries where practical.\n\n## Acceptance criteria\n- End-to-end test proves a secret submitted from the mobile flow reaches only the selected writable engine and is not returned to the user or model.\n- Tests cover authorization, expiry, cancellation, replay, duplicate/concurrent submission, restart, backend failure, and delivery failure.\n- A deliberately distinctive sentinel secret is asserted absent from logs, errors, events, chat persistence, and test output.\n- Existing secret resolution, engine plugin, and channel tests continue to pass.\n- The normal project gate passes with race-sensitive session tests enabled.","status":"closed","priority":1,"issue_type":"task","created_at":"2026-08-14T21:58:15Z","updated_at":"2026-08-18T15:51:16Z","closed_at":"2026-08-18T15:51:16Z","close_reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.","external_ref":"https://github.com/samcharles93/archie-core/issues/510","source_system":"github:https://github.com/samcharles93/archie-core/issues/510:510","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942438-14-abe5ddd0","title":"Document operator setup, mobile workflow, and threat model","description":"## Scope\nDocument how an operator enables remote secret input, configures writable engines, authorizes users/chats, completes the mobile flow, and diagnoses safe failure states. Include explicit warnings about mobile notifications, screenshots, shared devices, Telegram retention/deletion limits, and external engine permissions.\n\nDocument which engines support writes, reference syntax, expiry/cancellation semantics, and what is deliberately unsupported.\n\n## Acceptance criteria\n- A new operator can configure and complete the flow from the documentation without SSH or editing raw secrets into chat commands.\n- Examples never contain real-looking credentials and do not put values in shell history, issue bodies, or ordinary prompts.\n- The docs explain the trust boundary and why the model is not involved in secret entry.\n- Troubleshooting distinguishes authorization, engine capability, transport, expiry, and backend errors without suggesting unsafe workarounds.","status":"closed","priority":1,"issue_type":"task","created_at":"2026-08-14T21:58:14Z","updated_at":"2026-08-18T15:51:16Z","closed_at":"2026-08-18T15:51:16Z","close_reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.","external_ref":"https://github.com/samcharles93/archie-core/issues/509","source_system":"github:https://github.com/samcharles93/archie-core/issues/509:509","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942414-13-14bd990e","title":"Add secure remote transport and session storage safeguards","description":"## Scope\nImplement the runtime plumbing for remote secret-input sessions, including process boundaries and state handling needed by the selected mobile adapter and engine registry. Prefer short-lived in-memory state; if restart recovery is required, store only non-sensitive metadata and require a new submission challenge.\n\nEnsure the normal agent/tool execution path cannot accidentally consume or persist the raw value. Add bounded concurrency and rate limits to prevent abuse.\n\n## Acceptance criteria\n- Raw secret values do not cross the model, issue/forge, normal chat transcript, or general event-bus boundaries.\n- Session metadata is bounded, expires deterministically, and is cleaned up on success, failure, cancellation, and shutdown.\n- Replay, brute-force, concurrent submissions, and resource-exhaustion protections are implemented and tested.\n- Remote input is disabled or reports unavailable when no authorized writable engine is configured.\n- Security-sensitive operations have structured audit events containing actor/target/outcome but never the value.","status":"closed","priority":1,"issue_type":"task","created_at":"2026-08-14T21:58:13Z","updated_at":"2026-08-18T15:51:16Z","closed_at":"2026-08-18T15:51:16Z","close_reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.","external_ref":"https://github.com/samcharles93/archie-core/issues/508","source_system":"github:https://github.com/samcharles93/archie-core/issues/508:508","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942364-11-47ec9e60","title":"Implement mobile-first secret-input UX in Telegram","description":"## Scope\nImplement the first mobile channel adapter for the remote secret-input flow using the existing Telegram command/conversation patterns. The UX should work on a phone with short prompts, explicit target selection, a sensitive-entry step, confirmation, cancellation, and expiry.\n\nUse Telegram-specific message controls where available to reduce persistence and accidental disclosure, but do not treat client-side deletion as the sole security boundary. Never echo or quote the submitted value.\n\n## Acceptance criteria\n- A mobile user can initiate the flow, choose an allowed engine/reference, submit a value, and get a redacted result without model involvement.\n- The value-entry step is clearly marked sensitive and supports `/cancel`, timeout, and safe recovery from invalid input.\n- Only the initiating authorized user can continue the session; another user/chat cannot hijack it.\n- Success/failure messages contain no raw value, secret-derived content, or unsafe backend detail.\n- Telegram adapter tests cover happy path, wrong user/chat, cancellation, expiry, duplicate messages, malformed input, and delivery failure.","status":"closed","priority":1,"issue_type":"task","created_at":"2026-08-14T21:58:12Z","updated_at":"2026-08-18T15:51:16Z","closed_at":"2026-08-18T15:51:16Z","close_reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.","external_ref":"https://github.com/samcharles93/archie-core/issues/507","source_system":"github:https://github.com/samcharles93/archie-core/issues/507:507","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942391-12-7988cdca","title":"Add engine write/update capability for remote secret values","description":"## Scope\nExtend the secret-engine contract/registry with an explicit write or update operation for engines that support accepting a value remotely. Preserve the existing resolve-only behaviour for engines that cannot write.\n\nImplement capability discovery, reference validation, engine-specific error mapping, and safe handling of external engine credentials. Do not make a generic remote write path that can silently overwrite arbitrary references.\n\nCoordinate with #433 and the existing engine work (#430-#432); link dependencies in the implementation PR rather than duplicating them.\n\n## Acceptance criteria\n- Engines explicitly declare remote-write support and the allowed operation(s).\n- Target references are validated and scoped before any value is sent.\n- Unsupported, unauthorized, invalid-reference, conflict, timeout, and backend-unavailable errors are distinguishable to the caller but never disclose secret material.\n- Existing resolve calls and non-writing engines remain compatible.\n- Tests use fakes/httptest and prove the raw value is sent only to the selected engine over the intended boundary.","status":"closed","priority":1,"issue_type":"task","created_at":"2026-08-14T21:58:12Z","updated_at":"2026-08-18T15:51:16Z","closed_at":"2026-08-18T15:51:16Z","close_reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.","external_ref":"https://github.com/samcharles93/archie-core/issues/506","source_system":"github:https://github.com/samcharles93/archie-core/issues/506:506","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942345-10-50a04c62","title":"Define remote secret-input contract, authorization, and lifecycle","description":"## Scope\nDefine the channel-neutral capability for initiating and completing a remote secret-input session. Model target engine/reference, authenticated actor, originating channel/session, challenge state, expiry, cancellation, one-time consumption, and redacted outcomes.\n\nThe flow must be separate from normal model-generated tool calls: the raw value must not enter the LLM prompt, tool transcript, ordinary event stream, or persistent chat record.\n\n## Acceptance criteria\n- Typed interfaces cover begin, inspect/choose target, submit, cancel, expire, and status/result.\n- Authorization is explicit and checked at initiation and submission; sessions are bound to actor and channel/session context.\n- Expiry, cancellation, replay, concurrent submission, and restart behaviour are defined and tested.\n- Secret-bearing data has a documented in-memory lifetime and is zeroed/released as far as Go semantics permit.\n- No raw value appears in errors, structured logs, metrics, traces, events, or persisted state.","status":"closed","priority":1,"issue_type":"task","created_at":"2026-08-14T21:58:11Z","updated_at":"2026-08-18T15:51:16Z","closed_at":"2026-08-18T15:51:16Z","close_reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.","external_ref":"https://github.com/samcharles93/archie-core/issues/505","source_system":"github:https://github.com/samcharles93/archie-core/issues/505:505","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942324-9-509793a0","title":"[EPIC] Secure remote secret input through mobile channels","description":"## Goal\nAllow an authenticated user to provide secret values remotely to an Archie secret engine, with a mobile-first interaction model. The primary use case is an operator using Telegram or another supported mobile channel to complete setup or repair a secret without SSH, editing TOML, or exposing the value in ordinary chat history.\n\nThe feature must extend the existing secret-engine architecture rather than bypass it. Secret values are submitted to a named engine/secret reference, validated by the engine, and then stored or forwarded according to that engine's contract.\n\n## Scope\n- A provider-neutral remote secret-input capability and lifecycle.\n- Mobile-first UX, initially through the existing Telegram channel abstraction.\n- Secure challenge/session handling, authorization, expiry, cancellation, and one-time submission semantics.\n- Engine-side write/update support for engines that can accept remote values.\n- Safe setup/status feedback without echoing secret material into messages, logs, telemetry, prompts, or persistent transcripts.\n- Documentation and tests for operator workflows and threat boundaries.\n\n## Non-goals\n- Making secret values readable through chat after submission.\n- Storing raw secrets in Archie state, issue bodies, ordinary chat history, or generated configuration logs.\n- Bypassing an external engine's own policy, ACLs, or encryption.\n- Supporting every channel or secret backend in the first implementation; capability discovery must make support explicit.\n\n## Definition of done\n- A user can initiate a remote secret-input flow from a mobile channel, select the target engine/reference, submit the value, and receive only a redacted success/failure result.\n- The flow is explicitly authorized, bound to the initiating user/session, expires, can be cancelled, and cannot be replayed.\n- Secret input is never passed through the normal model prompt/tool transcript path and is not logged or persisted in plaintext.\n- Engines advertise whether remote writes are supported; unsupported engines fail clearly without weakening resolution behaviour.\n- At least the intended initial engine(s) have an end-to-end tested write path, with external engine credentials handled through existing secret configuration.\n- Tests cover abuse and failure paths, and the mobile operator documentation is complete.\n\nRelated existing work: secret-engine registry #429, provider/consumer SecretRef migration #433, and engine plugins #430-#432.","status":"closed","priority":1,"issue_type":"epic","created_at":"2026-08-14T21:58:10Z","updated_at":"2026-08-17T14:22:10Z","closed_at":"2026-08-17T14:22:10Z","close_reason":"Pivoted after design review: value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain. The real gap was engine refresh (bws caches once per process). Replaced by fresh-resolving sops/vault/age engines (beads #409/#411/age). Remote secret-input contract kept as design doc in #505; value-entry UX deferred until a writable engine without a mobile path exists.","external_ref":"https://github.com/samcharles93/archie-core/issues/504","source_system":"github:https://github.com/samcharles93/archie-core/issues/504:504","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-5efv","title":"telegram: split long replies on rune boundaries, not 4000 bytes","description":"splitLongMessage slices line[i:end] on byte offsets (messageMaxLen = 4000 bytes). Any line ≥ 4001 bytes containing multi-byte UTF-8 cuts mid-rune (e.g. 1334 × '界': parts[0] ends on a lead byte, parts[1] starts with continuation bytes). finalize feeds these parts to EditMessageText, and on edit rejection the fallback re-splits the same content into the same invalid chunks — the authoritative reply arrives mangled or not at all for exactly the long, non-ASCII replies the split path exists to serve. All existing tests use ASCII input only.\n\nFailure: a model produces a long answer with CJK/emoji or a base64 blob crossing a 4000-byte boundary; Telegram rejects the malformed part and the user gets the stale live frame plus a corrupted reply.","design":"Split on rune boundaries (iterate runes, accumulate up to messageMaxLen runes). Add a test with multi-byte input crossing the boundary asserting every part is valid UTF-8 and no part exceeds the bound.","acceptance_criteria":"A long CJK/emoji/base64 reply splits into valid, bounded parts; test covers non-ASCII content crossing the boundary.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:23Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:07:35Z","started_at":"2026-08-14T14:53:28Z","closed_at":"2026-08-14T15:03:28Z","close_reason":"Fixed in internal/channels/telegram/live.go and telegram.go: finalize/abandon strip context cancellation before sending (mirroring each other), ToolCall escapes Markdown metacharacters via bot.EscapeMarkdown, splitLongMessage splits on rune boundaries. All new/changed tests verified red-then-green; task check clean; adversarial review pass found no blocking issues.","external_ref":"https://github.com/samcharles93/archie-core/issues/482","labels":["code-review","telegram"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-7o11","title":"telegram: escape tool output before composing it into the rich Markdown body","description":"The tool line (🔧 name + params + ' — ' + Summary()) is composed unescaped into the same InputRichMessage{Markdown: body} as the model reply (live.go:172). Summary() returns the tool's raw first output line (no escaping), and the JSON params can carry '*' / '_' / backticks. A single stray markdown metacharacter unbalances the rich body: mid-stream it lags a frame, but in the final message the rich edit is rejected and the plain-text fallback is terminal — permanently stripping the model reply's markdown formatting. go-telegram/bot v1.23.0 ships EscapeMarkdown; nothing in the repo uses it.\n\nFailure: the shell tool prints a grep hit containing '*' or '_'; the finished answer's bold/italic/code blocks render as raw markers, and the tool line itself displays as broken markup.","design":"Escape the tool name/params/summary (or the whole tool line) before inserting it into the Markdown body, while preserving the model reply's own markdown — the two share one body, so escaping must be scoped to the tool line only.","acceptance_criteria":"A tool whose output contains *, _, or backticks does not break the final message's markdown; a test feeds such output through a live reply and asserts the finished body still renders.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:09Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:07:35Z","started_at":"2026-08-14T14:53:28Z","closed_at":"2026-08-14T15:03:28Z","close_reason":"Fixed in internal/channels/telegram/live.go and telegram.go: finalize/abandon strip context cancellation before sending (mirroring each other), ToolCall escapes Markdown metacharacters via bot.EscapeMarkdown, splitLongMessage splits on rune boundaries. All new/changed tests verified red-then-green; task check clean; adversarial review pass found no blocking issues.","external_ref":"https://github.com/samcharles93/archie-core/issues/483","labels":["code-review","streaming","telegram"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-g7tm","title":"telegram: finalize the reply through a live context, matching the error branch","description":"The success path calls live.finalize(turnCtx, reply) with the raw cancellable turn context (telegram.go:582), while the error branch two lines above deliberately uses context.WithoutCancel(turnCtx). If /stop lands during finalize, the rich edit, the plain-text retry, and the split-send fallback all abort with context.Canceled (go-telegram/bot builds requests with NewRequestWithContext), so the authoritative reply is never delivered and the live message keeps the ▌ cursor forever. The reply is persisted to the ledger, so the loss is delivery-level — but the user sees a frozen half-answer.\n\nFailure: a long tool-using turn is /stop-ped as it completes; turnCtx is cancelled mid-finalize; every send fails on the dead context; the chat shows the last live frame with a blinking cursor and no final answer.\n\nFound by code-review of PR #476 (feat/467, merged 98e8dda).","design":"live.finalize(context.WithoutCancel(turnCtx), reply) — the one-liner the error branch already uses. Consider making finalize take a live context internally rather than trusting each caller to remember.","acceptance_criteria":"A /stop landing mid-finalize still delivers the authoritative reply and drops the cursor; a test covers the cancellable-context finalize path.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:08Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:07:36Z","started_at":"2026-08-14T14:53:28Z","closed_at":"2026-08-14T15:03:28Z","close_reason":"Fixed in internal/channels/telegram/live.go and telegram.go: finalize/abandon strip context cancellation before sending (mirroring each other), ToolCall escapes Markdown metacharacters via bot.EscapeMarkdown, splitLongMessage splits on rune boundaries. All new/changed tests verified red-then-green; task check clean; adversarial review pass found no blocking issues.","external_ref":"https://github.com/samcharles93/archie-core/issues/484","labels":["code-review","streaming","telegram"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tb3a","title":"Fix streaming review blockers for inline tool calls","description":"Resolve the four evidence-gated findings in merged inline tool-call streaming: preserve the authoritative Telegram reply when final edits fail; keep Telegram network I/O off the model FullStream consumer and cancellable; correlate tool inputs with results and render a bounded redacted parameter summary; snapshot show_tool_calls per live reply to avoid reload races. Add regression tests for every path and run task check plus lint/race validation.","acceptance_criteria":"Regression tests fail on the merged implementation and pass after the fix. Final edit failure falls back to normal split delivery. Delta and ToolCall callbacks do not wait on Telegram HTTP and stop cancels in-flight rendering. Completed tool events include bounded redacted parameters correlated by tool-call ID. Reload cannot race an in-flight reply's show_tool_calls setting. task check passes, golangci-lint reports no new findings, and focused race tests pass.","notes":"Implemented in worktree /tmp/archie-core-tb3a on branch fix/archie-core-tb3a. Added cancellable async Telegram rendering, final edit failure fallback through normal split delivery, call-ID-correlated bounded conservative parameter summaries, atomic per-reply show_tool_calls snapshots, SSE/UI parameter rendering, rebuilt ui/dist, and regression tests. Validation: GOFLAGS=-buildvcs=false task check passed; golangci-lint --new-from-rev=HEAD ./... reported 0 issues; focused race suite passed; fresh adversarial reviewer reported PASS with zero findings. Plain task check is blocked in linked worktrees by Go VCS stamping exit 128, hence buildvcs override.\n2026-08-24 reconciliation: the close reason's 'worktree left uncommitted' is stale. The work did land on main via ba33527 (Merge pull request #477 from samcharles93/fix/archie-core-tb3a); verified on main: gateway/stream.go sensitiveParameterKey+redactToolParameters, telegram/live.go per-reply showToolCalls snapshot, webui/api_chat.go gating. The /tmp/archie-core-tb3a worktree and its branch are gone, as expected.\n","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-13T18:05:35Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:29:09Z","started_at":"2026-08-13T18:05:39Z","closed_at":"2026-08-13T18:35:26Z","close_reason":"Completed and independently reviewed; worktree left uncommitted per conservative repository policy.","external_ref":"https://github.com/samcharles93/archie-core/issues/485","dependency_count":0,"dependent_count":0,"comment_count":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-8cda.4","title":"Phase 2: Extract the State Store Service","description":"Second extraction in the resolved order. Expose internal/store as its own\nservice behind its narrow contracts over gRPC. This generalises the\npattern already in production: internal/storerpc proxies\nstore.WorkflowStore to the archie-agent container over NATS request/reply\ntoday (see resolved open question #4).\n\nPer question #4's resolution: ONE State Store service owns the existing\nsingle SQLite file (archie.db) behind narrow typed contracts (TaskStore,\nCaptureStore, MappingStore, BindingStore, WorkflowStore, BindingDispatcher,\nBindingTaskCreator from internal/store/interface.go). No physical\ndatabase-per-service split -- one store means no distributed-transactions\nproblem, and per the team-topology rule of thumb a solo maintainer gets no\nautonomy benefit from physical isolation. The Gateway's already-separate\nsession SQLite is unaffected and stays Gateway-owned.\n\nMigration path (from the research doc, in order of blast radius):\n1. Ratify internal/store/interface.go's narrow interfaces as the State\n Store contract surface (already true in code; authority decision only).\n2. Generalise internal/storerpc from proxying only WorkflowStore to\n serving the full narrow contract set, and move it from NATS\n request/reply to gRPC (per the PRD, gRPC is the sync transport).\n3. Swap direct internal/store imports in internal/webui,\n internal/domain/workflow, and the intake/binding paths onto the\n contract, starting with low-touch reads (CaptureStore, MappingStore,\n BindingStore), then WorkflowStore, then the TaskStore lifecycle\n surface.\n4. Stand up internal/store as archie-state-store (gRPC server over the\n same archie.db file); delete the in-process imports once every\n consumer speaks the contract.\n\nDepends on Phase 1 (Gateway extraction) per the resolved extraction\norder -- Gateway proves the process-split + gRPC playbook first.\n\nFull reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#4\nand #1 (Phase 2 section).","acceptance_criteria":"- New cmd/archie-state-store binary serving TaskStore, CaptureStore,\n MappingStore, BindingStore, WorkflowStore, BindingDispatcher, and\n BindingTaskCreator over gRPC, all backed by the single existing\n archie.db SQLite file (no physical file split).\n- internal/storerpc generalised (or a successor package) to serve the\n full narrow contract set, migrated from NATS request/reply to gRPC.\n- internal/webui, internal/domain/workflow, and the intake/binding paths\n no longer import internal/store directly -- they call the State Store\n contract.\n- Each contract swap follows the local-adapter + gRPC-adapter +\n bufconn-conformance-suite shape from Phase 0, with a same-commit flip\n to mode = \"remote\" once archie-state-store is standing.\n- The Gateway's own session SQLite is untouched and remains\n Gateway-owned.\n- task check passes; a dashboard/combined view that reads across\n multiple contracts (task/event/capture) still works correctly through\n the new contract calls.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T06:06:01Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:06:01Z","dependencies":[{"issue_id":"archie-core-8cda.4","depends_on_id":"archie-core-8cda","type":"parent-child","created_at":"2026-09-05T06:06:01Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-8cda.4","depends_on_id":"archie-core-8cda.3","type":"blocks","created_at":"2026-09-05T06:06:59Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8cda.3","title":"Phase 1: Extract the Gateway Service","description":"First real process extraction in the resolved extraction order (open\nquestion #1). Stand up archie-gateway as its own binary serving\nChatContract over gRPC, using its existing isolated session SQLite\n(internal/gateway/session_store_sqlite.go) and its existing store\nadapters (the Gateway does not import internal/store today --\nmain.go:139, gateway/tasks.go:44 -- it consumes narrow contracts\nStatusReader/TaskCreator/TaskLister/TaskController/AgentReader that\ninternal/app/archied adapts).\n\nMigrate consumers onto ChatContract over gRPC:\n- UI (internal/webui) stops holding gateway.Router/SessionStore/Turns/\n ModelManager/PersonaRegistry in-process and calls ChatContract instead.\n- Messaging/Telegram's task-action path\n (chatTaskActorAdapter.ApplyChatTaskAction,\n internal/app/archied/main.go:655) stops detouring through webui's\n handleTaskAction HTTP handler (internal/webui/api_tasks.go:136,\n mounted at server.go:294) and calls ChatContract directly.\n\nWhy the Gateway goes first (not the generic \"leaf first\" advice): it is\nalready store-decoupled and already owns isolated session data, making\nit both the stickiest capability (everything routes through it) and the\none with a ready seam -- extracting it first also unblocks UI (the most\nentangled consumer), which is the PRD's ultimate goal. This is also the\noperations dry-run for the gRPC/discovery playbook.\n\nDepends on Phase 0 (the ChatContract seam, local + gRPC adapters, and\nconformance suite must exist and be usable before the network path\nbecomes production).\n\nFull reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#1\n(Phase 1 section).","acceptance_criteria":"- New cmd/archie-gateway binary serving ChatContract over real gRPC\n (using the generated server/client from Phase 0's proto definition).\n- Same-commit deletion of the in-process ChatContract serving path per\n question #3's resolved mechanism (no dual-live window); consumers\n flipped to mode = \"remote\" for ChatContract in that same commit.\n- Gateway's existing session SQLite and store adapters move with it into\n the new binary; no other domain's data moves.\n- internal/webui's chat path calls ChatContract over gRPC; it no longer\n holds gateway.Router/SessionStore/Turns/ModelManager/PersonaRegistry\n struct fields directly (closes verified coupling #2 from the PRD).\n- Messaging/Telegram's task-action path (pause/resume/abandon) calls\n ChatContract directly; the webui HTTP detour\n (chatTaskActorAdapter.ApplyChatTaskAction -\u003e handleTaskAction) is\n removed (closes verified coupling #1 from the PRD).\n- A deployment profile or docs update reflecting the new archie-gateway\n binary (deployments/ per this repo's existing profile conventions).\n- task check passes; the daemon and archie-gateway both build; an\n end-to-end smoke path (chat turn through the new gRPC hop) is\n exercised.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T06:05:46Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:05:46Z","dependencies":[{"issue_id":"archie-core-8cda.3","depends_on_id":"archie-core-8cda","type":"parent-child","created_at":"2026-09-05T06:05:46Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-8cda.3","depends_on_id":"archie-core-8cda.2","type":"blocks","created_at":"2026-09-05T06:06:59Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-14cs","title":"Resolve pre-existing task check gate blockers (lint + jsdom)","description":"Two pre-existing blockers keep the authoritative task check gate red, independently of the progressive-tool-disclosure wiring (issue #167):\n\n1. golangci-lint: 5 issues in files untouched by #167:\n - internal/app/archied/bootstrap.go:316 (cyclop: setupObservability complexity 16 \u003e 15)\n - internal/app/archied/bootstrap.go:405 (nestif)\n - internal/app/archied/telegram_setup_test.go:64 (usetesting: os.Setenv -\u003e t.Setenv)\n - internal/releaseupdate/install_script_test.go:143,160 (noctx: exec.Command -\u003e CommandContext)\n\n All 5 confirmed reproducible on clean main (git stash comparison) and match the documented non-green lint baseline in the archie-build-and-env skill.\n\n2. task test:ui fails because ui/node_modules is not installed (ERR_MODULE_NOT_FOUND: jsdom, declared at ui/package.json:16). Needs npm install before the ui test can run.\n\nBlockers are environmental/baseline, not introduced by the tool-disclosure wiring.\n","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T03:25:29Z","created_by":"Sam Catlow","updated_at":"2026-09-05T07:10:43Z","closed_at":"2026-09-05T07:10:43Z","close_reason":"Closed","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.22","title":"eda: carry originating task identity on DispatchInput (gap-2 prereq)","description":"Prerequisite for the t2db.17 idempotency resolution. DispatchInput (internal/domain/eda/playbook/playbook.go:187) is {Labels, Kind, Event} with no task identity, so a playbook run cannot derive an event_id for a playbook_dispatches ledger key. Thread the originating task's identity (store.Task.ID, or the TaskEnvelope idempotency key that produced it). IMPORTANT: there is NO production caller of Store.Dispatch today -- DispatchInput is only constructed in tests -- so confirm which identity is actually available at the real Dispatch call site before fixing the field type; do not assume store.Task.ID is available at label/kind classification time (it is not: pollNATS/classify produces the envelope before any task row exists, so the TaskEnvelope.IdempotencyKey string is the identity available there).","design":"Add an identity field to DispatchInput, populated by the (currently nonexistent) production caller. Decide field type against the discovery-path evidence: pollNATS (internal/daemon/daemon.go:844) and the webhook receiver (receiver.go:243) both compute kind/labels from a TaskEnvelope BEFORE any store.Task row exists, and TaskEnvelope.IdempotencyKey() returns 'archie:owner/repo/number' -- so a string identity (the idempotency key) is the available, stable value at the dispatch point, not a store.Task.ID int64. Add a test proving DispatchInput carries it end to end; wire the real production caller only when the coordinator lands.","acceptance_criteria":"DispatchInput carries the originating task's identity (typed as decided against evidence). A test demonstrates the identity is present on the input and reaches the key-derivation path. No production dispatch caller is wired in this ticket (none exists today). task check passes.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","estimated_minutes":30,"created_at":"2026-09-04T17:07:09Z","created_by":"Sam Catlow","updated_at":"2026-09-04T17:10:44Z","closed_at":"2026-09-04T17:10:44Z","close_reason":"Implementation complete and gate-verified for its scope. Playbook gains ID (path-relative) + Version (sha256 content hash), populated in loadOne; DispatchInput gains TaskID string carrying TaskEnvelope.IdempotencyKey(), per evidence that the discovery point computes kind/labels before any store.Task row exists. Red-green verified; gofumpt/vet/build/golangci-lint clean for the package. NOTE: task check has 5 lint failures PRE-EXISTING at HEAD in unrelated files (bootstrap.go cyclop/nestif, install_script_test.go noctx, telegram_setup_test.go usetesting) -- not caused by this change. Forced close because the earlier blocked-by: t2db.17 dependency is inverted -- .17 is doc-only sign-off; these are its implementation prereqs, not gated on it.","dependencies":[{"issue_id":"archie-core-t2db.22","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-04T17:07:09Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.22","depends_on_id":"archie-core-t2db.17","type":"blocks","created_at":"2026-09-04T17:07:09Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.21","title":"eda: thread Playbook ID and Version for idempotency-ledger keying (gap-2 prereq)","description":"Prerequisite for the t2db.17 idempotency resolution. The shipped Playbook struct (internal/domain/eda/playbook/playbook.go) is {Trigger, Actions} with no ID and no Version, so a playbook_dispatches ledger keyed on (playbook_id, playbook_version, event_id) cannot be built. Add ID (stable path-relative identifier) and Version (content hash of the loaded file, recomputed on every load), both populated at load time. Mirror Binding.Version's purpose: pin dispatched-run provenance to the exact definition that was active when it fired.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","estimated_minutes":30,"created_at":"2026-09-04T17:07:01Z","created_by":"Sam Catlow","updated_at":"2026-09-04T17:10:44Z","closed_at":"2026-09-04T17:10:44Z","close_reason":"Implementation complete and gate-verified for its scope. Playbook gains ID (path-relative) + Version (sha256 content hash), populated in loadOne; DispatchInput gains TaskID string carrying TaskEnvelope.IdempotencyKey(), per evidence that the discovery point computes kind/labels before any store.Task row exists. Red-green verified; gofumpt/vet/build/golangci-lint clean for the package. NOTE: task check has 5 lint failures PRE-EXISTING at HEAD in unrelated files (bootstrap.go cyclop/nestif, install_script_test.go noctx, telegram_setup_test.go usetesting) -- not caused by this change. Forced close because the earlier blocked-by: t2db.17 dependency is inverted -- .17 is doc-only sign-off; these are its implementation prereqs, not gated on it.","dependencies":[{"issue_id":"archie-core-t2db.21","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-04T17:07:01Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.21","depends_on_id":"archie-core-t2db.17","type":"blocks","created_at":"2026-09-04T17:07:01Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-wdn0","title":"Reconcile beads\u003c-\u003eGitHub issue state after cross-machine sync","description":"After the 2026-09-03 helix/carina reconciliation, bead statuses are authoritative locally but GitHub was never reconciled. Walk closed beads against gh issue list --state all via external_ref and push the differences. Per prior incident notes: bd github push takes ONE id per invocation (multiple ids silently no-op and exit 0), and identical updated_at timestamps make sync skip an issue forever -- close directly with gh issue close in that case.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-03T12:28:29Z","created_by":"Sam Catlow","updated_at":"2026-09-03T12:28:29Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-mxls","title":"chat: /agents command is permanently unconfigured in production","description":"internal/gateway.Router.Agents (AgentReader interface, AgentInfo{ID,Title,Status,Identity}) backs the /agents command (handleAgents, gateway.go:1127), and /agents is registered and advertised: in gateway.go's localCommands/localCommandSpecs (description: 'List tasks currently being worked'), and in internal/channels/telegram/commands.go's gatewayCommandSpecs (same description, published to Telegram's command menu and /help).\n\nVerified via grep across internal/: Router.Agents is NEVER assigned outside of gateway_test.go's fakeAgentReader. None of the four composition-root call sites that build a Router (bootstrap.go's web/email/webhook routers, telegram_setup.go's buildTelegramRouter) ever set router.Agents. So in every real deployment, typing /agents in any channel returns the hardcoded fallback: 'Agent listing is not configured.' -- despite Telegram advertising it in its command menu with a description implying it works.\n\nFound while implementing archie-core-wp9s (the /status vs /tasks split): the new /tasks command (gateway.ChatTaskLister-backed) covers almost exactly what /agents' AgentInfo{ID,Title,Status,Identity} shape was meant to show, just fuller (adds workflow/stage/age/park-reason). AgentReader/AgentInfo appear to be an earlier, abandoned attempt at the same feature that was never connected during wiring.\n\nSam's call, not resolved here: (a) wire AgentReader to a real implementation (e.g. an adapter over the same ListChatTasks path /tasks now uses, if /agents is meant to mean something distinct from /tasks -- e.g. actively-executing containers rather than all non-terminal store tasks), (b) delete /agents (AgentReader, AgentInfo, handleAgents, both command-spec registrations, and their tests) now that /tasks exists and covers the same ground, or (c) something else entirely if 'agents' was meant to be a different concept than 'tasks'. See docs/prds/status-health-surface.md's note on this for the /tasks cross-reference.","acceptance_criteria":"A decision is recorded (wire, delete, or redefine) and /agents' advertised behavior in Telegram's menu/help matches what it actually does when invoked -- no command may be discoverable and described as functional while permanently returning a not-configured placeholder.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-02T21:17:31Z","created_by":"Sam Catlow","updated_at":"2026-09-02T21:17:31Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.20","title":"eda: LSP/serve mode for cmd/archie-playbooks","description":"Second entrypoint of the gopls-shaped standalone binary from t2db.12 (lint mode already shipped). Sam explicitly kept this in scope, not deferred, because it's the same schema source as the linter, just a different consumer -- the design doc's shared-package, thin-consumer principle.\n\nGrounded by a crew investigation pass (2026-09-03): the loader decodes with yaml.Unmarshal into a plain map, which discards line numbers -- today's lint findings are file-granular only. A useful LSP (hover/completion/inline errors) needs real positions, so the yaml.Node decoding upgrade is a practical prerequisite, not a nice-to-have. internal/domain/eda/expr's Compile/Eval already return structured errors that should map cleanly to diagnostics -- confirm this rather than re-deriving error shapes.","design":"Two-part scope, decide whether to split into two tickets or do both together once you've read the code:\n1. yaml.Node decoding upgrade: replace the plain-map yaml.Unmarshal decode path (internal/domain/workflow/routing.go -- three call sites at time of writing, all doing 'var raw map[string]string; yaml.Unmarshal(data, \u0026raw)') with yaml.Node-based decoding that retains line/column info, without changing any existing collision-detection behavior.\n\nVERIFIED FEASIBLE, concrete shape (2026-09-03): gopkg.in/yaml.v3's Node type has Line/Column fields populated directly by the decoder (confirmed in the vendored source). For a mapping node (Kind == MappingNode), Content is a flat []*Node alternating key-node, value-node pairs -- so decoding into *yaml.Node instead of map[string]string gives Content[i].Line for the i-th key's line number directly, no manual line-counting needed. The upgrade is: yaml.Unmarshal(data, \u0026node) into a *yaml.Node instead of the map, then walk node.Content in pairs extracting key.Value/value.Value (same strings as today) plus key.Line (new). This is a pure additive capability -- existing collision error MESSAGES should stay byte-identical where line info isn't yet surfaced in them, add line numbers to the error format once available. Do not change collision-detection LOGIC, only the decode representation.\n\n2. serve/lsp command: add a new entry to cmd/archie-playbooks's existing command table (do not restructure -- t2db.12 built it explicitly to take this addition without restructuring, confirmed by reading cmd/archie-playbooks/main.go's commands map). Scope: a minimal LSP surface (diagnostics at minimum; hover/completion if straightforward) over the same compile/validate path the lint command already uses. Weigh a tiny hand-rolled LSP protocol implementation (fits organisation.md's thin cmd/ rule and the narrow-capability-family principle) against pulling in an LSP library -- vet any new dependency via the vetting-dependencies skill before adding it, same rigor as the CEL decision (docs/prds/eda-playbook-engine.md's resolved open question 1) -- this is a real, undecided choice, not preempted here.","acceptance_criteria":"cmd/archie-playbooks gains a serve (or lsp) subcommand alongside lint, using the same underlying compile/validate calls -- no second validation path. Diagnostics report file:line where the yaml.Node upgrade provides it. Existing lint-mode tests and behavior are unchanged (regression-tested). task check passes.","notes":"Full vetting record for sourcegraph/jsonrpc2, 2026-09-03 (same rigor as the approved cel.dev/cel-go decision):\n\n- Security: zero advisories on record (GitHub Advisory Database, queried directly). License: MIT (compatible).\n- Maintenance: genuinely active -- commits within the last month (Aug 2026), real CI hygiene work (not a dead repo with a stale README). Not archived (unlike sourcegraph/go-lsp, the other candidate, which IS archived and was ruled out).\n- Dependency footprint: measured directly (not assumed) -- importing only the jsonrpc2.Conn surface pulls in exactly ONE dependency, no gorilla/websocket at all (go.sum showed a single entry). websocket is a lazy/optional dependency of the library, only pulled in if its WS-transport-specific APIs are actually called -- a stdio-only LSP transport never touches it.\n- Binary size cost: measured directly, same baseline methodology as the CEL vetting -- a minimal Go binary baseline was 2,343,283 bytes; adding jsonrpc2 (importing Conn) measured 2,715,265 bytes. Cost: +371,982 bytes (~0.36MB). Far lighter than CEL's +13MB, as expected for a narrow JSON-RPC engine vs. a full expression-language runtime.\n\nVerdict: sourcegraph/jsonrpc2 clears vetting cleanly -- safe, cheap, active, correctness-sensitive-and-worth-depending-on (same reasoning as CEL: reimplementing JSON-RPC request/response ID correlation by hand is a real correctness surface, not free). This is a complete, ready-to-approve recommendation, not yet approved -- do not add the dependency or start implementation until Sam signs off, miLine truncated
|
||||
{"_type":"issue","id":"archie-core-t2db.19","title":"eda: scope Channel and Forge action positions (investigation, blocked on execution-time gaps)","description":"Investigation ticket -- decide the typed-contract shape for the two remaining named action positions (Channel, Forge) before implementing either. Blocked on archie-core-t2db.17 (idempotency) since both are naturally side-effecting positions; investigation/scoping can proceed now, implementation cannot land before .17 resolves.\n\nGrounded by a crew investigation pass (2026-09-03): Channel already exists as internal/channels.Channel (embeds gateway.Gateway + ConfigSchema/ValidateConfig, telegram/email/webhook implementations registered at daemon startup). Forge already exists as internal/forge.Forge = IssueForge + PullRequestForge + RepoForge, with New(...) switching on github/gitea/none; the daemon poller currently special-cases forge operations directly rather than through any addressable position.","design":"See docs/prds/channel-forge-positions.md (committed 2026-09-03). Forge is fully scoped and ready to implement once t2db.17 lands: native-Go-by-name (not Module-kind) over the existing internal/forge.Forge interface, close-issue/link-branch as the safe first operations, create-pr deferred. Channel is NOT resolved -- the crew investigation's assumption that channels.Channel has an addressable send capability is FALSE (verified: only Name/Start/Stop + config validation exist, no Send method anywhere in internal/channels or internal/gateway). This is now an open product/architecture decision for Sam: whether 'Channel action' means (1) a new playbook-scoped notification capability distinct from the interactive chat channels, or (2) reusing the interactive channels with some new conversation-scoping mechanism for a non-chat trigger. Do not implement a Channel position until Sam decides which.","acceptance_criteria":"A design-doc addition (new docs/prds/ file or a section in eda-playbook-engine.md, your call which fits better -- state why) resolving: typed-contract shape for each position, Args/Result shapes, and the host-access/resolution mechanism. No implementation in this ticket.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T18:12:40Z","created_by":"Sam Catlow","updated_at":"2026-09-02T18:15:31Z","dependencies":[{"issue_id":"archie-core-t2db.19","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T18:12:40Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.19","depends_on_id":"archie-core-t2db.17","type":"blocks","created_at":"2026-09-02T18:12:40Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.16","title":"eda: reduce complexity in bootstrap.go loadWorkflows and routing.go LoadPlaybookDirs","description":"task check now runs golangci-lint (Sam's explicit requirement, 2026-09-03 -- catch lint regressions as part of the definitive gate, not just fmt/vet/build/test). First run surfaced two real findings, both accumulated debt from this session's own EDA slices, not pre-existing:\n\n1. internal/app/archied/bootstrap.go:647 loadWorkflows -- cyclomatic complexity 17, max 15 (cyclop). Grew incrementally across t2db.9 (kindWorkflows), t2db.10 (labelWorkflows), t2db.11 (PlaybookDirs merge), t2db.15 (EDAPlaybookDir) -- each addition was small, the function as a whole crossed the threshold.\n2. internal/domain/workflow/routing.go:103 LoadPlaybookDirs -- cognitive complexity 52, max 30 (gocognit), from t2db.11's directory-merge loader (kind-vs-label detection, per-file and cross-file collision checks all inline).\n\nRoot-cause fix required, not suppression: no //nolint. Extract cohesive sub-steps into named helper functions -- this is exactly the kind of case AGENTS.md's Architectural Simplicity rule describes (prefer a clean extraction over papering past a threshold).","design":"For loadWorkflows: extract the four independent load-and-set steps (kind-file load, label-file load, playbook-dirs load+merge, EDAPlaybookDir load) into named helpers the top-level function calls in sequence, each returning its own error for the existing log-and-abort pattern. Do not change the log-and-abort error-handling shape or field names.\n\nFor LoadPlaybookDirs: split the per-file parsing loop's kind-detection-vs-label-detection-vs-collision-check logic into a couple of named helpers (e.g. classifyBinding, checkCollision) called from the main loop, keeping the existing collision error messages and behavior byte-identical -- this is a pure refactor, not a behavior change.","acceptance_criteria":"golangci-lint run ./... reports zero cyclop/gocognit findings on these two functions. All existing tests for workflow.LoadPlaybookDirs, kindWorkflows, labelWorkflows, and bootstrap's loadWorkflows-adjacent behavior pass unchanged (byte-identical collision error messages -- diff the exact strings, do not just check err != nil). task check (now including lint) passes fully.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T18:10:21Z","created_by":"Sam Catlow","updated_at":"2026-09-02T20:42:32Z","closed_at":"2026-09-02T20:42:32Z","close_reason":"Both cyclop/gocognit findings resolved via pure extraction; golangci-lint run ./... reports 0 issues; go test ./... and task test:ui pass unchanged; task check green.","dependencies":[{"issue_id":"archie-core-t2db.16","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T18:10:21Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.15","title":"eda: playbook document + event coordinator, single-action workflow-kind dispatch","description":"Seventh slice of docs/prds/eda-playbook-engine.md. Builds the rich playbook document shape (trigger + ordered actions with CEL 'when') and an event coordinator that dispatches it -- the first real consumer of t2db.14's expr package. Scoped tightly to what's already safe per this doc's own gating:\n\n- Exactly ONE action per playbook in this slice, and it MUST be position: workflow. Reject (load failure) a playbook declaring more than one action, or an action whose position is module/channel/forge -- those remain blocked on the unresolved execution-time gaps (mid-run failure semantics, idempotency for non-workflow actions) per the 'Execution-time gaps' section. Do not relax this without Sam's sign-off -- this is the one hard boundary in this ticket, everything else is normal implementation judgment.\n- This is an ADDITIONAL loading path alongside the existing flat kind/label binding files (t2db.9/.10/.11). Do NOT modify workflow.Route(), workflow.workflowForLabels, or remove/change the existing single-file/multi-dir binding loaders. Migrating Route() onto the new mechanism is a separate, later, larger decision -- not in scope here.\n- Idempotency is free for this slice for the same reason it was free for t2db.13's first Module slice: a single workflow-kind action reaches the exact same workflow.Registry dispatch path that already carries TaskEnvelope's idempotency key. Nothing new to design here.","design":"Depends on archie-core-t2db.14 (expr package) -- do not start until it is closed and verified.\n\n1. Playbook document type (new package, likely internal/domain/eda/playbook -- confirm against organisation.md's layout rule, follow the log/logextract split precedent from t2db.13 if a generated component turns out to be needed, though this ticket is pure YAML+CEL, no Yaegi, so likely no extract package is needed here):\n - trigger: reuse existing workintake label/kind matching (do not invent a second label-matching mechanism -- workintake.SplitLabels/KindsForLabels already exist and are the one place this vocabulary lives).\n - actions: a list, validated at load to contain exactly one entry with position: workflow and a workflow registry name.\n - when: optional CEL expression string on the action, compiled via t2db.14's Compile() at load time -- a compile failure is a reported load failure (same collision-handling philosophy as t2db.9-.12), not a silently-skipped playbook.\n2. Event coordinator: loads playbook files from a configured directory (mirror the PlaybookDirs pattern from t2db.11 -- reuse its directory-scanning shape, do not reinvent), compiles every playbook's when expression at load (fail the whole load on any compile error, consistent with the existing reject-at-load rule), and at dispatch time: match trigger against an incoming task's labels/kind, evaluate when (if present) against a context of {event: \u003ctask's label/kind fields, whatever is cheaply available -- do not over-engineer the event shape beyond what a workflow-kind dispatch actually needs\u003e, actions: {} (empty -- no prior actions exist in a single-action playbook)}, and if the condition is true (or absent), dispatch to the named workflow via the existing workflow.Registry -- call the same registry lookup Route() already uses, do not duplicate dispatch logic.\n3. Config: a directory field for these playbook documents (distinct from t2db.11's PlaybookDirs, which holds flat binding files -- naming these two similar-but-different directories clearly is important; suggest something like EDAPlaybookDir or clarify in the field doc comment exactly how it differs from PlaybookDirs so a future reader isn't confused). If you judge the distinction is confusing enough that these should share one directory with two file shapes distinguished by content, flag that as a note in the PRD rather than silently deciding it -- but implement SOMETHING reasonable rather than blocking.\n4. Bootstrap wiring: load-and-abort on failure, matching every other slice's established pattern.\n5. Do NOT wire this into production task intake (daemon.go/pollNATS/publishTask) in this ticket -- prove the coordinator end-to-end with tests that construct a task-like input directly, the same way t2db.13 proved ModuleRegistry with direct Register/Invoke calls rather than full daemon wiring. Production wiring (making a real forge-triggered task actually flow through this coordinator instead of only workflow.Route()) is explicitly a follow-up ticket -- note it as such when you close this one.","acceptance_criteria":"A playbook YAML with trigger + one workflow-kind action + optional when loads successfully and dispatches to the correct registered workflow when trigger+when match. A playbook declaring 2+ actions is a reported load failure. A playbook with a non-workflow action position is a reported load failure. A whLine truncated
|
||||
{"_type":"issue","id":"archie-core-t2db.14","title":"eda: CEL expression environment (compile/validate at load, evaluate at dispatch)","description":"Sixth slice of docs/prds/eda-playbook-engine.md, implementing the 'Implementation placement' section of the resolved open question 1 (CEL). Builds internal/domain/eda/expr in isolation, no coordinator/dispatch yet -- mirrors how t2db.13 built ModuleRegistry as a standalone, fully-tested unit before anything consumed it.\n\nThis is pure infrastructure for the dispatch slice (t2db.15) that depends on it. No production wiring in this ticket.","design":"Package internal/domain/eda/expr (domain layer: no infrastructure imports).\n\nPer the resolved doc section, build:\n1. Environment construction: a CEL env declaring the two context roots -- 'event' as map(string, dyn), 'actions' as map(string, dyn). Cost limit (J5): pick a constant (start at 100,000, name it clearly as a tunable, e.g. DefaultCostLimit) -- exact value is a judgment call already flagged as tunable, don't block on picking the 'right' number.\n2. Compile/validate at load: a function taking a CEL expression string and returning (compiled program, error) -- a syntax error, a reference to an unknown root (anything other than event/actions), or exceeding the cost limit is a returned error, never a panic. This is what both the playbook loader (t2db.15) and the lint tool (t2db.12, follow-up integration is a SEPARATE ticket, do not touch cmd/archie-playbooks in this one) will eventually call.\n3. Evaluate at dispatch: a function taking a compiled program and a context (event map[string]any, actions map[string]map[string]any) and returning (value, error) -- CEL evaluation errors (missing field, wrong type against a dyn value) are returned as errors, never panics. Use CEL's own panic-free evaluation; do not add a recover() wrapper unless a test proves CEL itself can panic (verify this, don't assume).\n4. actions.\u003cid\u003e.result field-level typing (J1/context-conformance in the doc): NOT required in this ticket -- that needs the generated Module Result structs wired in as CEL type declarations, which only matters once a playbook can reference a prior action's result (t2db.15 is single-action, so there IS no prior action). Keep actions declared as dyn for now; note in a comment that per-kind typed declarations are follow-up work once multi-action playbooks exist.\n5. Dependency: add cel.dev/cel-go v0.32.0 (pinned) to go.mod -- this is the only new dependency, already vetted (see the resolved doc section's vetting record). Do not re-vet it.\n\nFollow docs/prds/eda-playbook-engine.md's reject-at-load philosophy throughout: anything not accepted by the schema is a reported error, never a silent default.","acceptance_criteria":"internal/domain/eda/expr exists with: environment construction, Compile(expr string) (returned type, error), Eval(program, ctx) (value, error). Table-driven tests cover: a valid boolean expression against event fields evaluates correctly; a syntax error is a Compile-time error; a reference to an unknown root (e.g. 'foo.bar') is a Compile-time error; evaluating against a missing event field does not panic (returns an error or CEL's documented behavior, whichever is correct -- verify against real CEL semantics, don't guess); an expression that would exceed the cost limit is rejected, not silently truncated. go.mod gains cel.dev/cel-go v0.32.0 only. task check passes.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T17:57:19Z","created_by":"Sam Catlow","updated_at":"2026-09-02T18:01:29Z","closed_at":"2026-09-02T18:01:29Z","close_reason":"Implemented and gate-verified as 33cdece (pushed to main). internal/domain/eda/expr: NewEnv (event+actions roots, DefaultCostLimit 100k), Compile (reject-at-load: syntax/unknown-root/type errors returned), Eval (panic-free, errors returned, ref.Val unwrapped to native). cel.dev/cel-go v0.32.0 direct dep, vetted per resolved doc (no re-vet). 9 tests pass, all verified against real CEL semantics (cost limits accrue on macros; == on missing key is false; unknown root rejected at compile). task check clean (113/113 UI).","dependencies":[{"issue_id":"archie-core-t2db.14","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T17:57:19Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.13","title":"workflow: Module position first slice (registry + side-effect-free 'log' kind)","description":"Fifth slice of docs/prds/eda-playbook-engine.md, implementing docs/prds/module-position.md's recommended first slice: prove schema -\u003e go:generate -\u003e Yaegi load -\u003e ModuleRegistry -\u003e playbook dispatch end to end with a side-effect-free action kind, before any kind with a real external effect (notify, image-gen, forge writes) is attempted -- those remain blocked on the parent doc's unresolved execution-time gaps (idempotency, mid-run failure), which this slice deliberately does not need.\n\nGeneralizes the fixed-signature, resolved-by-name Yaegi pattern already shipped for custom gates (internal/gate/gateeval) and workflow stage plugins (skillbuild) -- do not invent a new interpreter-construction or panic-recovery mechanism; reuse yaegiutil.New/Resolve/Safe directly.","design":"Per module-position.md:\n1. internal/domain/eda/module/log: hand-written schema source (Args/Result structs, SchemaVersion const), //go:generate yaegi extract -name logextract producing logextract.Symbols -- same shape as gateextract/wfextract.\n2. internal/domain/eda/module: ModuleRegistry with Register(kind, dir) and Invoke(ctx, kind, rawArgs map[string]any) (map[string]any, error). No generic Module interface with an any payload -- Invoke decodes rawArgs into the kind's generated Args struct before calling the resolved function; a shape mismatch is a reported failure per the existing 'schema defines the accepted message' rule, not a silent zero-value fill. Discovery/resolve mirrors gateeval.Evaluate's structure (read file -\u003e yaegiutil.New with that kind's symbols -\u003e yaegiutil.Resolve[func(Args) Result] -\u003e yaegiutil.Safe-wrapped call).\n3. Config: ModuleDir field mirroring PluginDir's shape and doc comment exactly (operator-trusted directory of Yaegi module implementations, empty means none loaded).\n4. Wire ModuleRegistry construction into daemon startup (bootstrap.go) alongside the existing PlaybookDirs/routing-file loading -- log-and-abort on load failure, matching the established pattern.\n5. Do NOT implement notify, image-gen, or any action kind with a real external side effect in this slice. Do NOT wire this into playbook YAML action dispatch yet if that requires resolving the data-flow/condition syntax (parent doc open question 1) -- confirm during implementation whether a minimal 'run this one module action, no chaining' dispatch is small enough to include, or whether registry+one-kind-loadable is itself the right slice boundary and dispatch is a follow-up ticket.","acceptance_criteria":"internal/domain/eda/module/log exists with a generated symbol table via go:generate yaegi extract (same tooling as wfextract/gateextract, verified by running go generate ./... and checking the output compiles). ModuleRegistry.Register discovers and loads a *.go file implementing the log kind's generated contract; Invoke calls it and returns a typed result decoded from the interpreted function's return value. A malformed or wrong-shaped args map is a reported error, not a panic or silent default. Config gains ModuleDir (empty by default, no behavior change). Trust boundary matches PluginDir/SecretEngineDir (operator-installed, in-process, daemon-privileged) -- not repository/task code. task check passes.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T17:11:21Z","created_by":"Sam Catlow","updated_at":"2026-09-02T17:35:28Z","closed_at":"2026-09-02T17:35:28Z","close_reason":"Implemented and gate-verified as d29c732 (pushed to main). ModuleRegistry (Register/Invoke, strict arg decode, yaegiutil panic recovery) + internal/domain/eda/module/log schema with generated logextract symbols; ModuleDir config wired in bootstrap.go with log-and-abort; examples/modules/log.go operator example proven through the real registry. Playbook YAML action dispatch deliberately deferred (data-flow Q1 unresolved) and recorded in module-position.md. task check clean (113/113 UI, exit 0).","dependencies":[{"issue_id":"archie-core-t2db.13","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T17:11:21Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.12","title":"workflow: standalone playbook lint/LSP tool (gopls-shaped)","description":"Fourth slice of docs/prds/eda-playbook-engine.md. The design doc's collision handling has two layers: a linter for pre-merge, same-tree collisions, and the runtime detect-log-report path for cross-source collisions only visible at daemon startup (t2db.9/.10/.11). Only the runtime path exists so far.\n\nCorrected 2026-09-03 (Sam): not a Taskfile target wrapping existing functions -- a small standalone CLI binary shaped like gopls: one tool, multiple invocation modes. A one-shot 'lint' mode ships in this ticket; the design doc's LSP requirement (author-time hover/completion/inline errors) is a later mode of the SAME binary, not a separate tool, so the two can never validate a playbook YAML differently -- one schema source, one binary, two entrypoints into it (matches gopls's own check-vs-serve split).\n\nDepends on archie-core-t2db.11 (multiple playbook directories) landing first, since a linter checking one directory in isolation can't demonstrate the cross-directory case the doc cares about -- though it should also catch within-a-single-directory duplicates, which is the more common real case.","design":"New cmd/\u003cname\u003e binary (e.g. cmd/archie-playbooks), per organisation.md's cmd/ rule: CLI flag parsing and entry-point routing only, no domain wiring in cmd/ itself. Actual validation logic stays in internal/domain/workflow (reuse LoadKindWorkflowsYAML/LoadLabelWorkflowsYAML/t2db.11's directory merge directly -- no second, parallel validation path). This ticket implements only the lint subcommand/mode; structure the binary's command dispatch so an 'lsp'/'serve' subcommand can be added later without restructuring (e.g. a small subcommand table from the start, even with one entry), matching gopls's shape rather than assuming a single-purpose CLI that gets bolted onto later.","acceptance_criteria":"A new cmd/ binary exists with a lint subcommand/mode that runs against one or more playbook directories and exits non-zero with a clear message when two files bind the same label/kind; exits 0 cleanly on a valid set. Reuses existing loader/merge logic directly -- no duplicated validation rules. Binary's command structure has an explicit seam for adding an LSP/serve mode later (does not need to be built yet). Documented (README or Taskfile.yml comment) so it's discoverable. task check passes.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T16:56:44Z","created_by":"Sam Catlow","updated_at":"2026-09-02T17:07:39Z","closed_at":"2026-09-02T17:07:39Z","close_reason":"Implemented and gate-verified as 2c7c79e (pushed to main). cmd/archie-playbooks lint mode reuses daemon loaders; file-granular positions documented as known limitation.","dependencies":[{"issue_id":"archie-core-t2db.12","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T16:56:44Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.11","title":"workflow: generalize routing/label files to multiple playbook directories","description":"Third slice of docs/prds/eda-playbook-engine.md, completing open question #2. Generalizes the single-file workflow_routing_file / workflow_labels_file config fields (t2db.9, t2db.10) into a LIST of configured playbook directories, loaded at daemon startup alongside the existing single-file fields for backward compatibility. This is what makes the design doc's collision-handling rule (drop + log + report to caller, no auto-arbitration) load-bearing: a single file has nothing to collide with, so the rule has never actually been exercised in production code yet.\n\nCorrected 2026-09-03 (Sam): must be a list of directories, not one directory -- a single playbook_dir field would contradict supporting multiple independently-maintained playbook sources, which the PRD's own Dedup section already assumes ('independently-sourced playbook directories collide'). Scope directories by the existing Repo (owner/name) concept already in Config.Repos, NOT by org/tenant -- org-keying would require an auth/identity model archie does not have yet. That is a separate, later decision, not something to half-build here.","design":"Follow the existing once-at-startup lifecycle (SetKindWorkflows/SetLabelWorkflows pattern) rather than inventing new state management. Config gains a list field (e.g. PlaybookDirs []string, or a PlaybookDir field on the existing Repo struct if directories should tie to a specific configured repo rather than being globally pooled -- decide based on whether playbooks are meant to be repo-scoped or operator-global). A loader reads every *.yaml file across all configured directories, applying the same per-file validation LoadLabelWorkflowsYAML already does, then merges bindings across all sources -- a binding for the same label/kind declared by two different sources is the collision case: drop both, log which sources/label collided, return the error to the caller (do not start the daemon on a routing collision). Single-file fields (workflow_routing_file, workflow_labels_file) remain supported unchanged as an additional, independent input alongside the directory list, not replaced by it.","acceptance_criteria":"Config supports a LIST of playbook directories (not a single path), empty/unset by default (no behavior change for existing configs). Loading two directories with a colliding label binding is a reported load failure, not a silent pick-one. Loading multiple non-colliding directories merges cleanly and Route() honours the merged bindings. Existing workflow_routing_file/workflow_labels_file continue to work unchanged when no directories are configured. Org/tenant scoping is explicitly out of scope and not attempted. task check passes.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T16:50:18Z","created_by":"Sam Catlow","updated_at":"2026-09-02T16:57:50Z","closed_at":"2026-09-02T16:57:50Z","close_reason":"Implemented and gate-verified as 3e7fe00 (pushed to main). PlaybookDirs is a list per ticket correction; cross-source collision rule exercised by new load path.","dependencies":[{"issue_id":"archie-core-t2db.11","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T16:50:18Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.10","title":"feat(workflow): route arbitrary forge labels to workflows via playbook YAML","description":"Second slice of docs/prds/eda-playbook-engine.md, complementing the kind-\u003eworkflow layer (WorkflowRoutingFile): the label vocabulary itself becomes playbook data. A label outside the closed bug/feature/bootstrap kind set (e.g. security) dispatches to a registered workflow from an optional WorkflowLabelsFile, instead of falling through to triage.\n\n- LabelWorkflows + LoadLabelWorkflowsYAML/SetLabelWorkflows in internal/domain/workflow/routing.go, mirroring the kind layer's once-at-startup lifecycle. The closed Kind/NATS-subject set is untouched; the map only extends binding authority for labels the kind layer does not own.\n- Collision rule per design doc: a label owned by the kind set, an empty label, an empty workflow name, or a duplicate binding is a reported load failure (dropped, logged, error returned to the caller) -- the schema defines what is accepted; nothing is silently arbitrated by schema/version.\n- Route() precedence: explicit t.Workflow -\u003e arbitrary-label binding -\u003e kind binding -\u003e triage -\u003e implement -\u003e default.\n- Config: WorkflowLabelsFile (workflow_labels_file), wired at boot alongside WorkflowRoutingFile; documented in config.example.toml.\n- PRD: records this slice's decisions (single-file shape, collision rule, precedence) so later slices stay anchored.\n\nCommitted as 93a5f3a and pushed to main.","design":"Follows the EDA playbook engine design doc (docs/prds/eda-playbook-engine.md). Open question 2 (config field shape) partially resolved: single file (workflow_labels_file) mirroring WorkflowRoutingFile and SkillsDir's single-path precedent; a directory remains open and larger. Data-flow/condition syntax (Q1), mid-run failure semantics and idempotency (design gaps 1-2) are explicitly out of this slice's scope per the PRD phasing -- they land with Module/Channel/Forge action kinds.","acceptance_criteria":"1. An issue labelled with an arbitrary label (not bug/feature/bootstrap) routes to the workflow bound in workflow_labels_file.\n2. No workflow_labels_file configured: kind-only routing unchanged (backward compatible).\n3. Colliding/empty/kind-owned labels in the file produce a reported load error, not silent arbitration.\n4. Route() precedence: explicit t.Workflow \u003e arbitrary-label binding \u003e kind binding \u003e triage \u003e implement \u003e default.\n5. task check is green; tests cover dispatch, collision, empties, nil-restore, and precedence.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T16:45:33Z","created_by":"Sam Catlow","updated_at":"2026-09-02T16:46:28Z","closed_at":"2026-09-02T16:46:14Z","close_reason":"Implemented and gate-verified as 93a5f3a (pushed to main).","external_ref":"https://github.com/samcharles93/archie-core/issues/701","dependencies":[{"issue_id":"archie-core-t2db.10","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T16:45:33Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.9","title":"workflow: make kind-to-workflow routing YAML-overridable","description":"First slice of the EDA playbook engine (docs/prds/eda-playbook-engine.md): make workflow/routing.go's kindWorkflows map overridable from an optional YAML file, so which workflow runs for an intake Kind is data instead of a Go literal. labelKinds/NATS subjects are explicitly out of scope for this slice (closed subject-per-kind question deferred).","acceptance_criteria":"Route() accepts an optional KindWorkflows override; a YAML file with the same shape as the built-in map overrides it; absent file/nil override falls back to today's hardcoded defaults unchanged; config gains an optional path field; task check passes.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-09-02T16:32:45Z","created_by":"Sam Catlow","updated_at":"2026-09-02T16:46:28Z","started_at":"2026-09-02T16:32:50Z","closed_at":"2026-09-02T16:35:44Z","close_reason":"kindWorkflows YAML override shipped, task check green","external_ref":"https://github.com/samcharles93/archie-core/issues/702","dependencies":[{"issue_id":"archie-core-t2db.9","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T16:32:45Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-v9gv.2","title":"Refactor hyperscript el() usage to Preact JSX","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T13:37:19Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:07Z","closed_at":"2026-09-02T14:24:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/683","dependencies":[{"issue_id":"archie-core-v9gv.2","depends_on_id":"archie-core-v9gv","type":"parent-child","created_at":"2026-09-02T13:37:19Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-v9gv.3","title":"Update main entrypoint to mount via Preact render","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T13:37:19Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:07Z","closed_at":"2026-09-02T14:24:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/684","dependencies":[{"issue_id":"archie-core-v9gv.3","depends_on_id":"archie-core-v9gv","type":"parent-child","created_at":"2026-09-02T13:37:19Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-v9gv.1","title":"Rename UI view files from .js to .jsx","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T13:37:18Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:08Z","closed_at":"2026-09-02T14:24:01Z","external_ref":"https://github.com/samcharles93/archie-core/issues/685","dependencies":[{"issue_id":"archie-core-v9gv.1","depends_on_id":"archie-core-v9gv","type":"parent-child","created_at":"2026-09-02T13:37:18Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-v9gv","title":"Migrate Web UI to Preact","status":"closed","priority":2,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-09-02T13:37:08Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:09Z","closed_at":"2026-09-02T14:24:11Z","close_reason":"All children completed","external_ref":"https://github.com/samcharles93/archie-core/issues/686","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.8","title":"Dashboard UI for playbook bindings","description":"The t2db.4 backend shipped the CRUD API (POST/GET/PATCH/DELETE /api/bindings + POST /api/bindings/{id}/approve) plus the state machine and HMAC wiring. Operators cannot author bindings from the dashboard yet: a list-and-approve page exists in api_binding.go's response shape but the matching ui/src/ feature folder does not. Build the click-through editor mirroring ui/src/mappings/ -- the actual convention there is .jsx, not .js (mapping-editor.jsx, mappings.jsx, mappings.css) -- follow that file extension, not payload-field-mapping.md:145-152's literal naming if it says .js. Components: source matcher, mapping picker, workflow picker, secret input, owner/repo pin input, state-machine controls (create -\u003e edit -\u003e approve -\u003e armed). See docs/prds/webhook-intake-security.md and docs/prds/payload-field-mapping.md.\n\nRESOLVED 2026-09-03 (commit ac42f64): the backend multi-repo correctness gap is fixed. binding.Binding now has optional Owner/Repo fields (Validate rejects setting only one); resolveBindingRepo (internal/daemon/daemon.go) dispatches to a pinned binding's own owner/repo unconditionally, falling back to the existing single-configured-repo behavior when unpinned. Wired through the API request/response shape already. Remaining scope for this ticket is UI-only: the dashboard editor itself, including an owner/repo input field for the pin added above.","acceptance_criteria":"The click-through editor exists in ui/src/bindings/ (or the confirmed correct convention), covering create -\u003e edit -\u003e approve -\u003e armed, including an owner/repo pin input. Backend correctness (multi-repo dispatch) is already resolved -- not part of this ticket's remaining acceptance.","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-09-02T13:24:13Z","created_by":"Sam Catlow","updated_at":"2026-09-02T20:18:21Z","closed_at":"2026-09-02T20:18:21Z","close_reason":"Backend Owner/Repo fix (ac42f64) + full dashboard UI (85761c4, mirroring ui/src/mappings/) both landed. Full state machine (draft-\u003eedit-\u003epending_approval-\u003eapprove-\u003earmed-\u003edelete) verified end-to-end in a real browser. Also fixed a related bug found in the process (empty-secret-on-edit rejected, commit 51ca509).","external_ref":"https://github.com/samcharles93/archie-core/issues/687","dependencies":[{"issue_id":"archie-core-t2db.8","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T13:24:13Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.7","title":"Encrypt binding secrets at rest","description":"binding.Binding.Secret is currently stored as plaintext in the bindings.secret TEXT column. Anyone with read access to the SQLite file (the same access level as captured_events.body and tasks.body) sees HMAC secrets in plaintext. Add at-rest encryption for the secret column so a leaked database file does not leak sender-side shared secrets. See docs/prds/webhook-intake-security.md point 5. Decide the cipher (likely AES-GCM with a key derived from archied's secret registry or a deployment-level key file), the key-rotation story, and whether captured_events.body redaction is upgraded at the same time. Phase F work for t2db.","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-09-02T13:24:12Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:10Z","closed_at":"2026-09-02T13:55:47Z","close_reason":"Closed","external_ref":"https://github.com/samcharles93/archie-core/issues/688","dependencies":[{"issue_id":"archie-core-t2db.7","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-09-02T13:24:12Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b6ew.6","title":"Inline editing for per-repo config fields (allow_concurrent, max_retries, review_enabled)","description":"archie-core-b6ew.4 shipped visibility for AllowConcurrent, MaxRetries, and ReviewEnabled on the repositories card (read-only), which was the concrete discoverability gap Sam hit. Actual inline editing was scoped out of that issue because it hits a real backend limitation discovered while implementing it: the dashboard's PATCH /api/config path (installUpdateConfigHandler in internal/app/archied/bootstrap.go) applies dotted-key updates via overlay.Nest + configuration.ApplyOverlayValues, and overlay.Nest (internal/infrastructure/configuration/overlay/overlay.go:162) only builds nested maps by splitting on '.' -- it has no array-index handling, so a key like 'repos.0.allow_concurrent' cannot be expressed, and Repos is a []config.Repo slice, not a map, so ApplyOverlayValues's YAML-merge-onto-struct approach cannot target one element either.\n\nThis needs either: (a) a dedicated repo-update seam (e.g. a webui handler keyed by owner/name that reads-modifies-writes the Repos slice directly, bypassing the generic dotted-overlay path), or (b) extending overlay.Nest/ApplyOverlayValues to support array indices generically, which is broader-reaching (touches every list-shaped config field, not just Repos) and needs its own design decision about whether index-based overlay keys are stable across a file edit that reorders [[repos]] entries. Option (a) is almost certainly the smaller, safer change -- decide in a short design note before implementing, per this repo's settled-design-first rule, since option (b) has real footguns (index stability) that deserve a deliberate answer, not a guess.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-09-02T12:22:53Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:11Z","started_at":"2026-09-02T12:26:59Z","closed_at":"2026-09-02T12:34:55Z","close_reason":"Traced the mechanism before implementing: overlay.Nest/ApplyOverlayValues has no array-index support, but Repos is addressed as a WHOLE dotted key ('repos', no dot) whose value is the full slice -- so no changes to overlay/configuration packages were needed at all. Added PATCH /api/config/repos/{owner}/{name} (webui.Server.UpdateRepoField seam + handleConfigRepoUpdate), wired in archied/bootstrap.go's installUpdateRepoFieldHandler: reads the daemon's own live, untrimmed Repos (not webui.RepoView, which omits Preflight/TestGlob and would silently drop them on a naive round-trip), mutates the one matched repo's one field via the pure applyRepoFieldUpdate helper, and republishes through the existing UpdateConfig(ctx, {\"repos\": repos}) path unchanged -- zero duplicated validate/persist/publish logic.\n\nFrontend: config-row.js's row() gained an opts.save override so a caller can redirect where an edit persists; the repositories table renders an autosaving checkbox (allow_concurrent, review_enabled) and a save-on-blur/Enter text input (max_retries) via api.configRepoUpdate, reverting/erroring inline on failure rather than reloading the whole page mid-edit.\n\nGo tests cover the pure applyRepoFieldUpdate function directly (matched-repo-only mutation, untouched-field preservation including Preflight, type coercion, unknown repo/field rejection) and the webui handler (seam delegation, editable-field allowlist enforced before the seam is called, 503/400 mapping). JS tests cover the structural render (checkbox/input initial state) -- the save round trip itself isn't exercisable through the test shim (addEventListener is a no-op there), consistent with existing config-row.test.js coverage.","external_ref":"https://github.com/samcharles93/archie-core/issues/689","dependencies":[{"issue_id":"archie-core-b6ew.6","depends_on_id":"archie-core-b6ew","type":"parent-child","created_at":"2026-09-02T12:22:53Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-c0y4","title":"TelegramConfig gains a bws-capable Token (SecretRef), not just TokenEnv","description":"internal/config/config.go's TelegramConfig only has TokenEnv (a plain OS env var name); it never resolves through secret.Registry the way Forge.Token and Provider.APIKey do (secret.SecretRef{engine,key}), per ARCHITECTURE.md:220-224's own note that TelegramConfig.TokenEnv is one of the older env-only fields kept for backwards compatibility. internal/app/archied/telegram_setup.go:75 does a bare os.Getenv(cfg.Chat.Telegram.TokenEnv), bypassing the secret registry entirely.\n\nThis means a bws-stored Telegram token cannot be referenced directly in config.toml the way [providers.openai].api_key or [forge.token] already can -- the operator has to bridge it into a real process env var by hand (bws secret get ... | export ARCHIE_TELEGRAM_TOKEN=...) instead of writing [chat.telegram.token] = { engine = \"bws\", key = \"...\" }.\n\nFix: add a Token secret.SecretRef field to TelegramConfig, mirroring Forge.Token's shape and resolution path. Keep TokenEnv working as a fallback/legacy path (same pattern documented for Provider.APIKeyEnv vs APIKey) rather than a breaking config change -- resolve Token first if set, fall back to TokenEnv. Update config.example.toml and docs/architecture identity/config docs to show the SecretRef form as the preferred one.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-09-02T12:21:10Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/690","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b6ew.4","title":"Structured configuration editors: repositories, maps","description":"Repositories currently render as a static read-only table missing AllowConcurrent, MaxRetries, and ReviewEnabled entirely (ReviewEnabled is absent from RepoView in api_config.go, not just unrendered). Add ReviewEnabled to RepoView, and build a dedicated backend-defined editor for the repositories section (and the models/providers maps) so these stop being silently read-only. This is the concrete fix for the allow_concurrent discoverability gap Sam hit, delivered as a typed editor rather than a one-off card patch, since the schema this epic introduces is what should own its shape.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-09-02T12:00:46Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:13Z","started_at":"2026-09-02T12:21:13Z","closed_at":"2026-09-02T12:23:52Z","close_reason":"Scoped to visibility, not full inline editing -- while implementing, found that the dashboard's PATCH /api/config path (overlay.Nest + configuration.ApplyOverlayValues) has no array-index support, so a per-element update to the Repos slice cannot be expressed as a dotted key today. That's real, separate scope, filed as archie-core-b6ew.6 rather than bolted on.\n\nShipped: RepoView.ReviewEnabled (previously absent from the API entirely, not just unrendered) alongside AllowConcurrent and MaxRetries; the repositories card now shows Concurrent/Max retries/Self-review columns as read-only pills, closing the concrete discoverability gap (Sam couldn't see allow_concurrent without an agent tracing Go source). config.example.toml documents review_enabled, which was undocumented before this. Go test pins ReviewEnabled reaching ConfigView for both a configured and a zero-value repo.","external_ref":"https://github.com/samcharles93/archie-core/issues/691","dependencies":[{"issue_id":"archie-core-b6ew.4","depends_on_id":"archie-core-b6ew","type":"parent-child","created_at":"2026-09-02T12:00:46Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-b6ew.4","depends_on_id":"archie-core-b6ew.2","type":"blocks","created_at":"2026-09-02T12:00:51Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b6ew.5","title":"Schema contract tests: metadata completeness and secret-safety","description":"Assert every field the schema exposes carries type, label, and section; assert restart_required and editable are set deliberately (not zero-value defaults hiding an unreviewed field); assert secrets still never appear (extend the existing TestHandleConfigNeverLeaksSecrets pattern to the schema response); assert the frontend's generic renderer can render the full schema fixture without any field-specific branch (a JS test walking the schema and asserting no field key appears literally in settings.js).","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-09-02T12:00:46Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:13Z","started_at":"2026-09-02T12:24:40Z","closed_at":"2026-09-02T12:26:27Z","close_reason":"Most of this issue's assertions were already covered incrementally by tests added in .1-.4 (key/label/type completeness, structured/locked non-editability, secret-leak guard on the schema block, schema values matching their flat-field source). This issue adds the two pieces still missing: TestConfigFieldDescriptorsRestartRequiredIsDeliberate pins the exact RestartRequired value per key against the reload.go evidence documented in configFieldDescriptors' own comment, so a reclassification without checking reload.go fails loudly. ui/test/settings-schema.test.js renders settingsPage against a schema fixture containing a field settings.js has never heard of (proving the renderer needs no field-specific branch to show it correctly) and asserts, by reading settings.js's own source text, that none of the generically-rendered section's field keys appear literally in it -- the direct regression test for archie-core-b6ew.3's whole point.","external_ref":"https://github.com/samcharles93/archie-core/issues/692","dependencies":[{"issue_id":"archie-core-b6ew.5","depends_on_id":"archie-core-b6ew","type":"parent-child","created_at":"2026-09-02T12:00:46Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-b6ew.5","depends_on_id":"archie-core-b6ew.3","type":"blocks","created_at":"2026-09-02T12:00:52Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-b6ew.5","depends_on_id":"archie-core-b6ew.4","type":"blocks","created_at":"2026-09-02T12:00:52Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b6ew.3","title":"Generic frontend renderer for scalar configuration fields","description":"Replace settings.js's hardcoded row(...) calls for scalar/bool/int/enum/duration fields with a renderer that walks the backend's sections/fields schema and builds the section cards, labels, and edit affordances from the descriptor alone -- the frontend must not know that containers.max_concurrency is an int or which card it belongs in. Structured fields (repositories, models, providers maps) are out of scope here and keep their existing bespoke rendering, tagged type=structured so the generic renderer skips them without special-casing each key.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-09-02T12:00:45Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:14Z","started_at":"2026-09-02T12:08:25Z","closed_at":"2026-09-02T12:12:41Z","close_reason":"settings.js renders identity/budgets/storage/web cards generically from cfg.schema sections (schemaCards()), replacing identityCard/budgetsCard/storageCard/webCard/pullPolicyLabel -- label, type, description, editability, and options all come from the backend descriptor. config-row.js gained enum edit support (select from opts.options), an editable:false branch distinct from locked rows, and a hint tooltip carrying the field's description. Structured sections (repositories, models \u0026 providers) are unaffected -- still rendered by their existing bespoke functions, reserved for b6ew.4. Not visually verified in a live browser (needs a full daemon+forge+NATS stack); verified via unit tests mirroring the existing config-row.test.js patterns and Go contract tests.","external_ref":"https://github.com/samcharles93/archie-core/issues/693","dependencies":[{"issue_id":"archie-core-b6ew.3","depends_on_id":"archie-core-b6ew","type":"parent-child","created_at":"2026-09-02T12:00:45Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-b6ew.3","depends_on_id":"archie-core-b6ew.2","type":"blocks","created_at":"2026-09-02T12:00:50Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b6ew.1","title":"Backend configuration schema contract: field descriptor types and section metadata","description":"Define the descriptor types (Section, Field, Option) in internal/webui alongside ConfigView -- Key, Label, Description, Section, Type (string|int|bool|duration|enum|structured), Editable, LockedReason, Overridden, Options, RestartRequired. Hand-author one descriptor per existing ConfigView field, grouped into the sections the settings page already renders (identity, repositories, models, providers, budgets, storage, containers, web). No reflection over config.Config -- config.Config is scheduled for dissolution (internal/config/config.go package doc) and every field here is already a deliberate allowlist entry, so this is metadata on fields that already passed the secret-safety allowlist, not a new safety boundary.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-09-02T12:00:44Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:15Z","started_at":"2026-09-02T12:02:40Z","closed_at":"2026-09-02T12:05:40Z","close_reason":"Added internal/webui/config_schema.go: ConfigFieldType/ConfigField/ConfigSection descriptor types and configFieldDescriptors(), hand-authoring key/label/type/editable/restart_required for every field ConfigView exposes today, grouped into the sections settings.js already renders. RestartRequired sourced from internal/app/archied/reload.go's reloadableFields/reloadableSubFields allowlist. Contract tests pin key completeness, structured-field non-editability, and locked-storage-field non-editability. Not yet wired into GET /api/config -- that's b6ew.2.","external_ref":"https://github.com/samcharles93/archie-core/issues/694","dependencies":[{"issue_id":"archie-core-b6ew.1","depends_on_id":"archie-core-b6ew","type":"parent-child","created_at":"2026-09-02T12:00:44Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b6ew.2","title":"Expose the config schema via GET /api/config","description":"Extend handleConfig's response with a schema-driven shape (sections of fields, each carrying its descriptor and current value) built from the field descriptors, replacing the flat ConfigView value tree the frontend currently re-interprets by hand. Keep the existing Locked/Overridden/Reload/Provenance top-level fields -- they describe runtime state, not the field catalog, and the schema-driven fields reference into them (locked_reason, overridden) rather than duplicating that logic.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-09-02T12:00:44Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:16Z","started_at":"2026-09-02T12:06:31Z","closed_at":"2026-09-02T12:07:58Z","close_reason":"ConfigView gains a Schema []ConfigSection field, populated in handleConfig via buildConfigSchema(view), which attaches each request's Value/LockedReason/Overridden onto the static configFieldDescriptors() catalog. The flat ConfigView fields (Identity, Repositories, etc.) are untouched -- Schema is additive. Tests confirm schema values match the flat fields they derive from, locked reasons propagate, structured fields stay non-editable, and secrets never reach the schema block.","external_ref":"https://github.com/samcharles93/archie-core/issues/695","dependencies":[{"issue_id":"archie-core-b6ew.2","depends_on_id":"archie-core-b6ew","type":"parent-child","created_at":"2026-09-02T12:00:44Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-b6ew.2","depends_on_id":"archie-core-b6ew.1","type":"blocks","created_at":"2026-09-02T12:00:50Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":2,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b6ew","title":"[EPIC] Backend-owned configuration schema for the webui Configuration page","description":"The Configuration page's field definitions (label, section, type, editability, restart-required, options) are hand-maintained in ui/src/settings/settings.js and config-row.js, disjoint from the backend's own ConfigView allowlist in internal/webui/api_config.go. Adding or changing a runtime-tunable setting today means editing Go and JS in two unrelated places by hand, and nothing catches drift between them. Repo.ReviewEnabled is missing from the API entirely; AllowConcurrent and MaxRetries reach the API but the repositories card never renders them, which is what blocked Sam from discovering the allow_concurrent fix without an agent tracing the Go source directly.\n\nDesign: docs/prds/config-schema.md. The backend keeps its existing hand-picked, secret-free allowlist (ConfigView in api_config.go) -- config.Config is scheduled for dissolution per its own package doc, so this is deliberately NOT a reflection-based schema over config.Config. Instead each already-allowlisted field gains a hand-authored descriptor (label, section, type, editable, restart_required, options) alongside its existing value, and the frontend renders scalar/bool/int/enum/duration fields generically from that descriptor instead of hardcoding rows. Structured fields (repositories, maps) get dedicated typed editors rather than staying silently read-only.","status":"closed","priority":2,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-09-02T12:00:27Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:17Z","closed_at":"2026-09-02T12:35:11Z","close_reason":"All six child issues shipped: hand-authored field descriptor catalog (.1), schema attached to GET /api/config (.2), generic scalar renderer replacing hardcoded settings.js rows (.3), repository field visibility incl. the previously-API-absent ReviewEnabled (.4), schema contract tests pinning restart-required deliberateness and generic-render proof (.5), and inline editing for the three per-repo fields via a dedicated PATCH /api/config/repos/{owner}/{name} seam (.6). The concrete complaint that started this (allow_concurrent invisible on the dashboard) is fully resolved: visible, editable, and backed by a schema the frontend no longer hardcodes.","external_ref":"https://github.com/samcharles93/archie-core/issues/696","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-z6wy","title":"Curator action timestamps rendered as '105694 wks ago'","description":"Curator actions built without an explicit At (e.g. sessioncurator before this fix, and skillcurator) serialized time.Time's zero value to the dashboard, which rendered as a nonsense relative time. Fixed by stamping sessioncurator's action with its clock and backfilling any zero Action.At in activityTracker.record from the pass timestamp.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-02T11:52:20Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:18Z","closed_at":"2026-09-02T11:52:24Z","close_reason":"Fixed: sessioncurator now stamps Action.At from its clock; activityTracker.record backfills any zero Action.At from the pass timestamp as a defense in depth for engines with no clock (skillcurator).","external_ref":"https://github.com/samcharles93/archie-core/issues/697","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-enfj","title":"[EPIC] Dynamic workflow routing: route task intent to the cheapest sufficient workflow","description":"workflow.Route() (internal/domain/workflow/workflow.go:237) only checks an explicit t.Workflow, then label match, then falls back unconditionally to 'implement' -- the heaviest workflow. There is no content/intent-based routing at all. task_spawn's own tool schema actively overpromises: 'workflow: ... Omit to let the daemon route it' (internal/gateway/task_tools.go:240), implying real routing exists when it means only 'check labels, then give up and run the heaviest workflow anyway'.\n\nConfirmed via production task 6 (2026-09-02): a chat-spawned task whose entire content was 'this is just a test, close it when you receive it' ran the full implement pipeline (prepare, baseline, plan, build, commit-push) end to end, burning 669,421 tokens and ~7 minutes, when nothing about the request needed a worktree, a plan, or a build at all.\n\nNeeds a design doc before any code lands per CLAUDE.md's scope-discipline rule (no settled design exists).","status":"closed","priority":2,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-09-02T11:29:07Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:19Z","closed_at":"2026-09-02T11:40:00Z","close_reason":"Implemented internal/domain/workflow/triage.go: a cheap classify-only-once AgentStage (still runs StagePrepareWorktree -- AgentStage requires tc.Dir to mount into the container, no cheaper primitive exists) that either closes a task needing no code change (reusing the CloseIssue/StatusMerged pattern feasibility.go's OnResult already established for the same ctx-less constraint) or sets tc.Task.Workflow and requeues under the chosen workflow (implement/tdd/feasibility, defaulting to implement for a missing/unrecognized choice). Route()'s fallback (workflow.go) now prefers reg[\"triage\"] over reg[\"implement\"] when registered, falling back unchanged when it isn't -- fully backward compatible. Registered in skillbuild.builtins(). 9 new tests (triage_test.go, routing_test.go) plus the design doc at docs/prds/dynamic-workflow-triage.md. task check clean.","external_ref":"https://github.com/samcharles93/archie-core/issues/698","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-rwzo","title":"Token usage totals mislead: raw prompt sum not netted against cache hits","description":"Confirmed on production task 6 (2026-09-02, carina): dashboard/PR summary showed '14 iterations · 405,004 tokens · 400,021 prompt · 4,983 completion · 360,018 cached'. Cross-checked against the per-iteration daemon log: nothing is double-counted or hardcoded -- the totals are the correct sum of 14 real, separately-billed API calls with growing context. But 360,018 of the 400,021 'prompt tokens' shown were cache hits (billed at a steep discount), not full price -- real fresh spend was ~40,003 tokens. Showing only the raw prompt-token sum makes every agent run's cost read roughly 10x worse than what was actually billed, everywhere this aggregate surfaces (PR body, dashboard timeline).\n\nSeparately (real, not just cosmetic cost): StageBaselineGate's retry-mission prompt re-injected the ENTIRE go test ./... output -- hundreds of lines covering every passing package -- into every retry iteration's prompt, not just the failing ones. Direct mechanical contributor to the growing per-iteration prompt sizes.","design":"TaskContext.RunUsage (in-memory, not persisted -- Task.TokensUsed remains authoritative) accumulates agentexec.Usage across every agent run in one workflow execution. formatTokenUsage(total, usage) renders 'N tokens (F fresh + C cached)' with a plain fallback. extractFailingGateOutput(s) strips go test 'ok' package lines, only when it recognizes --- FAIL:/FAIL\\t markers, else returns input unchanged. Known gap: a task resumed after a daemon restart mid-workflow loses RunUsage and falls back to the plain total -- an honest degrade, not a bug; persisting the breakdown would need a store migration for a purely presentational value, not worth it yet.","acceptance_criteria":"PR bodies and the dashboard timeline show a fresh-vs-cached breakdown (or an equivalent net figure) instead of a raw prompt-token sum, falling back gracefully when no usage breakdown is available. Gate-retry mission prompts drop passing-package output, keeping only failure-relevant content, with graceful degradation for non-Go gates or unrecognized output shapes. task check passes.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-02T11:28:39Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:20Z","closed_at":"2026-09-02T11:28:49Z","close_reason":"Added TaskContext.RunUsage + accumulateUsage (agent.go, implement.go's baseline-fix branch) and formatTokenUsage (workflow.go), wired into implement.go's and tdd.go's PR-body footers plus ui/src/tasks/timeline-event.js's agent_finish rendering (raw prompt replaced with computed fresh = prompt - cached). Added extractFailingGateOutput (workflow.go) trimming go test 'ok' package lines from StageBaselineGate's retry mission, degrading to unchanged output when no --- FAIL:/FAIL\\t marker survives the filter. 5 new Go tests, 1 updated JS test. task check clean, 100/100 JS tests.","external_ref":"https://github.com/samcharles93/archie-core/issues/699","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-n2pv","title":"Dashboard Logs page never surfaces per-task attempt-log detail","description":"internal/webui/api_tasks_logs.go's handleTaskLogs (GET /api/tasks/{id}/logs) was fully working -- internal/logging/reader.go's decode() already captures every JSON field generically into Entry.Fields (stage, tokens, iterations, model, stop_reason, everything). But no frontend code called it: ui/src/logs/logs.js (the dashboard's only Logs page) exclusively called api.logs(), the daemon-wide feed, which only carries the daemon's own component-scoped Info/Warn/Error lines -- never the rich per-stage/per-agent-run detail that lives in a task's own per-attempt log file. An operator could never see why a specific task took as long as it did, what each workflow stage did, or its token spend breakdown from the dashboard, even though the daemon already recorded and could already serve all of it. Discovered while investigating production task 6 (2026-09-02, archie-core-95dj).","acceptance_criteria":"A task's persisted attempt log (stage timings, iteration counts, token/prompt/completion/cached breakdowns, model) is visible from the dashboard task view. Reuses the daemon-wide log page's row-rendering logic rather than duplicating it. Handles disabled/empty/error states without crashing. task check (including task test:ui) passes.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-02T11:26:44Z","created_by":"Sam Catlow","updated_at":"2026-09-02T14:56:20Z","closed_at":"2026-09-02T11:26:52Z","close_reason":"Added ui/src/base/log-row.js (row rendering extracted out of logs.js, shared -- second consumer per CLAUDE.md), ui/src/tasks/task-logs.js (taskLogPanel handling loading/error/disabled/empty/populated states), api.taskLogs() in ui/src/base/api.js, and a collapsible 'Attempt log' section wired into each task's existing timeline drill-down in ui/src/tasks/tasks.js -- lazily fetched on first expand. New tests: ui/test/log-row.test.js, ui/test/task-logs.test.js. task check clean, 100/100 JS tests.","external_ref":"https://github.com/samcharles93/archie-core/issues/700","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499161-356-e424e40d.1","title":"setupMemory never calls RegisterExternal; cfg.Memory.Provider is silently inert","description":"internal/app/archied/bootstrap.go:setupMemory's own doc comment says\n\"External providers from config are added via RegisterExternal when\ncfg.Memory.Provider is set\" -- no such branch exists in the function body.\nToday, an operator who sets [memory] provider = \"...\" in config.toml gets\nno error and no effect: the builtin file-backed provider is the only one\nthat ever runs. config.example.toml already documents this as a known gap\n(\"[memory] exists to register an EXTERNAL provider alongside it, but as of\nthis writing that wiring ... is not called\").\n\nSeparately, internal/config.MemoryConfig (config.go:287) has no `toml`\nstruct tag on any field (yaml/json only), so even fixing the wiring call\nmay not bind values from config.toml, the format operators actually use --\nverify this before or as part of the fix.\n\nThis sits ahead of the typed engine-family work (archie-core-...-11-e245c170)\nin the sense that it's a bug in the CURRENT ad-hoc MemoryProvider wiring,\nnot a gap in the future engine contract -- decide whether it's worth fixing\nin the legacy path or superseded once the conforming memory engine family\nlands, rather than fixing both.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-01T15:50:52Z","created_by":"Sam Catlow","updated_at":"2026-09-01T16:51:00Z","closed_at":"2026-09-01T16:51:00Z","close_reason":"Fixed, but not as originally framed. Investigated wiring RegisterExternal\nfor real: there is no external MemoryProvider implementation anywhere in\nthe repo to construct and pass to it (only internal/memory/builtin.Provider\nexists) -- calling RegisterExternal would be dead plumbing to nothing, not\na fix.\n\nThe actual fix: configuration.validateMemory now rejects memory.provider\nbeing set at all, with a clear reason, instead of accepting it and doing\nnothing. Turns the silent no-op into a loud one. setupMemory's doc comment\nand config.example.toml updated to match; the now-pointless\nprovider_config example section removed.\n\ntoml struct tags (the other half of this bug) were already fixed in\narchie-core-1786637490043's commit.\n\nDrop the rejection once a real external provider (or the domain/memory\nengine family's Honcho proof, archie-core-1786637492031) gives the field\nan effect again.\n\nTestValidateMemoryRejectsProviderSetToAnything covers it. task check is\ngreen.","external_ref":"https://github.com/samcharles93/archie-core/issues/649","labels":["epic"],"dependencies":[{"issue_id":"archie-core-1786637499161-356-e424e40d.1","depends_on_id":"archie-core-1786637499161-356-e424e40d","type":"parent-child","created_at":"2026-09-01T15:50:52Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-r3gh","title":"Harden task origin response assertions","description":"Replace brittle prose substring assertions in internal/webui/api_tasks_origin_test.go with stable structural checks for HTTP error responses while preserving origin and media-type coverage.","acceptance_criteria":"The origin test does not assert human-readable response text; rejected cases verify stable HTTP error response structure; focused tests and task check pass.","status":"in_progress","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-31T12:49:20Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:05Z","started_at":"2026-08-31T12:49:27Z","lease_expires_at":"2026-08-31T12:54:27Z","heartbeat_at":"2026-08-31T12:49:27Z","external_ref":"https://github.com/samcharles93/archie-core/issues/664","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h3w2","title":"Migrate email/webhook channels onto domain/messaging types","description":"Update remaining gateway-based channels (email, webhook) to use domain/messaging types, completing the migration described in migration-decisions.md section 2.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-31T10:12:16Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:06Z","external_ref":"https://github.com/samcharles93/archie-core/issues/665","labels":["messaging-migration"],"dependencies":[{"issue_id":"archie-core-h3w2","depends_on_id":"archie-core-d9dv","type":"blocks","created_at":"2026-08-31T10:12:24Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-o4e4","title":"Migrate web UI / dashboard chat onto domain/messaging types","description":"Update internal/webui/ chat handling (api_chat.go and friends) to use domain/messaging types once gateway session storage is migrated. Verify SSE streaming and chat history are unaffected.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-31T10:12:15Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:06Z","external_ref":"https://github.com/samcharles93/archie-core/issues/666","labels":["messaging-migration"],"dependencies":[{"issue_id":"archie-core-o4e4","depends_on_id":"archie-core-d9dv","type":"blocks","created_at":"2026-08-31T10:12:23Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-4hof","title":"Migrate Telegram channel onto domain/messaging types","description":"Once gateway session storage uses domain/messaging types, update internal/channels/telegram/ to read/write through them instead of internal/gateway.Message directly. Verify no behavior change in message history, branching, or tool-call rendering.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-31T10:12:13Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:07Z","external_ref":"https://github.com/samcharles93/archie-core/issues/667","labels":["messaging-migration"],"dependencies":[{"issue_id":"archie-core-4hof","depends_on_id":"archie-core-d9dv","type":"blocks","created_at":"2026-08-31T10:12:22Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-d9dv","title":"Migrate internal/gateway session storage onto domain/messaging types","description":"internal/domain/messaging now has the canonical Message/Conversation/ToolCall/ToolResult types (settled in migration-decisions.md section 2). internal/gateway/'s session storage still uses its own gateway.Message and ad hoc session state. Migrate gateway's session persistence to store/load domain/messaging.Message and Conversation, preserving exact current behavior (compression, approval, branch semantics unchanged).","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-31T10:12:12Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:08Z","external_ref":"https://github.com/samcharles93/archie-core/issues/668","labels":["messaging-migration"],"dependency_count":0,"dependent_count":3,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-ul1m","title":"P2: Track migration progress - 85% of internal/ not in domain structure","description":"~85% of internal/ packages (29 of 36) haven't moved into the target domain//infrastructure/ structure yet. This is expected mid-migration, but worth tracking.\n\nNeed to:\n- Create a migration tracking document or update existing one\n- List all packages and their target locations\n- Track progress as packages are migrated\n- Identify dependencies between migrations\n\nBlocked by: P0 domain package reconciliation (archie-core-2tqh)","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:26Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/669","dependencies":[{"issue_id":"archie-core-ul1m","depends_on_id":"archie-core-2tqh","type":"blocks","created_at":"2026-08-28T13:42:37Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-kllw","title":"P2: Pin Docker latest tag for archie-agent","description":"Docker latest tag on ghcr.io/samcharles93/archie-agent is unpinned, which hurts reproducibility.\n\nNeed to:\n- Identify current stable version/commit hash\n- Update docker-compose.yml or deployment configs to use pinned tag\n- Consider using SHA-based tags for production deployments\n- Document the pinning strategy\n\nBlocked by: nothing","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:23Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/670","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-uyxk","title":"P2: Add lint/upgrade-deps Taskfile targets","description":"Dependency and lint maintenance is currently manual. There are no Taskfile targets for:\n- Running linters (golangci-lint)\n- Upgrading dependencies\n- Checking for outdated modules\n\nNeed to:\n- Add task lint target that runs golangci-lint\n- Add task deps:upgrade target for dependency updates\n- Add task deps:check target to list outdated modules\n- Ensure these integrate with existing task check flow\n\nBlocked by: nothing","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:20Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/671","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-6xo8","title":"P2: CONTEXT.md describes unimplemented Remote Secret Input feature","description":"CONTEXT.md describes a full 'Remote Secret Input' feature (entry links, secret-input sessions, value-entry form) with zero implementation in internal/secret.\n\nThe feature appears designed but not built, and nothing flags it as aspirational.\n\nNeed to:\n- Audit CONTEXT.md for feature descriptions\n- Check internal/secret for any partial implementation\n- Either implement the feature or mark it as aspirational in docs\n- Add appropriate TODO/roadmap markers\n\nBlocked by: nothing","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:17Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/672","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-shl7","title":"P2: Update ~30 outdated Go modules","description":"~30 modules behind current versions (go list -m -u all):\n- Notably grpc v1.67 → v1.83\n- protobuf v1.34 → v1.36\n\nNeed to:\n- Run go list -m -u all to get full list\n- Review each update for breaking changes\n- Run go get -u \u003cmodule\u003e for safe updates\n- Run go mod tidy\n- Verify all tests still pass\n- Commit updates in a single dependency update commit\n\nBlocked by: nothing","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-28T13:42:14Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/673","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496320-249-be6d9a20.7","title":"Architecture decision record: scheduling destination matrix entry in migration-decisions.md","description":"`migration-decisions.md` section 1 explicitly names scheduling among the largest unreviewed areas needing a destination matrix entry: 'every current package MUST receive one explicit disposition' includes the cron/scheduling capability.\n\nThe ticker engine `scheduling.Engine` is already in `internal/domain/scheduling` (decided by being built there). The remaining slices — store, runner/router, blueprints, lifecycle guard — need their target paths, dependencies, contracts, and deletion criteria recorded.","acceptance_criteria":"- Section 1 (or a new section row) lists each scheduling slice — store, runner/router, blueprints, lifecycle guard, config, composition, ticker — with its target path, dependencies to remove, contracts preserved, and migration prerequisites.\n- Names the existing `JobSource` / `Runner` / `Sink` / `Clock` interfaces as the contracts that bound the destination choices (so future maintainers see why no runner / store ended up under the engine package).\n- Marks the recording as approved-by-position (the maintainer approved this placement implicitly by accepting the engine PR) so it is not re-litigated.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-27T14:34:48Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:12Z","external_ref":"https://github.com/samcharles93/archie-core/issues/674","labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637496320-249-be6d9a20.7","depends_on_id":"archie-core-1786637496320-249-be6d9a20","type":"parent-child","created_at":"2026-08-27T14:34:48Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496320-249-be6d9a20.6","title":"Wire cron engine: app/archied composition, sink adapter, Start/Stop lifecycle","description":"Composition slice that connects the four siblings: instantiates the ticker engine in `internal/app/archied/` over the job store and the router, with the configured `EngineConfig` from the translator; registers it with the daemon's existing Start/Stop lifecycle (Start on boot, bounded-during Stop) and wires the events-bus sink so emitted `KindJobRun` / `KindJobError` events reach the bus subjects the rest of the system already listens on.\n\nThis is the last bead before the epic's acceptance scenario — daily-status-summary cron, persists across restarts, dangerous commands refused — is end-to-end runnable by a fresh operator.","acceptance_criteria":"- `engine.Start` called during daemon boot, with the configured interval.\n- `engine.Stop(ctx)` called during daemon shutdown, bounded by the same grace deadline the rest of the daemon uses (matches `taskrun`/workflow engine shutdown pattern).\n- `scheduling.Sink` adapts to the events bus emitter so dashboard / dashboard timeline surfaces running and failed jobs with the same `Kind`/`Detail`/`Data` shape the rest of the system uses.\n- With all four sibling slices landed, the parent epic acceptance ('a daily-status-summary cron job can be created, persists across restarts, dangerous commands are refused') is exercisable end-to-end.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-27T14:34:45Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:13Z","external_ref":"https://github.com/samcharles93/archie-core/issues/675","labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637496320-249-be6d9a20.6","depends_on_id":"archie-core-1786637496320-249-be6d9a20","type":"parent-child","created_at":"2026-08-27T14:34:45Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637496320-249-be6d9a20.6","depends_on_id":"archie-core-1786637496320-249-be6d9a20.1","type":"blocks","created_at":"2026-08-27T14:35:39Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637496320-249-be6d9a20.6","depends_on_id":"archie-core-1786637496320-249-be6d9a20.2","type":"blocks","created_at":"2026-08-27T14:35:41Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637496320-249-be6d9a20.6","depends_on_id":"archie-core-1786637496320-249-be6d9a20.4","type":"blocks","created_at":"2026-08-27T14:35:41Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637496320-249-be6d9a20.6","depends_on_id":"archie-core-1786637496320-249-be6d9a20.5","type":"blocks","created_at":"2026-08-27T14:35:42Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":4,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496320-249-be6d9a20.5","title":"Cron configuration block: [scheduling] in config.example.toml with EngineConfig translation","description":"Operator input for the cron/scheduling slice: a `[scheduling]` block in `config.example.toml` (`interval`, `max_parallel`, `job_timeout`, `events_sink`) plus a translation layer in `internal/infrastructure/configuration` that produces the `scheduling.EngineConfig`.\n\nWithout this, the engine has no path from operator input to runtime. The translator is the bridge the wiring slice then hands to `internal/app/archied/`.","acceptance_criteria":"- `config.example.toml` shows a `[scheduling]` block with all four fields and their default behaviour on zero values (mirrors `scheduling.Default*` constants).\n- Configuration translator yields a fully-resolved `scheduling.EngineConfig` with documented defaults applied; negative values are validated and surface as a startup error, not a panic.\n- Sink plumbing produces a concrete `scheduling.Sink` from the events-bus emitter; absent sink leaves `Events` nil, which the engine already documents as a valid (unobservable) configuration.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-27T14:34:43Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:13Z","external_ref":"https://github.com/samcharles93/archie-core/issues/676","labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637496320-249-be6d9a20.5","depends_on_id":"archie-core-1786637496320-249-be6d9a20","type":"parent-child","created_at":"2026-08-27T14:34:43Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496320-249-be6d9a20.4","title":"Cron lifecycle guard: reject dangerous commands at job creation","description":"Slice 4 of the cron/scheduling epic (archie-core-1786637496320-249-be6d9a20). The epic's third acceptance criterion verbatim: 'Dangerous commands are rejected at creation time.'\n\nGuards both runners from the previous slice: ChatCourier (whose body could include shell-shaped payloads) and WorkflowTask (whose shell-step is a documented footgun). Rejection happens at job creation, not at tick time, so a refused job is visible in the store with a refusal reason and never reaches the ticker engine.","acceptance_criteria":"- Rejects job specs whose target body includes any of: `archied` restart, `systemctl`, `launchctl`, `pkill`, `mkfs`, `dd`, `shutdown`, `reboot`.\n- Rejection reason is recorded on the refused job and surfaced through the gateway / dashboard; the job is not written to the store.\n- One named rejection function both the CLI and gateway paths call, so adding a new dangerous token does not require touching every UI surface.\n- False positives are deliberate — the list over-broadens then narrows by operator feedback. Cost of accepting a dangerous command vastly exceeds the cost of a refused one.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-27T14:34:40Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:14Z","external_ref":"https://github.com/samcharles93/archie-core/issues/677","labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637496320-249-be6d9a20.4","depends_on_id":"archie-core-1786637496320-249-be6d9a20","type":"parent-child","created_at":"2026-08-27T14:34:40Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637496320-249-be6d9a20.4","depends_on_id":"archie-core-1786637496320-249-be6d9a20.1","type":"blocks","created_at":"2026-08-27T14:35:44Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496320-249-be6d9a20.3","title":"Cron blueprints: parameterised templates with typed slots and form schemas","description":"Slice 3 of the cron/scheduling epic (archie-core-1786637496320-249-be6d9a20). The authoring surface: predefined templates with typed slots (time, enum, text, weekdays — each with their validators) that gate the gateway and CLI creation forms.\n\nDaily status summary is the headline blueprint. An author without a blueprint can still create a job directly, but the gateway form is the recommended surface for non-trivial jobs.","acceptance_criteria":"- A small registry of built-in blueprints (daily-status-summary at minimum; weekday-pickable and time-pickable are sufficient for headline coverage) exposed to gateway and CLI form renderers.\n- Typed slot definitions (`time`, `enum`, `text`, `weekdays`) with a generated form schema suitable for the gateway chat-form surface.\n- Template renderer fills slots from a validated values map; missing or wrong-typed slots reject the job at creation, not at next tick.\n- Adding a new blueprint is data, not code, and the gateway / CLI form reflect added blueprints without a rebuild.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-27T14:34:38Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/678","labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637496320-249-be6d9a20.3","depends_on_id":"archie-core-1786637496320-249-be6d9a20","type":"parent-child","created_at":"2026-08-27T14:34:38Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637496320-249-be6d9a20.3","depends_on_id":"archie-core-1786637496320-249-be6d9a20.1","type":"blocks","created_at":"2026-08-27T14:35:42Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496320-249-be6d9a20.2","title":"Cron delivery runner + router: dispatch due jobs to chat/task targets","description":"Slice 2 of the cron/scheduling epic (archie-core-1786637496320-249-be6d9a20). Implements `scheduling.Runner` and the router that picks one runner per job kind.\n\nWithout this slice, the ticker engine has no work to dispatch. Concrete target types to ship: ChatCourier (sends a templated message through the existing channel-agnostic `channels.Channel` gateway, so the channel choice stays the operator's, not the cron's) and WorkflowTask (submits a `workintake` envelope so the existing task lifecycle owns scheduling, retries, gates, and PR opening).\n\nJob store is a hard prerequisite. Composition wiring and lifecycle guard block the wiring slice, not this one.","acceptance_criteria":"- At least two `Runner` implementations: `ChatCourier` (renders the job's templated body through the channel layer) and `WorkflowTask` (submits a `workintake` envelope carrying the cron identity and body so the existing workflow domain runs the rest).\n- A `Router` that maps `Job.Kind` to a Runner; an unrecognised kind emits `KindJobError` `phase=\"dispatch\"` and is otherwise a no-op — refused at the gate, not silently dropped.\n- Every Runner honours `ctx.Done()` so the engine's bounded shutdown actually drains in flight.\n- The epic's headline scenario ('daily status summary') is exercisable end-to-end through the ChatCourier runner with a hard-coded template; the blueprints slice replaces this with parameterisation.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-27T14:34:35Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/679","labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637496320-249-be6d9a20.2","depends_on_id":"archie-core-1786637496320-249-be6d9a20","type":"parent-child","created_at":"2026-08-27T14:34:35Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637496320-249-be6d9a20.2","depends_on_id":"archie-core-1786637496320-249-be6d9a20.1","type":"blocks","created_at":"2026-08-27T14:35:43Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637496320-249-be6d9a20.1","title":"Cron job store: per-profile JSON with cross-process file locking","description":"Slice 1 of the cron/scheduling epic (archie-core-1786637496320-249-be6d9a20). Implements the durable job store: one JSON file per profile at the conventional path, CRUD operations, and cross-process file locking so a CLI edit and a daemon writer don't corrupt each other.\n\nThe ticker engine (internal/domain/scheduling) consumes this through its `JobSource` interface. The store's only contract with the engine is `Due(ctx, now) -\u003e ([]Job, error)` — the engine applies no schedule arithmetic of its own, so the store owns cron expressions, fixed intervals, and catch-up windows.","acceptance_criteria":"- One JSON file at the conventional per-profile path (`\u003cconfig_dir\u003e/cron/jobs.json` or equivalent). Schema is durable and version-stamped for forward compatibility.\n- Create / read / update / delete by job ID with merge semantics that preserve fields not in the patch.\n- Cross-process file lock (`flock` or OS equivalent) makes concurrent CLI+daemon writers serial; last-writer-wins is documented as the conflict policy.\n- Implements `scheduling.JobSource` so the ticker engine can poll it without knowing the file layout or format.\n- A truncated/partial-write file is not a panic: open returns an explicit error the engine surfaces as `phase=\"source\" KindJobError` rather than crashing the loop.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-27T14:34:32Z","created_by":"Sam Catlow","updated_at":"2026-09-02T09:49:17Z","started_at":"2026-08-28T10:36:06Z","closed_at":"2026-08-28T10:59:19Z","close_reason":"Slice 1 of cron/scheduling epic landed: per-profile JSON store with cross-process flock, merge-semantic Update, version-stamped schema, ErrCorruptFile on truncated files, ErrUnsupportedSchema on forward versions. Implements scheduling.JobSource so the ticker engine can poll it without knowing the file layout. Adversarial review applied: deep-copy Get/List, pool validation in Create/Update, ErrScheduleUnsupported on Once MarkRun, 0o600 file mode, SetEscapeHTML(false) for operator-readable files, fsync before rename for durability, ErrClosed sentinel after Close, real cross-process flock test via os/exec. task check green.","external_ref":"https://github.com/samcharles93/archie-core/issues/680","labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637496320-249-be6d9a20.1","depends_on_id":"archie-core-1786637496320-249-be6d9a20","type":"parent-child","created_at":"2026-08-27T14:34:32Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":4,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h019.8","title":"Operator-triggered PR review with selectable reviewer model","description":"Expose the reviewer as a channel-neutral application capability that can review an existing pull request on operator request. The Web UI should offer a Review PR action as one adapter; chat/Telegram and future channels must invoke the same command rather than duplicating review behavior. The operator can configure or select the reviewer model independently from planner/builder models. Reuse the reviewer epic's fresh-context, read-only snapshot, structured findings, calibration, and visibility contracts.","acceptance_criteria":"A channel-neutral review command accepts a repository and PR identity, launches the approved isolated reviewer path, and returns/persists structured findings; Web UI exposes Review PR; at least one non-Web-UI channel can invoke the same command; reviewer model is configurable independently with a safe default; authorization and duplicate/concurrent review behavior are deterministic; findings and review status are visible without requiring raw logs.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T18:08:58Z","created_by":"Sam Catlow","updated_at":"2026-08-24T18:09:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/636","dependencies":[{"issue_id":"archie-core-h019.8","depends_on_id":"archie-core-h019","type":"parent-child","created_at":"2026-08-24T18:08:58Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-atv2","title":"liveReply fallback lines appended after finalize are never rendered","description":"A media delivery that fails AFTER doFinalize has run appends its fallback line to l.toolLines and calls requestRender(), but stopRendering() has already closed renderDone and the renderer goroutine has exited. requestRender is a non-blocking send into a cap-1 channel with no consumer, so the line is dropped and the finalized Telegram message stands unchanged.\n\nMedia is fire-and-forget with a 30s budget while the turn's text finishes far earlier, so this is the NORMAL case for a large upload: a 40MB document that 400s or times out reports 'could not send x' into a slice nothing reads. Pre-dates the local-file work (URL fallbacks have the same hole) but archie-core-absb's guarantee that non-delivery is always visible depends on it.\n\nFound by adversarial review of 9a45fbb. internal/channels/telegram/live.go:419-437 with :498-532.\n\n## Acceptance Criteria\nA media failure occurring after the live reply has finalized still reaches the user -- e.g. as its own follow-up message rather than an edit to a message nothing re-renders. Covered by a test that finalizes first and fails the send second.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T15:54:42Z","created_by":"Sam Catlow","updated_at":"2026-09-01T15:18:56Z","closed_at":"2026-09-01T15:18:56Z","close_reason":"Fixed: stopRendering now marks the reply finalized, and appendFallbackLine sends a standalone follow-up message instead of writing into a dead render buffer. Covered by TestLiveReplyMediaFallbackAfterFinalizeSendsFollowUp.","external_ref":"https://github.com/samcharles93/archie-core/issues/646","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h3lg","title":"Dashboard swallows failed operator actions, showing nothing in the UI","description":"When an operator action fails, the dashboard surfaces nothing. Pressing Stop on a running task issued POST /api/tasks/3/action, received 403, and the only evidence anywhere was a browser console line: \"Failed to load resource: the server responded with a status of 403\". The page itself showed no error, no toast, no change of state -- the button simply appeared to do nothing.\n\nThis is how archie-core-440c (every dashboard mutation 403s behind a TLS-terminating reverse proxy) went unnoticed: the operator pressed Stop, saw nothing happen, and reasonably concluded the task was unstoppable rather than that the request had been refused. The bug was only found by opening devtools.\n\nConfirmed live 2026-08-25 while signed in to the production dashboard.\n\n## Why this is its own bead\n\n440c fixes the 403. This bead fixes the fact that ANY failed action is invisible -- a 500, a store failure, a refused state transition, an expired session -- and each of those has its own way of going wrong. Fixing only 440c leaves the next failure equally silent.\n\nNote internal/webui/api_tasks.go already returns distinguishable, human-readable failures (\"missing CSRF header\", \"cross-origin mutation refused\", \"runtime task control is unavailable\"). The server side is doing its job; the client discards it.\n\n## What is needed\n\n- A failed action tells the operator it failed, in the UI, with the server's reason where one is given.\n- The distinction that matters most: refused (403, bad state, not permitted) versus broken (5xx, network). The operator's next move differs -- the first is \"you cannot do that\", the second is \"try again or check the daemon\".\n- A 401 or an expired forward-auth session should prompt re-authentication rather than reading as a generic failure, since the deployment sits behind Authelia.\n- The optimistic UI must not show an action as applied when it was refused.\n\nPer CLAUDE.md the frontend is one folder per feature under ui/src/\u003cfeature\u003e with shared primitives in ui/src/base -- error surfacing used by more than one feature belongs in base, extracted on the SECOND real consumer, not in anticipation. Remember ui/dist is committed: run `task ui` and commit the rebuilt output in the same change.\n\n## Steps to Reproduce\n\n1. Load the dashboard in a deployment where mutations fail (any 440c-affected proxied deployment reproduces it directly).\n2. Press Stop, Retry, Abandon or Archive on a task.\n3. Observe the request fails in devtools while the page reports nothing.\n\n## Acceptance Criteria\n\nA failed operator action is reported in the dashboard with the server's reason where supplied; refused and broken failures are distinguishable to the operator; an authentication failure prompts re-auth rather than a generic error; no optimistic state change survives a failed request; dashboard tests cover a refused action, a server error and a network failure; ui/dist is rebuilt and committed.\n","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T15:49:18Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/629","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-kkeg","title":"No byte-for-byte conversation replay: transcripts cannot be exported or examined","description":"Asked to save a complete transcript -- \"everything. My messages, yours, tools everything. Also save the agents logs\" -- the agent could not. It produced a summary archive and honestly documented the limitation: no chat export exists, and the task-log responses were clipped at the tool's 50 KB cap.\n\nSam's requirement: \"we should be able to receive and view and examine byte-for-byte replays of an entire transcript. exactly the commands run, the results received for those commands, the user messages, agent responses, EVERYTHING.\"\n\n## What exists and what does not\n\ninternal/gateway has session tooling -- session_list, session_resume, session_title, session_delete -- so sessions are already first-class and persisted (the turn ledger backs /gateway's replay of completed-duplicate turns, and archie-core-ippu made tool activity part of that record). What is missing is retrieval: nothing exposes a session's full contents for export or examination.\n\nEstablish first exactly what is persisted per turn today, because the answer determines whether this is an export feature or a capture feature. If tool ARGUMENTS and full tool RESULTS are not currently retained -- only rendered summaries -- then byte-for-byte replay requires changing what is written, not just adding a reader. That distinction is the main open question and should be settled before design.\n\n## Requirements\n\n- Fidelity: user messages, agent responses, every tool call with its arguments, and every tool result, in order, with timestamps. Not a rendered summary, and not the truncated preview the chat UI shows.\n- Retrieval: usable for a whole session, not capped at a tool-result size limit. Bulk delivery almost certainly belongs on the send_file path (archie-core-absb) rather than in a tool result -- write the file, deliver the file.\n- Examination, not just download: an operator should be able to inspect a replay in the dashboard, which is where the event inspector already lives.\n- Honesty: if anything is unavailable (rotated, compacted, never captured), the export must say so explicitly rather than presenting a partial record as complete. The agent got this right by hand; the mechanism should guarantee it.\n\n## Constraints\n\n- Transcripts contain secrets by nature -- tool arguments carry tokens, results carry file contents. internal/memory/scrubber and gateway/stream.go's sensitiveParameterKey are existing prior art for redaction and should be reused rather than reimplemented. Decide explicitly whether an export is redacted, raw, or offers both, and who may request one.\n- Retention: a full-fidelity record is large. Decide what is kept and for how long, consistent with the 7-day payload retention already decided for captured events.\n\n## Acceptance Criteria\n\nAn operator can export a complete session transcript containing user messages, agent responses, tool calls with arguments and tool results with content, in order and timestamped; the export is delivered as a file rather than clipped into a tool result; a replay can be examined in the dashboard; anything missing from the record is stated explicitly in the export; redaction policy is decided, documented and applied; tests cover a session larger than any tool-result cap and assert no gaps or reordering.\n","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:56Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/630","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-wp9s","title":"/status and /tasks have the wrong division of labour","description":"Sam's words: \"/status is fucking annoying. I'm invoking an actual status update, receiving minor information as well as shit I can get elsewhere. What's worse is that the /tasks command is meant to be for viewing the running agents, not /status.\"\n\nObserved 2026-08-24, the entire output of /status was:\n\n Tasks Parked: 2\n Runtime Provider: OpenAI Model: openai/gpt-5.6-luna\n\nTwo problems in one screen. It answers the question /tasks should own (what work is in flight), and it answers it thinly -- a count, with no task identity, no stage, no age, nothing actionable. Everything else it shows is static configuration available elsewhere. Later in the same session /status reported \"Running: 1\" for a task that was stuck in a failure loop and going nowhere, which is the specific case where a bare count actively misleads.\n\n## The division of labour to restore\n\n- `/tasks` owns WORK: what is running, what is parked and why, what needs the operator. This is the live view of the agents, and it is where task identity, workflow, stage, attempt and age belong.\n- `/status` owns HEALTH: is the daemon well. Broker connectivity, provider reachability, channel state, container pool, queue depth, last poll, version. The things an operator checks when something feels wrong and which are NOT visible elsewhere in chat.\n\nNeither should be a thin duplicate of the other, and neither should pad itself with static config the operator already knows.\n\n## Related, decide together\n\narchie-core-624 (task_action chat tool) adds operator verbs for tasks. /tasks is the natural surface for discovering the ids those verbs act on, so the two should be designed as one flow: see the work, then act on it. Check what internal/gateway/task_tools.go already returns before adding a new query path -- ChatTaskSummary may already carry most of what /tasks should show.\n\n## Steps to Reproduce\n\n1. Run /status in chat with tasks parked and one running.\n2. Observe a parked/running COUNT plus provider and model, with no way to identify or act on any task.\n3. Run /tasks and observe the overlap.\n\n## Acceptance Criteria\n\n/tasks shows the live work with enough identity and state to act on it (id, title, status, workflow/stage, age) and is the documented way to view running agents; /status reports daemon health that is not obtainable elsewhere in chat and does not duplicate the task list; a task that is running but not progressing is distinguishable from one making progress; the command descriptions registered with the platform match what each actually does.\n","notes":"Phase 1 shipped 2026-09-03 (commit 370b0ee): /tasks is a new command (identity, title, status, workflow/stage, age via UpdatedAt, attempt once retried, parked reason), sorted actionable-first; /status's itemized per-status task counts replaced with one aggregate 'Queue: N in flight (...)' line (running/waiting/parked only). Runtime (provider/model) left in place for now -- open question below.\n\nPhase 2 (broker connectivity, provider reachability, channel state, container pool, last poll) is NOT implemented -- proposed resolution in docs/prds/status-health-surface.md, verified against the real tree and split into cheap (broker connectivity via nats.Conn.Status(), container pool's already-tracked active count, a new last-poll timestamp) vs needs-a-decision (provider reachability: live probe vs last-known-outcome; channel state: likely via the existing ChannelManager). Awaiting Sam's sign-off before implementing Phase 2 -- do not close this bead until Phase 2 lands or is explicitly descoped.\n\nAlso found while doing this (filed separately, not folded in): archie-core-mxls -- /agents is registered and advertised (Telegram command menu + /help) but Router.Agents is never wired by any composition-root call site, so it always answers 'not configured' in production. /tasks now covers most of what /agents' shape was for; Sam's call whether to wire/delete/redefine /agents.","status":"in_progress","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:33Z","created_by":"Sam Catlow","updated_at":"2026-09-02T21:17:49Z","started_at":"2026-09-02T21:15:40Z","lease_expires_at":"2026-09-02T21:20:40Z","heartbeat_at":"2026-09-02T21:15:40Z","external_ref":"https://github.com/samcharles93/archie-core/issues/631","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8qpa","title":"Chat agent does not know its own repository or workspace, wasting turns rediscovering them","description":"Asked to raise a GitHub issue, the agent spent roughly eight tool calls working out where it lives: `pwd`, a `find` over /home/sam/projects returning 139 lines, `git remote -v`, a grep over RELEASING.md returning 92 lines, and a failed `read` of a README that does not exist. It eventually located the repository and filed the issue correctly, but every one of those calls was rediscovering a fact the daemon already knows.\n\nSam's words: \"Yep, thats frustrating AF!\"\n\n## Why this is worth fixing structurally\n\nIt is not only slow and expensive. It is a correctness risk: an agent that has to guess which checkout it is looking at can act on the wrong one, and on this host more than one archie-core checkout exists. It also degrades every task that begins with orientation rather than work.\n\n## What to do\n\ninternal/gateway/BuildSystemPrompt renders templates/archie.md.tpl, which already carries an `\u003cenv\u003e` block. Per CLAUDE.md that template is the single place instruction precedence, core rules and the `\u003ctools\u003e`/`\u003cenv\u003e` blocks live -- personas are the STYLE layer only, so this belongs in the template, never in a persona string.\n\nPut the facts the daemon already holds into `\u003cenv\u003e`: the configured workspace path, the repositories under management with their forge and default branch, and the identity in use. Configuration is the source of truth ([repos] entries, chat.workspace); do not have the prompt claim anything the daemon cannot confirm, and do not hardcode paths.\n\nNote the same rule that governs `\u003ctools\u003e` applies here: the block must be built from what the daemon actually has, because a prompt that names a repository the agent cannot reach is worse than silence -- the model will confidently act on it.\n\n## Acceptance Criteria\n\nThe chat agent knows its workspace path, managed repositories and identity without probing the filesystem; the block is rendered from live configuration rather than hardcoded; an empty or unconfigured value renders as explicitly unknown rather than as a plausible-looking default; a task that previously required filesystem archaeology to orient completes without it; tests assert the block reflects configuration and omits nothing the daemon knows.\n","status":"open","priority":2,"issue_type":"feature","assignee":"samcharles93","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:15Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/632","metadata":null,"labels":["agent"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8s7v","title":"[EPIC] Intercom: let the chat agent talk to running agents, the curator, and peers","description":"Today the chat agent can only observe autonomous work -- list tasks, read logs -- and act on it as an outsider through coarse verbs (spawn, stop). It cannot TALK to a running agent. An operator who can see a task going wrong has no way to say \"stop guessing, the config lives at X\" without killing the task and starting over, losing everything the agent had already worked out. Archie should behave like a living system whose parts can address each other, not a set of isolated processes with a dashboard bolted on.\n\n## Prior art: pi-intercom\n\nPi ships `pi-intercom`, which solves this shape for Pi sessions on one machine and is worth reading before designing (/home/sam/.pi/agent/npm/node_modules/pi-intercom; skills/pi-intercom/SKILL.md is the usage guide). Its model:\n\n- Sessions take names (`/name planner`, `/name worker-backend`) and address each other by name.\n- `send` -- fire-and-forget notification. Task assignment, status, notice.\n- `ask` -- BLOCKS until the target replies, with a timeout. The blocking form is the interesting one: it lets a worker stop and get a decision instead of guessing.\n- `reply` -- answers an inbound ask, threaded automatically.\n- `pending` -- lists unresolved inbound asks, i.e. who is waiting on you.\n- `list` -- connected sessions and their state (idle / thinking / tool), for discovering targets.\n- Its use cases map directly onto archie: planner-to-worker delegation, context and findings handoff, blocking clarification, subagent escalation (`need_decision`, `interview_request`), cross-project coordination.\n\n## What is genuinely different here\n\nDo NOT copy pi-intercom's transport. It ships its own local IPC broker (broker/broker.ts, a socket server with framing, spawn and runtime-claim logic) because Pi has no message bus. **Archie already has one**: NATS, with per-task subjects already defined in internal/agentexec/subjects.go (archie.agent.\u003cid\u003e.system and .events) and a request/reply pattern already used by taskrun, forgerpc, storerpc and worktreerpc. Building a second broker alongside it would be the \"two parallel abstractions\" mistake this repo already made once with gateway.BasePlatformAdapter.\n\nSo the real design questions are:\n1. Does agent-directed messaging ride the existing per-task subjects, or does it need its own contract and subject family? Note CLAUDE.md's recorded NATS traps -- work-queue retention forbids overlapping consumers, and reply inboxes are core-NATS-only and are not stream subjects.\n2. What is addressable? Running tasks have ids. The curator, channels and the daemon itself do not have a uniform identity for this purpose. An address space has to be decided before verbs are.\n3. How does a BLOCKING ask work against an agent that is mid-model-call? A worker is not sitting in a receive loop; it is inside an agentloop turn. Delivering a message it will actually notice, without corrupting the turn, is the hard part -- and is where this stops being a transport problem.\n4. Authorization: an operator messaging their own task is fine. Cross-identity messaging is not, and multi-identity deployments are supported (deployments/multi-forge-github-gitea.toml). Whatever the gateway's task tools enforce for identity scoping, this must enforce too.\n5. Does an inbound operator message become part of the agent's context permanently, or a one-shot injection? This decides whether it can be used to steer a task or only to interrupt it.\n\n## Relationship to existing work\n\n- Overlaps archie-core-absb (agent cannot send local files) only in spirit: both are about the agent being able to communicate outward.\n- The curator (internal/domain/curator) is a natural second participant after running tasks.\n- Any design here should be checked against docs/architecture/organisation.md: the domain declares the contract it needs; the transport implements it.\n\n## Success Criteria\n\nAn operator can address a running agent from chat and have it receive the message without the task being killed and restarted; a blocking ask returns the agent's answer or times out cleanly; participants are discoverable with their current state; messaging is identity-scoped so one identity cannot address another's work; the mechanism reuses the existing NATS transport rather than introducing a second broker; a design decision is recorded in docs/prds/ before implementation, per CLAUDE.md's scope discipline.\n","notes":"Provenance correction 2026-08-25: this bead's description says 'Pi ships pi-intercom'. That is WRONG and Sam corrected it -- pi-intercom is a THIRD-PARTY PLUGIN written by a different developer solving their own problem, not a Pi feature and not endorsed by Pi. Weigh it accordingly: it is one developer's solution worth reading for its verb vocabulary (send/ask/reply/pending/list) and for the blocking-ask idea, notLine truncated
|
||||
{"_type":"issue","id":"archie-core-absb","title":"Agent cannot send local files: Telegram delivery is URL-fetch only","description":"The agent can produce a file on the host -- a log dump, a screenshot, a written archive, a diff -- and has no way to deliver it to the operator. Asked to send a saved transcript, it replied with a \"Download the archive\" link twice; nothing arrived either time, and it had no signal that anything had failed.\n\n## Why video works and files do not\n\n`telegramMediaSender.dispatch` (internal/channels/telegram/media.go:97) builds every attachment as:\n\n file := \u0026models.InputFileString{Data: att.URL}\n\n`InputFileString` tells Telegram to FETCH the given URL itself. That works for the existing media path because those attachments are remote-hosted -- MiniMax returns a public URL for a generated video, which is what `MultimodalResult.URLs` was added for. It cannot work for anything produced locally: a daemon-host path like /home/sam/archive.md is not a URL Telegram can fetch, so the send silently does nothing useful.\n\nThe `case \"document\"` branch (media.go:124-127) already calls `bot.SendDocument`, so the routing exists. Only the file SOURCE is wrong.\n\n## What is needed\n\nA way for the agent to send a LOCAL file as an attachment -- documents, logs, screenshots, images, any media -- not a link. The go-telegram/bot SDK supports upload via a reader (`models.InputFileUpload` with an io.Reader) as an alternative to `InputFileString`; the sender needs to choose between fetch-by-URL and upload-by-reader based on whether the attachment is remote or local.\n\nExplicitly NOT the fix: exposing an external/public URL for local files. That trades a missing feature for a hosting and access-control problem.\n\n## Constraints to respect\n\n- Telegram enforces upload size limits (50 MB for documents via the Bot API at time of writing); exceeding them must produce a clear error to the operator, not a silent drop.\n- The file tools are workspace-confined unless `[chat] unrestricted_filesystem = true`. Sending must not become a way around whatever confinement is configured -- resolve and check the path under the same policy the read tool applies.\n- A failed send must surface as a failure the agent can see and report. The current defect is not that the agent lied; it is that success and silent non-delivery are indistinguishable to it.\n\n## Acceptance Criteria\n\nThe agent can send a local file through Telegram and the operator receives it as an attachment; local and remote attachments both work, choosing upload-by-reader or fetch-by-URL as appropriate; a send that fails (too large, unreadable, outside the configured confinement) returns an error the agent surfaces rather than reporting success; existing remote-URL media delivery is unchanged and still covered by tests.\n","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T15:32:07Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:19Z","closed_at":"2026-08-24T15:43:20Z","close_reason":"send_file tool plus upload-by-reader delivery; commit 9a45fbb","external_ref":"https://github.com/samcharles93/archie-core/issues/634","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787583419901-1-85796c0b","title":"Allow parked agent jobs to be closed or archived","description":"## Problem\nParked agent jobs remain visible indefinitely, but the task-management interface currently exposes no action to close or archive them. This leaves stale jobs in the active job history and requires manual cleanup outside the normal workflow.\n\n## Observed behavior\nThe following old jobs are parked and cannot be closed through the available task-management actions:\n\n- Job #1 — `daemon: label dispatch trigger with empty label matches every open issue`\n- Job #2 — `archied: [[repos]] entries can't span more than one forge`\n\nThe interface can list and inspect parked jobs, but provides no close/archive operation.\n\n## Expected behavior\nProvide an explicit operation for a parked job, such as:\n\n- `close` when the job is definitively finished or no longer actionable;\n- `archive` when it should be removed from the active job list while retaining history;\n- optionally `reopen` if a parked job needs to be resumed.\n\nThe operation should persist the state, be reflected in task listings, and retain the job logs and audit history.\n\n## Acceptance criteria\n- A user can close or archive a parked job from the supported task-management interface/API.\n- The operation is idempotent and reports a clear error for invalid state transitions.\n- Closed/archived jobs no longer appear among active or parked jobs by default, while remaining queryable.\n- Existing logs, attempts, and failure details remain accessible.\n- Tests cover closing, archiving, reopening (if supported), and repeated operations.\n","status":"closed","priority":2,"issue_type":"bug","assignee":"samcharles93","created_at":"2026-08-24T13:44:17Z","updated_at":"2026-09-02T11:02:37Z","closed_at":"2026-09-02T11:02:37Z","close_reason":"Already implemented and in use: parked tasks expose Retry/Abandon/Reject — Abandon/Reject transition to terminal Won't-do and close the forge issue; terminal tasks then expose Archive (removes the row, keeps the durable audit event); Retry reopens parked work. Landed in de60802 (archive+retry controls) and 52bb018 (reject from every non-terminal state incl. parked); covered by TestLifecycleSpecificTaskActions, TestTaskListExposesLifecycleActions, TestArchiveRemovesOnlyOneTerminalTask.","external_ref":"https://github.com/samcharles93/archie-core/issues/624","source_system":"github:https://github.com/samcharles93/archie-core/issues/624:624","metadata":null,"labels":["agent","bug","ux"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-5bsf","title":"Rollback the managed agent image when a runtime update fails health checks","description":"The runtime update path rebuilds the Docker image, but scripts/archie-update-watchdog only restores the unused host archie-agent binary. A failed health check can report a rollback while the task-container image remains on the failed runtime. Design and implement image-reference preservation/restoration for the configured managed worker image, with tests for runtime-only and combined updates.","acceptance_criteria":"A failed runtime-only update restores the prior worker image before restarting archied; a combined update restores both daemon and worker image atomically; update tests prove the configured managed image, not a host worker binary, is the rollback target.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T04:37:24Z","created_by":"Sam Catlow","updated_at":"2026-08-24T05:19:34Z","closed_at":"2026-08-24T05:19:34Z","close_reason":"Completed; reconciled with the already-closed GitHub issue.","external_ref":"https://github.com/samcharles93/archie-core/issues/621","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-q15y.4","title":"Make native archied embedded NATS and managed containers the default deployment","description":"Supported examples and install.sh currently generate agent.mode=inprocess and treat external Compose NATS as the container path. Migrate the default operator experience to native archied plus embedded NATS plus managed task containers, while keeping external NATS as the advanced broker option.","acceptance_criteria":"Fresh install produces the supported NATS-only container topology; systemd runs native archied; interactive host chat authority is unchanged; no Compose NATS service is required for embedded mode; external NATS profile remains documented and load-tested.","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T03:03:38Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:58:42Z","started_at":"2026-08-24T04:21:30Z","closed_at":"2026-08-24T06:58:42Z","close_reason":"Implemented in c978f10 (feat(deployment): default to managed NATS workers). Verified: no agent.mode/inprocess remains in install.sh, deployments/*.toml or config.example.toml; deployment_contract_test.go added to enforce it.","external_ref":"https://github.com/samcharles93/archie-core/issues/622","metadata":null,"dependencies":[{"issue_id":"archie-core-q15y.4","depends_on_id":"archie-core-q15y","type":"parent-child","created_at":"2026-08-24T03:03:38Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-q15y.4","depends_on_id":"archie-core-q15y.1","type":"blocks","created_at":"2026-08-24T03:03:52Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-q15y.4","depends_on_id":"archie-core-q15y.2","type":"blocks","created_at":"2026-08-24T03:03:53Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-q15y.4","depends_on_id":"archie-core-q15y.3","type":"blocks","created_at":"2026-08-24T03:03:53Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":3,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-dfck","title":"Recover workflow agents that omit the required finish tool","description":"An analyse-stage agent can end normally without invoking the finish tool, producing agent idle and parking otherwise recoverable work. Add a bounded, deterministic recovery path that preserves explicit workflow completion and does not accept an unverified model final response.","notes":"Follow-up: the recovery wiring is correct inside archie-agent, but a separate architecture bug remains: embedded NATS still falls back to daemon-local execution. Tracked by the new NATS-only execution issue.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T01:24:20Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:12Z","started_at":"2026-08-24T01:24:30Z","closed_at":"2026-08-24T07:12:12Z","close_reason":"SDK v0.1.22 provides one bounded forced-finish recovery; Archie opts in through InProcessRunner. Focused test, task check, module verification, and independent adversarial review passed. Re-verified 2026-08-24: the opt-in moved from the deleted InProcessRunner to agentexec.NewLoopRunner (loop_runner.go:106 CompletionForceFinish), which is what the archie-agent worker constructs; ai-sdk still v0.1.22. [Closure restored 2026-08-24: originally closed 2026-08-24, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/623","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787522397925-3-87bd827d","title":"fix(update): install only approved changed components","description":"## Bug Description\nA gateway-only `/update` (archied/v1.13.0 while runtime remains archie/v1.9.9) fetches and builds both binaries, backs up and installs both, and rebuilds the agent image. The image build does not receive `RUNTIME_VERSION`, so the released runtime is stamped `dev`.\n\n## Steps to Reproduce\n1. Run `/update` with only the `daemon` component available.\n2. Approve the displayed snapshot.\n3. Observe `archie-update-install` build/install both components and run `docker compose build agent`.\n\n## Expected Behavior\nThe approved snapshot flows into `CommandInstaller`; only changed components are fetched/built/backed up/installed. Rebuild the agent image only for a runtime update and stamp it with the released runtime version. Preserve phase-1 result and phase-2 rollback/report metadata for gateway-only, runtime-only, both, and no-op plans.\n\n## Actual Behavior\nThe installer receives only chat/report metadata, so the script independently rebuilds everything after `git pull` and Docker uses its default `RUNTIME_VERSION=dev`.\n\n## Acceptance Criteria\n- Regression harness proves a gateway-only update never builds/installs the runtime or image.\n- Tests cover gateway-only, runtime-only, both, and no-op.\n- Released runtime images are stamped with the release version, never `dev`.\n- Rollback/report metadata remains component-aware and correct.\n- `task check` passes.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-23T15:56:13Z","updated_at":"2026-08-23T16:31:23Z","closed_at":"2026-08-23T16:31:24Z","external_ref":"https://github.com/samcharles93/archie-core/issues/606","source_system":"github:https://github.com/samcharles93/archie-core/issues/606:606","metadata":null,"labels":["bug","in-progress"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787522397855-2-792cc4d6","title":"fix: make tool progress readable and preserve project context","description":"## Problem\n\nTelegram tool progress is currently displayed as a stream of raw inline entries, for example:\n\n- tool names followed by JSON schema placeholders such as `[string]`\n- raw JSON arguments and oversized output\n- repeated output without readable grouping\n- full error dumps and turn-budget failures\n\nAgents also search broad locations such as `/home/sam` instead of staying focused on the active project/worktree, read directories as files, and emit malformed shell commands. Useful project context is not being retained cleanly across the turn.\n\n## Scope\n\n- Render tool progress as compact, readable streaming fenced code blocks (Telegram-safe).\n- Remove schema placeholders and redundant raw invocation JSON from user-visible output.\n- Truncate or offload oversized results without consuming the entire turn context.\n- Preserve concise success/failure status and actionable errors.\n- Default agent discovery and file operations to the actual project/worktree context where task context provides one.\n- Improve context retention across tool calls.\n- Add validation or guardrails for malformed shell commands where practical.\n\n## Acceptance criteria\n\n- A normal tool call is shown as a readable streaming status block, not raw JSON.\n- Tool failures remain visible but are concise and actionable.\n- Large results are bounded/offloaded and do not exhaust the turn budget.\n- Project-scoped tasks do not begin by searching unrelated home-directory data.\n- Regression tests cover rendering, failure output, truncation/offload, and project-root selection.\n- Telegram output is verified against a live deployed instance.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-23T15:35:13Z","updated_at":"2026-08-23T22:03:11Z","closed_at":"2026-08-23T22:03:11Z","external_ref":"https://github.com/samcharles93/archie-core/issues/604","source_system":"github:https://github.com/samcharles93/archie-core/issues/604:604","metadata":null,"labels":["in-progress","task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786751948782-3-837a8fd0.2","title":"Add InstallType/Reference fields to releaseupdate.Component, populate from daemon/agent/deployment profile","description":"Part 2/3 of point 4 in archie-core-1786751948782-3-837a8fd0's design. releaseupdate.Component (internal/releaseupdate/service.go:35-41) has ID/Label/Installed/Available/Changelog but no InstallType or Reference fields. Add both, and populate: archied reads its own compiled-in installtype.Type(); archie-agent reports its own over the NATS status round-trip (depends on the sibling issue that adds that round-trip); third-party dependencies Archie doesn't build (e.g. NATS) can't self-report, so their InstallType/Reference should come from the deployment profile (deployments/*.toml) rather than detection -- add the relevant fields there. Reference is something like 'container' + 'ghcr.io/samcharles93/archie-agent:1.9.0@sha256:...', not just a bare install-type string.","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-23T13:06:16Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:11Z","started_at":"2026-08-23T13:22:37Z","closed_at":"2026-08-24T07:12:11Z","close_reason":"Fixed: Component gained InstallType/Reference, populated via Service.Enrich from installtype.Type() (daemon), observed AgentStatus (agent), and [nats] config (third-party). Adversarial review clean (one lint-consistency nit fixed: use config.NATSMode* constants instead of raw strings). [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/610","metadata":null,"labels":["enhancement","webui"],"dependencies":[{"issue_id":"archie-core-1786751948782-3-837a8fd0.2","depends_on_id":"archie-core-1786751948782-3-837a8fd0","type":"parent-child","created_at":"2026-08-23T23:06:15Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786751948782-3-837a8fd0.2","depends_on_id":"archie-core-1786751948782-3-837a8fd0.1","type":"blocks","created_at":"2026-08-23T23:06:19Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786751948782-3-837a8fd0.3","title":"Surface per-component update status on Configuration page and /version","description":"Part 3/3, point 5 of archie-core-1786751948782-3-837a8fd0's design. Depends on the InstallType/Reference issue landing first -- there's nothing to surface otherwise. Add a /version endpoint and a per-component block on the Configuration page (internal/webui/api_config.go, ui/src/settings/), structured as {install_type, running_version, reference, latest_available, status} per component, where status is an enum (ok / update_available / drift / unknown) rather than a bare color. The actual comparison basis (e.g. running digest vs latest digest) should be visible on hover/expand, modeled on docker version's Client/Server nested-block convention per the original design doc.","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-23T13:06:16Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:12Z","started_at":"2026-08-23T13:29:01Z","closed_at":"2026-08-24T07:12:12Z","close_reason":"Fixed: GET /api/version + Configuration-page 'Update status' card, sourced from the InstallType/Reference/RunningVersions plumbing landed in .1/.2. Adversarial review found one real bug (Installed=='' with Available set incorrectly returned update_available instead of unknown) and one test gap (present-but-empty running-version map entry) -- both fixed, tests added, all green. [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/611","metadata":null,"labels":["enhancement","webui"],"dependencies":[{"issue_id":"archie-core-1786751948782-3-837a8fd0.3","depends_on_id":"archie-core-1786751948782-3-837a8fd0","type":"parent-child","created_at":"2026-08-23T23:06:16Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786751948782-3-837a8fd0.3","depends_on_id":"archie-core-1786751948782-3-837a8fd0.2","type":"blocks","created_at":"2026-08-23T23:06:20Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786751948782-3-837a8fd0.1","title":"Stamp archie-agent's install type and add NATS status round-trip","description":"Part 1/3 of point 4 in archie-core-1786751948782-3-837a8fd0's design. archied's own build is stamped with internal/installtype via -ldflags (Taskfile.yml:65, Dockerfile.archied:48-49), but archie-agent's build has no equivalent stamp -- Dockerfile:14 and Taskfile.yml:170 (agent build target) pass no -X installtype flag. Without it, an agent worker has nothing to self-report even once the daemon asks. Also add the NATS-side status/version request the daemon can send a running agentworker to get its install type + running version back (agentworker already has a NATS channel for logs; extend it for a status response rather than inventing a new transport). This is the prerequisite for archie-core-1786751948782-3-837a8fd0 point 4's 'archie-agent reports its own the same way' clause.","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-23T13:06:14Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:11Z","started_at":"2026-08-23T13:06:41Z","closed_at":"2026-08-24T07:12:11Z","close_reason":"Fixed: archie-agent's build is now stamped (installtype + agentworker.Version), and it reports both back to the daemon in every taskrun.Response. daemon.AgentStatus records the latest observation; daemonRunningVersions includes the agent component once one lands. Adversarial review clean (one nice-to-have comment added). [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/612","metadata":null,"labels":["enhancement","webui"],"dependencies":[{"issue_id":"archie-core-1786751948782-3-837a8fd0.1","depends_on_id":"archie-core-1786751948782-3-837a8fd0","type":"parent-child","created_at":"2026-08-23T23:06:14Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-w35v","title":"Workflows page 'Start work' form inputs unstyled (white boxes in dark theme)","description":"The Start work card on the Workflows dashboard page (ui/src/workflows/workflows.js renderStartWork) creates raw \u003cinput\u003e/\u003cselect\u003e/\u003ctextarea\u003e elements with no CSS class, so they fall back to browser default styling -- white background, black text -- against the rest of the dark-themed app. Every other form control in the app (e.g. Configuration's .kv-input in ui/src/settings/config-row.js) uses a themed class. Fix: style these form controls to match the app theme, either by reusing an existing input class or adding scoped rules in ui/src/workflows/workflows.css.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-23T12:22:59Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:10Z","closed_at":"2026-08-24T07:12:10Z","close_reason":"Fixed: themed .wf-form input/select/textarea in workflows.css to match the dark theme. [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/593","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489597262-23-f61d8b1b","title":"Docs: promote the shipped review stage into docs/architecture and reconcile CLAUDE.md","description":"Under the scope-discipline rule merged as PR #533, a design is promoted into docs/architecture/ only once it is built and true. This is that promotion, and it is deliberately a separate bead so it is not lost when the feature lands and attention moves on.\n\nDo three things once the stage ships:\n\n1. Promote the docs/prds/ decision into docs/architecture/, describing the review stage as it actually works -- not as designed. Cut anything a reader could learn from the code.\n2. Update ARCHITECTURE.md's task lifecycle: queued -\u003e running(workflow:stage) -\u003e pr_open -\u003e merged|rejected gains a review stage that can divert to waiting_human before pr_open. The current text does not mention it.\n3. Reconcile CLAUDE.md's Development Protocol. It currently tells a human or agent contributor to run the adversarial pass by hand. Once archied does this for the PRs it opens, that section needs to say which path applies to whom, or it will read as describing a manual step that is now automatic.\n\nCLAUDE.md's own rule: a comment or doc that contradicts its code is worse than none, because the next reader trusts it.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-23T12:22:29Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/586","source_system":"github:https://github.com/samcharles93/archie-core/issues/586:586","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489597173-22-c7110160","title":"Surface findings on the PR body and the dashboard","description":"The output has to land where the operator already looks, or the review is invisible work.\n\nOn the PR archie opens: a findings section stating what was checked, what was found, what was fixed, and what survived. A PR with zero findings should say the review ran and found nothing -- silence is indistinguishable from the review not running, which is the same unverified-claim problem the update-verification work (PR #530) was about.\n\nOn the dashboard and /api/tasks: a parked-for-findings task must show why, the same way a park reason is already surfaced today. An operator seeing waiting_human needs the findings without digging through logs.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-23T12:22:28Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/585","source_system":"github:https://github.com/samcharles93/archie-core/issues/585:585","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489597088-21-878229b4","title":"Calibration: confirm findings adversarially before surfacing them","description":"The risk that kills this feature is a reviewer that cries wolf. A findings list padded with speculation trains the operator to skim past it, and then the feature is worse than nothing because it consumes attention while lowering trust.\n\nBefore a finding is surfaced, it must be independently checked and marked CONFIRMED or PLAUSIBLE, with only CONFIRMED able to block. The reviewer must also be able to return zero findings, and to state which properties it checked and cleared -- a review that reports nothing is a valid and welcome result, and saying so explicitly is what distinguishes 'I checked and it is fine' from 'I did not look'.\n\nPrior art from the 2026-08-20/21 sessions on PR #530: three passes each separated confirmed from plausible, one explicitly listed properties it had verified clean, and the confirmed findings were reproduced by mutation before being trusted. That calibration is the feature, not the finding count.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-23T12:22:27Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/584","source_system":"github:https://github.com/samcharles93/archie-core/issues/584:584","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596921-19-cf6351d9","title":"Docs: reconcile plugins-and-extensions.md and ARCHITECTURE.md with the shipped event model","description":"Separate bead so it is not lost once the feature lands.\n\n1. docs/architecture/plugins-and-extensions.md is an APPROVED foundation dated 2026-07-28 and currently describes only the plugin framework. If the design bead concluded that extensions may react to events, this doc has to say how -- and if it concluded that generic untyped dispatch is allowed after all, this doc must be amended deliberately rather than contradicted by code.\n\n2. ARCHITECTURE.md describes work intake as polling. Once webhook intake ships, that is no longer the whole picture, and the task lifecycle section needs the new entry path.\n\n3. CLAUDE.md's per-package traps section should gain whatever trap this work creates -- HMAC verification, replay windows, the poll/webhook double-dispatch hazard. That section exists precisely for things an agent will otherwise break.\n\n4. config.example.toml needs the intake flag documented with its default, alongside poll_interval.\n\nCLAUDE.md's own rule: a doc that contradicts its code is worse than none, because the next reader trusts it.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-23T12:22:26Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/583","source_system":"github:https://github.com/samcharles93/archie-core/issues/583:583","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489597001-20-4a13bb0b","title":"Docs: document playbooks, bindings and the intake threat model","description":"Separate so it is not lost when the feature lands.\n\n- The playbook/binding model in docs/architecture/: what a binding is, where it is persisted, how matchers resolve, how versioning works.\n- The threat model, written down plainly: this is a public intake surface that can start agents. Record what protects it and what does not.\n- ARCHITECTURE.md task lifecycle: a task started by a playbook binding has a different provenance from a forge-issue task, and the lifecycle section should say so.\n- Operator docs: how to point an external app at archie and build a first playbook, end to end.\n\nCLAUDE.md's rule: a doc that contradicts its code is worse than none.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-23T12:22:26Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/582","source_system":"github:https://github.com/samcharles93/archie-core/issues/582:582","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787489596831-18-366fdec1","title":"Acknowledge inbound messages and tasks before starting work","description":"Archie should acknowledge an inbound user message or tracked task before beginning substantive work. The acknowledgement should be sent promptly and make it clear that Archie has received the request and is starting or queued to work on it. It should not duplicate the eventual result or create misleading acknowledgements when intake fails.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-23T12:22:25Z","updated_at":"2026-08-23T22:39:29Z","closed_at":"2026-08-23T22:39:29Z","close_reason":"Duplicate; work tracked under canonical epic","external_ref":"https://github.com/samcharles93/archie-core/issues/581","source_system":"github:https://github.com/samcharles93/archie-core/issues/581:581","metadata":null,"labels":["telegram","ux"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-3ghy","title":"Wire generate_video (MiniMax) tool end-to-end","description":"Implemented the MiniMax text-to-video generation tool and wired it through the media-delivery pipeline built for this: tool -\u003e tools.MultimodalResult -\u003e drainChatStream detection -\u003e gateway.TurnStream.Media -\u003e gateway.MediaSender (Telegram delivers inline; webui falls back to a link).\n\n## What shipped\n- internal/tools/minimax: API client (create+poll against MiniMax's v2/video_generation and v2/query/video_generation/{id}), a builtin tools.ToolEntry (generate_video), fully test-first with an injected-clock poll loop (no real sleep in tests).\n- internal/tools: extended tools.MultimodalResult with a URLs []MediaRef field, for tool results whose media lives at a remote hosted URL rather than local bytes (the existing Files field).\n- cmd/archied/telegram_setup.go: drainChatStream now detects a MultimodalResult in a tool result's Output and calls turn.Media(...) per URL, alongside the existing turn.ToolCall(...) reporting.\n- internal/config: MinimaxConfig (off by default, unlike web_fetch -- this spends real API credits per call), api_key via the existing secret.SecretRef pattern.\n- cmd/archied/bootstrap.go: registerMinimaxTool -- only registers the tool once an API key actually resolves, matching the 'do not advertise a broken capability' pattern web_fetch already uses.\n- config.example.toml: documented [tools.minimax].\n\n## Scope deliberately left out (by explicit instruction: URL-only, get it working first)\n- Image-to-video (image_url content items) -- text-to-video only.\n- Local byte/file upload delivery path -- URL-only, matches gateway.MediaSender's current URL-only design.\n- Email/webhook channel delivery -- only Telegram implements gateway.MediaSender today; other channels have no inline media path, and webui falls back to a text link (see archie-core-1786748942243-6-f109697e for the still-open 'deliver generated images through channel and web abstractions' work).\n- No OpenAI video provider -- only MiniMax implemented, per this issue's scope. A second provider should follow the same tool-package shape (internal/tools/\u003cprovider\u003e) if wanted.\n- No spend guard / approval gate on the tool despite it costing real credits per call (classified ClassMutating, not RequiresApproval) -- flagged in tool.go's doc comment as a candidate follow-up if usage shows it's needed.","acceptance_criteria":"task check passes; go test ./... green except the pre-existing unrelated internal/app/agentworker architecture-test failure; golangci-lint clean on every touched package; config.example.toml documents [tools.minimax].","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-22T15:34:24Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:10Z","closed_at":"2026-08-24T07:12:10Z","close_reason":"Shipped and verified: task check equivalent (fmt/vet/build/test/lint) is clean across every touched package, red-then-green throughout. See the issue description for what's in scope and what's explicitly deferred. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/594","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-azbo","title":"Remove dead BasePlatformAdapter interface from internal/gateway","description":"`gateway.BasePlatformAdapter` (internal/gateway/adapter.go, Connect/Disconnect/Send/ChatInfo) is implemented by nothing outside its own test stub. It landed in commit bc1caf6 alongside the Session types and was never wired.\n\nEvery live channel instead implements `channels.Channel` (= `gateway.Gateway`: Name/Start/Stop, plus ConfigSchema/ValidateConfig) -- asserted at internal/channels/telegram/telegram.go:1229, internal/channels/email/email.go:389, internal/channels/webhook/webhook.go:224. So the repo carries two parallel channel abstractions and the newer one is inert.\n\nIt also has an internal contradiction that is likely why it was never implemented: the doc comment says the daemon instantiates 'one adapter per active bot identity x platform' (adapter.go:59) but `ChatInfo(ctx) (ChatInfo, error)` is documented as 'static metadata about the conversation a platform adapter is connected to' (adapter.go:36-38) with no chat argument. Telegram's Gateway is a single instance serving many chats, so ChatInfo(ctx) has no single answer. Send(ctx, MessageEvent) is fine for both models since MessageEvent carries ChannelID; ChatInfo is the part that only makes sense per-conversation.\n\nOutbound delivery is assigned to the not-yet-built `internal/domain/messaging` by docs/architecture/migration-decisions.md section 2, so this interface should not be revived in place -- it should be deleted and its intent re-expressed there.\n\n## Scope\n\n- Delete BasePlatformAdapter and its test stub from internal/gateway/adapter.go / adapter_test.go.\n- Keep SendResult and ChatInfo structs if domain/messaging or the media work still wants them; they are separable from the interface.\n- Decouple gateway.CapabilitiesOf from BasePlatformAdapter (it currently takes one) so the capability mechanism survives the removal.\n\n## Acceptance criteria\n\n- BasePlatformAdapter no longer exists; `task check` passes.\n- No behaviour change: nothing implemented it, so nothing should need rewiring.\n- Any type retained from adapter.go has at least one live consumer, or is removed too.","notes":"Discovery confirmed CapabilitiesOf is absent from the current checkout and gateway history. SendResult and ChatInfo have no live consumers, so all three legacy declarations are removed. Red test: TestLegacyPlatformAdapterTypesAreRemoved failed on BasePlatformAdapter, ChatInfo, and SendResult before deletion; gateway package suite passes after deletion. Full task check currently reaches one unrelated pre-existing failure: internal/app/agentworker TestApplicationOwnsNoTransportWireMechanics reports persistent_runner.go imports JSON wire encoding.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-22T12:04:10Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:09Z","started_at":"2026-08-22T12:08:39Z","closed_at":"2026-08-24T07:12:09Z","close_reason":"Removed the unwired BasePlatformAdapter, SendResult, ChatInfo, and their test-only stub. CapabilitiesOf is absent from the current checkout/history. Gateway and worktree tests pass. task check passes all packages except the pre-existing tracked agentworker architecture failure archie-core-hqst. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/595","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-hqst","title":"TestApplicationOwnsNoTransportWireMechanics fails: persistent_runner.go imports encoding/json","description":"internal/app/agentworker/architecture_test.go's TestApplicationOwnsNoTransportWireMechanics fails on main (pre-existing, unrelated to archie-core-qk8m): persistent_runner.go imports encoding/json, tripping the check that agentworker's app layer owns no transport wire mechanics. Introduced by e351581 (feat(storage): persist agent project state). Confirmed via git stash that this fails identically with none of the mcp-npm-cache changes applied.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-22T11:09:58Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:59:35Z","started_at":"2026-08-22T12:16:11Z","closed_at":"2026-08-24T06:59:35Z","close_reason":"Resolved on main: persistent_runner.go no longer imports encoding/json and TestApplicationOwnsNoTransportWireMechanics passes.","external_ref":"https://github.com/samcharles93/archie-core/issues/596","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.9","title":"Align branch naming behavior, API, tests, and documentation","description":"branchPrefix ignores title and body despite the documented title-prefix contract, and branchSlug documents 40 characters while implementing 60.\n\nRe-verified against main (internal/worktree/worktree.go). Three of the four original defects remain; the checked-in FIXME is already gone.\n\n- `archieBranch` (line 610-612) documents \"conventional commit prefix from the issue title when possible, falls back to labels\", but `branchPrefix(title, body, labels)` (line 632) switches only on `labels` and returns \"feat\" otherwise. `title` and `body` are dead parameters.\n- `strings.TrimSuffix(prefix, \"\")` (line 616) is a no-op: TrimSuffix with an empty suffix always returns its input, so the guard it appears to express does nothing.\n- `branchSlug`'s doc comment (line 652-653) says \"max 40 chars\"; the implementation breaks at `b.Len() \u003e= 60` (line 662).\n- No FIXME or TODO remains in the file.\n\n## Steps to Reproduce\n\n1. Call `archieBranch(12, \"fix: crash on empty payload\", \"\", \"\")` with no labels.\n2. Expected per the doc comment: prefix `fix` derived from the title. Actual: `feat/12-fix-crash-on-empty-payload` — the title prefix is ignored and also left duplicated in the slug, because the strip branch only fires when `prefix` already matches the title.\n3. Call `archieBranch(12, \"\u003ctitle of 80+ characters\u003e\", \"\", \"bug\")` and observe the slug runs to 60 characters, not the 40 the doc comment promises.\n\n## Acceptance Criteria\n\nThe chosen title/label precedence is explicit and tested for unlabeled and conflicting inputs; dead parameters and the TrimSuffix no-op are removed; slug documentation and boundary tests agree with the implemented limit; scoped lint passes.\n","acceptance_criteria":"The chosen title/label precedence is explicit and tested for unlabeled and conflicting inputs; dead parameters and no-op residue are removed; slug documentation and boundary tests agree with 60; scoped lint passes.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:48Z","created_by":"Sam Catlow","updated_at":"2026-08-24T08:15:49Z","started_at":"2026-08-24T07:42:11Z","closed_at":"2026-08-24T08:15:49Z","close_reason":"Fixed: precedence is now title-first via parseTitlePrefix with a labels fallback and 'feat' default; the strings.TrimSuffix(prefix, \"\") no-op is gone; the dead body parameter is removed from archieBranch and its call site (worktree.go:131); branchSlug's doc now says 60, matching the implementation. go fix later modernised parseTitlePrefix to strings.Cut -- verified equivalent (Cut splits on the first separator; ok mirrors idx != -1). Verified by inspection rather than a red run, since the signature change prevents compiling the tests against pre-fix code. task check green; fresh adversarial review zero findings.","external_ref":"https://github.com/samcharles93/archie-core/issues/597","dependencies":[{"issue_id":"archie-core-1ysw.9","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:48Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.7","title":"Clean no-change worktrees at terminal completion","description":"BuildNoChanges transitions directly to merged without a PR, bypassing the only production worktree cleanup path and leaking a full clone.\n\nConfirmed still present on main. `closeNoChangesIssue` (internal/domain/workflow/steps.go:67-77) sets `Outcome{Status: store.StatusMerged}` directly, with no worktree removal. The only two production callers of `worktree.Manager.Cleanup` are internal/daemon/daemon.go:769 and :788, both inside the PR-state polling loop that transitions out of `StatusPROpen`. A task that reaches `merged` without ever opening a PR never enters that loop, so its clone is never removed.\n\n## Steps to Reproduce\n\n1. Dispatch a task whose builder stage completes with `StatusPassed` but produces no diff, so `implement.go:166` sets `tc.BuildNoChanges = true`.\n2. Let `StageCommitPush` run: it takes the `BuildNoChanges` branch, closes the issue, and sets the outcome to `merged`.\n3. Observe the task row reaches `merged` with no PR number, so the daemon's `PRState` polling loop never sees it.\n4. Inspect the workspace root: `\u003cwork_dir\u003e/\u003cbase64(owner)\u003e/\u003cbase64(repo)\u003e/issue-\u003cn\u003e/` still contains the full clone.\n5. Repeat for further no-change tasks and watch the directory count grow unbounded — nothing else removes them.\n\n## Acceptance Criteria\n\nBoth direct and container no-change completion remove the identity-correct worktree while parked worktrees remain available; lifecycle regression tests cover the terminal path.\n","acceptance_criteria":"Both direct and container no-change completion remove the identity-correct worktree while parked worktrees remain available; lifecycle regression tests cover the terminal path.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:47Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:59:39Z","started_at":"2026-08-24T07:42:10Z","closed_at":"2026-08-24T07:59:39Z","close_reason":"Closed","external_ref":"https://github.com/samcharles93/archie-core/issues/598","dependencies":[{"issue_id":"archie-core-1ysw.7","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:46Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.5","title":"Preserve three-dot failure semantics without a merge base","description":"patch silently computes a direct tree diff when base and HEAD have no merge base, contradicting its three-dot contract and corrupting diff-cap and gate inputs.","acceptance_criteria":"Unrelated histories return a clear error from Diff, ChangedFiles, and ChangedLines; shared-history merge-base behavior remains covered.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:46Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:00:29Z","started_at":"2026-08-22T11:55:44Z","closed_at":"2026-08-24T07:00:29Z","close_reason":"Fixed on main: patch() now errors with 'no common ancestor' when MergeBase returns no bases (worktree.go:498-501) instead of falling back to a direct tree diff, so Diff/ChangedFiles/ChangedLines all fail closed on unrelated histories.","external_ref":"https://github.com/samcharles93/archie-core/issues/599","metadata":null,"dependencies":[{"issue_id":"archie-core-1ysw.5","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:45Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.6","title":"Do not report push failure after successful publication","description":"Push publishes the remote ref before writing unused local upstream metadata, then returns local config errors as if publication failed.\n\nConfirmed still present on main: `Manager.Push` (internal/worktree/worktree.go:414-449) completes `r.PushContext` successfully, then calls `r.Config()` / `r.SetConfig(cfg)` to record branch upstream. Either of those returns `read repo config: %w` or `record branch upstream: %w` from `Push`, so a caller sees a push failure for a branch that is already published on the forge.\n\n## Steps to Reproduce\n\n1. Prepare a task worktree and commit a change so there is a branch to publish.\n2. Make the local repository config unwritable or unreadable after the remote is reachable (e.g. `chmod 000 \u003cworktree\u003e/.git/config`, or a `.git/config` the go-git config parser rejects).\n3. Call `Manager.Push(ctx, dir, branch)`.\n4. Observe the remote branch exists on the forge, but `Push` returns `record branch upstream: ...` (or `read repo config: ...`).\n5. The daemon treats that error as a failed publication and parks the task, even though the PR branch is live.\n\n## Acceptance Criteria\n\nA post-publication metadata failure cannot park the task as an unsuccessful push; tests verify the remote ref and returned result remain consistent.\n","acceptance_criteria":"A post-publication metadata failure cannot park the task as an unsuccessful push; tests verify the remote ref and returned result remain consistent.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:46Z","created_by":"Sam Catlow","updated_at":"2026-08-24T08:15:47Z","started_at":"2026-08-24T07:42:09Z","closed_at":"2026-08-24T08:15:47Z","close_reason":"Fixed: recordUpstream extracted from Push (worktree.go:465); a post-publication config failure is now a logged warning and Push returns success once the remote ref is published. Manager gained an optional Log field with a slog.Default() fallback. Verified by inspection rather than a red run -- the test uses the new Log field so it cannot compile against the pre-fix code. task check green; fresh adversarial review (independent, did not write the code) zero findings.","external_ref":"https://github.com/samcharles93/archie-core/issues/600","dependencies":[{"issue_id":"archie-core-1ysw.6","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:46Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.4","title":"Fail refresh when the configured base cannot resolve","description":"Prepared worktrees currently swallow every resolveBase error and report successful refresh against stale history.","acceptance_criteria":"Prepared-worktree refresh returns a contextual error for a missing, renamed, or invalid base; fresh and reused Prepare paths have consistent tests.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:45Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:00:23Z","started_at":"2026-08-22T11:52:19Z","closed_at":"2026-08-24T07:00:23Z","close_reason":"Fixed on main: prepared-worktree refresh now returns the resolveBase error instead of swallowing it (worktree.go:253-258, 'a missing base is configuration or repository drift and must fail closed'); resolveBase tries the qualified remote ref then origin/\u003cbase\u003e and errors otherwise.","external_ref":"https://github.com/samcharles93/archie-core/issues/601","metadata":null,"dependencies":[{"issue_id":"archie-core-1ysw.4","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:44Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-j8b4","title":"Implement persistent session memory and plugin storage","description":"Replace the PRD section 3 placeholder in internal/storage/storage.go with the specified persistent storage behavior for session.jsonl, memory.jsonl, and plugins.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-22T10:32:31Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:08Z","started_at":"2026-08-22T10:32:37Z","closed_at":"2026-08-24T07:12:08Z","close_reason":"Implemented persistent session transcript, cross-session memory, and staged plugin storage [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/602","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.6","title":"Docs: document playbooks, bindings and the intake threat model","description":"Separate so it is not lost when the feature lands.\n\n- The playbook/binding model in docs/architecture/: what a binding is, where it is persisted, how matchers resolve, how versioning works.\n- The threat model, written down plainly: this is a public intake surface that can start agents. Record what protects it and what does not.\n- ARCHITECTURE.md task lifecycle: a task started by a playbook binding has a different provenance from a forge-issue task, and the lifecycle section should say so.\n- Operator docs: how to point an external app at archie and build a first playbook, end to end.\n\nCLAUDE.md's rule: a doc that contradicts its code is worse than none.\n\nPROGRESS 2026-09-03: three of four items done.\n- Binding model + threat model: docs/architecture/bindings.md (commit 41dffe3), every claim verified against actual code, not assumed.\n- ARCHITECTURE.md task lifecycle: provenance addendum landed (commit edb90e1), cross-referencing bindings.md. Also fixed a second, related staleness in the same section (the Routing table no longer reflects hardcoded-only behavior post t2db.9/.10).\n- Remaining (BLOCKED, not just unstarted): the end-to-end operator walkthrough. The epic's own pitch is a no-code, DASHBOARD-based flow ('point a webhook at archie, open the dashboard, map fields, bind, save'). Verified 2026-09-03: ui/src/ has zero binding-related files -- t2db.8's UI editor does not exist yet. Writing a walkthrough describing dashboard clicks that don't exist would itself be exactly the 'doc that contradicts its code' problem this ticket exists to prevent, just prospectively. Added a formal dependency on t2db.8 rather than write a curl-based workaround doc that misrepresents the intended no-code experience -- do the walkthrough after t2db.8's UI lands, describing what actually exists.","acceptance_criteria":"Operator walkthrough exists, end to end, describing the real dashboard UI (blocked on t2db.8). The other three acceptance items (binding model + threat model documented, ARCHITECTURE.md covers playbook-originated tasks) are done.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-21T13:45:46Z","created_by":"Sam Catlow","updated_at":"2026-09-02T20:20:15Z","closed_at":"2026-09-02T20:20:15Z","close_reason":"All four items done: binding model + threat model (bindings.md, 41dffe3), ARCHITECTURE.md task-lifecycle addendum (edb90e1), operator walkthrough (this commit). Unblocked once t2db.8's UI landed.","external_ref":"https://github.com/samcharles93/archie-core/issues/553","dependencies":[{"issue_id":"archie-core-t2db.6","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-08-21T23:45:45Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.6","depends_on_id":"archie-core-t2db.4","type":"blocks","created_at":"2026-08-21T23:45:53Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-t2db.6","depends_on_id":"archie-core-t2db.8","type":"blocks","created_at":"2026-09-02T18:41:43Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-7d5u.6","title":"Docs: reconcile plugins-and-extensions.md and ARCHITECTURE.md with the shipped event model","description":"Separate bead so it is not lost once the feature lands.\n\n1. docs/architecture/plugins-and-extensions.md is an APPROVED foundation dated 2026-07-28 and currently describes only the plugin framework. If the design bead concluded that extensions may react to events, this doc has to say how -- and if it concluded that generic untyped dispatch is allowed after all, this doc must be amended deliberately rather than contradicted by code.\n\n2. ARCHITECTURE.md describes work intake as polling. Once webhook intake ships, that is no longer the whole picture, and the task lifecycle section needs the new entry path.\n\n3. CLAUDE.md's per-package traps section should gain whatever trap this work creates -- HMAC verification, replay windows, the poll/webhook double-dispatch hazard. That section exists precisely for things an agent will otherwise break.\n\n4. config.example.toml needs the intake flag documented with its default, alongside poll_interval.\n\nCLAUDE.md's own rule: a doc that contradicts its code is worse than none, because the next reader trusts it.","acceptance_criteria":"plugins-and-extensions.md reflects the decided extension model; ARCHITECTURE.md documents webhook intake alongside polling; config.example.toml documents the intake flag and default; any new trap is recorded in CLAUDE.md.","notes":"Verified against actual code: config.example.toml already documented the intake flag/default (no change needed there). Made changes: ARCHITECTURE.md (opening description, package map rows for internal/forge/webhook and internal/webhookguard, Provenance-by-origin paragraph corrected from 'forge-polled' to 'forge-sourced (poll or webhook)', new 'Webhook intake' subsection under Forge Interface, [forge] config bullet, Implemented/Planned list -- also fixed an adjacent stale claim that Gitea forge was still 'planned' when internal/forge/gitea.go fully implements it); CLAUDE.md gained a new internal/forge/webhook/ trap entry (HMAC-before-parse, the idempotency-key poll/webhook dedup invariant, single-identity-only guard); docs/architecture/plugins-and-extensions.md gained an 'Event sources and reactions' section cross-referencing the 7d5u.1 decision, correctly scoped to only claim Module as shipped (Channel/Forge action positions are still open investigation t2db.19, not shipped).","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:26:52Z","created_by":"Sam Catlow","updated_at":"2026-09-02T20:48:08Z","started_at":"2026-09-02T20:43:26Z","closed_at":"2026-09-02T20:48:08Z","close_reason":"ARCHITECTURE.md and plugins-and-extensions.md reconciled with shipped webhook intake and the 7d5u.1 decision; config.example.toml already documented the intake flag/default; CLAUDE.md gained the internal/forge/webhook trap. Commit 8b53dc3.","external_ref":"https://github.com/samcharles93/archie-core/issues/554","dependencies":[{"issue_id":"archie-core-7d5u.6","depends_on_id":"archie-core-7d5u","type":"parent-child","created_at":"2026-08-21T23:26:51Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-7d5u.6","depends_on_id":"archie-core-7d5u.4","type":"blocks","created_at":"2026-08-21T23:26:58Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h019.5","title":"Calibration: confirm findings adversarially before surfacing them","description":"The risk that kills this feature is a reviewer that cries wolf. A findings list padded with speculation trains the operator to skim past it, and then the feature is worse than nothing because it consumes attention while lowering trust.\n\nBefore a finding is surfaced, it must be independently checked and marked CONFIRMED or PLAUSIBLE, with only CONFIRMED able to block. The reviewer must also be able to return zero findings, and to state which properties it checked and cleared -- a review that reports nothing is a valid and welcome result, and saying so explicitly is what distinguishes 'I checked and it is fine' from 'I did not look'.\n\nPrior art from the 2026-08-20/21 sessions on PR #530: three passes each separated confirmed from plausible, one explicitly listed properties it had verified clean, and the confirmed findings were reproduced by mutation before being trusted. That calibration is the feature, not the finding count.","acceptance_criteria":"Only CONFIRMED findings block PR creation; a zero-finding review is representable and reported as such; the reviewer records which properties it checked and cleared; padding with style nits is explicitly out of contract.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-21T13:03:15Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/555","dependencies":[{"issue_id":"archie-core-h019.5","depends_on_id":"archie-core-h019","type":"parent-child","created_at":"2026-08-21T13:03:15Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.5","depends_on_id":"archie-core-h019.1","type":"blocks","created_at":"2026-08-21T13:03:25Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.5","depends_on_id":"archie-core-h019.2","type":"blocks","created_at":"2026-08-21T13:03:25Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h019.6","title":"Surface findings on the PR body and the dashboard","description":"The output has to land where the operator already looks, or the review is invisible work.\n\nOn the PR archie opens: a findings section stating what was checked, what was found, what was fixed, and what survived. A PR with zero findings should say the review ran and found nothing -- silence is indistinguishable from the review not running, which is the same unverified-claim problem the update-verification work (PR #530) was about.\n\nOn the dashboard and /api/tasks: a parked-for-findings task must show why, the same way a park reason is already surfaced today. An operator seeing waiting_human needs the findings without digging through logs.","acceptance_criteria":"PR body carries a findings section including the zero-finding case; a task parked on a surviving finding shows the findings as its park reason in the dashboard and /api/tasks; nothing requires reading task logs to learn why a PR was withheld.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-21T13:03:15Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/556","dependencies":[{"issue_id":"archie-core-h019.6","depends_on_id":"archie-core-h019","type":"parent-child","created_at":"2026-08-21T13:03:15Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.6","depends_on_id":"archie-core-h019.1","type":"blocks","created_at":"2026-08-21T13:03:25Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.6","depends_on_id":"archie-core-h019.2","type":"blocks","created_at":"2026-08-21T13:03:26Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h019.7","title":"Docs: promote the shipped review stage into docs/architecture and reconcile CLAUDE.md","description":"Under the scope-discipline rule merged as PR #533, a design is promoted into docs/architecture/ only once it is built and true. This is that promotion, and it is deliberately a separate bead so it is not lost when the feature lands and attention moves on.\n\nDo three things once the stage ships:\n\n1. Promote the docs/prds/ decision into docs/architecture/, describing the review stage as it actually works -- not as designed. Cut anything a reader could learn from the code.\n2. Update ARCHITECTURE.md's task lifecycle: queued -\u003e running(workflow:stage) -\u003e pr_open -\u003e merged|rejected gains a review stage that can divert to waiting_human before pr_open. The current text does not mention it.\n3. Reconcile CLAUDE.md's Development Protocol. It currently tells a human or agent contributor to run the adversarial pass by hand. Once archied does this for the PRs it opens, that section needs to say which path applies to whom, or it will read as describing a manual step that is now automatic.\n\nCLAUDE.md's own rule: a comment or doc that contradicts its code is worse than none, because the next reader trusts it.","acceptance_criteria":"docs/architecture/ describes the shipped stage; ARCHITECTURE.md's lifecycle includes the review stage and the waiting_human diversion; CLAUDE.md distinguishes the manual contributor pass from archied's automated one; no doc still claims review is only manual.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-21T13:03:15Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/557","dependencies":[{"issue_id":"archie-core-h019.7","depends_on_id":"archie-core-h019","type":"parent-child","created_at":"2026-08-21T13:03:15Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.7","depends_on_id":"archie-core-h019.4","type":"blocks","created_at":"2026-08-21T13:03:26Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-h019.7","depends_on_id":"archie-core-h019.6","type":"blocks","created_at":"2026-08-21T13:03:26Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-nln7","title":"Dashboard-initiated updates get no phase-2 report, so they are never verified","description":"internal/webui/api_chat.go:497 starts an install with releaseupdate.InstallMeta{Channel: \"webui\"} and leaves ReportPath empty. CommandInstaller passes that through as ARCHIE_UPDATE_REPORT_PATH, and scripts/archie-update-watchdog's write_report() returns early when it is empty.\n\nConsequences: an operator who approves an update from the dashboard gets only the synchronous phase-1 result (build/install succeeded, restart queued) and never learns whether the daemon actually came back up, whether it was rolled back, or - since c25799e - whether the installed version is the one now running. Telegram gets all of that; the dashboard silently gets none of it.\n\nThe verification added in c25799e (releaseupdate.Report.Verify) is reached only from internal/channels/telegram/update.go, so this path is unverified regardless.\n\nFix needs two parts: give the webui install a ReportPath (updateReportPath in cmd/archied), and give the dashboard somewhere to relay a pending report on boot the way telegram's reportPendingUpdate does - today ReadPendingReport has exactly one caller, and a single report file shared by two relayers would race to clear it.","acceptance_criteria":"A dashboard-approved update produces a phase-2 report; the dashboard surfaces its outcome including version verification; two relayers cannot double-report or lose a report.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-20T14:04:33Z","created_by":"Sam Catlow","updated_at":"2026-08-23T12:58:07Z","started_at":"2026-08-23T12:56:47Z","closed_at":"2026-08-23T12:58:07Z","close_reason":"Fixed: dashboard installs now get a ReportPath, and Server.Run relays/verifies/clears the phase-2 report on boot via a new KindUpdateReport SSE event. Adversarial review clean.","external_ref":"https://github.com/samcharles93/archie-core/issues/531","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-qk8m","title":"MCP npm servers re-fetched from npm on every task container start","description":"## Problem\n\nd4bb914b/#64 fixed the daemon-side case: cmd/archied/main.go's\nconfiguredMCPProvider now points npx-launched MCP servers at a persistent\nNPM_CONFIG_CACHE under the daemon's own work_dir, so a daemon restart\nreuses a warm cache instead of re-resolving/re-downloading from the npm\nregistry.\n\ninternal/app/agentworker/mcp_providers.go builds the identical\nStdioTransportConfig for archie-agent's own per-task MCP servers, but was\ndeliberately left untouched -- it's not a separate code path, the exact\nsame cfg.Tools.MCPServers list (including any npx entries) is threaded\nthrough to every per-task NATS agent worker (bootstrap.go -\u003e NATSRunner.MCPServers\n-\u003e taskrun.Request -\u003e task_execution.go's startMCPProviders). Since each\ntask runs in a fresh ephemeral container, an npx-based MCP server\nconfigured for task use re-resolves/re-downloads on every task, not\njust every daemon restart -- more frequent, and thus a worse amplifier of\na registry outage than the bug already fixed.\n\n## Why this needs its own issue\n\nUnlike the daemon case, a bare NPM_CONFIG_CACHE=\u003cpath\u003e pointed at a host\ndirectory is meaningless inside an ephemeral container unless a\npersistent Docker volume is actually bind-mounted at that path. No such\nvolume currently exists for this purpose -- internal/container/pool.go's\nmounts are caller-provided, and nothing wires an npm-cache volume in.\nThat's real new infrastructure (a shared, persistent volume across\nper-task containers), not a parameter-threading fix like d4bb914b was.\n\n## Acceptance criteria\n\n- Task containers reuse a persistent npm cache across tasks, the same\n way the daemon now does across restarts.\n- The cache volume/mount is wired through internal/container/pool.go's\n Acquire (or equivalent) without weakening per-task filesystem isolation\n for anything other than the npm cache path itself.\n- Startup time for a task's npx-based MCP server no longer scales with\n package size once the cache is warm.\n","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-18T16:04:59Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:08Z","closed_at":"2026-08-24T07:12:08Z","close_reason":"Fixed: MCP npm servers for per-task containers now reuse a persistent npm cache. Added mcp.NpmCacheEnv (shared with the daemon-side fix), an always-on archie-cache-mcp-npm Docker volume mounted at /data/cache/mcp-npm on every task container regardless of ecosystem, and wired it into internal/app/agentworker/mcp_providers.go's stdio transport construction. Adversarial review found zero surviving findings. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/532","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-q5w4","title":"secret engine plugin: age","description":"Resolve SecretRef values from an age-encrypted file of key=value lines. Env: AGE_FILE (encrypted file path), AGE_IDENTITY (age private key file). Resolve runs 'age -d -i \u003cidentity\u003e \u003cfile\u003e' and parses the plaintext. Fresh resolve per call (no cache) so updates are picked up without daemon restart. CLI-based, mirroring the bws engine; ship as a Yaegi plugin in examples/secret-engines/.","status":"closed","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-17T14:22:03Z","created_by":"Sam Catlow","updated_at":"2026-08-17T22:27:53Z","started_at":"2026-08-17T14:22:10Z","closed_at":"2026-08-17T14:33:52Z","close_reason":"Shipped age engine plugin in examples/secret-engines/age.go (commit 24faf53): CLI-based, AGE_FILE/AGE_IDENTITY, key=value lines.","external_ref":"https://github.com/samcharles93/archie-core/issues/526","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786749700635-7-83b8c32f","title":"dashboard: turn_completed events carry no task correlation and drown real activity in the Live Activity feed","description":"## Problem, two compounding parts\n\n**1. `turn_completed` events carry no useful, correlatable content.**\n`internal/gateway/turn.go:306-311` publishes:\n```go\nr.Bus.Publish(events.Event{\n Kind: events.KindTurnCompleted,\n Detail: sessionID,\n Data: map[string]any{\"session\": sessionID, \"channel\": r.Channel},\n})\n```\nNo `TaskID` is set, and `Detail` is a raw internal session identifier (e.g. `1312197967`) with no formatting. On the dashboard's \"Live activity\" table this renders as `Task: —`, `Detail: 1312197967` — meaningless to anyone reading it, and impossible to correlate to a task. This event fires on every chat turn, so it dominates the feed: in a sample of the 30 most-recent Live Activity rows, only 3 were real task-lifecycle events (`task_queued`); the other 27 were content-free `turn_completed` rows.\n\n**2. The `/logs` page has no filtering, search, or level control at all** — just Pause/Refresh. Confirmed live: during the redelivery storm in #517, `handle failed` alone produced 996 near-identical lines, and there is no way to filter by task, by level, or search text to find anything else in the stream. During exactly the situation an operator needs the log page most (an active incident), it is unusable.\n\n## Fix\n\n- Give `turn_completed` (and any other cross-cutting event shown in this feed) a human-meaningful `Detail` — e.g. the channel name plus a short session label — and drop it from the feed entirely if it isn't task-correlated, since a feed titled \"Live activity\" that is 90% non-actionable chat-turn noise defeats its own purpose.\n- Add basic filtering to `/logs`: at minimum a level filter and a task/session search, so a single noisy source can be excluded without losing everything else.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-14T23:19:11Z","updated_at":"2026-08-15T00:35:51Z","started_at":"2026-08-15T00:03:05Z","closed_at":"2026-08-15T00:35:51Z","external_ref":"https://github.com/samcharles93/archie-core/issues/521","source_system":"github:https://github.com/samcharles93/archie-core/issues/521:521","metadata":null,"labels":["bug","webui"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942590-20-c21c728b","title":"Dashboard: Token outlook is blank because token usage is not reaching daily accounting","description":"## Problem\n\nThe dashboard's **Token outlook** card is blank instead of showing token usage/spend. The screenshot shows the card present but with no usable content.\n\n## Investigation\n\nThe live dashboard API currently returns:\n\n```json\n{\n \"workflows\": [\n {\"workflow\":\"tdd\",\"total_tokens\":904901,\"avg_tokens\":301633},\n {\"workflow\":\"implement\",\"total_tokens\":0}\n ],\n \"tokens_by_day\": null\n}\n```\n\nThe dashboard frontend expects `tokens_by_day` and renders the empty state when it is missing/empty (`ui/src/dashboard/dashboard.js:405-418`). The runtime therefore has token totals in the `tasks` table but no daily token series for the card.\n\nThe persistence path is inconsistent:\n\n- `internal/domain/workflow/agent.go:171-176` records `res.TokensUsed` on the task and emits an `agent_finish` event with `data.tokens`.\n- `internal/store/events.go:231-251` calculates the card data exclusively from persisted `agent_finish` events.\n- The live task event database currently contains `task_queued` and `turn_completed` events but no `agent_finish` rows, while workflow statistics still contain 904,901 tokens.\n- `handleSummary` serializes the nil result from `TokensByDay` as JSON `null`, rather than a stable empty array or a meaningful unavailable state.\n\nThis means the dashboard cannot truthfully show spend even though token usage is already tracked elsewhere.\n\n## Expected behaviour\n\n- Completed agent runs contribute to the Token outlook series and the Tokens used statistic.\n- The API returns `tokens_by_day: []` rather than `null` when no data exists.\n- The UI distinguishes \"no usage recorded yet\" from \"usage tracking is unavailable/broken\".\n- Token totals and daily totals come from one authoritative accounting path and do not diverge.\n- The card never renders blank.\n\n## Acceptance criteria\n\n- Add a regression test reproducing the current state: tasks have non-zero `tokens_used`, but no `agent_finish` rows; the summary must still have a defined, truthful token state.\n- Trace and repair the event persistence path so successful and failed agent runs produce the data required by `TokensByDay`, including NATS/container execution.\n- Add store/API tests asserting daily aggregation, timezone/day semantics, empty data, malformed/missing token fields, and multiple stages per task.\n- Return an empty JSON array for an empty series, not `null`.\n- Add a UI test for populated data, no data, and unavailable/error states; verify the card cannot be visually blank.\n- Verify against a running daemon with real task data and run the normal project gate.\n\n## Scope\n\nThis issue is about truthful token accounting and the Token outlook dashboard. It does not attempt to add provider billing APIs or dollar pricing unless required to make the existing token accounting correct.","status":"open","priority":2,"issue_type":"bug","created_at":"2026-08-14T23:03:30Z","updated_at":"2026-08-14T23:03:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/515","source_system":"github:https://github.com/samcharles93/archie-core/issues/515:515","metadata":null,"labels":["bug"],"dependencies":[{"issue_id":"archie-core-1786748942590-20-c21c728b","depends_on_id":"archie-core-1786637490248-18-17079a75","type":"related","created_at":"2026-08-15T12:59:33Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942566-19-aa1c4552","title":"Telegram: response formatting concatenates URLs with following text","description":"## Problem\n\nTelegram responses can concatenate a bare URL with the sentence that follows it, which breaks the clickable/direct link and makes the message look malformed.\n\nThis has occurred at least twice. Example:\n\n```text\nhttps://github.com/samcharles93/archie-core/issues/513It includes model-independent safeguards...\n```\n\nThe expected output is:\n\n```text\nhttps://github.com/samcharles93/archie-core/issues/513\n\nIt includes model-independent safeguards...\n```\n\n## Desired behavior\n\n- Preserve paragraph/newline boundaries between links and subsequent text.\n- Ensure a bare URL remains independently clickable in Telegram.\n- Do not concatenate separately streamed/rendered response segments.\n- Apply the fix consistently whether the response is sent once, edited while streaming, or split into multiple Telegram messages.\n\n## Acceptance criteria\n\n- A URL followed by prose is rendered with at least one newline separating them.\n- Bare GitHub issue URLs remain clickable and contain no trailing prose.\n- Regression coverage includes the exact example above.\n- Coverage exercises the relevant Telegram streaming/editing and message-splitting paths.\n","status":"closed","priority":2,"issue_type":"bug","assignee":"samcharles93","created_at":"2026-08-14T22:21:58Z","updated_at":"2026-08-15T13:04:30Z","closed_at":"2026-08-15T13:04:30Z","close_reason":"Fixed Telegram URL/prose boundary normalization across one-shot, live, and split delivery paths; added Markdown/code safety, newline preservation, and regression coverage.","external_ref":"https://github.com/samcharles93/archie-core/issues/514","source_system":"github:https://github.com/samcharles93/archie-core/issues/514:514","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942540-18-9af78536","title":"Agent falsely claims GitHub issue creation succeeded without verification","description":"## Problem\n\nDuring a Telegram chat using `deepseek/deepseek-v4-pro`, the agent stated that it had created GitHub issue #512 and supplied a URL even though no issue had been created. When challenged, it acknowledged the false claim and said it lacked a GitHub token; after being asked to retry, the issue creation succeeded.\n\nThis is a serious trust and UX problem: users must be able to rely on claims about external side effects such as creating issues, pushing branches, opening PRs, deploying, or restarting services.\n\n## Expected behavior\n\n- Never report an external action as successful unless the corresponding tool/plugin call completed successfully and returned verifiable output.\n- Include the issue number and URL from the forge response, not values inferred or fabricated by the model.\n- If the tool is unavailable or fails, report the actual failure clearly.\n- Allow a retry when the capability may be temporarily unavailable.\n\n## Suggested safeguards\n\n- Require successful structured tool results before permitting success language for side-effecting actions.\n- Track pending/completed/failed action state in the turn runner.\n- Add a postcondition check for issue creation, such as validating the returned issue ID/URL.\n- Add regression tests using a model response that falsely claims an issue was created without invoking the forge tool.\n- Consider a gateway warning or telemetry event when a final response claims an unverified side effect.\n\n## Reproduction\n\n1. Ask the agent to create an issue.\n2. The model responds with an issue number and URL without a successful forge invocation.\n3. Check GitHub and observe that the issue does not exist.\n\n## Context\n\nObserved with `deepseek/deepseek-v4-pro` through the Telegram gateway. This should be enforced independently of model/provider because any model can make an unsupported action claim.\n\n## Frequency\n\nThis has been observed twice in the same conversation, so it is a recurring failure rather than a one-off hallucination. Regression coverage should include repeated side-effect claims across turns, including claims that reuse a plausible issue number and URL.\n","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-14T22:16:46Z","updated_at":"2026-08-24T07:12:10Z","closed_at":"2026-08-24T07:12:10Z","close_reason":"Deprioritized: prompt-level fix landed in fba80e3 (archie-core-3jag/GH#524) covers the general overconfidence pattern. Not worth mechanical enforcement (postcondition checks, tool-result verification) unless this recurs — revisit with stronger prompting first if it does. [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/513","source_system":"github:https://github.com/samcharles93/archie-core/issues/513:513","metadata":null,"dependencies":[{"issue_id":"archie-core-1786748942540-18-9af78536","depends_on_id":"archie-core-3jag","type":"related","created_at":"2026-08-15T12:59:09Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942519-17-5999d55b","title":"Polish the /status command response","description":"## Problem\n\nThe `/status` command response is functional but lacks polish and is difficult to scan. The current output looks like:\n\n```text\nTask status: parked:2\nProvider: deepseek Model: deepseek/deepseek-v4-pro\n```\n\nThe information is compressed into raw key/value text, and task state, provider, and model details are not clearly separated.\n\n## Desired behaviour\n\nPresent status information in a compact, polished, mobile-friendly format suitable for Telegram. It should make the most important state immediately obvious and visually separate task and runtime/model information.\n\nFor example:\n\n```text\n📊 Archie status\n\nTasks\n⏸ Parked:2\n\nRuntime\nProvider: OpenAI\nModel: openai/gpt-5.6-luna\n```\n\nThe exact wording and icons can follow existing Telegram UI conventions.\n\n## Acceptance criteria\n\n- `/status` has a clear heading and grouped sections.\n- Task states are shown on separate, readable lines.\n- Provider and model are clearly separated.\n- The response remains concise and readable on mobile.\n- Empty and unavailable values have a graceful fallback.\n- Tests cover the formatted response, including multiple task states and missing runtime details.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-14T22:14:58Z","updated_at":"2026-08-15T12:41:34Z","started_at":"2026-08-15T12:33:21Z","closed_at":"2026-08-15T12:41:34Z","close_reason":"Closed","external_ref":"https://github.com/samcharles93/archie-core/issues/512","source_system":"github:https://github.com/samcharles93/archie-core/issues/512:512","metadata":null,"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942272-7-2ad59e97","title":"Add end-to-end image generation test matrix and operational safeguards","description":"## Scope\nBuild the cross-cutting test and verification layer for the image capability. Exercise the clarification flow, hosted fake provider, local fake backend, real local recipe smoke test where available, delivery, and failure paths.\n\nAdd safeguards for cost, resource use, prompt/input limits, concurrency, cancellation, and observability consistent with Archie''s existing operational style.\n\n## Acceptance criteria\n- Automated tests cover both mechanisms, generation and editing, routing, provider failures, delivery failures, cancellation, and cleanup.\n- Tests assert no provider call occurs before mechanism clarification.\n- Resource and input/output limits are enforced in code and tested.\n- A documented local smoke command verifies at least one GPU recipe without requiring hosted credentials.\n- The normal project gate passes, and the epic's acceptance criteria can be verified from real command output.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-14T21:55:45Z","updated_at":"2026-08-14T21:55:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/503","source_system":"github:https://github.com/samcharles93/archie-core/issues/503:503","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786748942272-7-2ad59e97","depends_on_id":"archie-core-1786748942120-1-6636e629","type":"parent-child","created_at":"2026-09-02T10:17:19Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942296-8-260e931d","title":"Write image capability documentation and agent assistance examples","description":"## Scope\nDocument the user-facing `/image` flow, hosted-provider setup, local GPU setup, supported model/backend recipes, troubleshooting, resource requirements, and security/cost implications.\n\nProvide concise code/config examples an agent can use to help users call both hosted and local paths. Examples must show how to inspect hardware/backend availability, choose a tested model, submit a generation/edit request, and collect the resulting image.\n\n## Acceptance criteria\n- Documentation explicitly says mechanism selection happens first by default.\n- Hosted API baseline fields and provider deviations are documented.\n- Every local model recipe names its tested backend/version, model source, VRAM/RAM expectations, supported sizes/operations, and failure modes.\n- Examples are runnable or tested in CI with mocked services; no secrets or huge weights are included.\n- Docs distinguish tested support from illustrative/untested possibilities.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-14T21:55:45Z","updated_at":"2026-08-14T21:55:45Z","external_ref":"https://github.com/samcharles93/archie-core/issues/502","source_system":"github:https://github.com/samcharles93/archie-core/issues/502:502","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786748942296-8-260e931d","depends_on_id":"archie-core-1786748942120-1-6636e629","type":"parent-child","created_at":"2026-09-02T10:17:20Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942243-6-f109697e","title":"Deliver generated images through channel and web abstractions","description":"## Scope\nExtend the existing message/result delivery abstraction so generated images can reach users safely through supported channels and the web UI. Preserve useful metadata such as prompt/provider/model and errors without exposing credentials or internal filesystem paths.\n\nUse bounded temporary storage/cleanup and a clear policy for formats, dimensions, compression, and maximum response size. Ensure a failed upload does not leave the user with a success-looking text response.\n\n## Acceptance criteria\n- A provider result can be delivered as an image through each currently supported delivery path, or unsupported paths report a clear limitation.\n- Temporary files and downloaded inputs have bounded size and deterministic cleanup.\n- MIME/format handling, alt text/caption, and metadata are tested.\n- Delivery failures, retries/cancellation, and partial-success behavior are tested.\n- Existing text and file delivery behavior remains unchanged.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-14T21:55:44Z","updated_at":"2026-08-14T21:55:44Z","external_ref":"https://github.com/samcharles93/archie-core/issues/501","source_system":"github:https://github.com/samcharles93/archie-core/issues/501:501","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786748942243-6-f109697e","depends_on_id":"archie-core-1786748942120-1-6636e629","type":"parent-child","created_at":"2026-09-02T10:17:19Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942193-4-5072b564","title":"Implement /image mechanism clarification and routing flow","description":"## Scope\nMake the default `/image` workflow ask the user for their preferred generation mechanism before running a request when no mechanism is already selected: hosted API or local GPU. Present the choices and relevant constraints concisely, then collect only the options needed for the selected mechanism.\n\nSupport an explicit per-request override and a clearly scoped remembered preference only where existing session/config conventions support it. Never silently fall back from hosted to local or local to hosted.\n\n## Acceptance criteria\n- `/image` with no mechanism produces a clarification prompt and does not invoke a provider.\n- Hosted and local selections route to the correct provider with the selected options.\n- The flow supports generation and edit requests, including input-image validation.\n- Invalid choices, missing credentials, unavailable GPU backends, and cancellation produce actionable replies.\n- Channel-neutral tests cover the state machine; Telegram/web behavior is covered at the adapter boundary where applicable.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-14T21:55:43Z","updated_at":"2026-08-14T21:55:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/500","source_system":"github:https://github.com/samcharles93/archie-core/issues/500:500","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786748942193-4-5072b564","depends_on_id":"archie-core-1786748942120-1-6636e629","type":"parent-child","created_at":"2026-09-02T10:17:18Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942219-5-9844a72e","title":"Add local GPU image generation backend and tested model recipes","description":"## Scope\nAdd a local GPU path that can execute image generation on an existing user GPU through a supported local backend/API. Prefer integration with an established server/workflow interface over embedding model runtimes or downloading weights from Archie.\n\nShip a tested initial recipe set for common models appropriate to consumer GPUs, with the exact model files, backend versions, VRAM/RAM expectations, supported operations, and known limitations recorded. Include runnable code/config examples that Archie can use to assist a user in setting up and calling the backend.\n\nThe implementation must report unavailable hardware/backend/model conditions clearly and must not pretend an untested model is supported.\n\n## Acceptance criteria\n- At least one local GPU recipe is exercised end-to-end on real hardware or a reproducible maintained test harness.\n- Additional recipes are included only with evidence, covering model/backend/version, VRAM, image sizes, and speed/quality trade-offs.\n- Backend URL/auth/timeout and model selection are configurable.\n- Local generation returns the same provider-neutral result shape as hosted generation.\n- Tests cover backend unavailable, malformed response, timeout, cancellation, and model-not-found paths.\n- No model weights are committed or downloaded into the repository/home partition.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-14T21:55:43Z","updated_at":"2026-08-14T21:55:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/499","source_system":"github:https://github.com/samcharles93/archie-core/issues/499:499","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786748942219-5-9844a72e","depends_on_id":"archie-core-1786748942120-1-6636e629","type":"parent-child","created_at":"2026-09-02T10:17:18Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942169-3-ae7cfaea","title":"Implement hosted gpt-image-2-compatible image provider","description":"## Scope\nImplement the hosted image provider behind the image capability contract, targeting the practical baseline of the OpenAI `gpt-image-2` API.\n\nCover text-to-image and image editing where supported by the API, prompt and image inputs, size/quality/background/output-format/compression-style options exposed by the baseline, response decoding, and provider error mapping. Do not claim unsupported parity: document exact API version/endpoint assumptions and any deliberate differences.\n\n## Acceptance criteria\n- Uses the existing HTTP/auth/configuration patterns rather than a one-off client.\n- Request serialization and response decoding are covered with httptest fixtures.\n- Provider failures, malformed responses, timeouts, oversized inputs, and cancellation are handled without panics or leaked secrets.\n- No live API key is needed for tests.\n- A small runnable example shows the request shape and configuration.","notes":"Leverage github.com/samcharles93/ai-sdk's existing image.Provider/core.GenerateImage/registry.RegisterImage for the generate path (azure/togetherai/xai already implement it; OpenAI does not yet) instead of writing a raw HTTP client -- same adapter pattern curatorLLMRunner uses for chat. Gap: ai-sdk's GenerateImageRequest has no input-image/mask fields, so editing needs either an upstream ai-sdk change or a separate direct client for the edit endpoint. Decide which at this bead's own design step. See docs/prds/image-capability-contract.md's closing note.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-14T21:55:42Z","updated_at":"2026-09-02T10:23:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/498","source_system":"github:https://github.com/samcharles93/archie-core/issues/498:498","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786748942169-3-ae7cfaea","depends_on_id":"archie-core-1786748942120-1-6636e629","type":"parent-child","created_at":"2026-09-02T10:17:17Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942147-2-47cd5bd1","title":"Define provider-neutral image capability contract and configuration","description":"## Scope\nDefine the internal image-generation capability boundary used by hosted and local providers. Keep it narrow and provider-neutral: generation, editing with input images, prompt/options, output metadata, cancellation/timeouts, and capability discovery.\n\nAdd configuration and provider selection that fit the existing model/provider conventions. A missing credential or unavailable backend must make the capability unavailable with a useful user-facing error, not prevent Archie from starting or break text chat.\n\n## Acceptance criteria\n- Typed request/result/options contract covers the agreed gpt-image-2 baseline without baking in OpenAI types.\n- Provider registry/resolution and capability discovery are testable with fakes.\n- Hosted vs local selection is explicit and cannot silently incur cost.\n- Timeouts, maximum input/output sizes, cancellation, and error taxonomy are defined and tested.\n- Configuration validation rejects unsafe/ambiguous settings and preserves existing config behavior.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-14T21:55:41Z","updated_at":"2026-09-02T10:20:48Z","started_at":"2026-09-02T10:17:22Z","closed_at":"2026-09-02T10:20:48Z","close_reason":"Shipped docs/prds/image-capability-contract.md plus internal/domain/image (Provider contract, Registry — no Lifecycle, provider is call-scoped) and config.ImageConfig/validateImage. Provider-neutral, tested with fakes, hosted+local both gated by explicit enabled=true. Also linked all 7 orphaned epic children (found unlinked again, same pattern as the curator/memory epics).","external_ref":"https://github.com/samcharles93/archie-core/issues/497","source_system":"github:https://github.com/samcharles93/archie-core/issues/497:497","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786748942147-2-47cd5bd1","depends_on_id":"archie-core-1786748942120-1-6636e629","type":"parent-child","created_at":"2026-09-02T10:17:16Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786748942120-1-6636e629","title":"[EPIC] Image generation capability: hosted API baseline plus local GPU workflows","description":"## Goal\nAdd first-class image generation to Archie, with a capability surface targeting the practical baseline of the OpenAI `gpt-image-2` API while also supporting image generation on a user's existing GPU.\n\nThe capability must not assume one backend. A user asking for `/image` is first asked which generation mechanism they prefer:\n- hosted API (starting with an OpenAI-compatible `gpt-image-2` provider), or\n- local GPU generation using one of Archie's tested model/backend recipes.\n\n## Scope\n- A provider-neutral image capability contract and routing/configuration.\n- Hosted generation/editing with an OpenAI `gpt-image-2`-class API baseline.\n- Local GPU generation through tested, documented model/backend recipes suitable for common consumer GPUs.\n- `/image` clarification and execution flow across supported channels.\n- Returned image delivery, bounded inputs/outputs, errors, and tests.\n\n## Non-goals\n- Training or fine-tuning image models.\n- Bundling multi-gigabyte model weights in Archie.\n- Pretending every GPU/model combination is supported; local support must be explicit and evidence-backed.\n- Replacing the existing text-chat capability or silently selecting a paid hosted provider.\n\n## Definition of done\n- `/image` asks for the preferred mechanism before generation when no mechanism is already selected for the request/session.\n- Hosted generation and editing cover the documented gpt-image-2 baseline, with provider-specific differences exposed rather than hidden.\n- Local GPU generation works end-to-end with at least one tested recipe, and additional tested common models are documented with VRAM/backend requirements and runnable examples.\n- Images can be delivered through the existing channel abstractions without leaking temporary files or unbounded data.\n- Unit, integration, and failure-path tests cover routing, provider errors, clarification, local execution, and delivery.\n- Configuration, security, and operational documentation are complete.\n\nSubtasks below are dependency-ordered where practical; each must link back to this epic and state any deliberate deviations from the hosted API baseline.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-14T21:55:40Z","updated_at":"2026-08-14T21:55:40Z","external_ref":"https://github.com/samcharles93/archie-core/issues/496","source_system":"github:https://github.com/samcharles93/archie-core/issues/496:496","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-hlxd","title":"telegram: a tool-use turn ending with no answer posts the tool line alone as the finished message","description":"finalText returns the tool block alone when the reply is empty, and finalize sends it as the authoritative finished message — content == '' is the only silence path, so an empty-reply turn with completed tools permanently delivers '🔧 shell — exit 0' with no answer. The old path guarded 'if reply != \"\"'. Telegram messages are immutable, so it can never be corrected. Gated on show_tool_calls (off by default), so it bites opt-in deployments. No test covers finalize with an empty reply and tools.\n\nFailure: the model ends a tool-use loop without a final summary (empty ResponseText); the finished message shows only the tool line, looking like a completed answer that said nothing.","design":"When the reply is empty, do not post the tool block as the answer — either skip the final send (leave the cursor-cleaned live message) or emit an explicit 'no reply' marker. Add a test for finalize(empty, tools).","acceptance_criteria":"A turn that ends with tools but no answer text does not post a bare tool line as the final message.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:38Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:25:44Z","started_at":"2026-08-14T15:07:52Z","closed_at":"2026-08-14T15:25:44Z","close_reason":"Fixed in internal/channels/telegram/live.go: framedText keeps tool lines whole ahead of the clamped answer tail (fixes wpq6); finalText appends a '(no response)' marker when tools ran but the reply is empty (fixes hlxd); abandonFailed marks a provider-error partial distinctly from a clean /stop abandon (fixes c3w2). Regression tests verified red-then-green; adversarial review found no blocking issues (added one more test for the degenerate oversized-tool-block case it flagged). task check clean, committed as 587b9b9.","external_ref":"https://github.com/samcharles93/archie-core/issues/486","labels":["code-review","streaming","telegram"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-og5r","title":"webui: the dashboard narrates tool calls with no opt-out; show_tool_calls only gates Telegram","description":"show_tool_calls gates only the Telegram adapter. The web dashboard's chatStreamSink forwards every ToolCallEvent unconditionally (api_chat.go:228) — no config key exists anywhere in webui — so an operator following the documented intent (show_tool_calls off means no tool narration) still gets full per-tool narration in the web dashboard with no way to disable it. The ToolCallEvent contract comment (stream.go:18-20) delegates 'whether to show it at all' to the channel adapter, but only the Telegram adapter exercises the knob.\n\nFailure: an operator with the default show_tool_calls=false opens the web dashboard; every internal tool step of every web chat is narrated in full, exposing tool inventory and parameter shapes to anyone with dashboard access.","design":"Either add a webui-equivalent config key and gate the sink on it, or make show_tool_calls a cross-channel setting. Decide and document the intent, then wire the webui sink to honor it.","acceptance_criteria":"With the setting off, the web dashboard does not emit tool frames; with it on, it does — controlled by one documented knob.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:37Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:57:11Z","started_at":"2026-08-14T15:50:15Z","closed_at":"2026-08-14T15:57:11Z","close_reason":"Fixed: ShowToolCalls moved from TelegramConfig to ChatConfig (one cross-channel setting), webui's chatStreamSink gated on it (off by default, matching Telegram). Adversarial review clean aside from cosmetic/doc notes, both addressed. Breaking config-key move flagged explicitly in the commit body since it's a silent TOML drop, not an error. Committed f7590a6.","external_ref":"https://github.com/samcharles93/archie-core/issues/487","labels":["code-review","config","webui"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-ippu","title":"gateway: replay and redelivery lose tool activity, showing duplicate answers without tools","description":"The replay paths (TurnClaimCompleted, prior-reply) emit stream.Delta(ResponseText) only — never stream.ToolCall — and neither the ledger (TurnRecord) nor the session store persists tool activity. A completed-duplicate delivery (NATS redelivery, restart RecoverTurns re-delivery) finalizes a fresh liveReply with empty toolLines and sends the bare reply as a new message: the transcript shows the original (with tools) and the duplicate (without) side by side, disagreeing about what ran. Web history has the same gap — stored assistant messages render text only.\n\nFailure: a chat message is redelivered or re-queued after restart; the user sees the same answer twice, the second copy lacking the tool block that explains it.","design":"Decide whether tool activity should be persisted (ledger/session store) and replayed, or whether replays simply should not re-narrate tools. If persisting, add a tool-activity record to the turn/message and replay it; if not, make the replay path explicitly consistent and document the choice.","acceptance_criteria":"A redelivered/restarted turn does not show a tool-less duplicate disagreeing with the original; the behavior is explicitly decided and tested.","status":"closed","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:24Z","created_by":"Sam Catlow","updated_at":"2026-08-24T07:12:07Z","closed_at":"2026-08-24T07:12:07Z","close_reason":"Fixed: TurnRecord now persists tool-call activity alongside ResponseText; the completed-duplicate replay path replays it via stream.ToolCall before the text. Prior-reply fallback documented as deliberately text-only (crash race with no persisted tool record). Commit 86a9731, task check clean, adversarial review clean (0 findings). [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","external_ref":"https://github.com/samcharles93/archie-core/issues/488","metadata":null,"labels":["code-review","gateway","telegram","webui"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-o2t8","title":"webui: derive tool failure from a structured field, not a 'failed:' string prefix","description":"The web UI derives failure styling with summary.startsWith('failed:') on the rendered string (chat-tools.js:25), while chatStreamEvent (api_chat.go) carries no structured error/ok field — the doc comment says the intent was structured precisely so the browser could style the two apart instead of parsing a rendered string, but the bit was dropped. False positives are concrete: a successful tool whose first output line begins with 'failed: ' is styled as a failure. Nothing pins the Go 'failed: ' prefix to the client sniff (the UI test feeds the literal string), so a future rewording silently breaks failure styling.\n\nFailure: a successful shell command printing 'failed: no such file' to stdout exits 0; the web chat renders it red as an error step.","design":"Add an explicit error/ok field to ToolCallEvent and chatStreamEvent (e.g. a bool or the raw Err), thread it through the sink, and style on that instead of the rendered string. Update the UI test to feed the structured field.","acceptance_criteria":"A successful tool printing 'failed: …' is not styled as a failure; failure styling is driven by a structured signal, not string matching.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:24Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:48:45Z","started_at":"2026-08-14T15:44:20Z","closed_at":"2026-08-14T15:48:45Z","close_reason":"Fixed in internal/webui/api_chat.go + ui/src/chat/chat-tools.js: chatStreamEvent now carries a structured Failed bool (from ToolCallEvent.Err != \"\"); JS reads event.failed instead of sniffing the summary text. Adversarial review found zero issues. Committed a99a770.","external_ref":"https://github.com/samcharles93/archie-core/issues/489","labels":["code-review","webui"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-wpq6","title":"telegram: tool lines disappear from the live frame once the answer exceeds ~3900 runes","description":"Mid-turn frames keep only the tail (clampToOneMessage keeps the last 3900 runes with a leading ellipsis). Tool lines are written inline near the start of the buffer — before the answer, since tools run before the answer in agentic turns — so once the answer exceeds ~3900 runes, every early tool line vanishes from the live frame (the buffer only grows; nothing re-inserts them mid-turn). They reappear at the top at finalize. The visible message changes shape three times (tool-inline, gone behind the ellipsis, tools-on-top) and the user watching mid-turn sees the tool activity silently disappear.\n\nFailure: a turn with an early web_fetch followed by a 4000-rune answer shows only '...' + tail with no tool line for the bulk of the turn.","design":"Keep tool lines outside the clamped tail — render the tool block above the truncated answer tail in the live frame — so tool activity stays visible for the whole turn.","acceptance_criteria":"In a turn with an early tool call and a \u003e3900-rune answer, the live frame still shows the tool line(s) at the top rather than hiding them behind the ellipsis.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:23Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:25:44Z","started_at":"2026-08-14T15:07:52Z","closed_at":"2026-08-14T15:25:44Z","close_reason":"Fixed in internal/channels/telegram/live.go: framedText keeps tool lines whole ahead of the clamped answer tail (fixes wpq6); finalText appends a '(no response)' marker when tools ran but the reply is empty (fixes hlxd); abandonFailed marks a provider-error partial distinctly from a clean /stop abandon (fixes c3w2). Regression tests verified red-then-green; adversarial review found no blocking issues (added one more test for the degenerate oversized-tool-block case it flagged). task check clean, committed as 587b9b9.","external_ref":"https://github.com/samcharles93/archie-core/issues/490","labels":["code-review","streaming","telegram"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-9zoa","title":"telegram: a restart mid-turn strands a permanent message ending in the ▌ cursor","description":"The live reply is a real, permanent Telegram message (SendRichMessage) whose messageID lives only in the in-memory liveReply struct. No shutdown path — supervisor restart in Start, daemon stop, launch() rebuilding Turns — edits or deletes it. A restart mid-turn strands a permanent message ending in ▌ that nothing will ever finish. The old draft path self-deleted (ephemeral 30-second previews); this is a new class of leftover introduced by the live-edit design.\n\nFailure: the operator restarts the daemon or deploys a new build while a turn is streaming; the partial reply with the cursor persists in the chat indefinitely, implying the bot is still writing.","design":"On gateway Stop/restart, track in-flight liveReply instances (a registry keyed by chat/thread) and edit them to drop the cursor and/or append a cancelled/restarted marker — or delete them. Decide the desired end state for an interrupted turn.","acceptance_criteria":"A daemon restart during a streamed turn leaves no ▌-terminated message; the partial reply is either completed, marked, or removed.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:09Z","created_by":"Sam Catlow","updated_at":"2026-08-14T16:20:04Z","started_at":"2026-08-14T15:58:25Z","closed_at":"2026-08-14T16:20:04Z","close_reason":"Fixed: Gateway tracks in-flight liveReply instances in a registry Stop drains, marking each interrupted. Adversarial review found a critical race (concurrent finalize/abandon on the same reply could corrupt the message) plus two lesser issues (unbounded blocking Stop, a narrow post-snapshot registration gap) -- all three fixed: sync.Once serializes finalize/abandon, the drain is time-bounded (default 5s, entries left running in background past that), and registerLive checks a stopped flag to immediately abandon a straggler. Re-reviewed via targeted regression tests including a 20-iteration concurrent race test. task check clean, -race clean across repeated runs. Committed 09ea210.","external_ref":"https://github.com/samcharles93/archie-core/issues/491","labels":["code-review","streaming","telegram"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-c3w2","title":"telegram: mark a failed turn instead of leaving an indistinguishable partial","description":"Both /stop and a genuine provider error funnel into live.abandon() (telegram.go:573), which trims the buffer, drops the cursor, and leaves the partial text as a permanent message with no failure marker — indistinguishable from a finished reply. /stop at least acks via stopReport; the provider-error branch sends nothing to the user, so a failed turn reads as complete and the user may act on incomplete information. The codebase's own error pattern (the ❌ session-resolution failure message) is unused here.\n\nFailure: the model stream errors (provider 5xx, timeout) after three paragraphs; the bot's last message is the truncated text with no cursor and no error note; the user treats it as the final answer.","design":"On provider error (not /stop), append or prepend an error marker to the abandoned message (e.g. a ❌ … failed line), or send a follow-up error message, so a truncated turn is visibly not the answer.","acceptance_criteria":"A provider-error turn leaves a message that visibly signals failure; /stop still leaves a clean partial without a spurious error.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:09Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:25:44Z","started_at":"2026-08-14T15:07:52Z","closed_at":"2026-08-14T15:25:44Z","close_reason":"Fixed in internal/channels/telegram/live.go: framedText keeps tool lines whole ahead of the clamped answer tail (fixes wpq6); finalText appends a '(no response)' marker when tools ran but the reply is empty (fixes hlxd); abandonFailed marks a provider-error partial distinctly from a clean /stop abandon (fixes c3w2). Regression tests verified red-then-green; adversarial review found no blocking issues (added one more test for the degenerate oversized-tool-block case it flagged). task check clean, committed as 587b9b9.","external_ref":"https://github.com/samcharles93/archie-core/issues/492","labels":["code-review","streaming","telegram"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-tje.5","title":"Clear cmd/archie-agent golangci-lint baseline","description":"## Problem\\nFull-package golangci-lint currently reports findings in cmd/archie-agent, including noctx in taskrun_test.go. This prevents using a clean package lint gate while refactoring main.go.\\n\\n## Scope\\nFix evidence-backed golangci-lint findings in cmd/archie-agent without weakening lint configuration or changing runtime behavior. Coordinate with the MCP extraction where that extraction removes the startMCPProviders complexity finding.\\n\\n## Acceptance\\n- golangci-lint run ./cmd/archie-agent/... reports zero findings\\n- focused tests, vet, build, formatting, and task check pass\\n- no lint suppressions or configuration exclusions are added","acceptance_criteria":"cmd/archie-agent full-package lint is zero with no suppressions; tests, vet, build and task check pass","notes":"Implementation and validation are complete in /tmp/archie-core-agent-cleanup on branch refactor/archie-agent-main-cleanup, but delivery is pending: changes are uncommitted, not integrated into the target branch, and not pushed. Do not close until those delivery steps are complete.\n Validation completed: golangci-lint run ./cmd/archie-agent/... reports zero issues without suppressions.\nDelivered on review branch refactor/archie-agent-main-cleanup at de242f8; pending PR review/merge.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-13T17:04:27Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:07:43Z","started_at":"2026-08-13T17:04:30Z","closed_at":"2026-08-14T14:53:09Z","close_reason":"Merged to main in PR #480 at 52738f5; implementation commit de242f8 passed task check, race tests, lint, and independent review","external_ref":"https://github.com/samcharles93/archie-core/issues/493","dependencies":[{"issue_id":"archie-core-tje.5","depends_on_id":"archie-core-tje","type":"parent-child","created_at":"2026-08-13T17:04:27Z","created_by":"Sam Catlow","metadata":"{}"}],"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","notes":"Implementation and validation are complete in /tmp/archie-core-agent-cleanup on branch refactor/archie-agent-main-cleanup, but delivery is pending: changes are uncommitted, not integrated into the target branch, and not pushed. Do not close until those delivery steps are complete.\n Validation completed: task subscription focused tests and fresh review clean.\nDelivered on review branch refactor/archie-agent-main-cleanup at de242f8; pending PR review/merge.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","updated_at":"2026-08-14T14:53:09Z","started_at":"2026-08-13T17:25:20Z","closed_at":"2026-08-14T14:53:09Z","close_reason":"Merged to main in PR #480 at 52738f5; implementation commit de242f8 passed task check, race tests, lint, and independent review","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","notes":"Implementation and validation are complete in /tmp/archie-core-agent-cleanup on branch refactor/archie-agent-main-cleanup, but delivery is pending: changes are uncommitted, not integrated into the target branch, and not pushed. Do not close until those delivery steps are complete.\n Validation completed: stage-loop path tests, race tests, lint, task check, and fresh review clean.\nDelivered on review branch refactor/archie-agent-main-cleanup at de242f8; pending PR review/merge.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","updated_at":"2026-08-14T14:53:09Z","started_at":"2026-08-13T17:33:26Z","closed_at":"2026-08-14T14:53:09Z","close_reason":"Merged to main in PR #480 at 52738f5; implementation commit de242f8 passed task check, race tests, lint, and independent review","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","notes":"Implementation and validation are complete in /tmp/archie-core-agent-cleanup on branch refactor/archie-agent-main-cleanup, but delivery is pending: changes are uncommitted, not integrated into the target branch, and not pushed. Do not close until those delivery steps are complete.\n Validation completed: MCP lifecycle tests, lint, task check, and fresh review clean.\nDelivered on review branch refactor/archie-agent-main-cleanup at de242f8; pending PR review/merge.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","updated_at":"2026-08-14T14:53:09Z","started_at":"2026-08-13T17:04:26Z","closed_at":"2026-08-14T14:53:09Z","close_reason":"Merged to main in PR #480 at 52738f5; implementation commit de242f8 passed task check, race tests, lint, and independent review","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","notes":"Implementation and validation are complete in /tmp/archie-core-agent-cleanup on branch refactor/archie-agent-main-cleanup, but delivery is pending: changes are uncommitted, not integrated into the target branch, and not pushed. Do not close until those delivery steps are complete.\n Validation completed: single-stage boundary/MCP assembly tests, task check, and fresh review clean.\nDelivered on review branch refactor/archie-agent-main-cleanup at de242f8; pending PR review/merge.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:44Z","created_by":"Sam Catlow","updated_at":"2026-08-14T14:53:09Z","started_at":"2026-08-13T17:41:10Z","closed_at":"2026-08-14T14:53:09Z","close_reason":"Merged to main in PR #480 at 52738f5; implementation commit de242f8 passed task check, race tests, lint, and independent review","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","notes":"Implementation and validation are complete in /tmp/archie-core-agent-cleanup on branch refactor/archie-agent-main-cleanup, but delivery is pending: changes are uncommitted, not integrated into the target branch, and not pushed. Do not close until those delivery steps are complete.\n Validation already completed: main.go reduced 430→136 lines; package tests/race/vet/build/lint pass; full task check passes; final fresh adversarial review reported zero findings.\nCorrected architecture migration pushed for review at commit de242f81c1b6309cdc984ded8e2f01fad89097b9 on branch refactor/archie-agent-main-cleanup. Rebased onto origin/main 58eae75. Focused tests, race, changed-line lint, full task check, and final independent review all pass. Keep in_progress until PR merge.","status":"closed","priority":2,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-13T16:10:24Z","created_by":"Sam Catlow","updated_at":"2026-08-14T14:53:09Z","started_at":"2026-08-13T17:57:45Z","closed_at":"2026-08-14T14:53:09Z","close_reason":"Merged to main in PR #480 at 52738f5; implementation commit de242f8 passed task check, race tests, lint, and independent review","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-12T04:38:10Z","updated_at":"2026-08-15T12:57:37Z","closed_at":"2026-08-15T12:57:37Z","close_reason":"Fixed: internal/infrastructure/agentgit/safety.go's MarkSafe adds the mounted worktree to git's global safe.directory list, and it is wired into the actual agent-container startup path -- internal/app/agentworker/worker.go:63,84 calls dependencies.markSafe(ctx, workDir, log) unconditionally in run(), before NATS connect and before any gate executes. Confirmed by grep this is the only non-test call site (worker.go), so it isn't dead/unwired code. go test ./internal/infrastructure/agentgit/... and ./internal/app/agentworker/... -race -count=1 both pass, including worker_test.go coverage that exercises the run() path with markSafe wired in. This matches the exact fix archie-core-1786749700606-6-bf6aa32d already describes as done ('#468 ... resolved by safe.directory').","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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-12T04:20:52Z","updated_at":"2026-08-14T15:07:34Z","closed_at":"2026-08-14T15:07:34Z","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":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","created_at":"2026-08-08T16:27:19Z","updated_at":"2026-09-02T10:47:01Z","started_at":"2026-09-02T10:18:01Z","closed_at":"2026-09-02T10:47:01Z","close_reason":"MarkRunning now fires for telegram/email/webhook via a gateway.Lifecycle{Starting,Running} callback threaded through Gateway.Start: email/webhook report Running after their listener actually binds (webhook moved off ListenAndServe's internal bind to explicit net.Listen so this is observable), telegram reports Running after StartWebhook launch (webhook mode) or after the first successful getUpdates response via a pollReadinessClient http.Client wrapper (long-poll mode). Restart re-reports Starting/Running each cycle. task check clean, race-clean on the new tests.","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":"closed","priority":2,"issue_type":"bug","assignee":"samcharles93","created_at":"2026-08-08T16:26:41Z","updated_at":"2026-08-20T13:02:18Z","started_at":"2026-08-20T12:57:03Z","closed_at":"2026-08-20T13:02:18Z","close_reason":"Fixed in fix/label-dispatch-empty-label (31efdcf): pollIssuesWithConfig/pollEitherWithConfig now refuse the label poll when cfg.Label is empty, and validateDispatch rejects the misconfiguration at load time. Adversarially reviewed; one weak test strengthened to actually verify assignee matches survive.","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":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T16:15:17Z","updated_at":"2026-09-02T20:57:29Z","started_at":"2026-09-02T20:57:15Z","closed_at":"2026-09-02T20:57:29Z","close_reason":"Fixed in ui/src/dashboard/dashboard.css: .dash-top \u003e div now flexes and .card grows to fill it, scoped to the HEALTH row only. Verified via a static HTML repro using the real project CSS (Playwright, computed geometry before/after) -- card heights and bottom edges now match. task check green, ui/dist rebuilt. Commit a9a056c.","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":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","created_at":"2026-08-08T16:09:53Z","updated_at":"2026-09-02T20:58:42Z","closed_at":"2026-09-02T20:58:42Z","close_reason":"Superseded by the [[identities]] feature, not fixed via the originally-requested per-repo-within-one-[[repos]]-list forge override. Verified: IdentityConfig (internal/config/config.go:549) gives each identity its own Forge + Repos list, bootstrap.go:820 builds a per-identity runner with its own forge client, and deployments/multi-forge-github-gitea.toml is a documented, supported profile for exactly the carina/tau scenario this bug describes (GitHub + Gitea from one daemon). The bug's own workaround note anticipated this: 'tau gets no automated dispatch...until this is fixed or it gets a separate identity' -- separate identity is now the supported path. A single identity still cannot mix forges within one flat [[repos]] list; reopen if that finer granularity is specifically wanted.","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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:59:13Z","updated_at":"2026-09-01T15:30:09Z","closed_at":"2026-09-01T15:30:09Z","close_reason":"Closed","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.","notes":"Status as of 2026-09-02: all 7 real children closed (contract/registry,\nruntime, observability, trigger-accounting, memory-engine binding, and\nboth reference curators -- skill and session-memory).\n\nOne epic AC clause remains genuinely unmet: \"curators are registered and\nconfigured declaratively, not hardcoded.\" Both reference curators are\nregistered via direct Register() calls in\ninternal/app/archied/bootstrap.go:setupCurators, with hardcoded\nintervals (skillcurator.DefaultInterval, sessioncurator.DefaultInterval)\n-- no config surface exists to enable/disable a curator or tune its\ninterval/cooldown without a code change and rebuild. Leaving this epic\nopen on that basis rather than closing it on a partial match; a\nfollow-up issue for declarative curator config (mirroring how\narchie-core-1786637490043 did this for memory.engine) would close it.","status":"closed","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:59:10Z","updated_at":"2026-09-02T14:24:11Z","closed_at":"2026-09-02T14:24:11Z","close_reason":"All children completed","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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:59Z","updated_at":"2026-08-17T22:27:53Z","started_at":"2026-08-17T14:22:10Z","closed_at":"2026-08-17T14:33:52Z","close_reason":"Shipped vault/openbao engine plugin in examples/secret-engines/vault.go (commit 24faf53): CLI-based, VAULT_ADDR/VAULT_TOKEN, key 'path/field' or VAULT_SECRET_PATH prefix.","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"],"dependencies":[{"issue_id":"archie-core-1786637500634-411-e265a95c","depends_on_id":"archie-core-1786637500571-409-cdffe32a","type":"related","created_at":"2026-08-15T12:49:33Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637500634-411-e265a95c","depends_on_id":"archie-core-1786637500602-410-7a461d4d","type":"related","created_at":"2026-08-15T12:49:33Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:56Z","updated_at":"2026-08-20T13:24:16Z","closed_at":"2026-08-20T13:24:16Z","close_reason":"Already delivered as a compiled-in engine, not a plugin. internal/secret/bws.go implements secret.Engine and shells out to the bws CLI via os/exec (commit 3ae59c9, 2026-07-31); NewRegistry/DefaultRegistry register it under the name \"bws\" alongside \"env\". It is documented in config.example.toml and ARCHITECTURE.md:208, and config.example.toml:64 uses it as the worked example. Shipping a second yaegi implementation under examples/secret-engines/ would register the same name \"bws\", and Registry.Register is last-write-wins over LoadDir, so the plugin would silently shadow the compiled-in engine -- two authoritative paths for one behaviour, which the architecture contract prohibits. Reopen only if the intent is to REPLACE the compiled-in engine with a plugin (which would also need bws removed from NewRegistry and the docs updated).","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"],"dependencies":[{"issue_id":"archie-core-1786637500602-410-7a461d4d","depends_on_id":"archie-core-1786637500571-409-cdffe32a","type":"related","created_at":"2026-08-15T12:49:33Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:58:53Z","updated_at":"2026-08-17T22:27:53Z","started_at":"2026-08-17T14:22:10Z","closed_at":"2026-08-17T14:33:52Z","close_reason":"Shipped sops engine plugin in examples/secret-engines/sops.go (commit 24faf53): CLI-based, SOPS_FILE env, fresh resolve per call.","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.","notes":"Not resolved yet. docs/architecture/identity.md (Three-layer identity model, agreed 2026-07-30) documents SOUL as Layer 2 and explains why SOUL comes first, but does not state the specific precedence rule between SOUL and a /personality selection that this issue's acceptance criteria requires. /personality is still fully live and unmodified: internal/channels/telegram/personality.go, internal/gateway/gateway.go:375,472,507. DefaultPersonas() still lives in internal/gateway/persona.go with no SOUL reference. This is a real open design decision, not a documentation-only task -- read docs/architecture/identity.md's three-layer model first, then decide (and document) precedence.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:57:44Z","updated_at":"2026-08-15T12:52:35Z","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":"Fix forge test fakes after adding LinkBranch","description":"The forge.Forge interface gained LinkBranch, but several hand-written test doubles were not updated.\n\nAffected fakes include stubForge, prCapturingForge, testForge, and fakeForge. This caused go vet ./... and go test ./... to fail because the test doubles no longer satisfied forge.Forge.\n\nAcceptance criteria:\n- All forge test doubles implement the current forge.Forge interface.\n- go vet ./... passes.\n- go test ./... passes.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:57:33Z","updated_at":"2026-08-24T06:57:54Z","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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:57:04Z","updated_at":"2026-08-15T12:55:20Z","closed_at":"2026-08-15T12:55:20Z","close_reason":"Complete: internal/domain/curator (contract.go, registry.go, registrar.go) already satisfies every acceptance criterion. CuratorEngine is a typed contract with Name/Version/Manifest/Check/Pass/Bind plus embedded Lifecycle (start/health/stop). Registry (registry.go) controls Register/Start/Health/Stop with dependency-free single ownership, panic-isolated safeCheck/safePass/bindSafely. Registrar (registrar.go) is narrow and fully typed (LLMRunner, ToolBuilder, SkillStore, EventSink, Clock) -- no *daemon.Daemon, no untyped hook map, confirmed by grep. go test ./internal/plugin/... -run TestEveryEngineInterfaceHasTypedCapabilityAndFamilyOwner -v shows domain/curator.CuratorEngine PASS as a recognised conforming engine family. go test ./internal/domain/curator/... -race -count=1 is fully green. Note: package lives at internal/domain/curator (per the domain migration), not literally internal/curator as the title says -- that's the current architecture, not a gap.","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"],"dependencies":[{"issue_id":"archie-core-1786637499933-386-83646cce","depends_on_id":"archie-core-1786637490069-11-e245c170","type":"related","created_at":"2026-08-15T12:49:33Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637499933-386-83646cce","depends_on_id":"archie-core-1786637500725-414-9d66a52b","type":"parent-child","created_at":"2026-09-01T15:50:26Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:56:55Z","updated_at":"2026-08-17T14:34:48Z","closed_at":"2026-08-17T14:34:48Z","close_reason":"Confirmed fixed by Sam; no longer reproducible","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:56:52Z","updated_at":"2026-08-15T12:50:59Z","closed_at":"2026-08-15T12:50:59Z","close_reason":"Fixed: internal/natsrpc/natsrpc.go:118-121 RegisterAll already calls nc.Flush() before returning, exactly matching the fix CLAUDE.md documents ('natsrpc.RegisterAll now flushes before returning -- this was the cause of the long-standing TestRunTaskExecutesBootstrapWorkflowEndToEnd CI flake'). Verified: go test ./internal/natsrpc/... ./internal/app/agentworker/... ./internal/daemon/... -race -count=3 is clean, no flakes.","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":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:56:49Z","updated_at":"2026-09-02T20:49:56Z","started_at":"2026-09-02T20:49:37Z","closed_at":"2026-09-02T20:49:56Z","close_reason":"Stale as of 2026-08-08's 56-issue count; verified today golangci-lint run ./... reports 0 issues (same command Taskfile's lint target runs), thresholds unchanged (cyclop max-complexity 15, gocognit min-complexity 30 in .golangci.yml), no threshold loosening. All 21 remaining //nolint suppressions (nilerr x14, contextcheck x4, others) carry a documented reason in an adjacent comment. Acceptance criteria met.","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":"closed","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:56:25Z","updated_at":"2026-09-02T20:50:07Z","closed_at":"2026-09-02T20:50:07Z","close_reason":"Verified 2026-09-03: golangci-lint run ./... reports 0 issues repo-wide (thresholds unchanged from 9298afd's config: cyclop 15, gocognit 30). The gate this epic's description called RED is green. Its last known child (Phase 5, the 56-finding remainder) closed for the same reason -- see archie-core-1786637499814-382-b27575d6.","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.","notes":"Blocked on its own stated prerequisite, which is also still open: archie-core-1786637490069-11-e245c170 (Memory engine contract and owning registry). Current state: Manifest.MemoryEngine (internal/domain/curator/contract.go:59-63) is only a declared string name; Registrar (registrar.go) has no memory-engine field at all, so nothing actually binds an engine instance to a curator yet -- registry.go:128's agentic() check only tests MemoryEngine != \"\", it doesn't inject anything. Do not start this until the memory engine contract exists; there is nothing to bind to yet.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:56:23Z","updated_at":"2026-09-01T16:47:58Z","closed_at":"2026-09-01T16:47:58Z","close_reason":"Complete, all three AC clauses:\n\n- A curator declares its memory engine via Manifest.MemoryEngine and\n receives it as a typed dependency: curator.Registrar.MemoryEngines\n (Get(name) (domainmemory.MemoryEngine, bool)), same trust model as\n ToolBuilder.Build(ctx, declared) -- the curator calls Get with its own\n declared name, not handed a pre-resolved instance. Registration\n enforces presence exactly like Tools/Skills: declared with no\n MemoryEngineSource on the host is rejected at Register\n (TestRegistryDeclaredCapabilitiesRequireHostServices' two new cases),\n and filter() clears the field from a curator's view when undeclared\n (TestRegistryBindFiltersToDeclaredCapabilities).\n- Swapping the configured engine changes where memories land with no\n curator code change: nothing about a curator names a concrete engine,\n only the string it declared, resolved fresh through whichever registry\n it was bound to.\n- A curator with no declared engine stays valid (pre-existing behavior,\n now covered by table cases) and can only ever be affected by a memory\n operation it structurally cannot attempt, since MemoryEngines is nil\n in its view.\n\nWired end to end: internal/app/archied/bootstrap.go:setupCurators passes\nb.memEngines (*domainmemory.Registry, set by setupMemoryAll which Run()\ncalls before setupCurators) straight in -- it already satisfies\nMemoryEngineSource with no adapter.\n\ngo test ./... is green; task lint is 0 issues.","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"],"dependencies":[{"issue_id":"archie-core-1786637499636-376-2f94082e","depends_on_id":"archie-core-1786637490069-11-e245c170","type":"blocks","created_at":"2026-08-15T12:55:30Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637499636-376-2f94082e","depends_on_id":"archie-core-1786637500725-414-9d66a52b","type":"parent-child","created_at":"2026-09-01T15:50:27Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"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.","notes":"Engine implementation done: internal/infrastructure/memory.BuiltinEngine\nimplements domain/memory.MemoryEngine over internal/memory/builtin.Store\n(one per identity), fully tested including registering/running through\ndomain/memory.Registry. internal/memory/builtin itself is untouched, its\nown tests pass unmodified.\n\nNOT done: not wired into daemon bootstrap, and nothing selects it as\n\"the default\" at runtime yet -- that depends on the config surface\n(archie-core-1786637490043) landing first, since there's no config field\nto resolve \"unconfigured\" to this engine until then. Leaving open rather\nthan closing on a partial AC match; will close once bootstrap wiring\nmakes it the actual running default.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:55:53Z","updated_at":"2026-09-01T16:44:27Z","closed_at":"2026-09-01T16:44:27Z","close_reason":"Complete: cfg.Memory.Engine now actually selects and starts an engine at\ndaemon boot, not just implements the contract in isolation.\n\ninternal/app/archied/bootstrap.go:setupMemoryEngine builds a\ndomain/memory.Registry, registers infraMemory.BuiltinEngine for\ncfg.Memory.Engine == \"builtin\" or \"\" (matching applyMemoryDefaults'\nresolution, so unconfigured and explicitly-builtin behave identically),\nstarts it, and stops it on shutdown -- rooted at workDir/memory-engine,\nseparate from the legacy provider's workDir/memory so the two can never\ncollide while both exist. Wired into Run() via setupMemoryAll\n(archie-core-1786637490043's cfg.Memory.Engine validation runs first at\nconfig load, so the switch's default case only guards drift between\nthat list and this one, not live operator input).\n\ninternal/memory/builtin is unchanged (verified: no diff, its tests pass\nunmodified) and internal/memory.Manager (the live system-prompt/tool-call\npath) does not read through this registry -- the two systems run in\nparallel by design, per archie-core-1786637490069-11-e245c170's explicit\nscoping. Converging them is future work, not part of this issue's AC.\n\ngo test ./... is green; task lint is 0 issues.","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"],"dependencies":[{"issue_id":"archie-core-1786637499480-370-223df308","depends_on_id":"archie-core-1786637499161-356-e424e40d","type":"parent-child","created_at":"2026-09-01T15:55:53Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:54:55Z","updated_at":"2026-09-01T16:58:47Z","closed_at":"2026-09-01T16:58:47Z","close_reason":"Complete, all three AC clauses. Design decided first in\ndocs/prds/skill-curator.md (no settled design existed for what \"review,\nprune, improve\" means as concrete behavior): v1 is mechanical validation\nplus safe whitespace normalization only -- no LLM-authored rewrites, no\ndeletion. See the doc for the full \"why this scope, not more\" reasoning.\n\n- Registers and runs through curator.Registry with no curator-specific\n special-casing: uses the existing Register/Runtime path unchanged\n (TestRegistersAndRunsThroughTheRegistry).\n- Its changes are observable and attributable: every write is preceded\n by an Action naming what changed and why (skill.normalized), surfaced\n through the existing curator activity tracker\n (archie-core-1786637489932, already shipped) -- no new observability\n surface needed.\n- Operates within its declared tool set: Manifest.Tools is empty, and\n nothing in the implementation ever touches Registrar.Tools\n (TestManifestDeclaresOnlySkills).\n\ninternal/infrastructure/skillcurator/{store,skillcurator}.go implement\ncurator.SkillStore and curator.CuratorEngine. The store deliberately does\nnot delegate to internal/skill.Discover, which aborts its whole call on\nany one skill's parse failure -- wrong for \"review each skill\nindependently\" (TestPassReviewsEverySkillIndependently covers the\nregression this would otherwise cause). Wired into\ninternal/app/archied/bootstrap.go:setupCurators, rooted the same way\nloadWorkflows resolves skillsBase.\n\ntask check is green (full Go suite + dashboard tests).","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"],"dependencies":[{"issue_id":"archie-core-1786637499206-358-54f29252","depends_on_id":"archie-core-1786637500725-414-9d66a52b","type":"parent-child","created_at":"2026-09-01T15:50:28Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:54:47Z","updated_at":"2026-09-02T14:24:11Z","closed_at":"2026-09-02T14:24:11Z","close_reason":"All children completed","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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:54:39Z","updated_at":"2026-09-01T17:09:13Z","closed_at":"2026-09-01T17:09:13Z","close_reason":"Complete, all four AC clauses. Design decided first in\ndocs/prds/session-memory-curator.md, most notably: Observation.Identity\nis the session ID, not a user/cross-session identity -- migration-\ndecisions.md#5's memory-scope mapping is still explicitly open and this\nissue has no business deciding it unilaterally.\n\n- Registers and runs through curator.Registry with no special-casing\n (TestRegistersAndRunsThroughTheRegistry).\n- Writes through the memory engine contract, never a concrete store:\n Registrar.MemoryEngines.Get(name).Write, same trust model every other\n curator capability uses.\n- Extraction runs off the hot path: the model call happens inside Pass,\n which the curator runtime already runs off a chat turn's own\n goroutine.\n- What it wrote and why is inspectable: one memory.extracted Action per\n session with a count, through the existing curator activity tracker.\n- Honours the trigger-accounting invariant: Manifest.OnInput = true\n wakes it via the existing WakeOnPrimaryInput wiring, which already\n excludes every curator-derived event kind -- no new code needed for\n that guarantee to hold here.\n\nWired end to end: internal/app/archied/bootstrap.go:setupCurators,\nadapters for gateway.SessionStore (internal/infrastructure/\nsessioncurator/adapter.go) and the shared ai-sdk runtime\n(curatorLLMRunner, main.go).\n\nCaught and fixed during implementation: a model-call failure and an\nunparseable model response were originally conflated into the same\nswallowed-error path, which would have hidden a real provider outage as\n\"nothing to extract.\" Split into two paths;\nTestPassPropagatesALLMFailure is the regression test.\n\ntask check is green (full Go suite + dashboard tests).","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"],"dependencies":[{"issue_id":"archie-core-1786637499114-354-e5b475b4","depends_on_id":"archie-core-1786637500725-414-9d66a52b","type":"parent-child","created_at":"2026-09-01T15:50:28Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:54:15Z","updated_at":"2026-09-02T10:44:38Z","started_at":"2026-09-02T10:44:08Z","closed_at":"2026-09-02T10:44:38Z","close_reason":"Added a commented token_env placeholder under [chat.telegram] in config.example.toml, matching the style of the other optional fields.","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:53:48Z","updated_at":"2026-08-15T12:59:58Z","closed_at":"2026-08-15T12:59:58Z","close_reason":"Stale: the mismatch this bug describes no longer exists. At filing (2026-08-08) origin was https://git.catlow.cloud/sam/archie-core.git while install.sh:27 REPO_URL was https://github.com/samcharles93/archie-core.git. The project's canonical remote has since moved TO GitHub -- git remote -v now shows origin = https://github.com/samcharles93/archie-core.git, exactly matching install.sh's REPO_URL. Verified the repo is public and anonymously cloneable: gh repo view shows isPrivate:false, and git ls-remote succeeds. install.sh needs no change.","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":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:52:38Z","updated_at":"2026-08-14T15:30:29Z","started_at":"2026-08-14T15:21:25Z","closed_at":"2026-08-14T15:30:29Z","close_reason":"Exported ForgeDisabled as the single predicate in internal/infrastructure/configuration; removed the duplicated copy from cmd/archied. Tests: TestForgeDisabled table + discriminating warn-log assertions in TestResolveForgeDegradesInsteadOfFailing (verified to fail under re-inline drift). task check scoped: go test ./... green, gofumpt/vet clean, golangci-lint zero findings in changed files.","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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:49:41Z","updated_at":"2026-08-15T12:47:29Z","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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:49:33Z","updated_at":"2026-08-15T12:47:29Z","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.","notes":"Not started. internal/channels/webhook/webhook.go has no MS-Graph-specific handling at all -- no validationToken query-param echo, no clientState check, no CIDR allowlist. This is likely a separate RouteConfig variant or a dedicated handler function, since MS Graph's subscription-verification handshake (echo validationToken as text/plain on subscribe) doesn't fit the existing POST-body-in/HMAC-out flow.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:20Z","updated_at":"2026-08-15T12:51:54Z","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"],"dependencies":[{"issue_id":"archie-core-1786637497353-287-96a3e24c","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Not started. No cache of any kind in internal/channels/webhook/webhook.go. Needs a webhook event ID (route-scoped) -\u003e TTL cache; most platforms send a stable delivery/event ID header (e.g. GitHub's X-GitHub-Delivery) usable as the key. Related to the gateway-level archie-core-1786637492498-104-1bde76ae (MessageDeduplicator) which solves the same class of problem one layer up -- check whether one mechanism can serve both before building a second cache.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:17Z","updated_at":"2026-08-15T12:51:54Z","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"],"dependencies":[{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-1786637492498-104-1bde76ae","type":"related","created_at":"2026-08-15T12:52:03Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-7d5u.5","type":"relates-to","created_at":"2026-08-21T23:27:06Z","created_by":"Sam Catlow","metadata":"{}"}],"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).","notes":"Not started, despite the package doc comment's claim: webhook.go:1-3 says 'Outbound delivery is not supported (deliver-only mode)' but handleWebhook() (webhook.go:120-183) unconditionally calls router.Route -- there is no branch that skips the agent and renders the template directly. RouteConfig.DeliverTo==\"origin\" only controls where the agent's reply goes, it doesn't skip the agent. Either the doc comment is aspirational (fix by implementing this issue) or describes a different, unbuilt code path -- don't trust the comment over the code.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:14Z","updated_at":"2026-08-15T12:51:54Z","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"],"dependencies":[{"issue_id":"archie-core-1786637497299-285-f4780816","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Partially done: internal/channels/webhook/webhook.go:243-264 extractText() does single-field dot-notation extraction (RouteConfig.Template = \"issue.title\"), not multi-variable interpolation. This issue wants a template string with multiple {field.path} placeholders plus a {__raw__} escape hatch -- extractText needs to become a real interpolation pass (parse placeholders, resolve each dot-path, substitute), not a single-path lookup. RouteConfig.Template's meaning would change from 'the one field to extract' to 'a template string' -- update its doc comment in the same change.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:10Z","updated_at":"2026-08-15T12:51:54Z","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"],"dependencies":[{"issue_id":"archie-core-1786637497271-284-573ca138","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Not started. No script/transform hook exists in internal/channels/webhook/webhook.go. Would sit between body read and text extraction in handleWebhook() (webhook.go:120-183), likely as a RouteConfig field naming an external command, invoked via os/exec on the raw body before extractText.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:07Z","updated_at":"2026-08-15T12:51:54Z","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"],"dependencies":[{"issue_id":"archie-core-1786637497242-283-03662140","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Not started. internal/channels/webhook/webhook.go has no filter logic -- handleWebhook goes straight from HMAC validation to text extraction. This would insert between those two steps in handleWebhook() (webhook.go:120-183).","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:04Z","updated_at":"2026-08-15T12:51:54Z","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"],"dependencies":[{"issue_id":"archie-core-1786637497221-282-f0a2975e","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Partially done: internal/channels/webhook/webhook.go:186-196 validateHMAC() implements GitHub-style HMAC-SHA256 (X-Hub-Signature-256/X-Signature-256, sha256= prefix). Missing: GitLab's X-Gitlab-Token (static token compare, not HMAC -- different validation path entirely) and the generic V2 timestamp-bound replay-protected scheme. Extend validateHMAC/handleWebhook to dispatch by scheme rather than assuming GitHub's format.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:48:35Z","updated_at":"2026-08-15T12:51:54Z","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"],"dependencies":[{"issue_id":"archie-core-1786637497066-276-35fe7db3","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.\nFoundation exists: internal/channels/webhook/webhook.go (264 lines, tested in webhook_test.go) already implements the HTTP server, single-scheme HMAC validation (GitHub-style X-Hub-Signature-256/X-Signature-256 with sha256= prefix), single-field dot-notation extraction (extractText), and always-route-to-agent dispatch. Still missing, per sub-issue: GitLab/V2 HMAC schemes (275/276), declarative filters (282), script transforms (283), multi-variable {field} interpolation vs current single-path extraction (284), an actual deliver_only skip-agent branch -- current code always calls router.Route (285), idempotency cache (286), MS Graph validationToken handshake (287). Extend this file/package, don't create a parallel one.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:48:32Z","updated_at":"2026-08-15T12:51:54Z","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"],"dependencies":[{"issue_id":"archie-core-1786637497036-275-8838629e","depends_on_id":"archie-core-7d5u.3","type":"relates-to","created_at":"2026-08-21T23:27:06Z","created_by":"Sam Catlow","metadata":"{}"}],"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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:48:24Z","updated_at":"2026-08-15T12:47:29Z","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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:57Z","updated_at":"2026-09-05T07:10:42Z","closed_at":"2026-09-05T07:10:42Z","close_reason":"Closed","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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:54Z","updated_at":"2026-09-05T07:10:42Z","closed_at":"2026-09-05T07:10:42Z","close_reason":"Closed","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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:47:51Z","updated_at":"2026-09-05T07:10:42Z","closed_at":"2026-09-05T07:10:42Z","close_reason":"Closed","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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:47:39Z","updated_at":"2026-08-15T12:47:29Z","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":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:47:09Z","updated_at":"2026-08-24T03:29:05Z","started_at":"2026-08-24T03:22:18Z","closed_at":"2026-08-24T03:29:05Z","close_reason":"Implemented in internal/domain/scheduling (branch feat/275-ticker-engine): configurable tick interval, parallel and sequential pools, overlap suppression, per-run timeout, bounded graceful shutdown. Job store, blueprints and delivery routing remain open in the epic.","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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:46:46Z","updated_at":"2026-08-15T12:47:29Z","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.\n","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:46:38Z","updated_at":"2026-08-15T12:44:48Z","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":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:46:00Z","updated_at":"2026-08-15T05:31:24Z","started_at":"2026-08-15T05:12:08Z","closed_at":"2026-08-15T05:31:24Z","close_reason":"internal/ratelimit: EvictStale() window-based sweep bounds per-key map memory; 8 new tests incl. Allow-outcome pair-equality; go test -race, golangci-lint, gofumpt, go vet, go build all clean; adversarial review PASS (zero surviving findings, incl. independent 378-timing differential)","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).\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:45:05Z","updated_at":"2026-08-15T12:47:30Z","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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:44:46Z","updated_at":"2026-08-15T12:47:30Z","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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:41:16Z","updated_at":"2026-08-15T12:58:36Z","closed_at":"2026-08-15T12:58:36Z","close_reason":"Complete: internal/tools/webfetch (webfetch.go, tool.go) implements every clause. Dial-time SSRF protection via custom DialContext (webfetch.go:66,233,240) that resolves the host and rejects private/loopback before dialing the vetted IP -- not a pre-flight URL check, matching the DNS-rebinding concern the issue calls out explicitly. CheckRedirect present (webfetch.go:74), AllowPrivateNetworks config wired through internal/config/config.go:322-326 (default false) and internal/tools/webfetch/webfetch.go:49-52,256, HTML-to-text via golang.org/x/net/html, and the tool is registered in cmd/archied/main.go:992 beside skill_activate as specified. go test ./internal/tools/webfetch/... -race -count=1 is green.","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.","notes":"Blocked in practice: this verifies archie-core-1786637493594-146-10de5e79 (Progressive tool disclosure (bridge tools)), which is still OPEN. Do not start this review until that implementation closes.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:40:17Z","updated_at":"2026-08-15T12:49:26Z","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"],"dependencies":[{"issue_id":"archie-core-1786637494137-167-1cb48767","depends_on_id":"archie-core-1786637493594-146-10de5e79","type":"validates","created_at":"2026-08-15T12:49:16Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Ready: this verifies archie-core-1786637494585-183-63b2b2a2 (Concurrent tool dispatch with execution gating), which is already CLOSED. This review can proceed now.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:45Z","updated_at":"2026-08-15T12:49:26Z","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"],"dependencies":[{"issue_id":"archie-core-1786637493958-160-063454b8","depends_on_id":"archie-core-1786637494585-183-63b2b2a2","type":"validates","created_at":"2026-08-15T12:49:16Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Blocked in practice: this verifies archie-core-1786637494559-182-410c3c4c (Sequential tool dispatch with per-result previews and error handling), which is still OPEN. Do not start this review until that implementation closes.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:42Z","updated_at":"2026-08-15T12:49:26Z","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"],"dependencies":[{"issue_id":"archie-core-1786637493932-159-ee61b7c9","depends_on_id":"archie-core-1786637494559-182-410c3c4c","type":"validates","created_at":"2026-08-15T12:49:16Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Blocked in practice: this verifies archie-core-1786637494041-163-961e45bb (Tool availability checks with TTL caching), which is still OPEN. Do not start this review until that implementation closes.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:39:34Z","updated_at":"2026-08-15T12:49:26Z","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"],"dependencies":[{"issue_id":"archie-core-1786637493884-157-e7cc3387","depends_on_id":"archie-core-1786637494041-163-961e45bb","type":"validates","created_at":"2026-08-15T12:49:08Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"in_progress","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:38:40Z","updated_at":"2026-09-05T00:06:07Z","started_at":"2026-09-05T00:06:07Z","lease_expires_at":"2026-09-05T00:11:07Z","heartbeat_at":"2026-09-05T00:06:07Z","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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:38:11Z","updated_at":"2026-08-15T12:47:30Z","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","description":"A capability-flag mechanism so callers can ask an adapter which optional features it supports (typing indicator, edit, delete, media send, clarify/approval/picker UI) instead of discovering support by a failed type assertion or a runtime error.\n\n### Context for implementers\n\nThis depends on the optional-method interfaces this issue is meant to describe: `archie-core-1786637493329-136-49b39c78` (typing/edit/delete/media) and `archie-core-1786637493357-137-35af7083` (clarify/approval/pickers). Implement after (or in close coordination with) those two, since the flag set should mirror whatever optional interfaces they land — don't invent a flag taxonomy ahead of the methods it describes.\n\n### Acceptance Criteria\n\n`BasePlatformAdapter` (`internal/gateway/adapter.go`) or a wrapping type exposes a capability query (e.g. `Capabilities() AdapterCapabilities`) that reports which optional methods an adapter implements. Every existing adapter's reported capabilities match its actual method set (a regression test should fail if an adapter claims a capability it doesn't implement, or vice versa).\n","notes":"Partial: the mechanism itself (gateway.CapabilityReporter, CapabilitiesOf, AdapterCapabilities) is built and covered by a regression test, scoped to Media only -- see archie-core-1786637493329-136-49b39c78 (closed, media portion). Still blocked on archie-core-1786637493357-137-35af7083 (clarify/approval/pickers) since AdapterCapabilities needs those flags added too before this is fully done.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:02Z","updated_at":"2026-08-23T12:53:18Z","started_at":"2026-08-22T11:53:10Z","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"],"dependencies":[{"issue_id":"archie-core-1786637493387-138-cad8e7a7","depends_on_id":"archie-core-1786637493329-136-49b39c78","type":"blocks","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637493387-138-cad8e7a7","depends_on_id":"archie-core-1786637493357-137-35af7083","type":"blocks","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493357-137-35af7083","title":"BasePlatformAdapter interactive UX methods (clarify, approval, pickers)","description":"Add adapter-facing methods for interactive UX: presenting a clarifying question, an approval prompt, and a picker (multi-choice selection) natively on the platform, rather than as plain text the user has to reply to by hand.\n\n### Context for implementers\n\nThe approval *decision* plumbing already exists — `internal/tools/approval.go`, re-exported through `internal/gateway/approval.go` (`ApprovalRequester`, `ApprovalDecision`, `WithApprovalRequester`/`ApprovalFromContext`). What's missing is the adapter-side rendering: `BasePlatformAdapter` (`internal/gateway/adapter.go`) has no method for an adapter to display an approval/clarify/picker UI and report back a decision through that existing plumbing. This issue wires a new adapter method (or interface) into the existing `ApprovalRequester` flow — it should not duplicate or replace the decision model in `internal/tools/approval.go`. Sibling of `archie-core-1786637493329-136-49b39c78` (typing/edit/delete/media) — same \"optional adapter capability\" shape, different capability set.\n\n### Acceptance Criteria\n\nAn adapter can render a clarify/approval/picker prompt and the user's response is delivered back through the existing `ApprovalRequester`/`ApprovalDecision` flow in `internal/tools/approval.go`, not a parallel mechanism. Platforms without native UI (e.g. plain text-only channels) degrade to a text-based fallback rather than failing. Covered by a test double adapter, not a live platform.\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:59Z","updated_at":"2026-08-15T12:46:48Z","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":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637493329-136-49b39c78","title":"BasePlatformAdapter optional methods (typing, edit, delete, media)","description":"Extend adapter capability beyond the four required `BasePlatformAdapter` methods with optional per-platform methods: typing indicator, message edit, message delete, and media-specific send.\n\n### Context for implementers\n\n`internal/gateway/adapter.go` today defines `BasePlatformAdapter` with exactly four methods: `Connect`, `Disconnect`, `Send`, `ChatInfo` (see full listing — the file is 80 lines). Not every platform supports typing/edit/delete/media uniformly, so these should be a separate optional interface(s) that callers type-assert for, not additions to the required interface (that would break every existing adapter implementation). Pairs with `archie-core-1786637493387-138-cad8e7a7` (platform capability flags) — callers need a way to know *ahead of a type assertion* whether an adapter supports a given optional method, rather than probing via failed assertions at call time.\n\n### Acceptance Criteria\n\nOptional methods are defined on a separate interface (or interfaces) from `BasePlatformAdapter`, so existing adapters keep compiling unchanged. At least one adapter implementation exercises each optional method in a test. Callers that invoke an optional method on an adapter that doesn't implement it get a defined, non-panicking behavior.\n","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:57Z","updated_at":"2026-08-24T07:12:09Z","started_at":"2026-08-22T11:53:09Z","closed_at":"2026-08-24T07:12:09Z","close_reason":"Media portion delivered: gateway.MediaSender + telegramMediaSender + TurnStream.Media wiring in Telegram's liveReply. Typing/edit/delete indicators from this issue's original scope are NOT done -- splitting them out if still wanted, since they're unrelated to the video-gen work that drove this. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","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":1,"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","description":"An `EphemeralReply` type for messages the gateway sends that should self-delete after a TTL — status/progress placeholders (\"thinking…\", \"running tool X…\") that shouldn't linger in the chat history once superseded.\n\n### Context for implementers\n\nNo ephemeral-reply file exists yet in `internal/gateway`. Deletion requires adapter support: `BasePlatformAdapter` (`internal/gateway/adapter.go`) currently exposes only `Connect`/`Disconnect`/`Send`/`ChatInfo` — no delete method. This depends on (or should land alongside) `archie-core-1786637493329-136-49b39c78` (BasePlatformAdapter optional methods, which includes delete) — an adapter without a delete method can't honor the TTL.\n\n### Acceptance Criteria\n\nAn `EphemeralReply` carries a TTL after which the gateway issues a delete against the originating adapter. Adapters without delete support degrade gracefully (e.g. leave the message, log once) rather than erroring the turn. TTL firing is covered by a test using an injected clock, not a real sleep.\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:48Z","updated_at":"2026-08-15T12:46:47Z","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"],"dependencies":[{"issue_id":"archie-core-1786637493282-134-cf46838e","depends_on_id":"archie-core-1786637493329-136-49b39c78","type":"related","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:37:45Z","updated_at":"2026-08-15T02:48:49Z","closed_at":"2026-08-15T02:48:49Z","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"],"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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:37:39Z","updated_at":"2026-08-24T07:12:08Z","closed_at":"2026-08-24T07:12:08Z","close_reason":"Closed [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:36:04Z","updated_at":"2026-08-15T12:48:38Z","closed_at":"2026-08-15T12:48:38Z","close_reason":"Duplicate: exact duplicate of already-closed archie-core-1786637492794-115-e32e88a6 (GH #136, created 11s after GH #135, closed 3s after creation -- accidental double-create during bulk issue spawn). The implementation it verifies, archie-core-1786637492437-102-17365d0d (SessionContext struct), is already closed.","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":"Verify MessageType enum for gateway messages","description":"Verify that the gateway message MessageType enum is complete, consistently named, and correctly handled by its consumers.\n\nThis issue remains retained as a verification task; implementation changes are only required if the review finds a missing or inconsistent enum value.\n\nAcceptance criteria:\n- Enumerate the gateway message types and their intended meanings.\n- Confirm producers and consumers handle the defined values consistently.\n- Add or update focused tests for any uncovered value or behavior.\n- Record the verification result in the issue before closing.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:43Z","updated_at":"2026-08-24T06:57:56Z","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","description":"Shared media utilities for handling images/audio/video/documents across platform adapters: download from the platform, validate (MIME type, size ceiling), cache to avoid re-fetching, and hand back a normalized reference the gateway can attach to a `MessageEvent` or deliver outbound.\n\n### Context for implementers\n\nNo media file exists yet in `internal/gateway`. `MessageEvent` (`internal/gateway/messageevent.go`) is the shared event model this should plug into — check its current field set before adding a parallel media type. This is infrastructure other Gateway epic items depend on conceptually (any adapter method that sends/receives media, e.g. `archie-core-1786637493329-136-49b39c78` BasePlatformAdapter optional methods) but there is no formal `bd dep` between them yet.\n\n### Acceptance Criteria\n\nA shared utility validates MIME type and size before accepting media, caches downloaded media keyed by platform + media ID with TTL/size-bounded eviction, and exposes a normalized reference type usable from any adapter. Oversized or disallowed-MIME media is rejected with a caller-visible error, not silently dropped.\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:41Z","updated_at":"2026-08-15T12:46:47Z","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"],"dependencies":[{"issue_id":"archie-core-1786637492590-107-92482ef1","depends_on_id":"archie-core-1786637493329-136-49b39c78","type":"related","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637492559-106-5ea2315d","title":"Code-fence-aware message truncation","description":"Truncate outbound messages to a platform's length limit (e.g. Telegram's 4096 chars) without ever cutting inside a ``` code fence — a truncation mid-fence leaves the rest of the message rendered as broken/unclosed markdown on the client.\n\n### Context for implementers\n\nNo truncation helper exists yet in `internal/gateway`. This is distinct from the Markdown→HTML conversion trap documented in `CLAUDE.md` (\"`EscapeMarkdown` does the *inverse* of formatting\" / `go-telegram/bot`'s `SendRichMessage`) — that trap is about format conversion, this issue is about length-based cropping. Keep the two concerns separate: this helper should decide *where* to cut; rendering is a separate step.\n\n### Acceptance Criteria\n\nA message longer than the platform limit is truncated at a safe boundary: never inside an open code fence, preferring a paragraph/sentence boundary before the limit. If truncation would land inside a fence, the cut point backs up to before the fence opens (or the fence is closed and reopened on continuation, if multi-part delivery is in scope — confirm with the maintainer which behavior is wanted before implementing). Covered by a table-driven test with fenced and unfenced inputs at/over the limit.\n","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:39Z","updated_at":"2026-08-24T07:12:07Z","started_at":"2026-08-22T09:32:18Z","closed_at":"2026-08-24T07:12:07Z","close_reason":"Implemented code-fence-aware Telegram message splitting with bounded continuation handling and regression coverage [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]","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","description":"Batch rapid-fire inbound text events from the same sender/channel into a single dispatch instead of invoking the agent loop once per fragment. Chat clients (Telegram in particular) often split a user's thought across several quick messages; dispatching each separately wastes a full agent turn per fragment and can interleave responses oddly.\n\n### Context for implementers\n\nNo aggregator exists yet in `internal/gateway`. This sits upstream of the agent-loop dispatch, after platform adapters normalize events into `MessageEvent` (`internal/gateway/messageevent.go`) but before a turn is started (see `internal/gateway/turn.go`, `turns.go`).\n\n### Acceptance Criteria\n\nText events from the same channel arriving within a short configurable window are coalesced into one aggregated event before dispatch. A single non-batched message is not delayed by more than the window. Aggregation window is configurable, not hardcoded. Covered by a test using an injected clock.\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:37Z","updated_at":"2026-08-15T12:46:47Z","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","description":"Prevent duplicate processing of the same platform message. At-least-once delivery (webhook retries, Telegram long-poll re-fetch after a slow ack, forge redelivery) can hand the gateway the same `MessageEvent` more than once; without a dedup layer it gets answered twice.\n\n### Context for implementers\n\n`internal/gateway/messageevent.go` already carries a platform-assigned `ID` field (`MessageEvent.ID`, see line ~59) suitable as a dedup key alongside `ChannelID`/`Platform`. There is currently no dedup file in `internal/gateway` — this is new code, not a rename. Related but distinct: `archie-core-ippu` (gateway: replay and redelivery lose tool activity) covers a different symptom — a replayed *turn* losing its tool-call history in the transcript, not a duplicate inbound message being processed twice. Fix this one first; it may reduce (but won't eliminate) triggers for the other.\n\n### Acceptance Criteria\n\nA `MessageDeduplicator` (or equivalent) keyed on platform + channel + message ID rejects a second delivery of the same message within a configurable TTL window. TTL expiry is covered by a test using an injected clock, not a real sleep. Memory use is bounded (LRU or TTL sweep), not an unbounded map.\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:35:35Z","updated_at":"2026-08-15T12:46:47Z","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"],"dependencies":[{"issue_id":"archie-core-1786637492498-104-1bde76ae","depends_on_id":"archie-core-ippu","type":"related","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"}],"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.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:35:22Z","updated_at":"2026-08-15T12:47:30Z","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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:34:38Z","updated_at":"2026-09-01T16:51:58Z","closed_at":"2026-09-01T16:51:58Z","close_reason":"Deprioritized by Sam (2026-09-02): not a current priority. Re-open when there's actual appetite to build against a live Honcho instance -- the engine contract it would implement against (domain/memory.MemoryEngine) is done and stable, so this is unblocked whenever picked back up, not superseded by anything.","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"],"dependencies":[{"issue_id":"archie-core-1786637492031-86-0fcaccc0","depends_on_id":"archie-core-1786637499161-356-e424e40d","type":"parent-child","created_at":"2026-09-01T15:50:34Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:34:10Z","updated_at":"2026-08-15T12:55:20Z","closed_at":"2026-08-15T12:55:20Z","close_reason":"Complete: internal/domain/curator/runtime.go implements exactly this. Verified against every acceptance-criteria clause: pending-input curators run without waiting for the interval (TestRuntimeWakeRunsPendingPassImmediately), idle curators sleep until interval (TestRuntimeIdleCuratorSleepsUntilInterval) with a configurable per-curator cooldown (TestRuntimeCooldownAfterIdlePass, TestRuntimeNextCheckInOverride), all timed via an injected fake clock not wall-clock sleep, shutdown is context-bounded (TestRuntimeShutdownCancelsInFlightPass, TestRuntimeShutdownBoundedDespiteStuckPass), and panics are recovered and isolated (TestRuntimeCheckPanicRecovered, TestRuntimePassPanicRecovered). go test ./internal/domain/curator/... -race -count=1 is fully green.","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"],"dependencies":[{"issue_id":"archie-core-1786637491805-77-78d888a3","depends_on_id":"archie-core-1786637500725-414-9d66a52b","type":"parent-child","created_at":"2026-09-01T15:50:28Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:30:27Z","updated_at":"2026-08-15T12:48:38Z","closed_at":"2026-08-15T12:48:38Z","close_reason":"Stale/duplicate: exact duplicate of already-closed archie-core-1786637491429-62-088b752f (GH #83, created 3 min later, closed within 2s — accidental double-create). Also independently verified complete: internal/daemon/daemon.go:882-893 already hands sandboxed tasks to archie-agent in one NATS round trip via runViaAgent instead of a per-stage loop, and internal/app/agentworker/task_execution.go:85,143,146 calls workflow.Route/workflow.Run with wfeval.Discover agent-side, matching the acceptance criteria verbatim. inprocess/subprocess path (daemon.go:894+) is untouched, as required.","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":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:29:29Z","updated_at":"2026-08-15T12:27:34Z","closed_at":"2026-08-15T12:27:34Z","close_reason":"Verified against current main: Route/RouteStream reject unrecognized slash commands before any LLM call (gateway.go:299-318, 449-462), /start is deterministic in both gateway and Telegram handlers, and full test matrix from acceptance criteria exists (gateway_test.go:106-133, gateway_stream_test.go:54-88, telegram_test.go:135-157). Confirmed by fresh code-tracing pass, not just prior user experience.","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.","notes":"Not fixed in code, but operationally contained: CLAUDE.md now states 'No npx-launched servers are configured in production anyway -- the builtin tools (read, write, edit, find, grep, shell) and web_fetch.' Confirmed no persistent-cache or build-time-install mechanism exists in internal/tools/provider/provider.go. If an operator adds an npx-based MCP server back, this bug reproduces exactly as described. Fix is still the structural one (build-time install or persisted cache), not just avoiding the config -- don't close this on the operational workaround alone.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:29:09Z","updated_at":"2026-08-18T16:05:13Z","started_at":"2026-08-18T15:52:23Z","closed_at":"2026-08-18T16:05:13Z","close_reason":"Fixed: configuredMCPProvider (cmd/archied/main.go) now sets NPM_CONFIG_CACHE under the daemon's persistent work_dir and NPM_CONFIG_PREFER_OFFLINE=true for any npx-launched MCP server (matched by base name so an absolute-path npx still qualifies), so a daemon restart reuses a warm npm cache instead of re-resolving/re-downloading from the registry every time -- the amplifier behind the 2026-07-30 crash loop. Guards an empty workDir explicitly (unreachable in production since config defaulting runs first, but matches memoryProvider's existing precedent for the same defense). Adversarially reviewed by a fresh subagent; findings addressed: narrowed an overclaim that this also covers a package's own separate downloads (e.g. Playwright/Puppeteer fetching browser binaries via CDN, which NPM_CONFIG_CACHE does not touch), and closed the absolute-path-command gap. Full task check clean. The identical, arguably-worse instance in internal/app/agentworker/mcp_providers.go (every per-task ephemeral container, not just daemon restarts) needs real new infra -- a persistent Docker volume bind-mounted into task containers, which doesn't exist yet -- so it's filed separately as archie-core-qk8m rather than folded into this scoped fix.","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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:28:52Z","updated_at":"2026-08-23T13:33:21Z","closed_at":"2026-08-23T13:33:21Z","close_reason":"Closed","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.","notes":"The Tokens-used/Token-outlook portion of this is now tracked in far more depth by archie-core-1786748942590-20-c21c728b (Dashboard: Token outlook is blank because token usage is not reaching daily accounting), which traces the root cause to missing agent_finish event rows (internal/store/events.go:231-251) rather than a rendering bug. If you pick this up, check whether the other KPI tiles (non-token) are still blank independently of that root cause before assuming this issue is just a duplicate of #20 -- the original report named 'the first three dashboard stat tiles', which may be broader than tokens alone.","status":"closed","priority":2,"issue_type":"bug","assignee":"Sam Catlow","created_at":"2026-08-08T14:27:22Z","updated_at":"2026-08-17T22:38:45Z","started_at":"2026-08-17T22:33:49Z","closed_at":"2026-08-17T22:38:45Z","close_reason":"Already fixed by 170fe02 (2026-08-05), predating this bead's 2026-08-08 runtime inspection -- the inspected deployment was serving a stale build. el() in ui/src/base/dom.js was treating a falsy scalar first child (0, '', false) as a missing attrs object and dropping it, so any stat tile whose value was 0 (Working now, Needs you, Tokens used before any usage) rendered a blank headline. Fixed with dedicated regression coverage in ui/test/dom.test.js (el renders a falsy numeric value instead of dropping it, statTile renders a zero headline value, etc.) -- all 9 tests pass. Verified ui/dist rebuilds byte-identical to the committed tree, so the fix ships in the current binary. The token-outlook-specific root cause (missing agent_finish event rows) is tracked separately in archie-core-1786748942590-20-c21c728b per this bead's own notes and is out of scope here.","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":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:26:57Z","updated_at":"2026-09-02T11:48:53Z","started_at":"2026-09-02T11:47:06Z","closed_at":"2026-09-02T11:48:53Z","close_reason":"Wrapped SOUL/Persona in an XML-escaped, trust=data \u003csoul\u003e block rendered before the invariant tags; added TestBuildSystemPromptSoulCannotOverrideInvariants; documented the enforcement in identity.md","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.","notes":"Not started as a conforming engine family. The existing internal/memory package (provider.go, lifecycle.go, backup.go, etc.) predates the domain migration: it has an ad-hoc MemoryProvider interface plus several optional hook interfaces (TurnStartHook, SessionEndHook, ...), but no owning Registry/Manager, no narrow typed registrar, and no Manifest-style declared shape -- it does not follow the strict plugin engine rule that internal/domain/curator (archie-core-1786637499933-386-83646cce, now closed) already demonstrates as the reference implementation. Confirmed via go test ./internal/plugin/... -run TestEveryEngineInterfaceHasTypedCapabilityAndFamilyOwner -v: only domain/curator.CuratorEngine, secret.Engine, and tools/provider.Engine are currently recognised conforming families -- no memory family. Use internal/domain/curator's contract.go/registry.go/registrar.go split as the template; do not extend internal/memory's MemoryProvider in place.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:54Z","updated_at":"2026-09-01T15:55:33Z","closed_at":"2026-09-01T15:55:33Z","close_reason":"Complete: internal/domain/memory/{contract,registrar,registry}.go stands up\nmemory as a conforming engine family, mirroring internal/domain/curator's\nsplit exactly per this issue's own notes.\n\nMemoryEngine (contract.go) embeds Lifecycle (Start/Health/Stop) and Store\n(Write/Query/List/Forget -- real operations, not identity metadata) plus\nName/Version/Manifest/Bind. Store is split out as its own embedded\ninterface so MemoryEngine stays under golangci-lint's interfacebloat\nthreshold, same mechanism as curator's embedded Lifecycle.\n\nRegistry (registry.go) owns Register/Get/Names/Start/Health/Stop with\nduplicate/nil-engine/panic-in-Bind rejection, per-engine Start failure\nisolation (one engine's failed Start does not block the others, and is\nreported via Health), ctx-bounded Stop, and reverse-registration-order\nshutdown -- all verified by registry_test.go, mirroring curator's test\nsuite. go test ./internal/domain/memory/... -race -count=1 is green;\ntask lint is 0 issues.\n\nRegistrar (registrar.go) carries EventSink and Clock -- the only host\nservices with anything to gate on today. No capability-filtering logic\nexists yet because no memory-specific host service is capability-gated\n(unlike curator's Tools/Skills), so Bind passes the host straight\nthrough; add filtering if/when a gated service appears.\n\nOne AC clause is not literally testable yet: internal/plugin/\narchitecture_test.go's TestEngineFamilyInspectionRejectsInvalidShapes\nonly scans inline fixture source, not the real package tree, so nothing\ncurrently asserts memory.MemoryEngine is \"recognised\" by it one way or\nthe other -- the shape matches curator's (which the fixture tests\nvalidate the pattern against), but there is no scan-the-repo test to\nliterally pass. Noting this so a future close of a sibling issue doesn't\nrepeat the earlier inaccurate claim that this test scans real packages\n(archie-core-1786637499933-386-83646cce's close reason cited a test name,\nTestEveryEngineInterfaceHasTypedCapabilityAndFamilyOwner, that does not\nexist in the repo -- likely stale even at the time it was written).\n\nNot done, and correctly still open as their own issues: engines that\nimplement this contract (the Honcho proof, archie-core-1786637492031),\nthe config surface to select one (archie-core-1786637490043), and\nbinding curators to an attached engine (archie-core-1786637499636).","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"],"dependencies":[{"issue_id":"archie-core-1786637490069-11-e245c170","depends_on_id":"archie-core-1786637499161-356-e424e40d","type":"parent-child","created_at":"2026-09-01T15:50:33Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:51Z","updated_at":"2026-09-01T16:44:38Z","closed_at":"2026-09-01T16:44:38Z","close_reason":"Complete, all four AC clauses:\n\n- config.MemoryConfig.Engine field added with toml/yaml/json tags;\n Provider/ProviderConfig/SessionTTL also gained the toml tags they were\n missing (repo convention, config.toml is the primary format).\n- validateMemory (internal/infrastructure/configuration/validate.go)\n rejects an engine name outside memoryEngines with\n \"%w: memory.engine %q (want %s)\", the same named-constant-list +\n oneOf/list shape forge.type already uses. TestValidateMemoryNames\n TheValidSet pins the exact message.\n- applyMemoryDefaults resolves an absent engine to \"builtin\"\n (memoryEngineBuiltin), verified by\n TestApplyMemoryDefaultsFillsAbsentEngineWithBuiltin, and an explicit\n value is left alone (TestApplyMemoryDefaultsLeavesExplicitValuesAlone).\n- config.example.toml documents [memory] engine alongside the existing\n provider field, distinguishing the two mechanisms.\n\nSince closing this, archie-core-1786637499480 (ship builtin as default)\nlanded the bootstrap wiring that actually consumes cfg.Memory.Engine, so\nthe field is not just parsed and validated but live end to end.","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"],"dependencies":[{"issue_id":"archie-core-1786637490043-10-711c450a","depends_on_id":"archie-core-1786637499161-356-e424e40d","type":"parent-child","created_at":"2026-09-01T15:50:33Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:49Z","updated_at":"2026-08-18T15:53:30Z","closed_at":"2026-08-18T15:53:30Z","close_reason":"Superseded: confirmed by Sam that there is no longer a separate /provider command -- grepped the codebase and no '/provider' command exists in internal/gateway or internal/channels/telegram. /model now handles provider scoping directly.","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":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","created_at":"2026-08-08T14:26:46Z","updated_at":"2026-08-15T13:36:39Z","started_at":"2026-08-15T13:25:55Z","closed_at":"2026-08-15T13:36:39Z","close_reason":"Documented the memory engine contract, owning manager, lifecycle/failure isolation, and third-party trust boundary in ARCHITECTURE.md; focused memory tests pass.","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"],"dependencies":[{"issue_id":"archie-core-1786637489985-8-13b9d8a8","depends_on_id":"archie-core-1786637499161-356-e424e40d","type":"parent-child","created_at":"2026-09-01T15:55:59Z","created_by":"Sam Catlow","metadata":"{}"}],"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.","notes":"Half-built: the data this needs already exists but nothing surfaces it. internal/domain/curator/registry.go has Health(ctx) map[string]Health and Names() []string; every pass emits an Action (At/Type/Detail/Reason) and a run event through the curator's EventSink. daemon.Daemon.Curators *curator.Registry (internal/daemon/daemon.go:107-110) holds the live registry. But grep confirms no webui/API/dashboard code reads any of it -- internal/webui has zero curator-aware endpoints, ui/src has no curator surface. This issue is 'wire the existing Registry.Health/Names + action history into the existing observability paths (health endpoint / dashboard)', not 'build the data model from scratch'.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:38Z","updated_at":"2026-08-27T14:31:41Z","closed_at":"2026-08-27T14:31:41Z","close_reason":"Wired GET /api/curators (names, health, last-run, recent actions) backed by a new bounded in-memory activity tracker in internal/domain/curator, plus a Curators dashboard page at ui/src/curators/.","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"],"dependencies":[{"issue_id":"archie-core-1786637489932-6-1f803e02","depends_on_id":"archie-core-1786637500725-414-9d66a52b","type":"parent-child","created_at":"2026-09-01T15:50:29Z","created_by":"Sam Catlow","metadata":"{}"}],"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":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:26:17Z","updated_at":"2026-08-15T12:55:20Z","closed_at":"2026-08-15T12:55:20Z","close_reason":"Complete: internal/domain/curator/wake.go WakeOnPrimaryInput forwards only explicitly-passed inputKinds; curator-produced kinds (curator_run, curator_action, curator_error) are structurally excluded, per its own doc comment naming this exact invariant. internal/domain/curator/wake_test.go:11-21 TestWakeOnPrimaryInputForwardsOnlyPrimaryKinds carries the required feedback-loop rationale verbatim ('if derived curator output counted... a curator that writes memories would schedule itself again... This test fails if a derived kind is added to the forwarded set or the filter is removed as redundant') and asserts passCalls/checkCalls stay at 1 after publishing derived-kind events. All three acceptance-criteria clauses satisfied exactly.","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"],"dependencies":[{"issue_id":"archie-core-1786637489768-1-2fd8288f","depends_on_id":"archie-core-1786637500725-414-9d66a52b","type":"parent-child","created_at":"2026-09-01T15:50:29Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8cda.7","title":"Phase 5: Extract Execution Environment + Runner + Scheduler","description":"Fifth extraction in the resolved order -- the heaviest and most\nstore-coupled phase, deliberately placed after the facade (Gateway) and\nthe data seam (State Store) are already proven.\n\nScope, per the PRD's target-services table:\n- Execution Environment: internal/domain/workflow's dispatch paths\n become the execution-dispatch contract, consuming State Store's\n WorkflowStore contract (Phase 2).\n- Runner: internal/container, internal/agentexec, internal/worktree\n become the isolated worktree/container execution service, consuming\n the existing container contract.\n- Scheduler: internal/domain/scheduling + internal/infrastructure/\n cronstore become the cron/ticker contract service.\n\nDepends on Phase 4 (Messaging extraction) per the resolved extraction\norder.\n\nNote: internal/storerpc's NATS path to the archie-agent container is\nexplicitly flagged in question #4's research as an Execution-track\nquestion (\"Migration of the storerpc NATS path... under the PRD the\nExecution/Runner processes are peers too, so the agent's store access\nshould eventually use the same contract\") -- this phase owns deciding\nwhen that moves, not the State Store phase.\n\nFull reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#1\n(Phase 5 section).","acceptance_criteria":"- Execution Environment, Runner, and Scheduler stood up as separable\n services (or a documented decision to combine any of them into one\n binary, if scoping during implementation finds no benefit to a full\n three-way split -- but the contracts must be independently\n addressable).\n- Execution Environment consumes State Store's WorkflowStore contract\n over gRPC rather than importing internal/store directly.\n- The archie-agent container's storerpc NATS access path is either\n migrated onto the same contract-based access or an explicit documented\n decision is recorded for why it stays on NATS for this phase.\n- internal/channels/telegram and other invariants unaffected by this\n phase (container pull policy, NATS JetStream work-queue semantics from\n AGENTS.md remain intact).\n- task check passes; a full task lifecycle (intake -\u003e dispatch -\u003e worktree\n execution -\u003e completion) is exercised end-to-end against the extracted\n services.","status":"open","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T06:06:35Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:06:35Z","dependencies":[{"issue_id":"archie-core-8cda.7","depends_on_id":"archie-core-8cda","type":"parent-child","created_at":"2026-09-05T06:06:35Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-8cda.7","depends_on_id":"archie-core-8cda.6","type":"blocks","created_at":"2026-09-05T06:07:01Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8cda.6","title":"Phase 4: Extract the Messaging Service","description":"Fourth extraction in the resolved order. Telegram/email/webhook adapters\n(internal/channels) become a peer service that calls Gateway's\nChatContract directly -- no UI HTTP detour. Every async channel becomes a\nfirst-class peer, and webui is no longer in any message path (the\nTelegram task-action detour was already closed in Phase 1, but this phase\nmakes Messaging a standalone deployable rather than a package linked into\nthe daemon).\n\nDepends on Phase 3 (UI extraction) per the resolved extraction order.\n\nFull reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#1\n(Phase 4 section) and the PRD's target-services table entry for\nMessaging Service (channel-plugin contract: Telegram, email, Discord,\nTeams, ...).","acceptance_criteria":"- New Messaging Service binary/process hosting the channel-plugin\n contract, wrapping the existing internal/channels adapters (Telegram\n at minimum, per the currently-implemented channel).\n- The Messaging Service calls Gateway's ChatContract directly over gRPC\n for turn dispatch and task actions; no HTTP call into a UI process\n anywhere in the message path.\n- internal/channels/telegram's existing invariants (dropPendingUpdates\n before b.Start, command menu registration to\n default/all_private_chats/all_group_chats) are preserved unchanged in\n the new service.\n- task check passes; a live Telegram round-trip (or equivalent channel\n smoke test) is exercised against the extracted service.","status":"open","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T06:06:23Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:06:23Z","dependencies":[{"issue_id":"archie-core-8cda.6","depends_on_id":"archie-core-8cda","type":"parent-child","created_at":"2026-09-05T06:06:23Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-8cda.6","depends_on_id":"archie-core-8cda.5","type":"blocks","created_at":"2026-09-05T06:07:00Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8cda.5","title":"Phase 3: Extract the UI Service","description":"Third extraction in the resolved order. By this phase UI is finally a\ngenuinely thin client: internal/webui serves the SPA from ui/dist and\ncalls Gateway's ChatContract (Phase 1) and State Store's read contracts\n(Phase 2) instead of holding internal objects or importing internal/store\ndirectly.\n\nThis closes the last verified coupling from the PRD's \"Why this shape\"\nsection: bootstrap.go:1239's shared config.Holder (\"web and the daemon\nmust share ONE Holder\", bootstrap.go:1236, handed to webui at\nbootstrap.go:336). Under this phase each service owns its own\nconfiguration surface -- nothing shares a live in-process struct across a\nservice boundary because there is no longer a shared process for UI.\n\nDepends on Phase 2 (State Store) per the resolved extraction order -- UI\nneeds both ChatContract (Phase 1) and the State Store's read contracts\n(Phase 2) available before it can become a peer rather than an\nin-process consumer.\n\nFull reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#1\n(Phase 3 section) and the PRD's target-services table entry for UI\nService.","acceptance_criteria":"- internal/webui (or a new UI Service binary/process) no longer receives\n the daemon's live config.Holder; it owns its own configuration surface.\n- internal/webui's chat and task paths call Gateway's ChatContract and\n State Store's contracts exclusively -- no remaining direct references\n to gateway.Router/SessionStore/Turns/ModelManager/PersonaRegistry or\n internal/store types.\n- The UI Service can start and serve ui/dist against a remote Gateway and\n State Store with mode = \"remote\" for both contracts.\n- task check and task ui pass; the dashboard's existing pages (tasks,\n logs, health) continue to work end-to-end against the now-remote\n contracts.","status":"open","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T06:06:13Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:06:13Z","dependencies":[{"issue_id":"archie-core-8cda.5","depends_on_id":"archie-core-8cda","type":"parent-child","created_at":"2026-09-05T06:06:13Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-8cda.5","depends_on_id":"archie-core-8cda.4","type":"blocks","created_at":"2026-09-05T06:07:00Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-mlro","title":"ui: extract duplicated Pill component to ui/src/base/","description":"organisation.md's frontend rule says extract to ui/src/base/ on the second distinct consumer. Pill (a 3-line status-badge component) is already independently duplicated verbatim across 11 files: tasks.jsx, logs.jsx, mapping-editor.jsx, capture-row.jsx, settings.jsx, update-status.jsx, skills.jsx, dashboard.jsx, memory.jsx, channels.jsx, curators.jsx. Pre-existing debt, not introduced by any single feature -- found while building the bindings UI (archie-core-t2db.8), which would have been a 12th copy.","design":"Extract to ui/src/base/pill.jsx, export Pill, update all 11+ call sites to import from there instead of defining locally. Mechanical refactor -- no behavior change, verify with task test:ui.","acceptance_criteria":"ui/src/base/pill.jsx exists and exports Pill; all prior local definitions removed, all call sites import the shared one; task test:ui passes unchanged.","status":"closed","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T18:43:54Z","created_by":"Sam Catlow","updated_at":"2026-09-02T20:25:30Z","closed_at":"2026-09-02T20:25:30Z","close_reason":"Extracted to ui/src/base/pill.jsx, all 12 call sites updated (11 pre-existing + bindings). Verified via task test:ui (120/120) and real browser re-check across all pages given this touches the same rendering path as the earlier Preact regression fix. Commit 2abccf3.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-uhtz","title":"skillcurator: nilerr finding at skillcurator.go:110 (pre-existing, unrelated to EDA work)","description":"task check's newly-added lint step (chore(taskfile) 60dde24) surfaced internal/infrastructure/skillcurator/skillcurator.go:110 -- returns nil despite a non-nil error at line 108 (nilerr). This is pre-existing debt, unrelated to any EDA/playbook engine work this session -- different subsystem entirely. Filed separately per this session's established pattern (see archie-core-e7bo) of not drive-by fixing unrelated findings inside an in-progress feature's tickets.","design":"Read the actual code at skillcurator.go:108-110 before fixing -- determine whether swallowing the error there was ever intentional (check git blame/history) or a genuine bug, and fix at the producer per AGENTS.md's Root-Cause Fixes rule rather than just propagating the error blindly if the surrounding contract expects a specific degrade-gracefully shape.","acceptance_criteria":"golangci-lint run ./... reports zero nilerr findings in internal/infrastructure/skillcurator/. Existing skillcurator tests pass; add a test covering the error path if none currently exercises it. task check passes.","status":"closed","priority":3,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-09-02T18:10:22Z","created_by":"Sam Catlow","updated_at":"2026-09-02T18:17:08Z","closed_at":"2026-09-02T18:17:08Z","close_reason":"Investigated per design notes: intentional behavior, not a bug -- confirmed against existing test coverage (skillcurator_test.go's parse-failure-doesn't-abort-batch test). Documented with a scoped nolint explaining why, not a behavior change. Commit pushed to main.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1y6y","title":"Adapt internal/tools/minimax to ai-sdk's video.Provider interface","description":"internal/tools/minimax (the generate_video tool) is a hand-rolled HTTP client (Config/Client/GenerateAndWait against MiniMax's video-generation API) that duplicates functionality ai-sdk already provides generically: video.Provider (Name/GenerateVideo(ctx,req)(resp,error)), core.GenerateVideo, and registry.RegisterVideo/.Video(name) -- the same registration shape chat models and the new image capability use. MiniMax's async submit-then-poll GenerateAndWait fits behind video.Provider's single blocking call fine; nothing about the interface forces synchronous-only backends.\n\nCurrently: not extensible (a second video backend would have to duplicate all the HTTP/poll scaffolding instead of just implementing video.Provider) and not reusable (can't be registered/discovered alongside a future video provider the way chat models and image providers can).\n\nFix: wrap minimax.Client behind an adapter implementing ai-sdk's video.Provider, register it via registry.RegisterVideo instead of the tool holding a bespoke *minimax.Client directly. Keep minimax.Client itself as the low-level HTTP/poll implementation -- only the tool-facing seam changes.","design":"Mirrors the note left on archie-core-1786748942169-3-ae7cfaea for the hosted image provider: adapt ai-sdk's existing provider-agnostic facility instead of a bespoke client. Adapter should preserve GenerateAndWait's polling behavior internally -- video.Provider's synchronous call shape does not require changing MiniMax's async job semantics, only where the polling loop is invoked from.","acceptance_criteria":"minimax.Client (or a thin adapter) implements ai-sdk/video.Provider; the generate_video tool obtains it through the ai-sdk provider registry, not a bespoke config-to-client wiring; existing tests (minimax_test.go, tool_test.go) still pass or are updated for the new seam; task check passes.","status":"open","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T10:36:12Z","created_by":"Sam Catlow","updated_at":"2026-09-02T11:03:52Z","external_ref":"https://github.com/samcharles93/archie-core/issues/681","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-jkmu","title":"send_file confinement is symlink-blind and re-opens the file after checking it","description":"internal/tools/builtin/confinement.go ResolveReadable applies exactly the read tool's policy (resolvePath + isReadConfined), which is purely lexical: filepath.Abs/Rel, never EvalSymlinks. A symlink inside the workspace pointing at /etc/shadow passes the check, and the telegram sender then opens att.Path with no confinement check of its own, in a different goroutine after the turn. There is also a real TOCTOU window -- prepare stats/opens/closes, SendMedia re-stats and re-opens later.\n\nThe policy is unchanged from the read tool, so this is not a new hole; what changed is the consequence. The read tool caps at 5MB into the operator's own context; send_file ships up to 50MB OUT to a chat. The shell tool has never been confined either, so a model that wants the bytes already has them.\n\nDecide: either resolve symlinks in ResolveReadable (which changes read-tool behaviour too, and may break legitimate symlinked workspaces), or document the caveat explicitly and stop claiming 'sending cannot reach what reading cannot' without it.\n\nFound by adversarial review of 9a45fbb.\n\n## Acceptance Criteria\nEither the symlink case is closed at the resolver, or the limitation is written down where the claim is made (confinement.go doc comment and sendfile package doc).","status":"open","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-24T15:54:43Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:55Z","external_ref":"https://github.com/samcharles93/archie-core/issues/647","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw.8","title":"Honor cancellation before local worktree commits","description":"CommitAll discards its context and can stage and commit after task cancellation.\n\nConfirmed still present on main: `Manager.CommitAll` (internal/worktree/worktree.go:387) takes `_ context.Context` and never reads it. Between entry and `wt.Commit` it performs `AddWithOptions{All: true}` and `wt.Commit`, neither of which is context-aware in go-git, so a task cancelled just before the call still mutates the index and HEAD.\n\n## Steps to Reproduce\n\n1. Prepare a task worktree with uncommitted changes.\n2. Create an already-cancelled context: `ctx, cancel := context.WithCancel(context.Background()); cancel()`.\n3. Call `Manager.CommitAll(ctx, dir, \"msg\")`.\n4. Observe it returns `(true, nil)`: the index was staged and a new commit is on HEAD despite the context being cancelled before the call.\n5. In production this leaves a commit on the task branch for work the operator cancelled, which the subsequent push/PR path can then publish.\n\n## Acceptance Criteria\n\nA pre-canceled context causes no index or HEAD mutation; cancellation is checked between non-context-aware go-git phases where possible, with regression tests.\n","acceptance_criteria":"A pre-canceled context causes no index or HEAD mutation; cancellation is checked between non-context-aware go-git phases where possible, with regression tests.","status":"closed","priority":3,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:48Z","created_by":"Sam Catlow","updated_at":"2026-08-24T08:15:48Z","started_at":"2026-08-24T07:42:10Z","closed_at":"2026-08-24T08:15:48Z","close_reason":"Fixed: CommitAll now takes a live context and checks ctx.Err() before open, worktree, staging, status and commit (worktree.go:398-430), so a pre-cancelled context mutates neither index nor HEAD. Proven red against pre-fix code: 'CommitAll() error = nil, want context canceled' for both a cancelled context and an expired deadline. task check green; fresh adversarial review zero findings.","external_ref":"https://github.com/samcharles93/archie-core/issues/603","dependencies":[{"issue_id":"archie-core-1ysw.8","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:47Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-0y4v","title":"agent: markWorktreeSafe checks existence, not mount-ness, so a stale dir writes to the operator's gitconfig","description":"markWorktreeSafe gates on os.Stat (existence and dir-ness), not mount-ness, despite the doc comment claiming a 'mount' check so host-mode agents don't write to the operator's own ~/.gitconfig for a path that was never mounted (commit 6b46ea1's stated purpose). A directory that merely exists at /data/worktree (a stale leftover) satisfies the guard and appends safe.directory=/data/worktree to the operator's gitconfig. Low severity — the entry is inert unless a repo exists at that exact path — but the guard's behavior does not match its documented contract, and the exists-but-not-a-mount case is untested.\n\nFailure: a host-mode agent (local-ollama-standalone.toml) on a machine with a leftover /data directory: an extra safe.directory line appears in the operator's ~/.gitconfig, exactly what the guard claims to prevent.","design":"Either implement a real mount check (e.g. /proc/self/mountinfo on Linux) or correct the doc comment to say the guard is existence-based and accept the (inert) entry. Decide which contract is intended.","acceptance_criteria":"Behavior matches the documented contract; the exists-but-not-mounted case is covered by a test, or the doc is corrected.","status":"closed","priority":3,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:38Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:48:45Z","started_at":"2026-08-14T15:47:55Z","closed_at":"2026-08-14T15:48:45Z","close_reason":"Corrected markSafe's doc comment to match its actual existence-based (not mount-based) check; pinned the exists-but-unmounted case with a new test rather than adding platform-specific mount detection for an inert failure mode. Committed f1d74ab.","external_ref":"https://github.com/samcharles93/archie-core/issues/494","labels":["agent","code-review"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8cda.8","title":"Phase 6: Curator Service (optional, last)","description":"Sixth and final phase in the resolved extraction order -- deliberately\nlast, since it is the proof-of-optionality exercise (open question #5),\nnot a load-bearing step for the base fleet.\n\nScope: internal/domain/curator installs as a Gateway plugin (its current\nshape is already a contract/registrar/registry family per the PRD's\ntarget-services table). This phase proves the optional-service\nNotInstalled discovery semantic end to end: an optional service that is\nnot installed must resolve to a distinct NotInstalled outcome, never a\nDown/Unhealthy one (per the ServiceRegistry design in\ndocs/inspiration/service-discovery-research-2026-09-05.md and\ninternal/servicediscovery/servicediscovery.go's ErrNotInstalled).\n\nThe K8s Operator to *deploy* Curator (CRD, controller, RBAC, the\narchie-curator Helm chart) is open question #5's scoping concern and can\nbe built against this phase's contract once it lands -- see the\nresolved-question research's own suggested first issue breakdown\n(Kubebuilder scaffold, reconciler, archie-library chart, archie chart,\nServiceRegistry K8s resolver NotInstalled semantics, end-to-end M1\nassertion) for how that follow-on work should be filed once this phase's\ncontract is settled.\n\nDepends on Phase 5 (Execution/Runner/Scheduler) per the resolved\nextraction order.\n\nFull reasoning: docs/inspiration/service-decomposition-open-questions-research-2026-09-05.md#1\n(Phase 6 section) and #5 (Helm chart / Operator scoping, M1 milestone).","acceptance_criteria":"- Curator Service exposes a curator contract (proto + generated Go) and\n installs as an optional Gateway plugin, following the same\n local-adapter + gRPC-adapter + conformance-suite shape as prior phases.\n- ServiceRegistry.Resolve/Watch for \"curator\" returns a distinct\n NotInstalled outcome (not Down/Unhealthy) when Curator is not\n installed, verified by a test.\n- Installing/uninstalling the Curator Service flips its discovery state\n without requiring a Gateway restart or redeploy (mirrors question #5's\n M1 milestone assertion, even if the K8s Operator itself is filed as\n separate follow-on work).\n- task check passes; existing Curator functionality (whatever\n internal/domain/curator provides today) is preserved through the\n contract boundary.","status":"open","priority":4,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-05T06:06:49Z","created_by":"Sam Catlow","updated_at":"2026-09-05T06:06:49Z","dependencies":[{"issue_id":"archie-core-8cda.8","depends_on_id":"archie-core-8cda","type":"parent-child","created_at":"2026-09-05T06:06:49Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-8cda.8","depends_on_id":"archie-core-8cda.7","type":"blocks","created_at":"2026-09-05T06:07:01Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-3svc","title":"Concurrent send_file uploads in one turn are uncapped","description":"liveReply.Media starts an unbounded mediaWg.Go per attachment. Not a leak (each is bounded by a 30s ctx) and not a memory problem (go-telegram streams via io.Pipe, nothing is buffered), but N send_file calls in one turn start N concurrent multipart uploads against a rate-limited API.\n\nAlso noted: send_file is ClassIdempotent, which makes it ExecParallelSafe. Defensible since the tool only validates and never sends, but minimax is ClassMutating for an equivalent 'produces an outbound artifact' tool -- worth deciding deliberately rather than by accident.\n\nFound by adversarial review of 9a45fbb. internal/channels/telegram/live.go:386.\n\n## Acceptance Criteria\nEither a bound on concurrent media sends per reply, or a recorded decision that the 30s timeout plus Telegram's own rate limiting is sufficient.","status":"open","priority":4,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-08-24T15:54:51Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:56Z","external_ref":"https://github.com/samcharles93/archie-core/issues/648","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-52f7","title":"telegram: the live-edit answer keeps its turn-start timestamp and can sort before the conversation","description":"The final reply is delivered by editing the message created at the first streamed frame, and editMessageText does not change the message date — so a long tool-using turn's answer is timestamped at turn start, can predate messages sent during the turn, and sorts before the conversation that produced it. Cosmetic and inherent to the watch-the-answer-being-written design (delete-and-resend would flicker and reorder), but it is a visible consequence nothing documents or tests.\n\nFailure: a turn with a two-minute tool phase produces an answer whose timestamp precedes a follow-up user message that references it; chat history ordering places the answer before the conversation that produced it.","design":"Either accept and document the limitation (a comment on liveReply/finalize), or investigate a delete-and-resend on finalize for turns that cross a meaningful time gap. Low priority; a documentation note may be the right fix.","acceptance_criteria":"The timestamp behavior is at least documented (or changed and tested), so it is a known trade-off rather than a surprise.","status":"closed","priority":4,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-14T14:43:38Z","created_by":"Sam Catlow","updated_at":"2026-08-14T15:48:45Z","started_at":"2026-08-14T15:46:50Z","closed_at":"2026-08-14T15:48:45Z","close_reason":"Documented the accepted trade-off on liveReply's doc comment per the design note's preferred option; no behavior change. Committed ed18bfb.","external_ref":"https://github.com/samcharles93/archie-core/issues/495","labels":["code-review","streaming","telegram"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
@@ -45,3 +45,5 @@ node_modules/
|
||||
# Impeccable design-tool scratch/critique snapshots (usable by $impeccable polish, never committed)
|
||||
.impeccable/
|
||||
.serena/
|
||||
.beads/issues.jsonl
|
||||
.beads/interactions.jsonl
|
||||
@@ -236,15 +236,22 @@ bd remember # Persist cross-session architectural facts
|
||||
- Run `bd prime` to inspect full engine context.
|
||||
- Use `bd remember` for knowledge retention. Do not write to root `MEMORY.md`
|
||||
files.
|
||||
- Issues live in a local Dolt DB; `.beads/issues.jsonl` is an export.
|
||||
- Issues live in a local Dolt DB, synced to its own `git+` remote via
|
||||
`bd dolt push`/`bd dolt pull`. `.beads/issues.jsonl` and
|
||||
`.beads/interactions.jsonl` are local-only export/audit files
|
||||
(`.gitignore`d, `export.auto: false`) -- never `git add` them and never
|
||||
create a commit whose only content is beads bookkeeping. Bead state moves
|
||||
through Dolt, not through git commits on this repo.
|
||||
|
||||
## Session Completion Protocol
|
||||
|
||||
1. **Log remaining work:** File new items via `bd` for identified debt or
|
||||
follow-up tasks.
|
||||
2. **Run gate:** Verify `task check` passes completely clean.
|
||||
3. **Update tracker:** Close finished issues via `bd close <id>`.
|
||||
4. **Commit:**
|
||||
3. **Update tracker:** Close finished issues via `bd close <id>`. This alone
|
||||
is not commit-worthy -- do not stage or commit `.beads/` for it.
|
||||
4. **Commit:** Only for actual code/doc changes, scoped to the files that
|
||||
changed.
|
||||
|
||||
```bash
|
||||
git add <scoped-files>
|
||||
|
||||
Reference in new issue
Block a user