Skip to content

docs(plugins): downgrade forced-compliance emphasis at I28 sites (#4120) - #4622

Merged
cursor[bot] merged 7 commits into
mainfrom
cursor/i28-forced-compliance-downgrade-37e9
Sep 27, 2026
Merged

cursor[bot] merged 7 commits into
mainfrom
cursor/i28-forced-compliance-downgrade-37e9

Conversation

@kyle-sexton

@kyle-sexton kyle-sexton commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Closes #4120

Summary

Downgrades forced-compliance emphasis at live I28 rows (directive kept; all-caps / MANDATORY / Critical markers removed). 30 of 36 editable rows applied; six already fixed on main; four out of scope per issue.

Fix

Twelve plugins patched including the residual babysit-prs loop MANDATORY drop. Versions above main tip at last merge (ai-briefing 0.7.41, planning 0.44.2, source-control 0.61.1, …). Full list in /opt/cursor/artifacts/pr-4120.md.

Verification

Related

Open in Web Open in Cursor 

@cursor
cursor Bot marked this pull request as ready for review September 27, 2026 20:29
@cursor
cursor Bot enabled auto-merge (squash) September 27, 2026 20:29
@cursor
cursor Bot force-pushed the cursor/i28-forced-compliance-downgrade-37e9 branch from 5aaeee1 to 788ace4 Compare September 27, 2026 20:35
cursoragent and others added 3 commits September 27, 2026 20:35
Applies the live rows of the I28 batch from the 2026-09-08 audit-instructions
run across 12 plugins. Each directive survives; only its all-caps or
MANDATORY/Critical marker is removed, per the prompting best-practices
"Tool usage" guidance to dial back aggressive language.

Rows already fixed on main, the two demoted watch items, and the two
frontmatter description rows are left unchanged. Each touched plugin gets a
patch bump and a CHANGELOG entry.

Refs #4120

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
… finding extraction (I28)

Row 1 of the I28 batch (babysit-prs/reference/loop.md, now line 119) was
still live on main. The dispatch rule in review-discipline.md §2 stays.

Refs #4120

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Refs #4120

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
@github-actions

github-actions Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

PR body contract — issue linkage

This PR body conforms to the issue-linkage contract. Nothing to do.

@cursor
cursor Bot force-pushed the cursor/i28-forced-compliance-downgrade-37e9 branch from 788ace4 to 2e01792 Compare September 27, 2026 20:46
cursoragent and others added 2 commits September 27, 2026 20:51
…mpliance-downgrade-37e9

# Conflicts:
#	plugins/ai-briefing/CHANGELOG.md
#	plugins/claude-config/CHANGELOG.md
#	plugins/discovery/CHANGELOG.md
#	plugins/knowledge/CHANGELOG.md
#	plugins/planning/.claude-plugin/plugin.json
#	plugins/planning/CHANGELOG.md
#	plugins/review/CHANGELOG.md

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Applies the live rows of the I28 batch from the 2026-09-08 audit-instructions
run across 12 plugins. Each directive survives; only its all-caps or
MANDATORY/Critical marker is removed, per the prompting best-practices
"Tool usage" guidance to dial back aggressive language.

Rows already fixed on main, the two demoted watch items, and the two
frontmatter description rows are left unchanged. Each touched plugin gets a
patch bump and a CHANGELOG entry.

Refs #4120

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
@cursor
cursor Bot force-pushed the cursor/i28-forced-compliance-downgrade-37e9 branch from 2e01792 to 44fc69b Compare September 27, 2026 20:52
Keeps both 0.61.1 I28 changelog bullets and the babysit-prs MANDATORY drop.

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Re-serialize the I28 plugin bumps above main's tip (ai-briefing 0.7.42,
codebase-health 0.10.2, discovery 0.24.5, docs-hygiene 0.23.3, planning 0.44.3,
review 0.30.8, source-control 0.61.2) and resolve the conflict markers the
previous merge left in plugins/source-control/CHANGELOG.md, filing the
babysit-prs loop entry under 0.61.2.
@cursor
cursor Bot force-pushed the cursor/i28-forced-compliance-downgrade-37e9 branch from 4047acd to 7a43d63 Compare September 27, 2026 21:23
@cursor
cursor Bot merged commit 423f2eb into main Sep 27, 2026
19 checks passed
@cursor
cursor Bot deleted the cursor/i28-forced-compliance-downgrade-37e9 branch September 27, 2026 21:30
cursor Bot pushed a commit that referenced this pull request Sep 27, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
Fixes #4267

## Summary

Takes the fix the issue favours: flip the confidence rank order instead
of banning `low`.

- `plugins/review/context/severity.md` ranks `high` > `medium` > `low` >
`unscored` and labels every finding with the value its evidence
supports.
- `code-reviewer` keeps a `Confidence:` value even when the caller
supplies its own finding shape.
- Detector-findings convention rule 2 unchanged (`high` or omitted);
rationale rewritten. `mutation-testing` 0.4.2 drops the false clause.
New fanout eval 39 covers unscored sorting last.

`review` 0.30.6 → 0.31.0.

## Research trail

- `severity.md` owned the inverted order; fanout/fix-pass defer to it.
- Detector producers cite the unchanged rule, not the order.

## Test plan

- [x] validate-plugins, changed-skills, changelog parity,
detector-findings crosswalk
- [x] `standards-binding.test.sh` PASS=8; markdownlint clean

## Notes

