|
|
|
@@ -53,6 +53,16 @@
|
|
|
|
|
{"_type":"issue","id":"archie-core-abg.18","title":"[EPIC] Memory: pluggable provider architecture with file-backed persistence","description":"Pluggable memory system to match Hermes parity:\\n\\n1. **MemoryProvider interface**: Abstract interface with methods for initialize(), get_tool_schemas(), prefetch(), sync_turn(), and optional lifecycle hooks (on_session_end, on_session_switch, on_pre_compress, on_memory_write).\\n\\n2. **Built-in file-backed memory**: MEMORY.md and USER.md stored per-session/profile. LLM-callable memory tool with add/replace/remove actions. Frozen snapshot at session start (preserves prefix cache), immediate disk write on updates. Section-sign delimited entries with substring matching.\\n\\n3. **MemoryManager**: Orchestrates built-in + at most one external provider. Background serialized write executor. Prefetch with timeout (8s). Streaming context scrubber that strips injected memory spans from model output.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 4","acceptance_criteria":"An external memory provider (e.g. Honcho, Mem0) can be plugged in via config. The built-in memory tool persists across sessions. Conversation context is recalled on session resume.","status":"open","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-25T14:02:22Z","created_by":"Sam Catlow","updated_at":"2026-07-25T14:02:22Z","dependencies":[{"issue_id":"archie-core-abg.18","depends_on_id":"archie-core-abg","type":"parent-child","created_at":"2026-07-26T00:02:22Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-abg.16","title":"[EPIC] Gateway: rich message model, adapter lifecycle, session management","description":"Foundational gateway infrastructure to match Hermes parity. Three interdependent pieces:\\n\\n1. **Message model**: Replace the 3-field Message struct with a rich MessageEvent (MessageType enum: text/photo/video/audio/voice/document/sticker/command, media_urls, reply_to context, metadata dict, source). This is the wire type every adapter produces.\\n\\n2. **Adapter lifecycle**: Replace the 3-method Gateway interface with a BasePlatformAdapter interface: connect()/disconnect()/send() as required methods, plus optional overrides for typing indicators, edit/delete, image/voice/video/document send, interactive UX (clarify buttons, approval dialogs). Capability flags (supports_code_blocks, splits_long_messages, supports_async_delivery).\\n\\n3. **Session management**: SessionSource struct (platform, chat_id, chat_type, user_id, thread_id, guild_id, profile), AsyncSessionStore for persistent session storage, SessionContext for system prompt injection.\\n\\nAll three blocks together enable adding new platforms as plugins without touching core gateway code.\\n\\nRef: docs/prds/hermes-gap-analysis.md sections 1-2","acceptance_criteria":"New adapters can be added by implementing a Go interface with connect/disconnect/send + optional media methods. Messages carry full metadata through the pipeline. Sessions persist across gateway restarts.","status":"open","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-25T14:02:21Z","created_by":"Sam Catlow","updated_at":"2026-07-25T14:02:21Z","dependencies":[{"issue_id":"archie-core-abg.16","depends_on_id":"archie-core-abg","type":"parent-child","created_at":"2026-07-26T00:02:21Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-jfg","title":"Spawned archie-agent containers not on daemon's docker network — can't reach NATS","description":"Root cause of 'agent still failing on the server': archied's container.Pool.Acquire creates archie-agent containers via the Docker SDK with no NetworkMode set, so Docker attaches them to the default bridge network. archied and nats run on the compose-created 'archie-core_default' network instead, so the spawned container's hostname resolution for 'nats' (from NATS_URL=nats://nats:4222) fails and archie-agent can't connect. Confirmed on carina host logs: archied logs show repeating 'taskrun request failed err=\"nats: no responders available for request\"' for every task, containers created and destroyed within ~1.5s (consistent with archie-agent's NATS client failing fast). Fixed by detecting the daemon's own container's network in NewPool (selfNetwork, via ContainerInspect on os.Hostname()) and setting HostConfig.NetworkMode on spawned containers to match.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-24T03:10:26Z","created_by":"Sam Catlow","updated_at":"2026-07-25T13:04:34Z","closed_at":"2026-07-25T13:04:34Z","close_reason":"Fix already implemented and verified: selfNetwork() in internal/container/pool.go detects the daemon's own container network via ContainerInspect(os.Hostname()) and Acquire() sets HostConfig.NetworkMode to match, so spawned archie-agent containers join the same compose network as nats. Build and internal/container tests pass.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-sc5","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":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-27T12:14:08Z","created_by":"Sam Catlow","updated_at":"2026-07-27T12:14:08Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-qnm","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.","acceptance_criteria":"Telegram 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":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-27T09:00:56Z","created_by":"Sam Catlow","updated_at":"2026-07-27T09:00:56Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-alm.6","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.","acceptance_criteria":"For 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":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-27T08:59:54Z","created_by":"Sam Catlow","updated_at":"2026-07-27T09:01:52Z","dependencies":[{"issue_id":"archie-core-alm.6","depends_on_id":"archie-core-alm","type":"parent-child","created_at":"2026-07-27T18:59:53Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-alm.4","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.","acceptance_criteria":"/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":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-27T08:59:53Z","created_by":"Sam Catlow","updated_at":"2026-07-27T08:59:53Z","dependencies":[{"issue_id":"archie-core-alm.4","depends_on_id":"archie-core-alm","type":"parent-child","created_at":"2026-07-27T18:59:52Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-alm.5","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.","acceptance_criteria":"Every 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":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-27T08:59:53Z","created_by":"Sam Catlow","updated_at":"2026-07-27T08:59:53Z","dependencies":[{"issue_id":"archie-core-alm.5","depends_on_id":"archie-core-alm","type":"parent-child","created_at":"2026-07-27T18:59:53Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-alm.1","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.","acceptance_criteria":"Semantics 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":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-27T08:56:49Z","created_by":"Sam Catlow","updated_at":"2026-07-27T08:59:52Z","dependencies":[{"issue_id":"archie-core-alm.1","depends_on_id":"archie-core-alm","type":"parent-child","created_at":"2026-07-27T18:56:48Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-alm.2","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.","acceptance_criteria":"Each command accurately reports or navigates Archie-owned state; session listing/resume is safe and scoped; output/menu/help/tests are complete.","status":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-27T08:56:49Z","created_by":"Sam Catlow","updated_at":"2026-07-27T08:59:52Z","dependencies":[{"issue_id":"archie-core-alm.2","depends_on_id":"archie-core-alm","type":"parent-child","created_at":"2026-07-27T18:56:49Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-alm","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.","acceptance_criteria":"Command 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":1,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-27T08:56:36Z","created_by":"Sam Catlow","updated_at":"2026-07-27T08:56:36Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-ku8","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.","acceptance_criteria":"/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":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-27T08:42:54Z","created_by":"Sam Catlow","updated_at":"2026-07-27T08:51:34Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-0zp","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.","acceptance_criteria":"Interview 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":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-27T07:21:54Z","created_by":"Sam Catlow","updated_at":"2026-07-27T07:21:54Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-3ro","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.","acceptance_criteria":"Telegram 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":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-26T20:24:07Z","created_by":"Sam Catlow","updated_at":"2026-07-26T20:33:10Z","started_at":"2026-07-26T20:24:08Z","closed_at":"2026-07-26T20:33:10Z","close_reason":"Shipped locally: Telegram calls the assistant Archie rather than Gateway; restart copy is Archie-facing; new sessions receive and preserve an Archie baseline identity; model selector shows provider in the header and provider-free model names; successful selections acknowledge the chosen model; model/provider callbacks use stable tokens so stale keyboards cannot select a different option. task check and lint pass; fresh review clean.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-ubl","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.","acceptance_criteria":"Schedules 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":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-26T20:05:57Z","created_by":"Sam Catlow","updated_at":"2026-07-26T20:05:57Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-4sr","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.","acceptance_criteria":"Any 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":"in_progress","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-26T19:55:37Z","created_by":"Sam Catlow","updated_at":"2026-07-26T19:55:41Z","started_at":"2026-07-26T19:55:41Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
@@ -127,6 +137,8 @@
|
|
|
|
|
{"_type":"issue","id":"archie-core-s1r","title":"Test forge fakes missing LinkBranch method broke go vet/test for whole module","description":"forge.Forge gained LinkBranch(ctx, owner, repo, issueNumber, branch) error in the branch-linking feature (ff4c51e) but the hand-rolled test doubles (stubForge in cmd/archied/main_test.go, prCapturingForge in cmd/archie-agent/taskrun_test.go, testForge in internal/daemon/daemon_test.go, fakeForge in internal/forgerpc/forgerpc_test.go) never got the method added, so they stopped satisfying forge.Forge. This broke go vet ./... and go test ./... for the entire module, not just those 4 packages, since go vet type-checks all test files as part of module vet. Fixed by adding LinkBranch stubs to all four fakes.","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-24T03:04:53Z","created_by":"Sam Catlow","updated_at":"2026-07-24T03:04:58Z","closed_at":"2026-07-24T03:04:58Z","close_reason":"Added LinkBranch stub methods to stubForge, prCapturingForge, testForge, and fakeForge. go build/vet/test ./... now clean across the whole module.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-633","title":"config.docker.toml missing required fields, no overlay merge implemented","description":"config.docker.toml was rewritten to be a docs-as-overlay file (comment says base+overlay merge) but internal/config.Load has no merge logic and docker-compose.yml mounts only config.docker.toml at /etc/archie/config.toml. It is missing bot_user, [forge], [dispatch], [models], [providers], [budgets] which Load requires -\u003e daemon fails to start in docker as currently configured. Implement real base+overlay config loading (or restore a full standalone docker config) so there is one source of truth.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-24T02:42:07Z","created_by":"Sam Catlow","updated_at":"2026-07-24T02:44:53Z","started_at":"2026-07-24T02:42:11Z","closed_at":"2026-07-24T02:44:53Z","close_reason":"Implemented config.LoadOverlay (base decode + overlay decode into same struct, then shared finalize/validate), wired -config-overlay flag in cmd/archied, fixed docker-compose.yml to mount both base config.toml and config.docker.toml overlay, minimized config.docker.toml to true diff-only overlay, added tests proving overlay-omitted required fields (bot_user, repos) still come from base.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-u64","title":"Daemon: process multiple tasks concurrently (max_concurrency enforcement)","description":"Daemon currently processes one task at a time (docs/prds/archie-core-v2-architecture.md Phase 2). This is the core blocker between current state and any multi-agent scaling mode — needed before container max_concurrency or same-repo concurrency can matter. Wire the daemon's dispatch loop to run N tasks in parallel, respecting a configurable max_concurrency.","design":"internal/container/pool.go already enforces max_concurrency for container lifecycle — reuse that limit/pattern in the daemon's task dispatch rather than inventing a second concurrency control.","acceptance_criteria":"Daemon dispatch loop runs multiple tasks concurrently up to a configured max_concurrency limit; single-task-at-a-time behavior is gone.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-23T19:36:31Z","created_by":"Sam Catlow","updated_at":"2026-07-23T21:37:42Z","started_at":"2026-07-23T21:29:41Z","closed_at":"2026-07-23T21:37:42Z","close_reason":"Implemented concurrent SQLite and NATS task dispatch using containers.max_concurrency, with default same-repo serialization and race-tested dispatcher coverage.","dependency_count":0,"dependent_count":2,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-5dn","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","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-27T12:09:56Z","created_by":"Sam Catlow","updated_at":"2026-07-27T12:11:14Z","started_at":"2026-07-27T12:10:00Z","closed_at":"2026-07-27T12:11:14Z","close_reason":"Investigated local Hermes CLI and current Archie implementation; added the requested parity TODO checklist.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-alm.3","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.","acceptance_criteria":"Blocked 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","owner":"sam@catlow.tech","created_at":"2026-07-27T08:56:50Z","created_by":"Sam Catlow","updated_at":"2026-07-27T08:56:50Z","dependencies":[{"issue_id":"archie-core-alm.3","depends_on_id":"archie-core-alm","type":"parent-child","created_at":"2026-07-27T18:56:49Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-rqp.1","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","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-27T02:50:47Z","created_by":"Sam Catlow","updated_at":"2026-07-27T02:53:56Z","started_at":"2026-07-27T02:50:48Z","closed_at":"2026-07-27T02:53:56Z","close_reason":"Shipped: authorized /version reports installed gateway and runtime build versions from the composition root; menu/help parity covered; task check and scoped lint clean; fresh review found no blocking issues.","dependencies":[{"issue_id":"archie-core-rqp.1","depends_on_id":"archie-core-rqp","type":"parent-child","created_at":"2026-07-27T12:50:46Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-n55","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","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-27T01:41:43Z","created_by":"Sam Catlow","updated_at":"2026-07-27T01:44:06Z","started_at":"2026-07-27T01:41:50Z","closed_at":"2026-07-27T01:44:06Z","close_reason":"Shipped locally: /models removed from Telegram menu, help, and Router; /model is the sole model selector/direct-switch command; /help menu text is now 'See what Archie can do'; command docs updated. task check passes and fresh review reports no findings.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|
{"_type":"issue","id":"archie-core-rqp","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.","acceptance_criteria":"/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","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-26T19:47:21Z","created_by":"Sam Catlow","updated_at":"2026-07-27T03:02:11Z","started_at":"2026-07-27T02:49:27Z","closed_at":"2026-07-27T03:02:11Z","close_reason":"Shipped: deployment-neutral /update with configured argv check/install adapters, gateway/runtime release sections, per-user exact-version persisted deferrals, recipient-bound expiring single-use callback actions, global install serialization, callback authorization, and truthful progress/failure. Webhook callback queries enabled. task check and scoped lint clean; adversarial review findings remediated.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
|
|
|
|