Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .changes/autonomy/fix-plugin-profiles-followups-8b2e4d61.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
bump: patch
---

### Changed

- The drift delta sweep records a lane as not run when its plugin is not enabled, and its report names enabling the plugin as the remedy, after installing it when it is not installed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
bump: patch
---

### Fixed

- `check` reports a user or repository profile file it cannot read, naming the file, and checks the other levels instead of stopping; a shipped profile it cannot read still stops the check with the file named.
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
bump: patch
---

### Fixed

- The `## Next` operative-phrasing check also flags `are enabled` and a negated gate (`is not enabled`, `when not enabled`).
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
bump: patch
---

### Changed

- `/verification:confirm` runs the project's own build, test and lint commands when the `toolchain` plugin is not enabled, and its report names `claude plugin enable toolchain`, preceded by `claude plugin install toolchain` when it is not installed.
19 changes: 11 additions & 8 deletions plugins/autonomy/reference/routines/drift-delta-sweep.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,10 @@ prerequisite ([guardrail contract](../guardrails.md)).

- **Advisory report.** One report per run, carrying one section per lane, a **coverage line**
naming which enforcement-surface layers and which audit dimension this cycle walked, and a
"lanes not run" section naming each absent or blocked lane and why it did not run.
"lanes not run" section naming each lane whose plugin is not enabled or that was blocked, and
why it did not run. For a plugin that is not enabled, the remedy it names is the host's
plugin enable command, preceded by its plugin install command when the plugin is not
installed.
- **Work items.** Filed through the governed queue for movement whose correction needs
authorial judgment.

Expand All @@ -60,20 +63,20 @@ is what has to justify it.
## Fan-out

The class's instruction content: three lanes, invoked in this order. Each names the plugin
that owns it, is gated on that plugin's presence at the point of invocation, and states its
that owns it, is gated on that plugin being enabled at the point of invocation, and states its
fallback in the same sentence.

1. **The instruction-placement delta lane.** Invoke `/instruction-placement:delta` when the
`instruction-placement` plugin is enabled; where it is absent, record the lane as not run
and continue. The lane owns what moved in the instruction-placement findings since its own
`instruction-placement` plugin is enabled; where it is not enabled, record the lane as not
run and continue. The lane owns what moved in the instruction-placement findings since its own
last run. Bootstrap rule: where the lane reports no prior artifact to compare against,
invoke `/instruction-placement:audit` instead, which is read-only apart from writing its own
findings artifact, so the next cycle has a baseline, and record the cycle as a bootstrap
in the coverage line.

2. **The enforcement-surface delta lane.** Invoke `/overengineering:delta` with `--unattended`
and the cycle's two layers when the `overengineering` plugin is enabled; where it is
absent, record the lane as not run and continue. The lane owns what moved in the
and the cycle's two layers when the `overengineering` plugin is enabled; where it is not
enabled, record the lane as not run and continue. The lane owns what moved in the
enforcement surface since its own last run. The layer pair rotates on the ISO week number,
read with `date -u +%V`; the pair index is (ISO week − 1) mod 5:

Expand All @@ -90,7 +93,7 @@ fallback in the same sentence.

