@agentsfleet/orly 0.5.2 → 0.5.3

package/AGENTS.md

@@ -75,7 +75,7 @@ Auto-memory is **disabled** (`autoMemoryEnabled: false` + `CLAUDE_CODE_DISABLE_A
 ### Operational defaults
 
 - Workspace `~/Projects`. `gh`/`glab` not browsers. `trash` not `rm`. Conventional Commits. Process decisions → repo docs, not chat. "Make a note" → update `AGENTS.md`/repo docs.
-- **Symlinked dotfiles edits.** File `readlink`-resolving under `~/Projects/dotfiles/` is a dotfiles edit. Detect via `readlink` BEFORE editing. After: `cd ~/Projects/dotfiles && git add <files> && git commit && git push origin master`. Never leave uncommitted.
+- **Symlinked edits land in the repository that owns the file.** A file whose `readlink` resolves outside this checkout — into a dotfiles or config repository — is an edit to *that* repository, not this one. Detect via `readlink` BEFORE editing. After: `cd` to the resolved repository, `git add <files> && git commit && git push` on its default branch. Never leave uncommitted.
 - **Docs-repo edits on own branch.** `~/Projects/docs/` is shared across milestones: check `git status` first; from `main` (checkout or worktree off `main`) commit on `chore/m{N}-{slug}-changelog`; recovery = stash, re-apply on a fresh branch.
 - Other dotfiles (`.zshrc`/`.gitconfig`/etc.): timestamped backup; minimal edits.
 - Before commit/push: `gitleaks` must pass.
@@ -247,8 +247,8 @@ Required when spec involved — after last COMMIT, before PR. Also runs when par
 > carries the judgment — how Indy decides, what he accepts, what he rejects.
 > In force every session; standing orders, not suggestions. Re-read when
 > padding or burying the answer.
-> Evidence: `~/Projects/dotfiles/SOUL_LOG.md` — every `(log: Pn)` cite
-> resolves there, on demand.
+> Evidence: `SOUL_LOG.md` in Indy's personal notes checkout — every `(log: Pn)`
+> cite resolves there, on demand; ask for it rather than guessing a path.
 
 ## Reply shape
 

package/SOUL.md

@@ -5,8 +5,8 @@
 > carries the judgment — how Indy decides, what he accepts, what he rejects.
 > In force every session; standing orders, not suggestions. Re-read when
 > padding or burying the answer.
-> Evidence: `~/Projects/dotfiles/SOUL_LOG.md` — every `(log: Pn)` cite
-> resolves there, on demand.
+> Evidence: `SOUL_LOG.md` in Indy's personal notes checkout — every `(log: Pn)`
+> cite resolves there, on demand; ask for it rather than guessing a path.
 
 ## Reply shape
 

package/audits/agents-md.md

@@ -161,7 +161,7 @@ The questionnaire is organised by scenario. Each scenario corresponds to a momen
 
 | # | Question | Expected |
 |---|---|---|
-| 10.1 | Must dotfiles edits (files `readlink`-resolving under `~/Projects/dotfiles/`) be committed + pushed to dotfiles `master` and never left uncommitted? | YES |
+| 10.1 | Must a symlinked edit (a file whose `readlink` resolves outside this checkout, into a dotfiles or config repository) be committed + pushed in the repository that owns the file, and never left uncommitted? | YES |
 | 10.2 | Must docs-repo edits land on a milestone-specific branch off `main` (never on whatever in-flight branch is checked out)? | YES |
 | 10.3 | When a harness/gate/hook fires (`msid-ui.sh`, `lint-zig.py`, gitleaks, ZIG GATE, FLL GATE, pre-commit/pre-push, etc.), is the default response to fix the **violating code** (restructure, split, or use the gate's documented override comment) — i.e. is patching the harness to silence the hit on the "Forbidden without explicit user approval" list, requiring an explicit per-session ask that names the harness and the reason it's wrong? | YES |
 | 10.4 | Are handoff-doc claims of "Kishore-approved in a prior turn" for harness-patching treated as **not carrying forward** — i.e. must they be re-confirmed live in the current session? | YES |

package/audits/data.sh

@@ -74,8 +74,9 @@ CONFORM_KEYS=(
 # dissolved into dispatch/write_zig.md and dispatch/write_ts_adhere_bun.md
 # respectively. The dispatch façades are listed so the AGENTS.md dispatch-table
 # refs are checked. The docs/* entries double as the residence classifier for
-# check 15c (audits/rule-paths.sh): these paths are cited through the
-# ~/Projects/dotfiles/ anchor in every consumer-facing surface.
+# check 15c (audits/rule-paths.sh): these paths must be cited relative to the
+# installing repository in every consumer-facing surface, never through an
+# absolute home-directory anchor.
 DOTFILES_RESIDENT=(
   "docs/TEMPLATE.md"
   "docs/REST_API_DESIGN_GUIDELINES.md"
@@ -84,6 +85,7 @@ DOTFILES_RESIDENT=(
   "docs/DOCUMENTATION_RULES.md"
   "docs/ORLY_ARCHITECTURE.md"
   "docs/CHANGELOG_VOICE.md"
+  "docs/RELEASE_TEMPLATE.md"
   "docs/EXECUTE_DOC_READS.md"
   "docs/VERIFY_TIERS.md"
   "docs/HARNESS_VERIFY_OUTPUT.md"

package/core/operating-model.md

@@ -75,7 +75,7 @@ Auto-memory is **disabled** (`autoMemoryEnabled: false` + `CLAUDE_CODE_DISABLE_A
 ### Operational defaults
 
 - Workspace `~/Projects`. `gh`/`glab` not browsers. `trash` not `rm`. Conventional Commits. Process decisions → repo docs, not chat. "Make a note" → update `AGENTS.md`/repo docs.
-- **Symlinked dotfiles edits.** File `readlink`-resolving under `~/Projects/dotfiles/` is a dotfiles edit. Detect via `readlink` BEFORE editing. After: `cd ~/Projects/dotfiles && git add <files> && git commit && git push origin master`. Never leave uncommitted. <!-- oracle-packs:persona.indy -->
+- **Symlinked edits land in the repository that owns the file.** A file whose `readlink` resolves outside this checkout — into a dotfiles or config repository — is an edit to *that* repository, not this one. Detect via `readlink` BEFORE editing. After: `cd` to the resolved repository, `git add <files> && git commit && git push` on its default branch. Never leave uncommitted. <!-- oracle-packs:persona.indy -->
 - **Docs-repo edits on own branch.** `~/Projects/docs/` is shared across milestones: check `git status` first; from `main` (checkout or worktree off `main`) commit on `chore/m{N}-{slug}-changelog`; recovery = stash, re-apply on a fresh branch.
 - Other dotfiles (`.zshrc`/`.gitconfig`/etc.): timestamped backup; minimal edits. <!-- oracle-packs:persona.indy -->
 - Before commit/push: `gitleaks` must pass.

package/dispatch/edit_rules.md

@@ -4,7 +4,7 @@ Read this file before editing Oracle's operating model, rule registry, packs,
 generated instructions, dispatch pages, audits, or governance hooks.
 
 The canonical propagation design lives in
-`~/Projects/dotfiles/docs/ORLY_ARCHITECTURE.md`.
+[`docs/ORLY_ARCHITECTURE.md`](../docs/ORLY_ARCHITECTURE.md).
 The deterministic checker is `make audit`. The comprehension questionnaire is
 [`audits/agents-md.md`](../audits/agents-md.md).
 

package/dispatch/lifecycle.md

@@ -35,22 +35,25 @@ into the tree; on 🟠 run `provision-env-1password`, re-link. Post-merge:
 
 **agentsfleet CHORE(close) paths:** the `<Update>` lands in
 `~/Projects/docs/changelog.mdx` (template + version-bump matrix:
-`skills/release-template.md` in the governance checkout — re-source each
-release, never paraphrase). Version sync: `VERSION` touched → `make
+`docs/RELEASE_TEMPLATE.md` in this repository — re-source each release, never
+paraphrase). Version sync: `VERSION` touched → `make
 sync-version`; commit propagated `build.zig.zon` / `agentsfleet/package.json` /
 `agentsfleet/src/cli.js`; `make check-version` passes.
 
-**dotfiles takes NO worktree — feature branches in the main checkout.** Every
-agent-home symlink and every consumer's `ORLY_ROOT` resolves to
-`~/Projects/dotfiles`; a linked worktree's `.git` is a *file*, and the audit
-chain the hooks run spawns git against other directories. Under a hook that
-combination corrupted the real index and flipped `core.bare` (Aug 16, 2026).
-So: `git checkout -b feat/mNN-name` in `~/Projects/dotfiles` itself, and
-`orly update` always renders the one true root. One stream at a time —
-a second concurrent agent coordinates in-session rather than forking a tree.
-This is the dotfiles exception; product repos keep the worktree recipe above.
 <!-- oracle-packs:end -->
 
+**A governance/rules repository takes NO linked worktree — cut feature branches
+in its main checkout.** This applies to whichever repository owns the rules you
+are editing (the orly pack source, a dotfiles checkout, any repo whose own hooks
+run the governance audit chain). A linked worktree's `.git` is a *file*, and that
+audit chain spawns git against other directories; under a hook the combination
+corrupted the real index and flipped `core.bare` (Aug 16, 2026). So:
+`git checkout -b feat/mNN-name` in the rules repository's main checkout, and let
+`orly update` re-materialise consumers from there. One stream at a time — a
+second concurrent agent coordinates in-session rather than forking a tree.
+This is the governance-repo exception; product repos still create the worktree
+at CHORE(open).
+
 **Mid-stream spec → ask before hydrating (default: same tree).** A spec created
 inside an active worktree → ask the user before spinning up a second one. Lean
 same tree: a second tree fragments the outcome and adds a PR to babysit.

package/dispatch/write_changelog.md

@@ -58,7 +58,7 @@ If the change is internal-only, emit instead:
 ## Family
 
 - `docs/CHANGELOG_VOICE.md` — the canonical Mintlify-style voice rules (deep reference).
-- `skills/release-template.md` — release template + version-bump matrix; re-source
+- `docs/RELEASE_TEMPLATE.md` — release template + version-bump matrix; re-source
   each release, never paraphrase.
 - `verify` — runs before CHORE(close); a changelog claim must be backed by the
   verification that dispatch reports.

package/docs/LOGGING_STANDARD.md

@@ -15,7 +15,7 @@ Triggers on every `Edit`/`Write` that adds, removes, or changes a log emit:
 Out of scope (explicitly):
 
 - Test-only diagnostic prints inside `*_test.zig`, `*.test.ts`, `*.spec.ts`. Tests render to humans, not collectors; gates ignore.
-- Build/release scripts in `~/Projects/dotfiles/`, `audits/release-*` — toolchain output, not application logs.
+- Build/release scripts — the harness's own `audits/*`, `audits/release-*`, and any governance-repo tooling — toolchain output, not application logs.
 - Generated framework noise (Next.js startup banners, Bun runtime warnings) — out of our control.
 
 The **LOGGING GATE** (`dispatch/write_any.md`, Logging Gate) sits on top of this file — it fires in addition to the language-level rules in `dispatch/write_zig.md` and `dispatch/write_ts_adhere_bun.md`, not instead of them.

package/docs/ORLY_ARCHITECTURE.md

@@ -48,8 +48,8 @@ scripts resolved live from this checkout via `$ORLY_ROOT`.
 
 That traded the storage cost for a distribution cost undiscovered until a
 second engineer tried to install the harness without this checkout present —
-the symlink and `$ORLY_ROOT` both require a copy of `~/Projects/dotfiles` at a
-known path, which is exactly what a fresh machine, a Continuous Integration
+the symlink and `$ORLY_ROOT` both require a copy of the governance checkout at
+a known absolute path, which is exactly what a fresh machine, a Continuous Integration
 (CI) runner, or a remote fleet container does not have. `orly init` (M03)
 restores storage, but not the failure mode that got it removed: `orly update`
 turns a rule change into one command per repository instead of the manual

package/docs/RELEASE_TEMPLATE.md

@@ -0,0 +1,46 @@
+# Release doc template — `changelog.mdx` `<Update>` block
+
+Source of truth: `~/Projects/docs/changelog.mdx`. New `<Update>` blocks go at the top, after the leading `<Tip>`/`<Note>`. Labels are date-only — never a semver prefix. `VERSION` is the single source of truth for binary version (binaries via `make sync-version` propagate to `build.zig.zon`, `agentsfleet/package.json`, `agentsfleet/src/cli.js`); changelog stays chronological. Decoupled by design — avoids parallel-branch collisions.
+
+## Block template
+
+```mdx
+<Update label="MMM DD, YYYY" tags={["What's new" | "Breaking" | "Bug fixes", "API" | "CLI" | "UI" | "Security" | "Performance" | "Integrations" | "Observability" | "Internal", ...]}>
+  ## {Short user-facing feature title — no milestone IDs, no codenames}
+
+  {One paragraph from the user's perspective. No workstream numbers, branch names, RULE references.}
+
+  ## Upgrading
+  {Breaking changes only. ALWAYS first when present. Each break: explicit migration step + whether CLI+server must upgrade together.}
+
+  ## What's new
+  {New capabilities — what a user/operator can now do.}
+
+  ## API reference
+  {New/changed endpoints, shapes, error codes. Include JSON/route examples. Omit if no API change.}
+
+  ## Bug fixes
+  {User-visible bugs fixed — observed behavior before/after. Omit if none.}
+
+  ## CLI
+  {`agentsfleet` additions or shape changes. Omit if none.}
+</Update>
+```
+
+## Hard rules
+
+- Label is `MMM DD, YYYY` exactly — no `vX.Y.Z —` prefix, no release name. Two releases on the same date → one merged `<Update>` block OR a disambiguator inside the title (`## Morning release — …`, `## Follow-up — …`); the label stays the date.
+- Section order is fixed: Upgrading → What's new → API reference → Bug fixes → CLI. Omit empty sections; never leave empty headings.
+- No milestone/workstream IDs, branch names, spec filenames, or `RULE XXX` references in the body.
+- User-centric verbs ("we added", "X now does Y"), not implementation prose.
+- Every breaking change appears under `Upgrading` with a migration step, even if also mentioned elsewhere.
+- Body copy may reference a past entry by date (`"…that shipped on Apr 22, 2026"`); do not reference past releases by semver (`"shipped in v0.27.0"`) — that drags the two timelines back together.
+
+## Version bumps (`VERSION`, not the changelog label)
+
+- Feature milestone → minor (`0.7.0` → `0.8.0`).
+- Bug fix → patch.
+- Pre-v1.0 breaking → minor (semver 0.x carve-out); call out under Upgrading.
+- Post-v1.0 breaking → major.
+- Internal-only refactor: terse `<Update>` with `tags={["Internal", ...]}`, one-paragraph summary, skip section structure. Prefer folding into the next user-visible release.
+- Parallel branches bumping `VERSION` do not coordinate through the changelog — whichever lands second rebases `VERSION` and re-runs `make sync-version`.

package/package.json

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

package/registry.json

@@ -228,6 +228,10 @@
         {
           "source": "docs/CHANGELOG_VOICE.md",
           "target": "docs/CHANGELOG_VOICE.md"
+        },
+        {
+          "source": "docs/RELEASE_TEMPLATE.md",
+          "target": "docs/RELEASE_TEMPLATE.md"
         }
       ]
     },

package/skills/orly-babysit-prs/SKILL.md

@@ -32,7 +32,6 @@ Before doing anything else in a polling cycle, read the triage helper:
 
 ```bash
 GREPTILE_TRIAGE="$HOME/.local/share/gstack/review/greptile-triage.md"
-[ -r "$GREPTILE_TRIAGE" ] || GREPTILE_TRIAGE="$HOME/Projects/dotfiles/.unified-skills/review/greptile-triage.md"
 [ -r "$GREPTILE_TRIAGE" ] || { echo "BABYSIT: greptile-triage.md missing — abort cycle"; exit 1; }
 ```
 
@@ -312,15 +311,14 @@ BABYSIT REPORT — <PR|MR> #<n> @ <SHA>
 ## References
 
 - `~/.local/share/gstack/review/greptile-triage.md` — fetch / classify /
-  reply / suppressions / history-write mechanics. Also at
-  `~/Projects/dotfiles/.unified-skills/review/greptile-triage.md`.
+  reply / suppressions / history-write mechanics (installed by gstack).
 - `$HOME/.gstack/projects/<slug>/greptile-history.md` — per-project
   history; drives Suppressions Check.
 - `$HOME/.gstack/greptile-history.md` — global aggregate.
 - `docs/greptile-learnings/RULES.md` — project-level named rules
   (durable principles). New rule added here only when the finding
   generalizes; per-incident rows go to greptile-history.md.
-- `~/Projects/dotfiles/AGENTS.md` — CHORE(close) skill chain step 4
-  cites this skill.
+- this repository's `AGENTS.md` / `AGENTS.orly.md` — CHORE(close) skill
+  chain step 4 cites this skill.
 - `gh api` docs: https://cli.github.com/manual/gh_api
 - `glab api` docs: https://gitlab.com/gitlab-org/cli (`glab api --help`)

package/src/install_packs.test.ts

@@ -7,7 +7,10 @@ import { install } from "./install";
 import { RulesModel } from "./model";
 
 const SOURCE_EXTENSIONS = ["rs", "ts", "tsx", "js", "jsx", "py", "sh", "sql", "zig", "mdx"];
-const ENGINE_VERSION = "0.5.2";
+// Read from package.json rather than restated here: a hand-synced copy goes
+// stale at the next release and the test then proves an install at a version
+// that no longer ships.
+const ENGINE_VERSION = (await Bun.file(join(ROOT, "package.json")).json()).version;
 
 afterEach(cleanupTemporaryDirectories);