P2 · Vault → skill hygiene (creds without runbooks; op:// path drift) #8

New issue

Open

opened 2026-07-11 19:59:54 -05:00 by adam · 0 comments

adam commented

2026-07-11 19:59:54 -05:00

Owner

Priority: P2 · Size: S · Depends on: none

Goal

A broad "go" from Adam shouldn't get blocked mid-flow for routine lab-API calls. Keep genuine break-glass writes gated, but stop re-prompting on reads and make the write path predictable.

Why (from the 2026-07-11 session)

After "all three" / "go", the auto-mode classifier blocked the Dockhand POST /api/git/stacks twice as an unnamed shared-infra write — resolved only when Adam switched permission modes. Reads were fine; the writes needed per-action naming at a specificity that a broad delegation doesn't provide.

Steps

Via the update-config skill, add scoped Bash allow-rules for lab-API reads (at minimum curl to 192.168.4.200:8647 Dockhand; also :3000 Forgejo API, :2700 Hindsight, :18080 1Password Connect). Consider the fewer-permission-prompts skill to mine the transcript for the exact call shapes.
Decide the write policy: keep writes break-glass, but document a convention — e.g. "infra-write sessions start in non-auto mode" — so a block is expected, not a surprise mid-flow.
Capture the convention in a feedback_* memory + .claude/skills/README.md. Align with (don't contradict) feedback_unraid_mcp_access (MCP writes = break-glass).

Acceptance

settings.json has the scoped allow-rules; a test read call to a lab API runs with no prompt; the infra-write convention is documented.

Resources

Skills: update-config, fewer-permission-prompts. Memory: feedback_unraid_mcp_access. Note the permissions file was slimmed to ~50 entries on 2026-06-26 — extend that curated set, don't bloat it.

**Priority:** P2 · **Size:** S · **Depends on:** none ## Goal A broad "go" from Adam shouldn't get blocked mid-flow for routine lab-API calls. Keep genuine break-glass writes gated, but stop re-prompting on reads and make the write path predictable. ## Why (from the 2026-07-11 session) After "all three" / "go", the auto-mode classifier blocked the Dockhand `POST /api/git/stacks` **twice** as an unnamed shared-infra write — resolved only when Adam switched permission modes. Reads were fine; the writes needed per-action naming at a specificity that a broad delegation doesn't provide. ## Steps - Via the `update-config` skill, add **scoped Bash allow-rules** for lab-API reads (at minimum `curl` to `192.168.4.200:8647` Dockhand; also `:3000` Forgejo API, `:2700` Hindsight, `:18080` 1Password Connect). Consider the `fewer-permission-prompts` skill to mine the transcript for the exact call shapes. - Decide the write policy: keep writes break-glass, but document a **convention** — e.g. "infra-write sessions start in non-auto mode" — so a block is *expected*, not a surprise mid-flow. - Capture the convention in a `feedback_*` memory + `.claude/skills/README.md`. Align with (don't contradict) `feedback_unraid_mcp_access` (MCP writes = break-glass). ## Acceptance `settings.json` has the scoped allow-rules; a test read call to a lab API runs with no prompt; the infra-write convention is documented. ## Resources Skills: `update-config`, `fewer-permission-prompts`. Memory: `feedback_unraid_mcp_access`. Note the permissions file was slimmed to ~50 entries on 2026-06-26 — extend that curated set, don't bloat it.

adam added the

lab-honing

label

2026-07-11 19:59:54 -05:00

No labels

lab-honing

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

adam/foundry#8

No description provided.

Rows
Columns