chore(beads): note builtin engine progress
This commit is contained in:
1 parent
7b39f7bd0c
commit
4252897fa8
1 file changed
+2
-2
+2
-2
@@ -238,7 +238,7 @@
|
||||
{"_type":"issue","id":"archie-core-1786637499562-373-11ad6000","title":"fix(nell): counters squat on the SDK-reserved meta: prefix, blocking all writes after restart","description":"TOTAL OUTAGE. No task can be queued and no event recorded; survives restarts.\n\ninternal/nell/adapter.go:946,952 store auto-increment counters at meta:task_id_counter and meta:event_id_counter. The NellDB SDK reserves the meta: prefix for its own bookkeeping (sdk/replicate.go:841 isInternalID = id[:5]==\"meta:\").\n\nDocDB.reindex() skips internal ids when rebuilding the in-memory rev cache (sdk/docdb.go:128-137), but the record stays in the log. So after a restart Get returns the counter doc WITH its _rev while d.revs has no entry, and putIn rejects exactly that: 'incomingRev != \"\" \u0026\u0026 !exists' -\u003e ErrConflict (sdk/docdb.go:213-217). Permanent.\n\nHits nextTaskID (every EnqueueIssue) and nextEventID (every InsertEvent). processNATSTask Naks on error so NATS redelivers forever.\n\nReproduced: internal/nell/counter_repro_test.go - open, insert, close, reopen, insert -\u003e ErrConflict in 7ms with no daemon/NATS/forge.\n\nSECOND DEFECT: isInternalID exists to exclude records from replication, so the two carina instances never converge their counters and would allocate COLLIDING task IDs. Masked only because allocation currently fails outright.\n\nFIX: move the keys out of the reserved namespace (counter:task_id / counter:event_id) AND migrate on open - the old doc is readable (only Put fails), and its next_id is load-bearing because restarting at 1 would reissue live task IDs. Also teach isMetaKey (adapter.go:803) to skip the new prefix so scans do not parse a counter as a task.\n\nREJECTED: stripping _rev before Put is one line and works, but leaves the prefix squat, leaves counters unreplicated, and turns a loud failure into silent last-write-wins.\n\nFull writeup: docs/incident-nelldb-counter-conflict.md","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-08-08T14:56:07Z","updated_at":"2026-08-08T14:56:09Z","closed_at":"2026-08-08T14:56:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/394","source_system":"github:https://github.com/samcharles93/archie-core/issues/394:394","metadata":null,"labels":["bug"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499539-372-295c7dd9","title":"Simplify Telegram model command surface","description":"Remove the redundant /models command from Telegram's published and executable command surface; retain /model selector. Make /help menu copy useful rather than self-referential.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:56:02Z","updated_at":"2026-08-08T14:56:04Z","closed_at":"2026-08-08T14:56:05Z","external_ref":"https://github.com/samcharles93/archie-core/issues/393","source_system":"github:https://github.com/samcharles93/archie-core/issues/393:393","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499513-371-52235c61","title":"Consolidate 6 duplicated Yaegi interpreter bootstraps","description":"internal/gate/gateeval/yaegi.go, internal/workflow/wfeval/yaegi.go, internal/workflow/skillbuild/skillbuild.go, internal/skillscript/yaegi.go, internal/plugin/plugin.go, internal/skill/plugin.go each hand-roll interp.New/i.Use(stdlib.Symbols)/panic-recovery. Extract a shared helper (new package, e.g. internal/yaegiutil) for interpreter construction + panic-safe eval, used by all six.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:55:56Z","updated_at":"2026-08-08T14:55:59Z","closed_at":"2026-08-08T14:56:00Z","external_ref":"https://github.com/samcharles93/archie-core/issues/392","source_system":"github:https://github.com/samcharles93/archie-core/issues/392:392","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1786637499480-370-223df308","title":"Ship the file-writing store as the default memory engine","description":"Reframe internal/memory/builtin as the reference engine implementation behind the new contract, so the standard install keeps writing memories to files with no configuration and no behaviour change.\n\n### Acceptance Criteria\n\nThe builtin store implements the engine contract and registers as the default. A config that names no memory engine behaves exactly as today, verified by existing internal/memory tests continuing to pass unmodified where they assert behaviour rather than structure. Its lifecycle methods are real or explicit no-ops, not stubs that silently do nothing surprising.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:55:53Z","updated_at":"2026-08-08T14:55:53Z","external_ref":"https://github.com/samcharles93/archie-core/issues/391","source_system":"github:https://github.com/samcharles93/archie-core/issues/391:391","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-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":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:55:53Z","updated_at":"2026-09-01T16:36:27Z","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}
|
||||
@@ -600,7 +600,7 @@
|
||||
{"_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":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:26:51Z","updated_at":"2026-08-08T14:31:57Z","external_ref":"https://github.com/samcharles93/archie-core/issues/31","source_system":"github:https://github.com/samcharles93/archie-core/issues/31:31","metadata":null,"labels":["enhancement"],"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"],"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}
|
||||
|
||||
Reference in new issue
Block a user