chore(beads): switch to embedded Dolt

dolt_mode in .beads/metadata.json is what selects the storage engine --
'embedded' runs in-process out of .beads/embeddeddolt with no server, 'server'
runs a project-local sql-server out of .beads/dolt. The dolt.shared-server key
in config.yaml only chooses between a shared and a project-local server; it
does not reach embedded mode, which is why the earlier switch landed on
server mode instead.

Data moved from .beads/dolt/archie_core to .beads/embeddeddolt/archie_core;
508 issues intact and the Dolt remote push verified from the new location.
Both paths were already gitignored.
This commit is contained in:
sam committed 2026-08-21 23:59:55 +10:00
1 parent b4d0dd18db
commit d4d6199025
2 files changed
+3 -3

No files matched your search

+2 -2
View File
@@ -218,7 +218,7 @@
{"_type":"issue","id":"archie-core-1786637497395-289-8308ccd7","title":"Verify: WebhookAdapter: declarative filters","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:28Z","updated_at":"2026-08-08T14:49:30Z","closed_at":"2026-08-08T14:49:31Z","external_ref":"https://github.com/samcharles93/archie-core/issues/310","source_system":"github:https://github.com/samcharles93/archie-core/issues/310:310","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637497373-288-22cb0426","title":"Verify: WebhookAdapter: HTTP server with per-route HMAC validation","description":"### Acceptance Criteria\n\nIndependent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:23Z","updated_at":"2026-08-08T14:49:25Z","closed_at":"2026-08-08T14:49:26Z","external_ref":"https://github.com/samcharles93/archie-core/issues/309","source_system":"github:https://github.com/samcharles93/archie-core/issues/309:309","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637497353-287-96a3e24c","title":"MS Graph webhook adapter: validationToken handshake","description":"Implement MS Graph webhook adapter with validationToken handshake for subscription verification, clientState verification, and CIDR IP allowlisting.","notes":"Not started. internal/channels/webhook/webhook.go has no MS-Graph-specific handling at all -- no validationToken query-param echo, no clientState check, no CIDR allowlist. This is likely a separate RouteConfig variant or a dedicated handler function, since MS Graph's subscription-verification handshake (echo validationToken as text/plain on subscribe) doesn't fit the existing POST-body-in/HMAC-out flow.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:20Z","updated_at":"2026-08-15T12:51:54Z","external_ref":"https://github.com/samcharles93/archie-core/issues/308","source_system":"github:https://github.com/samcharles93/archie-core/issues/308:308","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786637497353-287-96a3e24c","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637497328-286-9c985f28","title":"WebhookAdapter: idempotency cache","description":"Implement TTL-based idempotency cache to deduplicate retried webhook deliveries. Cache based on webhook event ID and route.","notes":"Not started. No cache of any kind in internal/channels/webhook/webhook.go. Needs a webhook event ID (route-scoped) -\u003e TTL cache; most platforms send a stable delivery/event ID header (e.g. GitHub's X-GitHub-Delivery) usable as the key. Related to the gateway-level archie-core-1786637492498-104-1bde76ae (MessageDeduplicator) which solves the same class of problem one layer up -- check whether one mechanism can serve both before building a second cache.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:17Z","updated_at":"2026-08-15T12:51:54Z","external_ref":"https://github.com/samcharles93/archie-core/issues/307","source_system":"github:https://github.com/samcharles93/archie-core/issues/307:307","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-1786637492498-104-1bde76ae","type":"related","created_at":"2026-08-15T12:52:03Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-7d5u.5","type":"relates-to","created_at":"2026-08-21T23:27:06Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637497328-286-9c985f28","title":"WebhookAdapter: idempotency cache","description":"Implement TTL-based idempotency cache to deduplicate retried webhook deliveries. Cache based on webhook event ID and route.","notes":"Not started. No cache of any kind in internal/channels/webhook/webhook.go. Needs a webhook event ID (route-scoped) -\u003e TTL cache; most platforms send a stable delivery/event ID header (e.g. GitHub's X-GitHub-Delivery) usable as the key. Related to the gateway-level archie-core-1786637492498-104-1bde76ae (MessageDeduplicator) which solves the same class of problem one layer up -- check whether one mechanism can serve both before building a second cache.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:17Z","updated_at":"2026-08-15T12:51:54Z","external_ref":"https://github.com/samcharles93/archie-core/issues/307","source_system":"github:https://github.com/samcharles93/archie-core/issues/307:307","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-1786637492498-104-1bde76ae","type":"related","created_at":"2026-08-15T12:52:03Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637497328-286-9c985f28","depends_on_id":"archie-core-7d5u.5","type":"relates-to","created_at":"2026-08-21T23:27:06Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637497299-285-f4780816","title":"WebhookAdapter: deliver_only mode","description":"Implement deliver_only mode that skips agent processing and directly renders the prompt template as a deliverable (e.g. plain text, HTML, JSON response).","notes":"Not started, despite the package doc comment's claim: webhook.go:1-3 says 'Outbound delivery is not supported (deliver-only mode)' but handleWebhook() (webhook.go:120-183) unconditionally calls router.Route -- there is no branch that skips the agent and renders the template directly. RouteConfig.DeliverTo==\"origin\" only controls where the agent's reply goes, it doesn't skip the agent. Either the doc comment is aspirational (fix by implementing this issue) or describes a different, unbuilt code path -- don't trust the comment over the code.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:14Z","updated_at":"2026-08-15T12:51:54Z","external_ref":"https://github.com/samcharles93/archie-core/issues/306","source_system":"github:https://github.com/samcharles93/archie-core/issues/306:306","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786637497299-285-f4780816","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637497271-284-573ca138","title":"WebhookAdapter: prompt templates with dot-notation","description":"Implement prompt template system with dot-notation variable interpolation ({pull_request.title}, {__raw__}) for building dynamic prompts from webhook payloads.","notes":"Partially done: internal/channels/webhook/webhook.go:243-264 extractText() does single-field dot-notation extraction (RouteConfig.Template = \"issue.title\"), not multi-variable interpolation. This issue wants a template string with multiple {field.path} placeholders plus a {__raw__} escape hatch -- extractText needs to become a real interpolation pass (parse placeholders, resolve each dot-path, substitute), not a single-path lookup. RouteConfig.Template's meaning would change from 'the one field to extract' to 'a template string' -- update its doc comment in the same change.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:10Z","updated_at":"2026-08-15T12:51:54Z","external_ref":"https://github.com/samcharles93/archie-core/issues/305","source_system":"github:https://github.com/samcharles93/archie-core/issues/305:305","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786637497271-284-573ca138","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637497242-283-03662140","title":"WebhookAdapter: script transforms","description":"Support external script transforms per route. Allow bash/python scripts to transform incoming webhook payloads before processing.","notes":"Not started. No script/transform hook exists in internal/channels/webhook/webhook.go. Would sit between body read and text extraction in handleWebhook() (webhook.go:120-183), likely as a RouteConfig field naming an external command, invoked via os/exec on the raw body before extractText.","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:49:07Z","updated_at":"2026-08-15T12:51:54Z","external_ref":"https://github.com/samcharles93/archie-core/issues/304","source_system":"github:https://github.com/samcharles93/archie-core/issues/304:304","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786637497242-283-03662140","depends_on_id":"archie-core-1786637497036-275-8838629e","type":"related","created_at":"2026-08-15T12:52:04Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
@@ -366,7 +366,7 @@
{"_type":"issue","id":"archie-core-1786637493467-141-ffb91b17","title":"ToolEntry data type definition","description":"Design and implement the ToolEntry data type carrying: name, toolset (which tool group this belongs to), schema (JSON Schema for invocation), handler (function ref), check_fn (availability predicate), requires_env (env vars needed), is_async (async/sync distinction), description, emoji, max_result_size_chars (per-tool result cap), and dynamic_schema_overrides (runtime schema mutations). This is the foundational type that everything in the tools subsystem builds upon.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:14Z","updated_at":"2026-08-08T14:38:16Z","closed_at":"2026-08-08T14:38:17Z","external_ref":"https://github.com/samcharles93/archie-core/issues/162","source_system":"github:https://github.com/samcharles93/archie-core/issues/162:162","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637493439-140-2cee2e9b","title":"[EPIC] Tools: central registry, MCP client, guardrails","description":"Central tool infrastructure to match Hermes parity:\n\n1. **Tool registry**: A central registry where tool modules register themselves with name, schema, handler, toolset membership, and availability check. Dynamic discovery of built-in tools. This replaces the current pattern of manually constructing core.ToolSet maps per invocation.\n\n2. **MCP client**: Connect to external MCP servers via stdio, HTTP/StreamableHTTP, or SSE transport. Discover their tools and register them into the tool registry. Support automatic reconnection with backoff, configurable timeouts, per-server parallel tool call opt-in.\n\n3. **Guardrails**: Tool-call loop detection (repeated calls, repeated failures, no-progress loops). Idempotent/mutating tool classification. Warning vs hard-stop decisions.\n\n4. **Progressive disclosure**: When tool schemas exceed a context-window threshold, replace them with bridge tools (tool_search/tool_describe/tool_call) and surface on demand. Core tools are always visible.\n\nRef: docs/prds/hermes-gap-analysis.md section 3\n\n### Acceptance Criteria\n\nMCP servers can be configured with a TOML block and their tools appear alongside built-ins. The agent loop is protected against tool-call loops. Tool schemas stay within context budget.\n","notes":"docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:38:11Z","updated_at":"2026-08-15T12:47:30Z","external_ref":"https://github.com/samcharles93/archie-core/issues/161","source_system":"github:https://github.com/samcharles93/archie-core/issues/161:161","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637493413-139-d157cc71","title":"SessionSource struct for platform identity","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:06Z","updated_at":"2026-08-08T14:38:08Z","closed_at":"2026-08-08T14:38:09Z","external_ref":"https://github.com/samcharles93/archie-core/issues/160","source_system":"github:https://github.com/samcharles93/archie-core/issues/160:160","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637493387-138-cad8e7a7","title":"Platform capability flags for adapters","description":"A capability-flag mechanism so callers can ask an adapter which optional features it supports (typing indicator, edit, delete, media send, clarify/approval/picker UI) instead of discovering support by a failed type assertion or a runtime error.\n\n### Context for implementers\n\nThis depends on the optional-method interfaces this issue is meant to describe: `archie-core-1786637493329-136-49b39c78` (typing/edit/delete/media) and `archie-core-1786637493357-137-35af7083` (clarify/approval/pickers). Implement after (or in close coordination with) those two, since the flag set should mirror whatever optional interfaces they land — don't invent a flag taxonomy ahead of the methods it describes.\n\n### Acceptance Criteria\n\n`BasePlatformAdapter` (`internal/gateway/adapter.go`) or a wrapping type exposes a capability query (e.g. `Capabilities() AdapterCapabilities`) that reports which optional methods an adapter implements. Every existing adapter's reported capabilities match its actual method set (a regression test should fail if an adapter claims a capability it doesn't implement, or vice versa).\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:02Z","updated_at":"2026-08-15T12:46:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/159","source_system":"github:https://github.com/samcharles93/archie-core/issues/159:159","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786637493387-138-cad8e7a7","depends_on_id":"archie-core-1786637493329-136-49b39c78","type":"blocks","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637493387-138-cad8e7a7","depends_on_id":"archie-core-1786637493357-137-35af7083","type":"blocks","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637493387-138-cad8e7a7","title":"Platform capability flags for adapters","description":"A capability-flag mechanism so callers can ask an adapter which optional features it supports (typing indicator, edit, delete, media send, clarify/approval/picker UI) instead of discovering support by a failed type assertion or a runtime error.\n\n### Context for implementers\n\nThis depends on the optional-method interfaces this issue is meant to describe: `archie-core-1786637493329-136-49b39c78` (typing/edit/delete/media) and `archie-core-1786637493357-137-35af7083` (clarify/approval/pickers). Implement after (or in close coordination with) those two, since the flag set should mirror whatever optional interfaces they land — don't invent a flag taxonomy ahead of the methods it describes.\n\n### Acceptance Criteria\n\n`BasePlatformAdapter` (`internal/gateway/adapter.go`) or a wrapping type exposes a capability query (e.g. `Capabilities() AdapterCapabilities`) that reports which optional methods an adapter implements. Every existing adapter's reported capabilities match its actual method set (a regression test should fail if an adapter claims a capability it doesn't implement, or vice versa).\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:38:02Z","updated_at":"2026-08-15T12:46:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/159","source_system":"github:https://github.com/samcharles93/archie-core/issues/159:159","metadata":null,"labels":["task"],"dependencies":[{"issue_id":"archie-core-1786637493387-138-cad8e7a7","depends_on_id":"archie-core-1786637493357-137-35af7083","type":"blocks","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-1786637493387-138-cad8e7a7","depends_on_id":"archie-core-1786637493329-136-49b39c78","type":"blocks","created_at":"2026-08-15T12:46:57Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":2,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637493357-137-35af7083","title":"BasePlatformAdapter interactive UX methods (clarify, approval, pickers)","description":"Add adapter-facing methods for interactive UX: presenting a clarifying question, an approval prompt, and a picker (multi-choice selection) natively on the platform, rather than as plain text the user has to reply to by hand.\n\n### Context for implementers\n\nThe approval *decision* plumbing already exists — `internal/tools/approval.go`, re-exported through `internal/gateway/approval.go` (`ApprovalRequester`, `ApprovalDecision`, `WithApprovalRequester`/`ApprovalFromContext`). What's missing is the adapter-side rendering: `BasePlatformAdapter` (`internal/gateway/adapter.go`) has no method for an adapter to display an approval/clarify/picker UI and report back a decision through that existing plumbing. This issue wires a new adapter method (or interface) into the existing `ApprovalRequester` flow — it should not duplicate or replace the decision model in `internal/tools/approval.go`. Sibling of `archie-core-1786637493329-136-49b39c78` (typing/edit/delete/media) — same \"optional adapter capability\" shape, different capability set.\n\n### Acceptance Criteria\n\nAn adapter can render a clarify/approval/picker prompt and the user's response is delivered back through the existing `ApprovalRequester`/`ApprovalDecision` flow in `internal/tools/approval.go`, not a parallel mechanism. Platforms without native UI (e.g. plain text-only channels) degrade to a text-based fallback rather than failing. Covered by a test double adapter, not a live platform.\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:59Z","updated_at":"2026-08-15T12:46:48Z","external_ref":"https://github.com/samcharles93/archie-core/issues/158","source_system":"github:https://github.com/samcharles93/archie-core/issues/158:158","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":1,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637493329-136-49b39c78","title":"BasePlatformAdapter optional methods (typing, edit, delete, media)","description":"Extend adapter capability beyond the four required `BasePlatformAdapter` methods with optional per-platform methods: typing indicator, message edit, message delete, and media-specific send.\n\n### Context for implementers\n\n`internal/gateway/adapter.go` today defines `BasePlatformAdapter` with exactly four methods: `Connect`, `Disconnect`, `Send`, `ChatInfo` (see full listing — the file is 80 lines). Not every platform supports typing/edit/delete/media uniformly, so these should be a separate optional interface(s) that callers type-assert for, not additions to the required interface (that would break every existing adapter implementation). Pairs with `archie-core-1786637493387-138-cad8e7a7` (platform capability flags) — callers need a way to know *ahead of a type assertion* whether an adapter supports a given optional method, rather than probing via failed assertions at call time.\n\n### Acceptance Criteria\n\nOptional methods are defined on a separate interface (or interfaces) from `BasePlatformAdapter`, so existing adapters keep compiling unchanged. At least one adapter implementation exercises each optional method in a test. Callers that invoke an optional method on an adapter that doesn't implement it get a defined, non-panicking behavior.\n","status":"open","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:57Z","updated_at":"2026-08-15T12:46:47Z","external_ref":"https://github.com/samcharles93/archie-core/issues/157","source_system":"github:https://github.com/samcharles93/archie-core/issues/157:157","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":1,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637493304-135-95070200","title":"BasePlatformAdapter interface with required methods","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:37:51Z","updated_at":"2026-08-08T14:37:54Z","closed_at":"2026-08-08T14:37:55Z","external_ref":"https://github.com/samcharles93/archie-core/issues/156","source_system":"github:https://github.com/samcharles93/archie-core/issues/156:156","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
+1 -1
View File
@@ -1,7 +1,7 @@
{
"database": "dolt",
"backend": "dolt",
"dolt_mode": "server",
"dolt_mode": "embedded",
"dolt_database": "archie_core",
"project_id": "e8a66150-1f5f-42d2-8653-dcf8463cef74",
"global_dolt_database": "beads_global",