docs(active-work): refresh this lane to match revision 5

The lane described the pre-re-scout state: head ab42a79, 1,570 lines,
"re-scout under way", and a five-owner rename census. All four are now
wrong. It rides this PR rather than a standalone refresh, because a
separate ledger PR with several others open re-conflicts on every merge.

What the lane now records:

- Head e7f811b, 2,304 lines, integrated to main @ ad41cf1, status
  PROPOSED and never formally approved — four revisions and three review
  rounds are not approval and must not be read as one.
- Seven of rev 4's own claims about pmacs were wrong. The load-bearing
  one is kept in full because it is a trap anyone can repeat:
  drain_external_cancelled (:1561) and drain_cancelled_externals (:1596)
  are two different functions 35 lines apart, and rev 4 named one while
  citing the other's line. Following the citation gives the per-tick
  token sweep instead of the unconditional server-scoped drain, so the
  drain half becomes a silent no-op and the awaiting coroutine hangs.
- The path-owner census is six, not five. The sixth is lean.lua's
  M.file_progress, a URI-keyed Lua table in no Rust store, which is the
  first evidence outside dired that the hook rather than the Rust method
  is what scales.
- The journey ratchet is split across journey_acceptance.rs and
  gpu_invocation_acceptance.rs; both are gates, and a scout checking only
  the first concludes #183 added nothing.
- open_directory now commits under pmacs.window.commit_to, whose scope
  refuses an await, which constrains the proposed batch contract.

Scope moved OUT of this lane: Q#DR25's adoption of
set_generated_contents turned out to address a class bug shared with
listview, compile and search/grep, so it is owned by the
generated-buffer immutability lane now. This PR needs a rev 6 deferring
Q#DR25 there once that framing is approved.

Also records two live bugs this lane confirmed but does not fix, both
owned elsewhere: apply_resource_op's delete arm destroying unsaved work,
and View still lacking rename_resource.

docs/active-work.md

