Dark-Alex-17/coyote
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs(plans): record implementation-verified correction from T6

Browse Source 
no_workspace_mcp (and therefore no_workspace_macros, per the exact-mirror
ruling) is CLI-flag-only: AppConfig field exists but there is no
Config-struct key and no env arm, so a config.yaml entry is non-functional.
Pre-existing issue: config.example.yaml:140 documents the dead
no_workspace_mcp key — recorded as follow-up, out of scope.
This commit is contained in:
Dark-Alex-17
2026-08-21 11:55:13 -06:00
parent 4323d4823c
commit 125360033d
1 changed files with 11 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plans/custom-commands-design.md
+11 -6
View File
@@ -286,10 +286,14 @@ workspace-artifact conventions (VERIFIED mechanics):
skills (`list_skills` iterates [workspace, global] with shadowing, skills (`list_skills` iterates [workspace, global] with shadowing,
paths.rs:478-501; `has_skill` checks workspace first, :503-505) and paths.rs:478-501; `has_skill` checks workspace first, :503-505) and
workspace MCP (HashMap insert, workspace wins, mcp/mod.rs:239). workspace MCP (HashMap insert, workspace wins, mcp/mod.rs:239).
- Opt-out mirrors MCP: new `--no-workspace-macros` CLI flag + - Opt-out mirrors MCP: new `--no-workspace-macros` CLI flag, modeled on
`no_workspace_macros` config key (default false), modeled on `--no-workspace-mcp` (cli/mod.rs:96-98 → main.rs:222-223).
`--no-workspace-mcp` (cli/mod.rs:96-98 → main.rs:222-223, IMPLEMENTATION-VERIFIED CORRECTION (T6): `no_workspace_mcp` is
app_config.rs:98). CLI-flag-only — AppConfig field exists but there is NO Config-struct key
and NO env arm, so a config.yaml entry is non-functional. The exact-mirror
ruling therefore makes `no_workspace_macros` CLI-flag-only too.
(Pre-existing bug, out of scope: config.example.yaml:140 documents
`no_workspace_mcp:` as a yaml key even though it does nothing — follow-up.)
- Trust model: no confirmation prompt — consistent with workspace MCP and - Trust model: no confirmation prompt — consistent with workspace MCP and
skills, which load with no gate (mcp/mod.rs:225-268 merely eprintlns); skills, which load with no gate (mcp/mod.rs:225-268 merely eprintlns);
macros are strictly lower-risk since they run only on explicit user macros are strictly lower-risk since they run only on explicit user
@@ -404,8 +408,9 @@ install-time warning if an installed macro's name shadows a built-in.
invocation; `isolated` semantics with the role-switch-persists warning. invocation; `isolated` semantics with the role-switch-persists warning.
- `config.example.yaml`, `config.role.example.md`, - `config.example.yaml`, `config.role.example.md`,
`config.agent.example.yaml`: `enabled_macros` entries mirroring the `config.agent.example.yaml`: `enabled_macros` entries mirroring the
existing `enabled_skills` doc comments; `no_workspace_macros` entry existing `enabled_skills` doc comments. Do NOT add a `no_workspace_macros`
alongside the existing `no_workspace_mcp` one (config.example.yaml:140-145). yaml entry — the flag is CLI-only (see §5 correction); the existing
`no_workspace_mcp` yaml line documents a dead key (pre-existing, follow-up).
- New `macro.example.yaml` (or extend existing docs) showing all fields incl. - New `macro.example.yaml` (or extend existing docs) showing all fields incl.
description/isolated. description/isolated.
- Workspace macros: document `.coyote/macros/` alongside the existing - Workspace macros: document `.coyote/macros/` alongside the existing