release: PRFlow v2.37.0 — publish as a generated distribution tree

[The01Geek]

Release v2.37.0 — publish PRFlow as a generated distribution tree

This pull request replaces the tracked tree on main with a deterministic,
verified projection of the plugin. Development has moved to a private canonical
repository; this repository becomes the release and distribution point.

Nothing consumers depend on changes. Install commands, marketplace name, plugin
name, command names, repository URL and every root-relative runtime path are
identical. Existing installations and version pins keep working.

Why the diff is unreviewable file-by-file, and what to read instead

This removes 768 files, so GitHub will truncate the diff. Review the summary below
instead — and verify the artifact yourself rather than trusting this description.

Removed, by class

Files	Class
539	test suite (lib/test/)
124	internal maintainer documentation
54	logs
29	repo-local prompt extensions
12	development CI and probe workflows
5	root development files (CLAUDE.md, CHANGELOG.md, requirements.txt, ruff.toml, dev config)
3	learnings corpus
2	changesets, editor state

None of it is reachable from a consumer installation. The two consumer workflows
and all three composite actions stay — they are distribution assets.

Added

Six files: .release/source.json, .release/files.sha256, docs/README.md,
and three runtime files from this release's own changes
(lib/repo-identity.{json,sh}, scripts/migrate-record-repo.py). A further 27
files are modified, chiefly docs/ship-pr.png moving out of docs/internal/
and the version pins.

The verification workflow and its verifier are not added here — they already
landed on main in a separate preparatory pull request, and this branch carries
them byte-identical to base. That is what lets this candidate be judged by a
verifier it cannot modify.

docs/README.md is load-bearing, not a placeholder: every released version of the
vendoring action copies a fixed set of root members — .claude-plugin agents docs lib scripts skills LICENSES — before pruning. Removing docs/ would break already
installed consumers before they reach their own prune.

Verify it yourself

The tree carries its own integrity data, so this description needs no trust:

python3 .github/verify-release.py --candidate <a checkout of this branch>

That re-derives every file's SHA-256 from .release/files.sha256 and re-runs every
structural gate.

Evidence

• Reproducible: exporting the same source commit twice yields byte-identical
  trees and the same artifact digest.
• Refusal fixtures: 4 exporter, 18 verifier, and 7 stager cases fail closed,
  including three injected mid-operation failures that leave HEAD unchanged.
• Ancestry: this commit has exactly one parent — the previous public main —
  and no private development commit is reachable from any public ref.
• Compatibility: every supported historical vendoring generation (v2.29.0
  onward) vendors successfully from this tree. Generations older than v2.29.0 fail
  identically against today's main; they were broken by an earlier state-directory
  rename, not by this change, and the fix for them is re-running install.sh.
• Install and upgrade: fresh marketplace install, plugin- and marketplace-mode
  validation, install.sh in thin and committed-vendor modes, local-edit
  preservation, and a real upgrade from v2.36.19 all pass.
• This upgrade changes no functional consumer artifact. Both shipped workflows
  and all three composite actions are byte-identical to v2.36.19; only three
  provenance files move.

Rollback

Forward-only, by design. A bad release is corrected with a new patch version and a
new tag — never by force-pushing main, moving a tag, or reusing a version. All
prior commits, tags and history remain reachable.

Contributing after this change

Issues remain the supported channel and are unaffected. Patch pull requests are
still welcome; maintainers reproduce accepted changes in the canonical source and
ship them in a subsequent release, crediting the author. See CONTRIBUTING.md.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
pr-flow	🟢 Ready	View Preview	Aug 29, 2026, 7:32 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.