@@ -459,57 +459,71 @@ has **no branch and no framing yet**.
   `FrontendView.fold_projection` to `true` for semantic frontends, which
   Stage 2 deliberately left `false` (Q#FD21).
 
-## dired Stage 2 framing lane — PR #171 OPEN, STALE, DO NOT MERGE AS-IS
+## dired Stage 2 framing lane — PR #171 AT REVISION 5, AWAITING APPROVAL
 
-- Portable branch: `githubsucks/dired-stage2-framing` (head `ab42a79`,
+- Portable branch: `githubsucks/dired-stage2-framing` (head `e7f811b`);
-  four framing commits); worktree `../pmacs-dired-stage1`. **PR #171**,
+  worktree `../pmacs-dired-stage1`. **PR #171**, base `main`, integrated
-  base `main`. Framing only — `docs/dired-stage2-framing.md`, 1,570
+  up to `main` @ `ad41cf1`. Framing only —
-  lines, no runtime code.
+  `docs/dired-stage2-framing.md`, now **2,304 lines**, no runtime code.
-- **Measured 2026-07-28: 4 commits ahead of `main`, 153 behind**, merge
+- **Status: PROPOSED, never formally approved.** GitHub records no
-  base `c8ec8f3`. GitHub reports it mergeable, and its old CI run is
+  formal review on it. The commit history embodies four revisions and
-  green — **both facts are about a tree nobody has looked at in 153
+  three review rounds; **that is not the same as approval**, and it must
-  commits**, and the document still says PROPOSED.
+  not be read as one.
-- **The commit history embodies three review rounds. That is not the
+- **Rev 4 was scouted at `c8ec8f3`, which is dired Stage 1's own merge
-  same as approval**, and GitHub records no formal review or comment on
+  commit (#165)** — so dired Stage 1 and find-file (#162) were always
-  it. Do not read the round count as a green light.
+  its base, not new arrivals. Eighteen PRs landed on top before the
-- **Its dependencies moved materially underneath it**, which is the real
+  re-scout. Rev 5 is that re-scout, against `6bee09d` and then
-  reason not to merge. Note that dired Stage 1 (#165) and find-file
+  integrated forward.
-  (#162) are its *base*, not new arrivals — the merge base `c8ec8f3`
+- **Seven of rev 4's own claims about pmacs were wrong**, which is the
-  **is** #165's merge commit. Eighteen PRs landed after it, and at least
+  lane's most transferable lesson: a framing can verify all its external
-  three change ground the framing stands on:
+  facts and still be wrong about the codebase it is for. The load-bearing
-  - **#178 gave generated buffers a write invariant**
+  one: §5 named `drain_external_cancelled` but cited `lsp.rs:1596`.
-    (`Buffer::set_generated_contents`). Dired's listing is a generated
+  **Those are two different functions 35 lines apart** —
-    buffer, and dired is named in the handoff as one of the writer
+  `drain_external_cancelled` (`:1561`) is the unconditional
-    mechanisms that has **not** adopted it. Stage 2's marks and
+  server-scoped drain and is the right precedent;
-    operations write that buffer constantly.
+  `drain_cancelled_externals` (`:1596`) is a per-tick token/timeout
-  - **#182 (Journey Stage 1a) made `resolve_target_buffer` the single
+  sweep. A rename flips no token, so following the line number yields a
-    directory-open path**, with dired demoted to a *replaceable slot*
+  `forget_uri` whose drain half is a silent no-op and the awaiting
-    (`pmacs.path.directory_handler`) rather than a hook subscriber. Any
+  coroutine hangs forever — exactly the failure that step exists to
-    Stage 2 claim about how a directory reaches dired is now describing
+  prevent.
-    a mechanism that no longer exists in that form.
+- **The rename path-owner census is SIX, not five.** The sixth is
-  - **#179/#181 landed the typed-edit consumer chain**, which is the
+  `lean.lua`'s `M.file_progress`, a URI-keyed Lua module table living in
-    fan-out a rename transaction has to survive.
+  no Rust store, so `forget_uri` structurally cannot reach it. That is
-
+  the first case outside dired proving the **hook**, not the Rust
-  Re-scout against `6bee09d`, publish a new revision, and get explicit
+  method, is the mechanism that scales. The other five: buffer path,
-  framing approval before any implementation. **The re-scout is under
+  buffer name, the URI-keyed LSP stores plus `DiagnosticView` (URI set
-  way** on the existing branch, so PR #171 keeps its three-round
+  once at construction), dired's pathless handles, and a captured Lua
-  history; the product is a revision 5, not a new document. (`main` has
+  local no transaction can reach.
-  since advanced to `0442d78`, but the only difference is the test-only
+- **The journey ratchet is split across two files**, and both are gates:
-  #174, so no re-scout conclusion turns on it.)
+  `tests/journey_acceptance.rs` (24 tests, "stages add rows, none
-- **The rename problem the framing must still answer**, restated because
+  removes them", seven rows asserting on dired) and
-  it is the hard part: a rename is a transaction across **five** path
+  `gpu_invocation_acceptance.rs`, where #183 actually put the GPU row.
-  owners — the buffer path, the buffer name, the URI-keyed LSP stores
+  A scout that checks only the first will think #183 added nothing.
-  plus `DiagnosticView` (whose URI is set once at construction), dired's
+- **`open_directory` now commits under `pmacs.window.commit_to`, whose
-  pathless handles, and a captured Lua local that no transaction can
+  scope REFUSES an `await`** (#182). That directly constrains the
-  reach.
+  serialize-and-await batch contract the framing proposes.
+- **The typed-edit chain does not reach dired** — verified rather than
+  assumed. Its lessons bind the framing's two *new* hooks instead.
+- **Scope has MOVED OUT of this lane.** Rev 5 added Q#DR25 to adopt
+  `set_generated_contents` at the head of 2b, because dired's listing is
+  a generated buffer whose paint bypasses an intercept over a still
+  writable rope. That turned out to be a **class bug, not dired's** —
+  the same idiom is in listview, compile and search/grep — so it is now
+  owned by the generated-buffer immutability lane. **#171 needs a
+  revision 6 that defers Q#DR25 to that lane** once its framing is
+  approved; do not implement Q#DR25 from this document.
 - Intended serial implementation once approved: **2a** rename/delete
   reconciliation substrate with no dired UI, **2b** marks and
   operations, **2c** mkdir/copy/recursive-delete primitives, then Stage
-  3 wdired.
+  3 wdired. The re-scout re-examined this cut and it holds unchanged.
 - **Ownership warning:** dired 2a overlaps `src/editor_core.rs`,
   `builtin/runtime/lsp.lua`, and the URI-keyed LSP state with other
   coherence work. Do not run it concurrently with Journey Stage 1b
   without assigning those files to one lane first.
+- **Two live bugs on `main` this lane confirmed but does NOT fix**, both
+  now owned elsewhere: `apply_resource_op`'s delete arm destroys unsaved
+  work (no dirty check anywhere on the path), and `View` still lacks
+  `rename_resource`.
 
 ## Parked lane: kill-ring browser + persistence