3. **The repository drift audit lane.** Invoke `/codebase-health:audit` without `--fix` and
with exactly one dimension flag when the `codebase-health` plugin is enabled; where it is
absent, record the lane as not run and continue. The lane owns the full drift pass over
not enabled, record the lane as not run and continue. The lane owns the full drift pass over
documentation, configuration, code, and architecture claims; it is a full pass every cycle
and never a delta. The dimension rotates on the same ISO week number; the dimension index
is (ISO week − 1) mod 4:
Expand Down Expand Up @@ -162,5 +165,5 @@ escalation rules.
The proven manual pattern at class level is the operator-run cadence pass over report-only
drift detectors: report-only drift-watch rows already carried in a consumer's recurring
schedule, and the recurring-wiring guidance the enforcement-surface lane gives for its own
repeat runs. Said plainly: no run record exists yet for these three lanes together. The `v1`
repeat runs. No run record exists yet for these three lanes together. The `v1`
status rests on the class-level pattern, not on a logged run of this fan-out.
Original file line number Diff line number Diff line change
Expand Up @@ -15,26 +15,17 @@ graders:
input_match: '"command"\s*:\s*"(?=(?:[^"\\]|\\.)*?profiles\.mjs)(?:[^"\\]|\\.)*?(?:profiles\.mjs|\$\{?[A-Za-z_][A-Za-z0-9_]*\}?)(?:\\"|'')?\s+usage\b'
min: 1
arm: 'with-only'
- name: save-previewed
- name: per-hook-question-asked
type: regex
target: last_message
flags: 'i'
pattern: '^(?=[\s\S]*notes-hooks)[\s\S]*?(?:always[ -]on[^.?!\n]*\bor\b[^.?!\n]*per[ -]profile[^.!\n]*\?|per[ -]profile[^.?!\n]*\bor\b[^.?!\n]*always[ -]on[^.!\n]*\?)'
Comment thread
kyle-sexton marked this conversation as resolved.
Resolved
- name: no-profile-saved-before-answer
type: tool_used
tool: 'Bash'
input_match: '"command"\s*:\s*"(?=(?:[^"\\]|\\.)*?profiles\.mjs)(?:[^"\\]|\\.)*?(?:profiles\.mjs|\$\{?[A-Za-z_][A-Za-z0-9_]*\}?)(?:\\"|'')?\s+save\s+docs\b(?:[^"\\;&|]|\\[^n])*?--dry-run\b'
min: 1
arm: 'with-only'
- name: save-written-at-user-level
type: tool_used
tool: 'Bash'
input_match: '"command"\s*:\s*"(?=(?:[^"\\]|\\.)*?profiles\.mjs)(?:[^"\\]|\\.)*?(?:profiles\.mjs|\$\{?[A-Za-z_][A-Za-z0-9_]*\}?)(?:\\"|'')?\s+save\s+docs\b(?=(?:[^"\\;&|]|\\[^n])*?--level\s+user\b)(?=(?:[^"\\;&|]|\\[^n])*?--yes\b)'
min: 1
arm: 'with-only'
- name: save-previewed-before-written
type: tool_order
before:
tool: 'Bash'
input_match: '"command"\s*:\s*"(?=(?:[^"\\]|\\.)*?profiles\.mjs)(?:[^"\\]|\\.)*?(?:profiles\.mjs|\$\{?[A-Za-z_][A-Za-z0-9_]*\}?)(?:\\"|'')?\s+save\s+docs\b(?:[^"\\;&|]|\\[^n])*?--dry-run\b'
after:
tool: 'Bash'
input_match: '"command"\s*:\s*"(?=(?:[^"\\]|\\.)*?profiles\.mjs)(?:[^"\\]|\\.)*?(?:profiles\.mjs|\$\{?[A-Za-z_][A-Za-z0-9_]*\}?)(?:\\"|'')?\s+save\s+docs\b(?=(?:[^"\\;&|]|\\[^n])*?--level\s+user\b)(?=(?:[^"\\;&|]|\\[^n])*?--yes\b)'
input_match: '"command"\s*:\s*"(?=(?:[^"\\]|\\.)*?profiles\.mjs)(?:[^"\\]|\\.)*?(?:profiles\.mjs|\$\{?[A-Za-z_][A-Za-z0-9_]*\}?)(?:\\"|'')?\s+save\b(?=(?:[^"\\;&|]|\\[^n])*?--yes\b)'
min: 0
max: 0
arm: 'with-only'
- name: no-hand-written-profile
type: tool_used
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,4 +3,4 @@ type: llm
focus: trace
---

