Merge pull request 'Docs: filed PRs open in Frank's browser immediately' (#10) from docs/pr-browser-rule into main

AGENTS.md

@@ -34,6 +34,8 @@ with YAML frontmatter, spec at `omp-docs/references/okf-spec.md`).
 - Branch naming: `<type>/<issue#>-<slug>`, type ∈ feat|fix|docs|chore.
 - **Pull requests target `main` directly.** Merge with `--no-ff` so feature arcs
   stay visible in history. **Never merge a PR without an explicit OK from Frank.**
+- **The moment a PR is open, open it in Frank's browser** — `xdg-open <PR-URL>`
+  lands a tab in his Firefox; never make him hunt for it in Gitea.
 - Releases: tag `vX.Y.Z` straight on `main` after verifying; tags are the deploy
   markers every other machine pulls to. Hotfixes are ordinary branches off the
   tag you are fixing forward from.

omp-docs/log.md

@@ -11,6 +11,14 @@ timestamp: 2026-08-28
 
 # Bundle Change Log
 
+## 2026-10-18 — Fleet law: filed PRs open in Frank's browser immediately
+
+Both repos' git rules now require it: the moment a PR is opened, `xdg-open <PR-URL>` drops a Firefox tab on the workstation (AGENTS.md § Trunk-based SDLC here; § Git Workflow step 6 in `dank/serverAppConfigs`, riding their PR #6 branch).
+
+## 2026-10-18 — Trunk law: extension route closed unmerged; direct repo alignment instead
+
+Built and live-verified a cwd-scoped `before_agent_start` extension (quote probes: fires under `~/Projects`, silent elsewhere; kept as `.AGENTTRASH/trunk-law.js`). **Operator closed PR #9 unmerged** in favor of editing each repo's own AGENTS.md. Durable finding from the exploration: every context-file provider (AGENTS.md walk-up, `.omp/` dirs, CLAUDE.md) resolves at or below the repo root — a `~/Projects/AGENTS.md` for ancestor scope can never load; user-level `APPEND_SYSTEM.md` broadcasts to *all* sessions. Second finding: **serverAppConfigs never had git-flow** — its AGENTS.md mandated no branch regime at all (direct commit+push); a trunk + PR law is being added there by PR in that repo, not corrected.
+
 ## 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.