Serialized behind #4624. Open PRs #4622 and #4590 also bump `review`
(version-line only).
<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-ab53da24-b89d-4314-a060-0da474e837e9?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-ab53da24-b89d-4314-a060-0da474e837e9&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
cursor Bot pushed a commit that referenced this pull request Sep 27, 2026
…rable (#4286) (#4637)

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
Fixes #4286

## Summary

`planning:interview` Step 4 named `docs/topics/<slug>/` as the contract
destination but never said the slice is pruned before merge.

- Step 4 gains "Neither slice is a durable home": contract slice pruned
before merge; memory slice never reaches git; lasting content goes to
ADR/spec/tracker.
- `topic-docs.md` contract rows say "pruned before merge".
- New interview eval 24; defenses digests re-pinned (153/153).

`planning` 0.44.1 → 0.44.2 (serialized above #4566).

## Research trail

- `docs/conventions/topic-docs/README.md` Contract-slice lifecycle
(prune with pointer).
- `scripts/check-contract-slice-prune.sh`.

## Test plan

- [x] `interview-defenses.test.sh` PASS=153; `standards-binding.test.sh`
PASS=9
- [x] changelog parity; contract-slice-prune check; markdownlint

## Notes

Open PRs #4628 and #4622 also bump `planning` (version-line only).
<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-ab53da24-b89d-4314-a060-0da474e837e9?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-ab53da24-b89d-4314-a060-0da474e837e9&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
kyle-sexton added a commit that referenced this pull request Sep 29, 2026
…model-invocable /context7:check (#5252)

Refs: #4120
Refs: #4240

## Summary

Two changes to the `context7` plugin from the audit of the unattended
Cursor agent's PRs.

- #4120: PR #4622 removed `even for libraries you "know."` from the
`lookup` philosophy line and shipped it as 0.5.9. #4120's acceptance
criterion left that clause unedited pending a human decision. This
branch returns the clause to the state the issue reserved. The owner
decision (keep the removal or keep the clause) is still open on #4120
and this PR does not settle it.
- #4240: `prerequisites.json` named `/context7:setup check`, but `setup`
sets `disable-model-invocation: true`, so Claude cannot run it.
`/context7:check` is a model-invocable read-only check that follows only
the `check` section of `setup`.

## Fix

- `plugins/context7/skills/lookup/SKILL.md`: the Philosophy line has the
pre-Cursor text back. Nothing else in the file changed, including the
description's blanket trigger.
- `plugins/context7/skills/check/SKILL.md` and `evals/evals.json`: new
skill with the shape of `go-format:check`, plus three evals (hook notice
runs the read-only check, install request is routed not performed,
passing check has no successor).
- `plugins/context7/prerequisites.json`: `check` is now
`/context7:check`.
- `plugins/context7/README.md`, `docs/skill-cheat-sheet.md` (generated):
list the new skill.
- `plugins/context7/.claude-plugin/plugin.json` 0.5.11 to 0.6.0 (new
skill), with a 0.6.0 CHANGELOG entry.
- Cross-group request from `core-docs` (F18): the 0.5.10 CHANGELOG entry
described the claude-ops prerequisites mechanism, not what context7
shipped. It now reads "Declares the `ctx7` CLI in `prerequisites.json`
so `/claude-ops:prerequisites` can report it when missing."
- Cross-group request from `core-docs` (F19): the `lookup`
`**Arguments.**` line ends "Default action is lookup, e.g.
/context7:lookup react "useEffect cleanup"." No behavior change;
recorded in the 0.6.0 entry, no second version bump.

Both use `Refs`, not `Closes`: #4120 needs an owner decision, and #4240
covers other plugins that are still open.
`plugins/playwright/prerequisites.json` still names a human-only check;
no fix group owns that plugin.

## Verification

- `scripts/check-changelog-parity.sh --check --check-order`: pass.
`--check-bump origin/main`: pass.
- `scripts/validate-plugins.sh`: pass (58 setup skills, catalog
validated).
- `scripts/check-prerequisite-probes.test.sh`: 18 cases, 0 failed.
- `scripts/check-changed-skills.sh origin/main`: 2 skills checked, 0
failed (one pre-existing `## Next` warning on `lookup`).
- `scripts/check-skill-leaf-names.sh`,
`scripts/check-skill-count-claims.sh` (24 claims, 0 mismatched),
`scripts/check-skill-portability.sh origin/main`: pass.
- `node scripts/generate-catalog.mjs --check` and `node
scripts/generate-cheatsheet.mjs --check`: in sync.
- `markdownlint-cli2` on the changed markdown: 0 issues.
- `context7` has no test scripts of its own.

## Related

- Audit report: `.work/audit/REPORT.md`, findings #4120 (decision,
medium; row 3b) and #4240 (correctness, low).
- Cross-group requests: `core-docs` (#3574,
`docs/plugin-philosophy.md:690-696` install-cli wording; keep the
heading "Setup is explicit and repeatable" stable), `biome-format` (note
on #4240 that context7 is covered), `claude-ops` (word the
human-only-check note in `prerequisites/SKILL.md` generally),
`firecrawl` (#4120 row at `firecrawl/SKILL.md:126`), `event-storming`
(#4120 row at `agentic-simulation.md:60`, line 60 only).
- Requests not applied: `core-docs` #3574 finding about
`docs/plugin-philosophy.md` (that doc is `core-docs`' file; it becomes
evidence in the #3574 decision packet, and `apply install-cli` stays as
is). `claude-ops` F13 (heads-up): this PR adds the model-invocable
`/context7:check`, so a `claude-ops` `prerequisites/SKILL.md` sentence
saying a setup-skill check is typed by the person is stale for the
context7 row; to be told to the `claude-ops` group in the second pass.
- Recommendation for #4120 (goes in the issue comment): option B, drop
the clause; basis `plugins/context7/skills/lookup/context/update.md:52`.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01EugXnFddtpHcY5gTuyEirB

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

I28 batch: downgrade forced-compliance emphasis in 40 skill-body and agent sites

2 participants