docs: release v1.1.0 — the packaged install by default, checked in real sessions

[mauricios]

What changed and why

v1.1.0, a minor release (decision 0017): a new default for new projects, and evals for the packaged install. Nothing asks anything of an adopted team.

• CHANGELOG.md: Unreleased becomes ## v1.1.0 — 2026-10-04 — The packaged install by default, checked in real sessions, covering:

  • feat: the plugin-hooks session eval — the plugin's hooks in real sessions #29: the plugin's hooks, checked in real sessions;
  • feat: evals for the packaged install's two ways in; /upgrade stamps the release's commit #30: evals for adopting on the packaged install and switching to it, plus the /upgrade stamp fix they found;
  • feat: the packaged install is the default (decision 0018) #31: the packaged install as the default (decision 0018);
  • the fix below.

  It opens with a short note on upgrading from v1.0.x.

• plugin.json: 1.1.0. The README and the plugin README's pinned-entry example name the release.

One more fix: /aplyca-adf:adopt takes the framework at the release it pins. It used to copy the skeleton from wherever the framework source was (a clone of the default branch, or a checkout) while pinning the plugin to the newest release tag. A project's committed files could then be newer than its pinned plugin, which matters more now that packaged is the default. The packaged eval in #30 found this. Step 1 now:

1. finds the newest release tag;
2. takes the framework at that tag, from a shallow clone of the tag or a worktree of a local checkout;
3. records that tag's commit for the stamp.

docs/SETUP.md's manual copy says the same, and a static check holds it.

Upgrade impact

None for adopted projects. /aplyca-adf:upgrade moves the pin to v1.1.0, and recommends the switch to packaged to a committed project whose team works in Claude Code only.

How to verify

• ./evals/run-evals.sh: the version check matches 1.1.0 against the heading.
• ./evals/dynamic/run-session-evals.sh --suite adopt --cases packaged --models sonnet.

Verified / not verified

• Verified:
  • Static suites pass: 154, 81, 45, and 11.
  • git clone --depth 1 --branch v1.0.6 gives commit ab56cb6.
  • The packaged adopt eval, rerun on Sonnet: 8 of 8, $1.30. The session set the framework up at v1.0.6 in a scratch worktree, stamped ab56cb6, and recommended packaged first. The run is added to the 2026-10-04-packaged-paths report.
• Not verified:
  • An adoption that pins v1.1.0, which doesn't exist until the tag is pushed. The new project is the first.

Merge danger

• Release notes, a version number, and /adopt's Step 1. A revert is safe.
• Tag v1.1.0 right after the merge, before the new project adopts, so it pins this release.

🤖 Generated with Claude Code