From 9ed5f57ccbadf855145d3947aa1e29a02f80c969 Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Thu, 3 Sep 2026 00:55:50 +1000 Subject: [PATCH] chore: mark completed issues and epics as closed --- .beads/interactions.jsonl | 4 ++++ .beads/issues.jsonl | 14 +++++++------- 2 files changed, 11 insertions(+), 7 deletions(-) diff --git a/.beads/interactions.jsonl b/.beads/interactions.jsonl index 37c156310..e238fd420 100644 --- a/.beads/interactions.jsonl +++ b/.beads/interactions.jsonl @@ -184,3 +184,7 @@ {"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"}} diff --git a/.beads/issues.jsonl b/.beads/issues.jsonl index ca539691b..1bdd4d0a9 100644 --- a/.beads/issues.jsonl +++ b/.beads/issues.jsonl @@ -91,12 +91,12 @@ {"_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-v9gv.2","title":"Refactor hyperscript el() usage to Preact JSX","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T13:37:19Z","created_by":"Sam Catlow","updated_at":"2026-09-02T13:37:19Z","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":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T13:37:19Z","created_by":"Sam Catlow","updated_at":"2026-09-02T13:37:19Z","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":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-09-02T13:37:18Z","created_by":"Sam Catlow","updated_at":"2026-09-02T13:37:18Z","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":"open","priority":2,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-09-02T13:37:08Z","created_by":"Sam Catlow","updated_at":"2026-09-02T13:37:08Z","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:24:02Z","closed_at":"2026-09-02T14:24:02Z","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:24:03Z","closed_at":"2026-09-02T14:24:03Z","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:24:01Z","closed_at":"2026-09-02T14:24:01Z","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:24:11Z","closed_at":"2026-09-02T14:24:11Z","close_reason":"All children completed","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/ (three-file split: bindings.js, binding-editor.js, bindings.css per docs/prds/payload-field-mapping.md:145-152): source matcher, mapping picker, workflow picker, secret input, state-machine controls (create -\u003e edit -\u003e approve -\u003e armed). Also add binding.Owner / binding.Repo fields so multi-repo deployments have a UI to pin a binding to one repo (today the dispatch loop falls back to the single configured repo with a warning; multi-repo is broken). See docs/prds/webhook-intake-security.md and docs/prds/payload-field-mapping.md.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-09-02T13:24:13Z","created_by":"Sam Catlow","updated_at":"2026-09-02T13:24:13Z","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":0,"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":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-09-02T13:24:12Z","created_by":"Sam Catlow","updated_at":"2026-09-02T13:24:12Z","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-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-02T13:55:47Z","closed_at":"2026-09-02T13:55:47Z","close_reason":"Closed","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-02T12:34:55Z","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.","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-02T12:21:10Z","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-02T12:23:52Z","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.","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} @@ -214,7 +214,7 @@ {"_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":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:59:10Z","updated_at":"2026-09-01T17:09:33Z","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-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} @@ -272,7 +272,7 @@ {"_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":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:54:47Z","updated_at":"2026-08-08T14:54:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/377","source_system":"github:https://github.com/samcharles93/archie-core/issues/377:377","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-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}