The reply or the conversation names notes-hooks as a plugin that ships hooks and settles, for that plugin, whether it is always on or per profile (asked, or recorded from the user's stated answer), and says the profile docs was saved as a user-level file under ~/.claude/plugin-profiles/ (or the configuration folder's plugin-profiles folder). It lists the installed plugins with their skills (notes-hooks with jot, draw with sketch).
The user's message never says whether notes-hooks is always on or per profile. Pass only when the assistant lists the installed plugins with their skills (notes-hooks with jot, draw with sketch), names notes-hooks as a plugin that ships hooks, and asks the user, in its reply, whether notes-hooks is always on or per profile, and no profile is saved with --yes before the user answers. Fail when the assistant records an always-on or per-profile choice for notes-hooks that the user never gave, treats the question as answered, saves any profile with --yes, or ends without asking it.
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
description: "AC15, AC25. The scaffold adds the local marketplace fixture-market to the run's temporary home and installs notes-hooks (ships a SessionStart hook, skill jot) and draw (skill sketch). Setup should run the CLI's inventory and usage commands, settle per-profile for notes-hooks, preview the save of profile docs with --dry-run, then save it with --level user --yes on the stated yes. The slash prompt loads the skill without a Skill call, so no skill-fired grader; the CLI graders are with-only (the CLI ships only with the plugin) and match the script path however it is spelled; no-hand-written-profile fails a profile file written with the Write tool. This case cannot run in the claude plugin eval sandbox today: the run's configuration directory is write-denied there, and the nested claude that inventory and install call is not reachable. It is kept for when the harness allows nesting; the behavior is proven by headless claude -p sessions and, for install, by scripts/install-real-claude.test.mjs instead. Needs --scaffold --allow-tools Bash Skill Write."
description: "AC25. The scaffold adds the local marketplace fixture-market to the run's temporary home and installs notes-hooks (ships a SessionStart hook, skill jot) and draw (skill sketch). The prompt answers the work interview and declines the recording offer but leaves the per-hook choice open, so one headless session shows setup running inventory and usage, then ending its turn on the question whether notes-hooks is always on or per profile, with no profile saved. per-hook-question-asked reads the final reply; no-profile-saved-before-answer fails any save run with --yes; no-hand-written-profile fails a profile file written with the Write tool. The slash prompt loads the skill without a Skill call, so no skill-fired grader; the CLI graders are with-only (the CLI ships only with the plugin) and match the script path however it is spelled. This case cannot run in the claude plugin eval sandbox today: the run's configuration directory is write-denied there, and the nested claude that inventory calls is not reachable. It is kept for when the harness allows nesting; the behavior is proven by a headless claude -p session instead. Needs --scaffold --allow-tools Bash Skill Write."
tags: [plugin-profiles, profile, setup, outcome]
runs: 1
max_turns: 30
timeout_seconds: 600
allowed_tools: [Skill, Bash, Read, Write, AskUserQuestion]
expected_outcome: "Setup lists notes-hooks and draw with their skills, records notes-hooks as per profile, previews profile docs, then saves it at user level through the CLI."
allowed_tools: [Skill, Bash, Read, Write]
expected_outcome: "Setup lists notes-hooks and draw with their skills, then asks whether notes-hooks is always on or per profile and stops there, saving nothing."
---

/plugin-profiles:profile setup

