chore(beads): record task observability work
This commit is contained in:
1 parent
4b340d2b56
commit
d8478e1a4d
2 files changed
+10
-1
No files matched your search
@@ -131,3 +131,7 @@
|
||||
{"id":"int-084477087493b06c289d87dfc319c6d3","kind":"field_change","created_at":"2026-08-24T17:19:41.96078947Z","actor":"Sam Catlow","issue_id":"archie-core-y1hv","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented, regression-tested, full task check passed, and adversarial review finding resolved."}}
|
||||
{"id":"int-9de2b83189f32eec56dd588dd4b1c439","kind":"field_change","created_at":"2026-08-24T17:28:38.936618176Z","actor":"Sam Catlow","issue_id":"archie-core-15iq","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented with regression coverage, full task check passing, and adversarial review clean."}}
|
||||
{"id":"int-45a964f90a687ff51f5d7678683f2706","kind":"field_change","created_at":"2026-08-24T17:28:38.999458853Z","actor":"Sam Catlow","issue_id":"archie-core-473l","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Implemented with regression coverage, full task check passing, and adversarial review clean."}}
|
||||
{"id":"int-208089f7a06402742d9c8765472ed479","kind":"field_change","created_at":"2026-08-24T17:55:34.430893806Z","actor":"Sam Catlow","issue_id":"archie-core-jy5m","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Task timelines now render stage/retry context; baseline and gate-cycle logs expose useful bounded failure output. task check and independent review pass."}}
|
||||
{"id":"int-196298a33f71370a0a0c538590985b53","kind":"field_change","created_at":"2026-08-24T19:48:32.993325535Z","actor":"Sam Catlow","issue_id":"archie-core-n5sr","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Provider usage is durable by stage, baseline repair is included, model-adaptive compaction is enabled without a token cap, and ai-sdk preserves partial/compaction usage. task check and fresh adversarial review pass."}}
|
||||
{"id":"int-574291f5bd917eaf7b78056b15abffcb","kind":"field_change","created_at":"2026-08-24T19:48:34.38833081Z","actor":"Sam Catlow","issue_id":"archie-core-nq0c","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Commit identity now crosses the task boundary, per-identity email defaults are derived when omitted, and the worker end-to-end test verifies author and committer. task check and fresh adversarial review pass."}}
|
||||
{"id":"int-b91d5f4013ec1fde90a34b440e87b986","kind":"field_change","created_at":"2026-08-24T19:48:34.825217514Z","actor":"Sam Catlow","issue_id":"archie-core-z0u8","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"The API now supplies canonical per-task GitHub or Gitea URLs and the dashboard consumes them directly. Regression coverage, task check, and fresh adversarial review pass."}}
|
||||
+6
-1
@@ -1,3 +1,5 @@
|
||||
{"_type":"issue","id":"archie-core-n5sr","title":"Measure and reduce task-agent context amplification","description":"PR #635 consumed at least 1,286,449 tokens across baseline repair, analysis, repro, and fix, while the PR footer reported only 997,900. Do not impose a hard token stop: successful and failed tasks are evaluation evidence. Measure prompt/completion/cached usage by stage and iteration, include every agent stage in task totals, enable adaptive history compaction, and bound redundant tool-result replay so task completion remains the authority while efficiency becomes observable and improvable.","acceptance_criteria":"Task telemetry attributes prompt, completion, cached, total tokens and iterations by workflow stage; baseline-repair usage is included in task totals; task agents compact redundant accumulated history without imposing a token stop; successful and failed tasks remain comparable; regression coverage and quality gate pass.","notes":"Maintainer decision: max_tokens is not desired as a blocker. Optimize context economics and preserve outcomes as metrics.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:58:59Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:48:33Z","started_at":"2026-08-24T18:02:41Z","closed_at":"2026-08-24T19:48:33Z","close_reason":"Provider usage is durable by stage, baseline repair is included, model-adaptive compaction is enabled without a token cap, and ai-sdk preserves partial/compaction usage. task check and fresh adversarial review pass.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-nq0c","title":"Preserve Git author identity in sandboxed task commits","description":"PR #635 contains three commits with empty author and committer names/emails despite configured bot_user and the documented GitHub noreply default. Trace and preserve commit identity across the daemon-worker boundary.","acceptance_criteria":"Sandboxed task commits carry configured/defaulted author and committer name/email; regression covers the live RPC/local commit composition; quality gate passes.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T17:58:58Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:48:34Z","closed_at":"2026-08-24T19:48:34Z","close_reason":"Commit identity now crosses the task boundary, per-identity email defaults are derived when omitted, and the worker end-to-end test verifies author and committer. task check and fresh adversarial review pass.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-473l","title":"Reconcile task clone ownership after container commits","description":"Agent containers write Git objects as root into bind-mounted task clones, while ownership is currently repaired only before push. A stopped or failed workflow before push leaves unreadable objects and makes the next host-side worktree prepare fail instantly. Reconcile ownership after every CommitAll result as well as before push.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:24:57Z","created_by":"Sam Catlow","updated_at":"2026-08-24T17:28:39Z","started_at":"2026-08-24T17:25:30Z","closed_at":"2026-08-24T17:28:39Z","close_reason":"Implemented with regression coverage, full task check passing, and adversarial review clean.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-15iq","title":"Make UUIDv7 session references distinguishable","description":"UUIDv7 session IDs created close together share their first eight characters, making displayed chat session references unusable and allowing /topic to select the wrong first prefix match. Surface a sufficiently distinguishing shorthand and resolve topic references unambiguously.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:20:49Z","created_by":"Sam Catlow","updated_at":"2026-08-24T17:28:39Z","started_at":"2026-08-24T17:20:53Z","closed_at":"2026-08-24T17:28:39Z","close_reason":"Implemented with regression coverage, full task check passing, and adversarial review clean.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-4tye","title":"Install updates without requiring a source checkout","description":"Make the automatic updater fetch approved release source into an invocation-scoped temporary clone, build and install the binary from that source, and never require or mutate an operator or agent checkout.","status":"closed","priority":0,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:11:05Z","created_by":"Sam Catlow","updated_at":"2026-08-24T17:19:42Z","started_at":"2026-08-24T17:11:11Z","closed_at":"2026-08-24T17:19:42Z","close_reason":"Implemented, regression-tested, full task check passed, and adversarial review finding resolved.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
@@ -7,6 +9,8 @@
|
||||
{"_type":"issue","id":"archie-core-1ysw.1","title":"Bind worktree RPC operations to the dispatched task","description":"The sandboxed agent can currently choose owner, repo, issue, base, and branch on worktree RPC requests. The daemon then performs host deletion and credentialed forge operations without correlating the request to the dispatched task or enforcing WorkDir containment.","acceptance_criteria":"Reject traversal and unconfigured or task-mismatched coordinates before any filesystem or forge side effect; derive or validate the permitted branch; regression tests fail on the old behavior and pass on the fix.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:43Z","created_by":"Sam Catlow","updated_at":"2026-08-24T06:59:58Z","started_at":"2026-08-22T11:02:03Z","closed_at":"2026-08-24T06:59:58Z","close_reason":"Fixed on main: worktreerpc now exposes only Push, authorized by an opaque per-dispatch grant issued from the dispatched *store.Task (worktreerpc.go:71-83). Sandbox input no longer selects host path, repo or branch; ValidCoordinates rejects traversal. Package tests pass.","external_ref":"https://github.com/samcharles93/archie-core/issues/589","metadata":null,"dependencies":[{"issue_id":"archie-core-1ysw.1","depends_on_id":"archie-core-1ysw","type":"parent-child","created_at":"2026-08-22T21:01:42Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1ysw","title":"Repair internal/worktree correctness and trust-boundary defects","description":"Track the concrete worktree-package defects proven by the 2026-08-22 evidence-gated review. Child bugs cover RPC authority/path containment, repository-key isolation, retry/base/diff correctness, push lifecycle, terminal cleanup, cancellation, and branch naming. This epic groups implementation only; each child has its own observable acceptance criteria.","acceptance_criteria":"All child bugs are closed with red-green regression tests, scoped lint passes, and the repository quality gate is clean.","status":"closed","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-08-22T11:01:18Z","created_by":"Sam Catlow","updated_at":"2026-08-24T08:16:00Z","closed_at":"2026-08-24T08:16:00Z","close_reason":"All 9 children complete. The P0/P1 trust-boundary and correctness defects (.1 RPC task binding, .2 colliding directory keys, .3 untracked cleanup, .4 fail-closed base resolution, .5 three-dot merge-base semantics) were already fixed on main and reconciled 2026-08-24. The remaining four (.6 push result, .7 no-change worktree leak, .8 commit cancellation, .9 branch naming contract) were implemented this session, merged as 474c31d and its two merge commits, task check green, with an independent adversarial review reporting zero findings.","external_ref":"https://github.com/samcharles93/archie-core/issues/590","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-t2db.5","title":"Security: an unauthenticated endpoint must not be able to run an agent","description":"P0 within this epic because the feature's own pitch is the threat model: a public intake surface whose output is an agent with tool access and a repo. Get this wrong and a webhook URL is remote code execution with extra steps.\n\nNon-negotiables to design:\n\n- Per-source authentication. A source registers with a secret (HMAC, as internal/channels/webhook already does per route) before its events can trigger anything. Capture-only for unknown senders is acceptable; triggering is not.\n- Human approval before a binding goes live. An operator authoring a binding is a deliberate act; an event arriving is not. Nothing should self-arm.\n- Rate and volume limits per source, so capture cannot be used to exhaust disk or drown the inspector.\n- Payload content is untrusted input flowing into an agent prompt. Treat prompt injection as expected, not exceptional -- the sender controls that text, and the agent has tools. Bound what a playbook-triggered workflow may do.\n- Captured payloads may contain secrets from the sending system. Decide retention, redaction and who can view them; internal/memory/scrubber may already have applicable prior art.\n\nArchie's own principle applies: environmental enforcement over prompt rules. 'The agent should ignore instructions in the payload' is not a control.","acceptance_criteria":"An event from an unauthenticated source can be captured but cannot trigger a workflow; a new binding requires explicit human approval before it arms; per-source rate limits exist; the blast radius of a playbook-triggered workflow is bounded by code rather than by prompt text; retention and visibility of captured payloads is decided and documented.","notes":"2026-08-22: security design decided and documented in docs/prds/webhook-intake-security.md, covering all five non-negotiables from this bead's description:\n1. Per-source auth reuses internal/channels/webhook's existing HMAC-SHA256 scheme; capture accepts unsigned events (visible, marked unauthenticated), only authenticated events can ever match a binding.\n2. Bindings gain a draft -\u003e pending_approval -\u003e armed state machine; any edit to an armed binding drops it back to pending_approval so approval can't be bypassed by editing. Modeled on telegram's existing dangerousAction/pendingApproval flow (dangerous.go/approval.go).\n3. Per-source token-bucket rate limiting (precedent: pairing/store.go's MaxPendingPerPlatform); limit-exceeded is an observable 429, not a silent drop.\n4. Blast radius bounded by the SAME code-level controls every task already gets -- gate, diff_cap_lines, sandboxed container, worktree isolation -- no new relaxation for playbook-triggered work, and payload text is ordinary untrusted prompt input, never a trusted instruction.\n5. 7-day configurable retention on captured payloads; best-effort redaction reusing gateway/stream.go's sensitiveParameterKey heuristic before persisting; visibility gated by the same dashboard auth as every other webui surface.\n\nThis bead's code-level acceptance criteria (capture-can't-trigger, rate limits exist, blast-radius bounded, approval gate) cannot be implemented yet: they constrain t2db.1 (capture), 7d5u.3 (intake family) and t2db.4 (binding), none of which have landed. This document is the contract those beads build against -- do not build any of them without satisfying it. Leaving this bead in_progress rather than closing it; it closes when t2db.1/7d5u.3/t2db.4 land and demonstrably satisfy points 1-5, not before.","status":"in_progress","priority":0,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-21T13:45:46Z","created_by":"Sam Catlow","updated_at":"2026-08-22T09:25:01Z","started_at":"2026-08-21T14:51:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/536","dependencies":[{"issue_id":"archie-core-t2db.5","depends_on_id":"archie-core-t2db","type":"parent-child","created_at":"2026-08-21T23:45:45Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-z0u8","title":"Fix dashboard PR links to target the pull request","description":"The task dashboard Open PR action builds GitHub /pulls/\u003cnumber\u003e, which GitHub interprets as the pull-request listing and a numeric author filter. Link directly to /pull/\u003cnumber\u003e.","acceptance_criteria":"Open PR links use the forge's direct pull-request URL shape; a regression test fails against the plural route and passes after the fix; quality gate passes.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:57:39Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:48:35Z","started_at":"2026-08-24T17:57:46Z","closed_at":"2026-08-24T19:48:35Z","close_reason":"The API now supplies canonical per-task GitHub or Gitea URLs and the dashboard consumes them directly. Regression coverage, task check, and fresh adversarial review pass.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-jy5m","title":"Make task timeline events operationally informative","description":"Task timelines currently render generic stage_start/stage_finish entries with no stage name or outcome, and task_retried entries add little beyond the event kind. Surface the existing event stage, workflow, detail, and relevant structured data so operators can understand what happened without opening raw logs.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:39:51Z","created_by":"Sam Catlow","updated_at":"2026-08-24T17:55:34Z","started_at":"2026-08-24T17:39:57Z","closed_at":"2026-08-24T17:55:34Z","close_reason":"Task timelines now render stage/retry context; baseline and gate-cycle logs expose useful bounded failure output. task check and independent review pass.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-y1hv","title":"Relay dashboard update completion through Telegram","description":"Integrate the existing Carina-side behavior so dashboard-initiated updates can deliver their post-restart watchdog result to an authorized Telegram recipient, while retaining the web UI report path fallback.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T17:18:30Z","created_by":"Sam Catlow","updated_at":"2026-08-24T17:19:42Z","started_at":"2026-08-24T17:18:35Z","closed_at":"2026-08-24T17:19:42Z","close_reason":"Implemented, regression-tested, full task check passed, and adversarial review finding resolved.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-b7f1","title":"Fix Web UI session UUID compatibility and update-status synchronization","description":"The production Web UI crashes when crypto.randomUUID is unavailable, preventing chat session creation. Review and fix UUID generation compatibility plus the recovered Web UI/Telegram update-status synchronization issue, with regression tests and production-path verification.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-08-24T16:50:12Z","created_by":"Sam Catlow","updated_at":"2026-08-24T17:00:21Z","started_at":"2026-08-24T16:50:18Z","closed_at":"2026-08-24T17:00:21Z","close_reason":"Implemented UUIDv7 identities, replayable archived chat tool activity, and post-start update report delivery; full quality gate passes.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-vq92","title":"task_logs truncates at 50KB with no pagination, so full logs are unreachable","description":"The task_logs chat tool caps its response at 50 KB and offers no way to fetch the rest. An operator asking the agent to retrieve or archive a task's logs gets a silently clipped window, and the agent has no mechanism to page past it. Observed 2026-08-24: asked to save a full transcript and agent logs, the agent could only produce a partial archive and had to document the truncation as a limitation rather than satisfy the request.\n\nThe failure compounds with archie-core-p1bl (errors logging as `{}`): a truncated log of uninformative errors leaves an operator with nothing at all, precisely when a task is stuck.\n\n## What is needed\n\nTruncation itself is legitimate -- a tool result must be bounded, and unbounded log text would blow the model's context. The defect is that truncation is TERMINAL: there is no continuation, no offset/cursor, no way to narrow the window, and the caller cannot tell how much was lost.\n\nEstablish first where the cap is applied (the task_logs tool in internal/gateway/task_tools.go and whatever log reader it calls in internal/logging -- note internal/logging owns the on-disk format end to end and internal/webui parses nothing, per CLAUDE.md, so the reader is the right place for range support).\n\nDesign points to decide:\n- A cursor or offset so successive calls walk the whole log, rather than always returning the same head or tail.\n- Filters that make bounded retrieval useful rather than merely possible: by level (errors only), by time range, by stage.\n- The response must state explicitly that it was truncated and how much remains, so the agent can report honestly instead of implying completeness.\n- Consider whether bulk retrieval belongs in a tool result at all, or whether the right answer for \"save the full logs\" is to write the file and deliver it via the new send_file path (archie-core-absb), keeping the tool result small.\n\n## Acceptance Criteria\n\nAn operator can obtain a task's complete logs through the agent, by paging or by file delivery; a truncated response says so and reports what remains rather than ending silently; level and time-range filtering exist so a bounded call can still answer a specific question; the cap remains enforced so no single response can exhaust the model's context; tests cover a log larger than the cap and assert that repeated calls retrieve all of it without gaps or duplication.\n","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:15Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:10Z","external_ref":"https://github.com/samcharles93/archie-core/issues/625","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
@@ -73,11 +77,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-h019.8","title":"Operator-triggered PR review with selectable reviewer model","description":"Expose the reviewer as a channel-neutral application capability that can review an existing pull request on operator request. The Web UI should offer a Review PR action as one adapter; chat/Telegram and future channels must invoke the same command rather than duplicating review behavior. The operator can configure or select the reviewer model independently from planner/builder models. Reuse the reviewer epic's fresh-context, read-only snapshot, structured findings, calibration, and visibility contracts.","acceptance_criteria":"A channel-neutral review command accepts a repository and PR identity, launches the approved isolated reviewer path, and returns/persists structured findings; Web UI exposes Review PR; at least one non-Web-UI channel can invoke the same command; reviewer model is configurable independently with a safe default; authorization and duplicate/concurrent review behavior are deterministic; findings and review status are visible without requiring raw logs.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T18:08:58Z","created_by":"Sam Catlow","updated_at":"2026-08-24T18:09:03Z","external_ref":"https://github.com/samcharles93/archie-core/issues/636","dependencies":[{"issue_id":"archie-core-h019.8","depends_on_id":"archie-core-h019","type":"parent-child","created_at":"2026-08-24T18:08:58Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-atv2","title":"liveReply fallback lines appended after finalize are never rendered","description":"A media delivery that fails AFTER doFinalize has run appends its fallback line to l.toolLines and calls requestRender(), but stopRendering() has already closed renderDone and the renderer goroutine has exited. requestRender is a non-blocking send into a cap-1 channel with no consumer, so the line is dropped and the finalized Telegram message stands unchanged.\n\nMedia is fire-and-forget with a 30s budget while the turn's text finishes far earlier, so this is the NORMAL case for a large upload: a 40MB document that 400s or times out reports 'could not send x' into a slice nothing reads. Pre-dates the local-file work (URL fallbacks have the same hole) but archie-core-absb's guarantee that non-delivery is always visible depends on it.\n\nFound by adversarial review of 9a45fbb. internal/channels/telegram/live.go:419-437 with :498-532.\n\n## Acceptance Criteria\nA media failure occurring after the live reply has finalized still reaches the user -- e.g. as its own follow-up message rather than an edit to a message nothing re-renders. Covered by a test that finalizes first and fails the send second.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T15:54:42Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:54:42Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-h3lg","title":"Dashboard swallows failed operator actions, showing nothing in the UI","description":"When an operator action fails, the dashboard surfaces nothing. Pressing Stop on a running task issued POST /api/tasks/3/action, received 403, and the only evidence anywhere was a browser console line: \"Failed to load resource: the server responded with a status of 403\". The page itself showed no error, no toast, no change of state -- the button simply appeared to do nothing.\n\nThis is how archie-core-440c (every dashboard mutation 403s behind a TLS-terminating reverse proxy) went unnoticed: the operator pressed Stop, saw nothing happen, and reasonably concluded the task was unstoppable rather than that the request had been refused. The bug was only found by opening devtools.\n\nConfirmed live 2026-08-25 while signed in to the production dashboard.\n\n## Why this is its own bead\n\n440c fixes the 403. This bead fixes the fact that ANY failed action is invisible -- a 500, a store failure, a refused state transition, an expired session -- and each of those has its own way of going wrong. Fixing only 440c leaves the next failure equally silent.\n\nNote internal/webui/api_tasks.go already returns distinguishable, human-readable failures (\"missing CSRF header\", \"cross-origin mutation refused\", \"runtime task control is unavailable\"). The server side is doing its job; the client discards it.\n\n## What is needed\n\n- A failed action tells the operator it failed, in the UI, with the server's reason where one is given.\n- The distinction that matters most: refused (403, bad state, not permitted) versus broken (5xx, network). The operator's next move differs -- the first is \"you cannot do that\", the second is \"try again or check the daemon\".\n- A 401 or an expired forward-auth session should prompt re-authentication rather than reading as a generic failure, since the deployment sits behind Authelia.\n- The optimistic UI must not show an action as applied when it was refused.\n\nPer CLAUDE.md the frontend is one folder per feature under ui/src/\u003cfeature\u003e with shared primitives in ui/src/base -- error surfacing used by more than one feature belongs in base, extracted on the SECOND real consumer, not in anticipation. Remember ui/dist is committed: run `task ui` and commit the rebuilt output in the same change.\n\n## Steps to Reproduce\n\n1. Load the dashboard in a deployment where mutations fail (any 440c-affected proxied deployment reproduces it directly).\n2. Press Stop, Retry, Abandon or Archive on a task.\n3. Observe the request fails in devtools while the page reports nothing.\n\n## Acceptance Criteria\n\nA failed operator action is reported in the dashboard with the server's reason where supplied; refused and broken failures are distinguishable to the operator; an authentication failure prompts re-auth rather than a generic error; no optimistic state change survives a failed request; dashboard tests cover a refused action, a server error and a network failure; ui/dist is rebuilt and committed.\n","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T15:49:18Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:15Z","external_ref":"https://github.com/samcharles93/archie-core/issues/629","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-kkeg","title":"No byte-for-byte conversation replay: transcripts cannot be exported or examined","description":"Asked to save a complete transcript -- \"everything. My messages, yours, tools everything. Also save the agents logs\" -- the agent could not. It produced a summary archive and honestly documented the limitation: no chat export exists, and the task-log responses were clipped at the tool's 50 KB cap.\n\nSam's requirement: \"we should be able to receive and view and examine byte-for-byte replays of an entire transcript. exactly the commands run, the results received for those commands, the user messages, agent responses, EVERYTHING.\"\n\n## What exists and what does not\n\ninternal/gateway has session tooling -- session_list, session_resume, session_title, session_delete -- so sessions are already first-class and persisted (the turn ledger backs /gateway's replay of completed-duplicate turns, and archie-core-ippu made tool activity part of that record). What is missing is retrieval: nothing exposes a session's full contents for export or examination.\n\nEstablish first exactly what is persisted per turn today, because the answer determines whether this is an export feature or a capture feature. If tool ARGUMENTS and full tool RESULTS are not currently retained -- only rendered summaries -- then byte-for-byte replay requires changing what is written, not just adding a reader. That distinction is the main open question and should be settled before design.\n\n## Requirements\n\n- Fidelity: user messages, agent responses, every tool call with its arguments, and every tool result, in order, with timestamps. Not a rendered summary, and not the truncated preview the chat UI shows.\n- Retrieval: usable for a whole session, not capped at a tool-result size limit. Bulk delivery almost certainly belongs on the send_file path (archie-core-absb) rather than in a tool result -- write the file, deliver the file.\n- Examination, not just download: an operator should be able to inspect a replay in the dashboard, which is where the event inspector already lives.\n- Honesty: if anything is unavailable (rotated, compacted, never captured), the export must say so explicitly rather than presenting a partial record as complete. The agent got this right by hand; the mechanism should guarantee it.\n\n## Constraints\n\n- Transcripts contain secrets by nature -- tool arguments carry tokens, results carry file contents. internal/memory/scrubber and gateway/stream.go's sensitiveParameterKey are existing prior art for redaction and should be reused rather than reimplemented. Decide explicitly whether an export is redacted, raw, or offers both, and who may request one.\n- Retention: a full-fidelity record is large. Decide what is kept and for how long, consistent with the 7-day payload retention already decided for captured events.\n\n## Acceptance Criteria\n\nAn operator can export a complete session transcript containing user messages, agent responses, tool calls with arguments and tool results with content, in order and timestamped; the export is delivered as a file rather than clipped into a tool result; a replay can be examined in the dashboard; anything missing from the record is stated explicitly in the export; redaction policy is decided, documented and applied; tests cover a session larger than any tool-result cap and assert no gaps or reordering.\n","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:56Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:16Z","external_ref":"https://github.com/samcharles93/archie-core/issues/630","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-wp9s","title":"/status and /tasks have the wrong division of labour","description":"Sam's words: \"/status is fucking annoying. I'm invoking an actual status update, receiving minor information as well as shit I can get elsewhere. What's worse is that the /tasks command is meant to be for viewing the running agents, not /status.\"\n\nObserved 2026-08-24, the entire output of /status was:\n\n Tasks Parked: 2\n Runtime Provider: OpenAI Model: openai/gpt-5.6-luna\n\nTwo problems in one screen. It answers the question /tasks should own (what work is in flight), and it answers it thinly -- a count, with no task identity, no stage, no age, nothing actionable. Everything else it shows is static configuration available elsewhere. Later in the same session /status reported \"Running: 1\" for a task that was stuck in a failure loop and going nowhere, which is the specific case where a bare count actively misleads.\n\n## The division of labour to restore\n\n- `/tasks` owns WORK: what is running, what is parked and why, what needs the operator. This is the live view of the agents, and it is where task identity, workflow, stage, attempt and age belong.\n- `/status` owns HEALTH: is the daemon well. Broker connectivity, provider reachability, channel state, container pool, queue depth, last poll, version. The things an operator checks when something feels wrong and which are NOT visible elsewhere in chat.\n\nNeither should be a thin duplicate of the other, and neither should pad itself with static config the operator already knows.\n\n## Related, decide together\n\narchie-core-624 (task_action chat tool) adds operator verbs for tasks. /tasks is the natural surface for discovering the ids those verbs act on, so the two should be designed as one flow: see the work, then act on it. Check what internal/gateway/task_tools.go already returns before adding a new query path -- ChatTaskSummary may already carry most of what /tasks should show.\n\n## Steps to Reproduce\n\n1. Run /status in chat with tasks parked and one running.\n2. Observe a parked/running COUNT plus provider and model, with no way to identify or act on any task.\n3. Run /tasks and observe the overlap.\n\n## Acceptance Criteria\n\n/tasks shows the live work with enough identity and state to act on it (id, title, status, workflow/stage, age) and is the documented way to view running agents; /status reports daemon health that is not obtainable elsewhere in chat and does not duplicate the task list; a task that is running but not progressing is distinguishable from one making progress; the command descriptions registered with the platform match what each actually does.\n","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:33Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/631","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8qpa","title":"Chat agent does not know its own repository or workspace, wasting turns rediscovering them","description":"Asked to raise a GitHub issue, the agent spent roughly eight tool calls working out where it lives: `pwd`, a `find` over /home/sam/projects returning 139 lines, `git remote -v`, a grep over RELEASING.md returning 92 lines, and a failed `read` of a README that does not exist. It eventually located the repository and filed the issue correctly, but every one of those calls was rediscovering a fact the daemon already knows.\n\nSam's words: \"Yep, thats frustrating AF!\"\n\n## Why this is worth fixing structurally\n\nIt is not only slow and expensive. It is a correctness risk: an agent that has to guess which checkout it is looking at can act on the wrong one, and on this host more than one archie-core checkout exists. It also degrades every task that begins with orientation rather than work.\n\n## What to do\n\ninternal/gateway/BuildSystemPrompt renders templates/archie.md.tpl, which already carries an `\u003cenv\u003e` block. Per CLAUDE.md that template is the single place instruction precedence, core rules and the `\u003ctools\u003e`/`\u003cenv\u003e` blocks live -- personas are the STYLE layer only, so this belongs in the template, never in a persona string.\n\nPut the facts the daemon already holds into `\u003cenv\u003e`: the configured workspace path, the repositories under management with their forge and default branch, and the identity in use. Configuration is the source of truth ([repos] entries, chat.workspace); do not have the prompt claim anything the daemon cannot confirm, and do not hardcode paths.\n\nNote the same rule that governs `\u003ctools\u003e` applies here: the block must be built from what the daemon actually has, because a prompt that names a repository the agent cannot reach is worse than silence -- the model will confidently act on it.\n\n## Acceptance Criteria\n\nThe chat agent knows its workspace path, managed repositories and identity without probing the filesystem; the block is rendered from live configuration rather than hardcoded; an empty or unconfigured value renders as explicitly unknown rather than as a plausible-looking default; a task that previously required filesystem archaeology to orient completes without it; tests assert the block reflects configuration and omits nothing the daemon knows.\n","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:15Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/632","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8qpa","title":"Chat agent does not know its own repository or workspace, wasting turns rediscovering them","description":"Asked to raise a GitHub issue, the agent spent roughly eight tool calls working out where it lives: `pwd`, a `find` over /home/sam/projects returning 139 lines, `git remote -v`, a grep over RELEASING.md returning 92 lines, and a failed `read` of a README that does not exist. It eventually located the repository and filed the issue correctly, but every one of those calls was rediscovering a fact the daemon already knows.\n\nSam's words: \"Yep, thats frustrating AF!\"\n\n## Why this is worth fixing structurally\n\nIt is not only slow and expensive. It is a correctness risk: an agent that has to guess which checkout it is looking at can act on the wrong one, and on this host more than one archie-core checkout exists. It also degrades every task that begins with orientation rather than work.\n\n## What to do\n\ninternal/gateway/BuildSystemPrompt renders templates/archie.md.tpl, which already carries an `\u003cenv\u003e` block. Per CLAUDE.md that template is the single place instruction precedence, core rules and the `\u003ctools\u003e`/`\u003cenv\u003e` blocks live -- personas are the STYLE layer only, so this belongs in the template, never in a persona string.\n\nPut the facts the daemon already holds into `\u003cenv\u003e`: the configured workspace path, the repositories under management with their forge and default branch, and the identity in use. Configuration is the source of truth ([repos] entries, chat.workspace); do not have the prompt claim anything the daemon cannot confirm, and do not hardcode paths.\n\nNote the same rule that governs `\u003ctools\u003e` applies here: the block must be built from what the daemon actually has, because a prompt that names a repository the agent cannot reach is worse than silence -- the model will confidently act on it.\n\n## Acceptance Criteria\n\nThe chat agent knows its workspace path, managed repositories and identity without probing the filesystem; the block is rendered from live configuration rather than hardcoded; an empty or unconfigured value renders as explicitly unknown rather than as a plausible-looking default; a task that previously required filesystem archaeology to orient completes without it; tests assert the block reflects configuration and omits nothing the daemon knows.\n","status":"open","priority":2,"issue_type":"feature","assignee":"samcharles93","owner":"sam@catlow.tech","created_at":"2026-08-24T15:48:15Z","created_by":"Sam Catlow","updated_at":"2026-08-24T19:49:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/632","metadata":null,"labels":["agent"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-8s7v","title":"[EPIC] Intercom: let the chat agent talk to running agents, the curator, and peers","description":"Today the chat agent can only observe autonomous work -- list tasks, read logs -- and act on it as an outsider through coarse verbs (spawn, stop). It cannot TALK to a running agent. An operator who can see a task going wrong has no way to say \"stop guessing, the config lives at X\" without killing the task and starting over, losing everything the agent had already worked out. Archie should behave like a living system whose parts can address each other, not a set of isolated processes with a dashboard bolted on.\n\n## Prior art: pi-intercom\n\nPi ships `pi-intercom`, which solves this shape for Pi sessions on one machine and is worth reading before designing (/home/sam/.pi/agent/npm/node_modules/pi-intercom; skills/pi-intercom/SKILL.md is the usage guide). Its model:\n\n- Sessions take names (`/name planner`, `/name worker-backend`) and address each other by name.\n- `send` -- fire-and-forget notification. Task assignment, status, notice.\n- `ask` -- BLOCKS until the target replies, with a timeout. The blocking form is the interesting one: it lets a worker stop and get a decision instead of guessing.\n- `reply` -- answers an inbound ask, threaded automatically.\n- `pending` -- lists unresolved inbound asks, i.e. who is waiting on you.\n- `list` -- connected sessions and their state (idle / thinking / tool), for discovering targets.\n- Its use cases map directly onto archie: planner-to-worker delegation, context and findings handoff, blocking clarification, subagent escalation (`need_decision`, `interview_request`), cross-project coordination.\n\n## What is genuinely different here\n\nDo NOT copy pi-intercom's transport. It ships its own local IPC broker (broker/broker.ts, a socket server with framing, spawn and runtime-claim logic) because Pi has no message bus. **Archie already has one**: NATS, with per-task subjects already defined in internal/agentexec/subjects.go (archie.agent.\u003cid\u003e.system and .events) and a request/reply pattern already used by taskrun, forgerpc, storerpc and worktreerpc. Building a second broker alongside it would be the \"two parallel abstractions\" mistake this repo already made once with gateway.BasePlatformAdapter.\n\nSo the real design questions are:\n1. Does agent-directed messaging ride the existing per-task subjects, or does it need its own contract and subject family? Note CLAUDE.md's recorded NATS traps -- work-queue retention forbids overlapping consumers, and reply inboxes are core-NATS-only and are not stream subjects.\n2. What is addressable? Running tasks have ids. The curator, channels and the daemon itself do not have a uniform identity for this purpose. An address space has to be decided before verbs are.\n3. How does a BLOCKING ask work against an agent that is mid-model-call? A worker is not sitting in a receive loop; it is inside an agentloop turn. Delivering a message it will actually notice, without corrupting the turn, is the hard part -- and is where this stops being a transport problem.\n4. Authorization: an operator messaging their own task is fine. Cross-identity messaging is not, and multi-identity deployments are supported (deployments/multi-forge-github-gitea.toml). Whatever the gateway's task tools enforce for identity scoping, this must enforce too.\n5. Does an inbound operator message become part of the agent's context permanently, or a one-shot injection? This decides whether it can be used to steer a task or only to interrupt it.\n\n## Relationship to existing work\n\n- Overlaps archie-core-absb (agent cannot send local files) only in spirit: both are about the agent being able to communicate outward.\n- The curator (internal/domain/curator) is a natural second participant after running tasks.\n- Any design here should be checked against docs/architecture/organisation.md: the domain declares the contract it needs; the transport implements it.\n\n## Success Criteria\n\nAn operator can address a running agent from chat and have it receive the message without the task being killed and restarted; a blocking ask returns the agent's answer or times out cleanly; participants are discoverable with their current state; messaging is identity-scoped so one identity cannot address another's work; the mechanism reuses the existing NATS transport rather than introducing a second broker; a design decision is recorded in docs/prds/ before implementation, per CLAUDE.md's scope discipline.\n","notes":"Provenance correction 2026-08-25: this bead's description says 'Pi ships pi-intercom'. That is WRONG and Sam corrected it -- pi-intercom is a THIRD-PARTY PLUGIN written by a different developer solving their own problem, not a Pi feature and not endorsed by Pi. Weigh it accordingly: it is one developer's solution worth reading for its verb vocabulary (send/ask/reply/pending/list) and for the blocking-ask idea, notLine truncated
|
||||
{"_type":"issue","id":"archie-core-absb","title":"Agent cannot send local files: Telegram delivery is URL-fetch only","description":"The agent can produce a file on the host -- a log dump, a screenshot, a written archive, a diff -- and has no way to deliver it to the operator. Asked to send a saved transcript, it replied with a \"Download the archive\" link twice; nothing arrived either time, and it had no signal that anything had failed.\n\n## Why video works and files do not\n\n`telegramMediaSender.dispatch` (internal/channels/telegram/media.go:97) builds every attachment as:\n\n file := \u0026models.InputFileString{Data: att.URL}\n\n`InputFileString` tells Telegram to FETCH the given URL itself. That works for the existing media path because those attachments are remote-hosted -- MiniMax returns a public URL for a generated video, which is what `MultimodalResult.URLs` was added for. It cannot work for anything produced locally: a daemon-host path like /home/sam/archive.md is not a URL Telegram can fetch, so the send silently does nothing useful.\n\nThe `case \"document\"` branch (media.go:124-127) already calls `bot.SendDocument`, so the routing exists. Only the file SOURCE is wrong.\n\n## What is needed\n\nA way for the agent to send a LOCAL file as an attachment -- documents, logs, screenshots, images, any media -- not a link. The go-telegram/bot SDK supports upload via a reader (`models.InputFileUpload` with an io.Reader) as an alternative to `InputFileString`; the sender needs to choose between fetch-by-URL and upload-by-reader based on whether the attachment is remote or local.\n\nExplicitly NOT the fix: exposing an external/public URL for local files. That trades a missing feature for a hosting and access-control problem.\n\n## Constraints to respect\n\n- Telegram enforces upload size limits (50 MB for documents via the Bot API at time of writing); exceeding them must produce a clear error to the operator, not a silent drop.\n- The file tools are workspace-confined unless `[chat] unrestricted_filesystem = true`. Sending must not become a way around whatever confinement is configured -- resolve and check the path under the same policy the read tool applies.\n- A failed send must surface as a failure the agent can see and report. The current defect is not that the agent lied; it is that success and silent non-delivery are indistinguishable to it.\n\n## Acceptance Criteria\n\nThe agent can send a local file through Telegram and the operator receives it as an attachment; local and remote attachments both work, choosing upload-by-reader or fetch-by-URL as appropriate; a send that fails (too large, unreadable, outside the configured confinement) returns an error the agent surfaces rather than reporting success; existing remote-URL media delivery is unchanged and still covered by tests.\n","status":"closed","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-08-24T15:32:07Z","created_by":"Sam Catlow","updated_at":"2026-08-24T15:50:19Z","closed_at":"2026-08-24T15:43:20Z","close_reason":"send_file tool plus upload-by-reader delivery; commit 9a45fbb","external_ref":"https://github.com/samcharles93/archie-core/issues/634","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
{"_type":"issue","id":"archie-core-1787583419901-1-85796c0b","title":"Allow parked agent jobs to be closed or archived","description":"## Problem\nParked agent jobs remain visible indefinitely, but the task-management interface currently exposes no action to close or archive them. This leaves stale jobs in the active job history and requires manual cleanup outside the normal workflow.\n\n## Observed behavior\nThe following old jobs are parked and cannot be closed through the available task-management actions:\n\n- Job #1 — `daemon: label dispatch trigger with empty label matches every open issue`\n- Job #2 — `archied: [[repos]] entries can't span more than one forge`\n\nThe interface can list and inspect parked jobs, but provides no close/archive operation.\n\n## Expected behavior\nProvide an explicit operation for a parked job, such as:\n\n- `close` when the job is definitively finished or no longer actionable;\n- `archive` when it should be removed from the active job list while retaining history;\n- optionally `reopen` if a parked job needs to be resumed.\n\nThe operation should persist the state, be reflected in task listings, and retain the job logs and audit history.\n\n## Acceptance criteria\n- A user can close or archive a parked job from the supported task-management interface/API.\n- The operation is idempotent and reports a clear error for invalid state transitions.\n- Closed/archived jobs no longer appear among active or parked jobs by default, while remaining queryable.\n- Existing logs, attempts, and failure details remain accessible.\n- Tests cover closing, archiving, reopening (if supported), and repeated operations.\n","status":"open","priority":2,"issue_type":"bug","assignee":"samcharles93","created_at":"2026-08-24T13:44:17Z","updated_at":"2026-08-24T13:48:20Z","external_ref":"https://github.com/samcharles93/archie-core/issues/624","source_system":"github:https://github.com/samcharles93/archie-core/issues/624:624","metadata":null,"labels":["agent","bug","ux"],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||
|
||||
Reference in new issue
Block a user