Delete the decisions and design logs; scripts, rigs and xtask off the root

Iris: "remove both decisions and iris.md. I've decided to instead make
decisions when planning with agents rather than after they do things, and
they're both too long for me to wanna read, + don't cover all the
decisions I'll wanna make about the code anyways. I'll just naturally run
into things for now. Todo is important though."

So docs/DECISIONS.md (850 lines) and docs/IRIS.md (1,986) are gone, and
AGENTS.md now says not to start another: raise a choice while planning it
with her, otherwise decide it and put the reasoning at the code it
governs. The TODO lists stay. docs/SUBAGENTS_DECISIONS.md went with them
-- same artefact, same reasoning, and she did not name it, so its six
decisions were folded into docs/SUBAGENTS.md rather than deleted.

Deleting the logs left ~30 citations dangling in code comments and docs.
Each states its reason inline and cited the file only for provenance, so
they now read "decided 2026-09-07" or name the module doc that carries
the reasoning.

The root had six things that were not a program or a document. Moved,
per "I only meant top level sh files":

  run-tests.sh, test-wg-tunnel.sh, wg-setup-host.sh  -> scripts/
  rigs/                                              -> scripts/rigs/
  xtask/                                             -> scripts/xtask/

A project's own scripts stayed with the project: app/*.sh, app-rust/*.sh,
iris/*.sh and server/enroll-link.sh did not move.

`target/` at the root is deleted and cannot come back: there was never a
workspace there, and the 29 MB was only xtask's scratch space, now in
scripts/xtask/target/. `cargo xtask apk` still runs from the repo root
and now publishes to scripts/build/outputs/apk/<mode>/ -- one directory
deep, because that is what Dev Updater's `*/build/outputs/apk/*/*.apk`
discovery pattern needs, and scripts/xtask/build would have been two.

Verified: ./scripts/run-tests.sh and `cd iris && cargo test` green, clippy
and fmt clean everywhere, `cargo xtask apk debug --abi x86_64` builds and
signs an APK carrying lib/x86_64/libai_app.so at the new publish path, and
the repo root is now eleven entries with no build output among them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/RUST.md

@@ -10,8 +10,8 @@ piece from scratch where it does not fit is fine; effort and elapsed time
 do not matter, long-term robustness does.
 
 **The framework question is closed.** Iris chose her own library,
-[iris](https://github.com/cat16/iris), over Masonry on 2026-09-05
-(`DECISIONS.md`); the bake-off that got there, and the twelve experiments
+[iris](https://github.com/cat16/iris), over Masonry on 2026-09-05.
+The bake-off that got there, and the twelve experiments
 that proved it on a device, are summarised in "What the experiments
 settled" below rather than kept at length. What is left in this file is
 the plan for the rest of the app and the findings that outlive the tasks
@@ -57,7 +57,7 @@ re-derived: measurements, dead ends, invariants and their reasons.
   at the end -- it is the layout everything else here assumes.
 - **Open across the rest of the docs**: `docs/IRIS_TODO.md` is iris's own
   list (streaming re-layout is the live one), `docs/TODO.md` is the Compose
-  app's, and `docs/DECISIONS.md` is the queue of choices for Iris to review.
+  app's.
 
 ## Desktop and phone share the code (Iris, 2026-09-07)
 
@@ -358,7 +358,7 @@ needs its reasoning, the reasoning is at the thing itself.
   posts a real notification and receives a real share, and `cargo xtask
   apk` packages an installable APK with `javac`/`d8`/`aapt2`/`zipalign`/
   `apksigner` and one disclosed Gradle call, documented at
-  `xtask/src/apk.rs`'s module doc.
+  `scripts/xtask/src/apk.rs`'s module doc.
 - **E4 -- the same screen on the desktop**, which is now
   `app-rust`'s `src/desktop` and the `ai-app-desktop` binary.
 
@@ -516,13 +516,13 @@ device.
             (`ui::markdown::BlockFrame`) — plain, verbatim, quote — with
             fences and tables verbatim, headings scaled, and inline
             styling per span. `app-rust/src/ui/markdown.rs` is the code
-            and `docs/IRIS.md`'s 2026-09-06 entry the design.
+            and its module doc the design.
       - [x] **P1b — tool-call cards and grouping.** Done 2026-09-06.
             `ToolRows.kt`/`ToolInput.kt` ported to
             `app-rust/src/ui/tool.rs`: a run of calls is one collapsible
             group, each card carries its state and summary, and the five
             `ToolState` values each have their own appearance.
-            `docs/DECISIONS.md`'s 2026-09-06 entries have what was chosen.
+            `tool.rs`'s module doc has what was chosen.
       - [ ] **P1c — history paging and jump-to-latest.** Wire
             `client::transcript_source` into `src/ui`:
             the opening page, paging back on scroll with the cushion
@@ -599,13 +599,12 @@ device.
       paged). Re-take the I5 `FrameReport` (`iris frame report` in
       logcat, same as I5's box) once this screen has real paging and
       compare it against I5's own numbers, not against Compose's — the
-      three measurement sources still are not comparable per
-      `DECISIONS.md`'s DEFERRED item.
+      three measurement sources still are not comparable.
 
 - [ ] **P2 — the shell merge and a real phone install.** Merge this
       screen's cdylib into the E3/E5 shell (`src/shell` +
       `app/shellApp`) behind the same feature-flag pattern I5 used to
-      extend `src/android` (`DECISIONS.md`, 2026-09-05), so there is
+      extend `src/android` (decided 2026-09-05), so there is
       one app — notification service, share target and the real screen —
       rather than a demo shell and a service shell side by side. Package
       with `cargo xtask apk` (E5) and get it onto the real GrapheneOS
@@ -753,7 +752,7 @@ push, in the session that picked the task up.
    `main` and not in `ai-app`. Nothing on this branch is production until
    Iris says so. Commit and push as you go.
 3. The E- and I-steps (the framework decision) are done — iris won,
-   `DECISIONS.md` 2026-09-05. Take the next unchecked P-box in "## The
+   decided 2026-09-05. Take the next unchecked P-box in "## The
    port, in order (decided 2026-09-05)"; **P1 — session screen parity —
    is next.**
 4. Every step ends with its measurement written into this file beside the
@@ -764,7 +763,7 @@ push, in the session that picked the task up.
    for a server with fixtures, `transcript-bench.sh` for the scroll
    baseline, `ui-trace` for anything positional, `emu up` for the
    emulator, `iris/run-headless.sh EXAMPLE --shot PNG` for an iris
-   example on this displayless machine, and `rigs/gpu-probe` to ask a
+   example on this displayless machine, and `scripts/rigs/gpu-probe` to ask a
    device (this VM, the emulator, or a real phone over `adb push`) what
    `wgpu` features and limits it actually has before building anything on
    the assumption it does. The Vulkan section below says how to get a
@@ -810,7 +809,7 @@ Nine cargo workspaces, each with its own `Cargo.lock` and `target/`, and
 the port's project code in five places — `iris/transcript-ui`,
 `iris/transcript-fixture`, `iris/desktop-app`, `iris/android-app` (all
 *inside* the framework), plus `client-core` and `android-shell` at the
-root. Two root markdown files (`DECISIONS.md`, `SUBAGENTS.md`) sat outside
+root. Two root markdown files sat outside
 `docs/`.
 
 ### What it is
@@ -896,7 +895,7 @@ So: three workspaces where there were nine — `event-model`, `server`,
 
 ### Verified
 
-`./run-tests.sh` (event-model, server, app-rust) and `cd iris && cargo
+`./scripts/run-tests.sh` (event-model, server, app-rust) and `cd iris && cargo
 test` green; `cargo clippy --all-targets` and `cargo fmt` clean in every
 workspace. `cargo ndk -t x86_64` links `libai_app.so`; `./build-apk.sh
 debug --abi x86_64` produces an installable APK; installed and launched on