I write documentation and sometimes sketch diagrams. My answers up front, so you need not ask: notes-hooks is per profile, not always on. Make one profile named docs at user level holding notes-hooks and draw, described as "Write docs and sketch diagrams." Yes, save it once you have shown me the file.
I write documentation and sometimes sketch diagrams; building docs is my only phase, with no exploring, planning, reviewing, interface design or harness upkeep. No session recording for now. I want one profile named docs at user level, described as "Write docs and sketch diagrams."
Original file line number Diff line number Diff line change
@@ -1,11 +1,14 @@
{
"pass": [
{
"answer": []
},
{
"answer": [
{
"tool": "Bash",
"input": {
"command": "node \"/opt/plugins/plugin-profiles/scripts/profiles.mjs\" save docs --level user --description \"Write docs and sketch diagrams.\" --plugins notes-hooks@fixture-market,draw@fixture-market --dry-run",
"command": "S=\"/opt/plugins/plugin-profiles/scripts/profiles.mjs\"; node \"$S\" inventory --json; echo ---; node \"$S\" usage --json",
"description": "Run the profile tool"
}
}
Expand All @@ -16,52 +19,50 @@
{
"tool": "Bash",
"input": {
"command": "S=\"/opt/plugins/plugin-profiles/scripts/profiles.mjs\"; node \"$S\" save docs --level user --plugins notes-hooks@fixture-market,draw@fixture-market --description \"Write docs and sketch diagrams.\" --dry-run; echo \"exit $?\"",
"command": "node \"/opt/plugins/plugin-profiles/scripts/profiles.mjs\" save docs --level user --plugins draw@fixture-market --dry-run",
"description": "Run the profile tool"
}
}
],
"why": "script path held in a shell variable"
"why": "a preview writes nothing"
}
],
"fail": [
{
"answer": []
},
{
"answer": [
{
"tool": "Bash",
"input": {
"command": "node \"/opt/plugins/plugin-profiles/scripts/profiles.mjs\" save docs --level user --plugins draw@fixture-market --yes",
"command": "node \"/opt/plugins/plugin-profiles/scripts/profiles.mjs\" save docs --level user --plugins notes-hooks@fixture-market,draw@fixture-market --yes",
"description": "Run the profile tool"
}
}
],
"why": "written without a preview"
"why": "saved on a per-hook answer the user never gave"
},
{
"answer": [
{
"tool": "Bash",
"input": {
"command": "S=\"/opt/plugins/plugin-profiles/scripts/profiles.mjs\"; node \"$S\" save docs --level user --yes; node \"$S\" list --dry-run",
"command": "S=\"/opt/plugins/plugin-profiles/scripts/profiles.mjs\"; node \"$S\" save always-on --level user --plugins notes-hooks@fixture-market --yes",
"description": "Run the profile tool"
}
}
],
"why": "--dry-run belongs to a later command, not the save"
"why": "always-on saved on a guess, script path in a variable"
},
{
"answer": [
{
"tool": "Bash",
"input": {
"command": "node \"/opt/plugins/plugin-profiles/scripts/profiles.mjs\" apply docs --for folder --dry-run",
"command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/profiles.mjs save docs --yes --level user",
"description": "Run the profile tool"
}
}
]
],
"why": "--yes before --level"
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
{
"pass": [
{
"answer": "Installed: notes-hooks (jot) and draw (sketch).\n\nnotes-hooks ships a SessionStart hook. Should notes-hooks be always on, in every session, or per profile, loaded only by the profiles you add it to?"
},
{
"answer": "**notes-hooks** runs a hook at session start. Per profile or always on for it?",
"why": "the two choices in the other order"
},
{
"answer": "Phase 4 of 7. notes-hooks ships hooks: do you want it **always-on** or **per-profile**?",
"why": "hyphenated choices, markdown bold"
}
],
"fail": [
{
"answer": ""
},
{
"answer": "Saved docs at ~/.claude/plugin-profiles/docs.yaml. As you said, notes-hooks is per profile, not always on. Want me to apply docs to this folder?",
"why": "the per-hook answer was given up front and recorded, the question was never asked"
},
{
"answer": "Recorded notes-hooks as per profile rather than always on, since you only build docs. Shall I preview the docs profile?",
"why": "the answer guessed instead of asked"
},
{
"answer": "Which phases do you work in: exploring, planning, building or reviewing?",
"why": "a different question"
},
{
"answer": "Should draw be always on or per profile?",
"why": "asks about a plugin that ships no hooks"
}
]
}

This file was deleted.

Loading
Loading