Papertiger 0.19.0

Planner schema v13 and Mise schema v10 are unchanged; no init is needed.
Verify the archive against its published .sha256, then upgrade a project by unpacking the archive over the project root or by running setup-project from the new release binary, and a personal installation with setup-user.
Scripts that pass --replace-managed or check setup result schemas need updating.

Added

• --project-root <root> selects an existing <root>/state/papertiger.sqlite when the root has neither a project-install receipt nor a release bundle, so a personal installation can reach a project's planning history without a committed Papertiger integration.
  It still refuses when that file is absent, and discovery without --project-root still uses only receipts and bundles.

Changed

• Installed skills, the project reference and installed binaries are release files: setup-project and setup-user overwrite them with the release version, and uninstall-project/uninstall-user remove them, whether or not they were edited.
  Keep project-specific guidance in AGENTS.md or CLAUDE.md, which setup never touches.
• Binaries are verified once, at download, against the release's .sha256 file; Papertiger no longer hashes installed binaries when it runs.
  Project discovery, --project-root, release bundles and the personal runtime check only that the receipt or manifest names the running release (and, for the personal runtime, its home), and each refusal names the command that fixes it.
  setup-project still replaces an installed binary that differs from the release binary running it.
• setup-project no longer writes the host-local tools/papertiger/bin/papertiger[.exe].runtime-install.json receipt, and removes one left by an earlier release.
  Its result no longer has runtime_receipt_path or runtime_install, and uninstall-project no longer lists that receipt.
• init --json names init's plain-text report in its refusal instead of the generic "no JSON projection" message.
• The project reference installed as tools/papertiger/agent_integration.md teaches planning use only; installation, upgrade and removal are in the README and --help.
• Project receipts are papertiger.project_install.v3 and personal receipts papertiger.user_install.v2; neither records file or binary hashes.
  The next setup-project or setup-user rewrites a v2 project or v1 personal receipt.
  An older receipt is refused: move it aside and rerun setup to reinstall.
• setup-project reports papertiger.project_install_result.v7, uninstall-project reports papertiger.project_uninstall.v3 and setup-user reports papertiger.user_setup.v2; update scripts that check these schemas.
  The uninstall result's only refusal action is non_file_refusal, for a symlink or non-regular file at an owned path; it replaces modified_refusal.
• Mise refuses an unrecognized schema or protocol id by naming the id it expects.
  papertiger_mise::schema_ids is no longer public.
• Mise command messages consistently say "paired execution" (for example paired recover on an unknown id), and refusals raised by the authority's own integrity checks no longer end with a raw SQLite error code.

Removed

• --replace-managed on setup-project and setup-user.
• Cleanup of files from pre-receipt project installations and release bundles with a papertiger.release_manifest.v1 manifest; reinstall such a project with setup-project from this release.

Fixed

• setup-project no longer reports a successful upgrade that leaves the project unusable.
  When tools/papertiger/manifest.json from an unpacked release archive names another release or cannot be read, setup-project and --dry-run now refuse before writing anything.
  Before this fix, setup exited 0 and every later command refused the manifest.
  To upgrade such a project, unpack the new release archive over the project root, or move the manifest aside and rerun setup-project.
  A custom authority path stays selected either way.

Prebuilt archives are attached for Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS.
Merge .agents, .claude, and tools into the project root. Skills are ready to discover; executables, documentation, licenses and the source manifest live under tools/papertiger.
Verify the adjacent SHA-256 asset before extraction.