chore(changesets): normalize non-breaking bumps to patch per the pre-1.0 rule

[ScriptedAlchemy]

Summary

Audit of every .changeset/*.md on main against the pre-1.0 semver rule in AGENTS.md / .changeset/README.md (minor = breaking, patch = everything else including new features).

117 changesets carried a minor bump. 98 of them describe additive work (new commands, exports, subpaths, config keys, capability rows, proof levels, host adapters, diagnostics for new features, or fixes/loosened validation) and are normalized to patch. 19 keep minor because their text or PR describes a breaking change:

changeset	why it stays minor
canonical-component-kinds	explicit: inspect --json kind/name fields change for event routes
component-feature-sets	previously accepted commands/rules now fail the build (AB4927/AB4907)
evidence-backed-capability-states	replaces the Boolean adapter capability record shape
framework-mode-agent-bundle, framework-mode-rsc-runtime	feat! PR #67; runtime removes the structural JSX layer
notice-inbox-resource-updated (runtime)	AgentNoticeLedger gains required methods (explicit "breaking")
portable-normative-rules-fail-closed	previously publishable portable bundles now fail the build
remove-vendored-inspector	removes the vendored Inspector surface from the Workbench
rename-rsc-runtime-package	package rename
rendered-cli-stage3	retires diagnostic AB4816 (removed diagnostic code)
required-provider-fixtures	explicit "breaking for provider-enabled projects"
rsc-mcp-listing-title-meta	stops synthesizing annotation defaults — wire-visible change for unchanged operations
runtime-app-reload-channel	removes webSocketOrigin/webSocketPath/webSocketToken fields
script-dispatch-and-workbench-surface (agent-bundle)	AgentBundleTestManifest.scripts becomes required
shared-route-layouts	explicit "Breaking for typed consumers" + decodeAgentDocument behavior change
skills-under-src	top-level conventional documents are no longer discovered (AB4736)
strip-capability-self-pins	removes/renames public fields
create-agent-bundle-scaffolder, fresh-runtimes-curate	first publishable version of a 0.0.0 package (0.1.0)

Judgment calls applied consistently: a fix:-typed PR is patch unless its text names a removal; validation that newly loosens is patch; validation that newly fails a previously accepted project is minor; adapter-revision bumps that only change emitted output for a rebuild are patch.

Effect on the Version Packages PR (#411)

Resulting versions are unchanged — pnpm changeset status --verbose still reports agent-bundle -> 0.2.0, @agent-bundle/runtime -> 0.1.0, create-agent-bundle -> 0.1.0 — because each package keeps at least one genuine minor. What changes is the CHANGELOG that #411 regenerates on its next refresh: the 98 normalized entries move from Minor Changes to Patch Changes, so the breaking entries are readable on their own. #411 is machine-owned and will pick this up on merge; do not edit it by hand.

Evidence

• pnpm changeset status --verbose → exit 0, versions above (/tmp/final-sweep/changeset-status.txt).
• git diff --stat: 98 files, frontmatter-only changes (minor → patch); no summaries edited.

Test plan

• pnpm changeset status --verbose passes and reports the same target versions as before.
• CI: Changeset present (no publishable package changed; passes without a changeset).

Review status

• @codex review requested at 16:32 UTC for head 122c3731555fd024cb8176153e77dac17026891b; the connector answered usage limits reached (maintainer credits exhausted). Unreviewed SHA: 122c3731555fd024cb8176153e77dac17026891b. Merged on CI green per the quota fallback in AGENTS.md; changesets-only diff (no source changes).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 122c373

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 2 packages

Name	Type
agent-bundle	Patch
@agent-bundle/runtime	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[ScriptedAlchemy]

@codex review

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[pkg-pr-new]

npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle@429

npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/create-agent-bundle@429

npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/@agent-bundle/runtime@429

commit: 122c373