chore(beads): persist interactions log
Append-only audit entries for four issue transitions: the persona overconfidence fix (archie-core-3jag), the empty label-trigger dispatch fix (archie-core-...-424), and closing the bws secret-engine plugin task (archie-core-...-410) as already delivered by the compiled-in engine. Issue data itself lives in Dolt and was pushed separately (bd dolt push); this file is the passive export.
This commit is contained in:
1 parent
b5d08d0d93
commit
992b17c524
1 file changed
+4
@@ -20,3 +20,7 @@
|
||||
{"id":"int-b6e06d7e49ee35af64ad21b7b99a7f67","kind":"field_change","created_at":"2026-08-18T15:51:15.949055267Z","actor":"Sam Catlow","issue_id":"archie-core-1786748942463-15-78823975","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic."}}
|
||||
{"id":"int-726497f741b07352a4f67d3ba8be8c5b","kind":"field_change","created_at":"2026-08-18T15:53:29.554375007Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490011-9-d5e4f9a4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Superseded: confirmed by Sam that there is no longer a separate /provider command -- grepped the codebase and no '/provider' command exists in internal/gateway or internal/channels/telegram. /model now handles provider scoping directly."}}
|
||||
{"id":"int-7096095a0791399004afa1648103b4d4","kind":"field_change","created_at":"2026-08-18T16:05:12.750527752Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490923-43-d4bb914b","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed: configuredMCPProvider (cmd/archied/main.go) now sets NPM_CONFIG_CACHE under the daemon's persistent work_dir and NPM_CONFIG_PREFER_OFFLINE=true for any npx-launched MCP server (matched by base name so an absolute-path npx still qualifies), so a daemon restart reuses a warm npm cache instead of re-resolving/re-downloading from the registry every time -- the amplifier behind the 2026-07-30 crash loop. Guards an empty workDir explicitly (unreachable in production since config defaulting runs first, but matches memoryProvider's existing precedent for the same defense). Adversarially reviewed by a fresh subagent; findings addressed: narrowed an overclaim that this also covers a package's own separate downloads (e.g. Playwright/Puppeteer fetching browser binaries via CDN, which NPM_CONFIG_CACHE does not touch), and closed the absolute-path-command gap. Full task check clean. The identical, arguably-worse instance in internal/app/agentworker/mcp_providers.go (every per-task ephemeral container, not just daemon restarts) needs real new infra -- a persistent Docker volume bind-mounted into task containers, which doesn't exist yet -- so it's filed separately as archie-core-qk8m rather than folded into this scoped fix."}}
|
||||
{"id":"int-0379f6f196262497f6642169c943afd6","kind":"field_change","created_at":"2026-08-20T12:55:17.903920351Z","actor":"Sam Catlow","issue_id":"archie-core-3jag","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed in fix/persona-overconfidence (fba80e3): reworded core rule 1 and added rules 8/9 to the chat agent system prompt enforcing this-turn verification before labelling claims verified/confirmed."}}
|
||||
{"id":"int-0e6d7b43d42215a9a41b1736f4b049d7","kind":"field_change","created_at":"2026-08-20T12:57:02.748858938Z","actor":"Sam Catlow","issue_id":"archie-core-1786637501009-424-5b8332dd","extra":{"field":"status","new_value":"in_progress","old_value":"open"}}
|
||||
{"id":"int-dec9f9d1307c51147ea510842ef80d1a","kind":"field_change","created_at":"2026-08-20T13:02:18.330112565Z","actor":"Sam Catlow","issue_id":"archie-core-1786637501009-424-5b8332dd","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Fixed in fix/label-dispatch-empty-label (31efdcf): pollIssuesWithConfig/pollEitherWithConfig now refuse the label poll when cfg.Label is empty, and validateDispatch rejects the misconfiguration at load time. Adversarially reviewed; one weak test strengthened to actually verify assignee matches survive."}}
|
||||
{"id":"int-c00194f10222de956f7ad8987d09a9fb","kind":"field_change","created_at":"2026-08-20T13:24:15.962276702Z","actor":"Sam Catlow","issue_id":"archie-core-1786637500602-410-7a461d4d","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Already delivered as a compiled-in engine, not a plugin. internal/secret/bws.go implements secret.Engine and shells out to the bws CLI via os/exec (commit 3ae59c9, 2026-07-31); NewRegistry/DefaultRegistry register it under the name \"bws\" alongside \"env\". It is documented in config.example.toml and ARCHITECTURE.md:208, and config.example.toml:64 uses it as the worked example. Shipping a second yaegi implementation under examples/secret-engines/ would register the same name \"bws\", and Registry.Register is last-write-wins over LoadDir, so the plugin would silently shadow the compiled-in engine -- two authoritative paths for one behaviour, which the architecture contract prohibits. Reopen only if the intent is to REPLACE the compiled-in engine with a plugin (which would also need bws removed from NewRegistry and the docs updated)."}}
|
||||
Reference in new issue
Block a user