Feat: trunk-law extension scopes fleet git rules to ~/Projects sessions

before_agent_start handler appends the trunk-based git law to the system
prompt only when cwd is under ~/Projects/. Hard cwd scope because every
context-file provider resolves at or below the repo root - an ancestor
AGENTS.md is never loaded by descendant repos. Verified live: quote probe
fires under serverAppConfig, silent in /tmp and ~/.omp. Fires for subagent
sessions too (shared cwd). Changelog entry added.

omp-docs/log.md

@@ -11,6 +11,10 @@ timestamp: 2026-08-28
 
 # Bundle Change Log
 
+## 2026-10-18 — Trunk law propagated to ~/Projects repos via extension
+
+New tracked extension `agent/extensions/trunk-law.js`: a `before_agent_start` handler that appends the trunk-based git law to the system prompt **only when the session cwd is under `~/Projects/`** (hard-scoped; verified live with quote-the-prompt probes: fires under `serverAppConfig`, silent in `/tmp` and `~/.omp`). This was the only mechanism that works — every context-file provider (AGENTS.md walk-up, `.omp/` dirs, CLAUDE.md) resolves at or below the repo root, so a hypothetical `~/Projects/AGENTS.md` is never loaded by ancestor sessions. Subagent sessions inherit the cwd and get the law too. Note: repo-local git-flow text (serverAppConfigs' AGENTS.md) contradicts it until that repo is updated; the injected law declares precedence explicitly.
+
 ## 2026-10-18 — SDLC switched to trunk-based development
 
 `develop` retired by operator decision (single-dev repo; the branch bought nothing and cost a back-merge every release). New law in AGENTS.md § *Trunk-based SDLC*: branch off the freshest `origin/main` before every work item, PRs target `main` directly, `--no-ff` merges, tags `vX.Y.Z` straight on main. No back-merges, no release branches. The last back-merge (`527596a`) lands with this switch; the managed skill `gitflow-back-merge-plumbing` is now historical.