@agentsfleet/orly 0.11.0 → 0.12.0

package/README.md

@@ -42,22 +42,26 @@ Works with Claude Code, Codex, OpenCode, and Amp.
 
 ---
 
-## 0.11.0 experiment: explicit Jev advice
+## 0.12.0: migration verification
 
-The Bun command line adds `orly judge` for selected planning, test, review and
-documentation questions.
+0.12.0 is a local release candidate. Published 0.11.0 already provides the
+`.orly/` layout and the six existing `orly judge` questions.
+This release focuses on package verification, migration evidence and clearer setup guidance; it adds no new runtime judgment question.
 
-- **Judgments** — selected evidence produces a fixed next action; existing checks retain control of gate results.
-- **Installation** — `bunx` runs the source package through Bun, continuing the `0.10.x` setup on macOS and Linux.
+The `agentsfleet` trial upgraded a dedicated worktree from 0.10.14 using the packed candidate.
+Owner files, hooks and verification commands survived; a second update wrote nothing.
+See the [release report](evals/release/release-report.md) for exact proof and remaining release checks.
 
-Use `orly judge --help` and the [judgment reference](docs/JUDGMENTS.md) for the
-manifest, atomic criteria and explicit source upload. This page describes the
-0.11.0 source package, which is not yet published. The commands below fetch the
-published package; use them for this behavior after 0.11.0 is published.
+Jev, TypeSafe's bounded judgment model, supplies advice only when requested.
+Existing deterministic checks retain control of gate results.
+The comparison evaluator is parked for proposed 0.13 work; model accuracy and candidate benefits remain unmeasured.
+See the [judgment reference](docs/JUDGMENTS.md) for evidence selection, offline replay and explicit source upload.
+
+The install commands below fetch the published package. They do not select this unpublished candidate.
 
 ---
 
-## Prerequisites for 0.11.0
+## Prerequisites
 
 | You need | Why | Version |
 |---|---|---|
@@ -71,7 +75,7 @@ published package; use them for this behavior after 0.11.0 is published.
 
 ---
 
-## Install 0.11.0 after publication
+## Install the published package
 
 Run this inside the repository you want governed.
 
@@ -120,6 +124,32 @@ Unknown settings and malformed values are refused; `schemas/profile.schema.json`
 
 ---
 
+## Upgrade from 0.10.x
+
+Run the update from the consumer repository. If the repository owns its hooks, preserve them explicitly:
+
+```bash
+bunx --bun @agentsfleet/orly update --no-hooks
+```
+
+Expected: managed files move under `.orly/`; owner hooks remain unchanged. Conflicting owner edits stop the update and name the affected path.
+Use the installed candidate executable for an unpublished release trial; the command above fetches the published version.
+
+Update repository-owned callers that still read `.oracle/orly.json`, root `dispatch/`, or managed root audit paths.
+Their replacements are `.orly/orly.json`, `.orly/dispatch/`, and `.orly/audits/`.
+Repository-owned audit scripts and project documents retain their existing locations.
+Review existing hooks before choosing an update without `--no-hooks`.
+
+```bash
+bunx --bun @agentsfleet/orly doctor
+```
+
+Expected: installed rules match `.orly/orly.json` and work and verification commands are declared.
+Then run the repository's declared checks; `doctor` alone does not run them.
+An empty old directory can remain after its files move. Git does not track empty directories; remove one only after checking it is empty.
+
+---
+
 ## What lands in your repository
 
 ```text

package/docs/CHANGELOG.md

@@ -0,0 +1,10 @@
+# Changelog
+
+## 0.12.0 — unreleased
+
+Setup guidance now distinguishes the published package from the local release candidate.
+
+- **Migration guidance** — names `.orly/` destinations and explains preserving repository-owned hooks with `--no-hooks`.
+- **Release scope** — retains the six existing judgment questions and records the comparison evaluator as parked for proposed 0.13 work.
+
+The `.orly/` layout and judgment commands already shipped in 0.11.0; this entry claims no new runtime behavior.

package/docs/JUDGMENTS.md

@@ -1,8 +1,8 @@
 ---
 type: reference
 audience: contributor
-verified: 2026-10-04
-product_version: 0.11.0
+verified: 2026-10-07
+product_version: 0.12.0
 executable: false
 ---
 
@@ -10,6 +10,9 @@ executable: false
 
 ## Synopsis
 
+The 0.12.0 candidate retains the six questions shipped in 0.11.0.
+The comparison evaluator is parked for proposed 0.13 work; this release makes no new model-quality claim.
+
 `orly judge` asks one bounded question about evidence you select.
 It accompanies planning, verification, review and documentation.
 Its answer suggests an inspection or a fixed next action.

package/llms.txt

@@ -12,9 +12,11 @@ Package: `@agentsfleet/orly` (npm)
 Source: https://github.com/agentsfleet/orly
 License: Massachusetts Institute of Technology (MIT)
 
-This guide describes the unpublished 0.11.0 source package. The `bunx` commands
-below fetch the published package, not this source checkout. Use this install
-sequence for the described behavior after 0.11.0 is published.
+This checkout prepares the unpublished 0.12.0 candidate. Published 0.11.0 already
+contains the same runtime commands and `.orly/` layout. The `bunx` commands below
+fetch the published package. Use the installed local tarball for candidate checks.
+The comparison evaluator is parked for proposed 0.13 work; do not claim measured
+judgment improvement or enable new questions from its unfinished results.
 
 ---
 
@@ -79,6 +81,13 @@ suites. `init` reports missing configuration; `doctor` rejects it.
 
 ---
 
+For a 0.10.x consumer with repository-owned hooks, run `orly update --no-hooks`
+using the intended installed version. Change repository callers from
+`.oracle/orly.json` to `.orly/orly.json` and shared rule/audit paths to `.orly/`.
+Keep repository-owned scripts and documents in place. Run `orly doctor` and the
+declared checks before accepting the migration; doctor alone does not run checks.
+Empty old directories may remain, but contain no tracked managed files.
+
 ## 4. Read order before you edit anything
 
 1. `AGENTS.md` — the user's own rules. **These win on any conflict.**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentsfleet/orly",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "Repository-scoped engineering harness: renders agent rules, materialises the gates that enforce them, and proves the PR boundary \u2014 for any coding agent.",
   "license": "MIT",
   "type": "module",