Forge-wide wipe: Buzz and Vikunja dead references (agents are still contacting them) #38

Open

opened 2026-08-07 05:11:15 +00:00 by agent.odin · 0 comments

agent.odin commented

2026-08-07 05:11:15 +00:00

Collaborator

Owner order 2026-08-07. Twice yesterday an agent contacted Buzz or Vikunja. The dead references are still live enough to mislead. Wipe them across the estate.

Root cause

larandar.flake/AGENTS.md still declared "Buzz is the live workflow authority" — agents entering that repo obeyed the instruction. Fixed in-tree (commit follows). Remaining references across the estate are dead code, historical plans, and encrypted secrets that create false confidence.

Scope — forge-wide

1. AGENTS.md files (DONE / VERIFY)

repo	status
`larandar.flake`	FIXED — Buzz/Vikunja section rewritten to name Forgejo as sole authority
`larandar.flaky-mesh`	Already clean — Buzz named as dead, instructs against Nostr
`lar.ad/modron`	Already clean — Buzz/Vikunja named as decommissioned

2. Dead code — `larandar.flake` (163 references)

These files are dead Buzz code and should be deleted or archived in one commit:

packages/_buzz/ — 4 files (buzz.nix, default.nix, relay-module.nix, versions.nix)
modules/systems/server/buzz-relay.nix — 25 refs
modules/systems/server/default.nix — buzz-relay include
packages/default.nix — _buzz package reference
secrets/ad-hoc.yaml — buzz-related secrets
modules/inputs.nix — buzz input references
hosts/odin/configuration.nix — buzz host wiring
modules/apps/coding.nix, modules/desktop/niri.nix — incidental refs

3. Dead secrets — `larandar.flaky-mesh`

From the backlog, confirmed inert:

outputs/hosts/odin/secrets.ad-hoc.yaml — BUZZ_RELAY_PRIVATE_KEY (encrypted, nothing decrypts it)
outputs/hosts/bifrost/secrets.yaml — buzz/* keys (may already be cleaned; verify)

4. Plans (gitignored, on-disk only — no VCS action)

plans/ holds 214 buzz references across 10 files (BUZZ_AGENT_KEY_MINTING, BUZZ_SIDECAR_SPEC, BUZZ_SIDECAR_TICKETS, LIBREFANG_BUZZ_BRIDGE_PLAN, ET0_RELAY_BRINGUP, etc.). These are research notes, not code. They stay on disk as history; no action needed unless they confuse an agent.

5. flake.lock — ALREADY CLEAN

Buzz and librefang-sidecar-buzz inputs are gone from both flake.lock files. The DEFERRED.md prerequisite #1 is stale.

6. External cleanup

Cloudflare R2 bucket et0-buzz and its scoped API token — delete once confirmed nothing in the bucket is wanted.

Acceptance

larandar.flake/AGENTS.md rewritten (done this session)
Dead buzz code deleted from larandar.flake (packages/_buzz, buzz-relay.nix, wiring)
Dead buzz secrets confirmed inert and removed from flaky-mesh secrets files
rg -i 'buzz' larandar.flake --glob '!*.md' returns zero results outside of historical comments
R2 bucket et0-buzz deleted
No agent can reach a buzz/vikunja endpoint from any estate repo

Blocked by: nothing. This is fire.

**Owner order 2026-08-07. Twice yesterday an agent contacted Buzz or Vikunja. The dead references are still live enough to mislead. Wipe them across the estate.** ## Root cause `larandar.flake/AGENTS.md` still declared "Buzz is the live workflow authority" — agents entering that repo obeyed the instruction. **Fixed in-tree** (commit follows). Remaining references across the estate are dead code, historical plans, and encrypted secrets that create false confidence. ## Scope — forge-wide ### 1. AGENTS.md files (DONE / VERIFY) | repo | status | |------|--------| | `larandar.flake` | **FIXED** — Buzz/Vikunja section rewritten to name Forgejo as sole authority | | `larandar.flaky-mesh` | Already clean — Buzz named as dead, instructs against Nostr | | `lar.ad/modron` | Already clean — Buzz/Vikunja named as decommissioned | ### 2. Dead code — `larandar.flake` (163 references) These files are dead Buzz code and should be deleted or archived in one commit: - `packages/_buzz/` — 4 files (buzz.nix, default.nix, relay-module.nix, versions.nix) - `modules/systems/server/buzz-relay.nix` — 25 refs - `modules/systems/server/default.nix` — buzz-relay include - `packages/default.nix` — _buzz package reference - `secrets/ad-hoc.yaml` — buzz-related secrets - `modules/inputs.nix` — buzz input references - `hosts/odin/configuration.nix` — buzz host wiring - `modules/apps/coding.nix`, `modules/desktop/niri.nix` — incidental refs ### 3. Dead secrets — `larandar.flaky-mesh` From the backlog, confirmed inert: - `outputs/hosts/odin/secrets.ad-hoc.yaml` — `BUZZ_RELAY_PRIVATE_KEY` (encrypted, nothing decrypts it) - `outputs/hosts/bifrost/secrets.yaml` — buzz/* keys (may already be cleaned; verify) ### 4. Plans (gitignored, on-disk only — no VCS action) `plans/` holds 214 buzz references across 10 files (BUZZ_AGENT_KEY_MINTING, BUZZ_SIDECAR_SPEC, BUZZ_SIDECAR_TICKETS, LIBREFANG_BUZZ_BRIDGE_PLAN, ET0_RELAY_BRINGUP, etc.). These are research notes, not code. They stay on disk as history; no action needed unless they confuse an agent. ### 5. flake.lock — ALREADY CLEAN Buzz and `librefang-sidecar-buzz` inputs are gone from both flake.lock files. The DEFERRED.md prerequisite #1 is stale. ### 6. External cleanup - Cloudflare R2 bucket `et0-buzz` and its scoped API token — delete once confirmed nothing in the bucket is wanted. ## Acceptance - [x] `larandar.flake/AGENTS.md` rewritten (done this session) - [ ] Dead buzz code deleted from `larandar.flake` (packages/_buzz, buzz-relay.nix, wiring) - [ ] Dead buzz secrets confirmed inert and removed from flaky-mesh secrets files - [ ] `rg -i 'buzz' larandar.flake --glob '!*.md'` returns zero results outside of historical comments - [ ] R2 bucket `et0-buzz` deleted - [ ] No agent can reach a buzz/vikunja endpoint from any estate repo Blocked by: nothing. This is fire.

Commenting is not possible because the repository is archived.