8 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Opus 5.5	f41c7dbeff	chore(context): resync derived adapters from canonical AGENT.md ... Clears ContextAdapterDrift; canonical changed in local-dev 12f694b/218cf0d. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-04 22:49:54 +02:00
mathiasandClaude Opus 5	628a664fda	chore(context): adopt canonical context-sync.sh and re-sync adapters ... infra's scripts/context-sync.sh is the estate canonical, and it moved in infra 262369b (a SIGPIPE fix on the placeholder-reporting path: `printf | grep -o | head -1` became `head -1 < <(grep -o ...)`). Every other repo still carried the old line, so ContextSyncScriptDrift and ContextAdapterDrift were both firing. Also picks up the canonical AGENT.md change from local-dev a01ee80 — rule 5's GitOps review lane and the new precedence rule — which every repo's adapters need regenerated for regardless of the script. Refs mathias/infra#470 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-30 10:38:43 +02:00
mathiasandClaude Opus 5	cb8fe89991	chore(context): regenerate derived adapters from the canonical root context ... ContextAdapterDrift was firing for 13 repos. Picks up behaviour rule 7 ("Finish what's closable"), which landed in ~/dev/.context/AGENT.md and never reached any repo's derived files. Where mcp.json changes, it also picks up root MCP config the repo was stale on: brain/gitea/infra move from public hostnames to tailnet Serve URLs, and gitea's bearer changes from GITEA_MCP_TOKEN to DMABE_GITEA_API_TOKEN — gitea-mcp authenticates by pass-through and 401s on the former, so a harness syncing from the old file had a dead gitea server and no signal saying so. No literal secrets: mcp.json carries ${VAR} placeholders only. CLAUDE.md deliberately unchanged — context-sync writes it from PROJECT.md alone, since Claude Code walks up to ~/dev/CLAUDE.md for root context. Refs mathias/infra ContextAdapterDrift Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-25 07:35:06 +02:00
mathias	7c70489efe	fix(context): sync to the estate canonical context-sync.sh (ADR-0019) ... Caught by the new estate-wide context-sync-drift gate (infra, ADR-0019). This repo's copy had diverged from the canonical established in dma-cli/ infra -- synced to it, dead Cursor/Aider artifacts removed (2026-09-01 harness decision), Taskfile's drift assertion narrowed to match, adapters regenerated against the current canonical AGENT.md. Changed: D .aider.conf.yml D .aider.conventions.md M .context/system-prompt.txt D .cursorrules M AGENTS.md M Taskfile.yml M scripts/context-sync.sh Refs: ADR-0019 (infra)	2026-09-05 08:33:36 +02:00
mathiasandClaude Opus 4.8	8a22a28ab4	fix(template): parameterize scaffold with __PROJECT_NAME__/__MODULE_PATH__ (gitea-mcp#44) ... template-go-web was seeded from the real `hostexecutor` project and never parameterized: go.mod hardcoded `module gitea.d-ma.be/mathias/hostexecutor` and `hostexecutor` appeared throughout (cmd dir, Dockerfile, Taskfile, CI, context docs). create_project_from_template therefore substituted nothing and returned a "no placeholders" partial_failure on the zero-config default path. Replaced the full module path with __MODULE_PATH__ and the bare project name with __PROJECT_NAME__ (incl. renaming cmd/hostexecutor → cmd/__PROJECT_NAME__), matching the substitution the tool performs. Also drops the stale gitea.d-ma.be host (the placeholder resolves to git.d-ma.be/<owner>/<name>). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-03 23:33:46 +02:00
gitea-actions[bot]	04fa3cf36e	chore: bootstrap hostexecutor from template	2026-05-12 21:47:36 +02:00
mathias	e2810b9209	feat: add agent scaffold (context-sync, skills, context tasks) (#2)	2026-05-12 15:24:42 +00:00
mathias	a25120cd1d	feat: initial template (Go + Templ + HTMX + CDN Tailwind)	2026-05-05 08:19:04 +02:00