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>

app-rust/src/android/app_log.rs

@@ -11,7 +11,7 @@
 //! another's `logcat`. Nothing outside this process can recover what it
 //! wrote, so the process keeps a copy -- and hands it to Dev Updater on
 //! the same phone through `devlog`'s `ContentProvider`. See
-//! `docs/DECISIONS.md`, 2026-09-07.
+//! decided 2026-09-07.
 
 use crate::client::log_ring::{self, LogRing};
 

app-rust/src/bin_desktop.rs

@@ -10,7 +10,7 @@
 //!     desktop-app --ca /path/to/ca.pem   # a link that carries no CA
 //!
 //! `--link` is the same text `app/ui-sandbox.sh`'s banner prints and a
-//! phone would scan as a QR (DECISIONS.md, 2026-09-05) -- pasted rather
+//! phone would scan as a QR (decided 2026-09-05) -- pasted rather
 //! than scanned, since a desktop has no camera to assume. It is parsed and
 //! saved once; later runs read it back and `--link` is only needed again
 //! to enrol against a different server.

app-rust/src/client/markdown_blocks.rs

@@ -8,7 +8,7 @@
 //! the stream phase at p50 18.2ms against Compose's 13.4ms for exactly
 //! that reason (docs/IRIS_TODO.md). A row is a column of one widget per
 //! block now, and a delta that lands in the last block leaves every
-//! earlier block's layout alone. `docs/DECISIONS.md`'s 2026-09-06 entry has
+//! earlier block's layout alone. the 2026-09-06 decision has
 //! what that rejected and why the split lives here rather than in the UI
 //! crate: `docs/CLIENT_CORE.md` already wanted a block model for P1, and
 //! keeping it here means iris stays a text renderer that knows nothing

app-rust/src/ui/markdown.rs

@@ -18,7 +18,7 @@
 //! a quote is *text behind a coloured bar*. Everything else markdown can
 //! say is expressed in the spans, which cost no widgets and no layout
 //! nodes. `app/.../Markdown.kt`'s component table is the reference for the
-//! sizes and colours; docs/DECISIONS.md's 2026-09-06 entry records where
+//! sizes and colours; the 2026-09-06 decision records where
 //! this deliberately differs.
 //!
 //! **What this deliberately does not attempt**, each for a reason recorded
@@ -450,7 +450,7 @@ const TABLE_MAX_COL: usize = 28;
 /// and pixel widths the same thing, so padding each cell to its column's
 /// width *is* alignment, the column widths are measured from the cells,
 /// and the block reuses `BlockFrame::Verbatim`'s sideways pan for a table
-/// too wide to fit. docs/DECISIONS.md, 2026-09-06, has what this trades.
+/// too wide to fit. decided 2026-09-06, has what this trades.
 pub fn table_text(src: &str) -> Rendered {
     let rows = table_cells(src);
     if rows.is_empty() {

app-rust/src/ui/mod.rs

@@ -37,8 +37,8 @@
 //! every frame it was pressed. `row.rs` now routes every row's drag
 //! through one shared `iris::sense::DragArbiter`
 //! (`Selection::drag`, `selection.rs`), which decides pan vs. select the
-//! way Android itself does -- see `DragArbiter`'s own doc and
-//! `DECISIONS.md` for the exact rule. `LazySpan` scrolls correctly when
+//! way Android itself does -- `DragArbiter`'s own doc has the exact
+//! rule. `LazySpan` scrolls correctly when
 //! driven programmatically (I3's benchmark), via the mouse wheel (wired
 //! below, `CursorSense::Scroll`), and now via a touch pan starting on a
 //! row's own text too.
@@ -275,8 +275,8 @@ impl TranscriptScreen {
                 // delta path: the row is a column of one widget per
                 // markdown block, so a delta that lands in the last block
                 // is one `set_with_spans` and the earlier blocks keep
-                // their layouts (`row::RowBlocks::apply_delta`, and
-                // docs/DECISIONS.md for why the row is shaped that way).
+                // their layouts (`row::RowBlocks::apply_delta`, whose doc
+                // says why the row is shaped that way).
                 let old_key = row::row_key(&old_rows[common].key());
                 let new_key = row::row_key(&new_rows[common].key());
                 if new_key == old_key && self.apply_tail_delta(rsc, new_key, &new_rows[common]) {
@@ -764,7 +764,7 @@ mod apply_tests {
         (draws, shapes)
     }
 
-    /// The pass condition for docs/DECISIONS.md's per-block row: a delta
+    /// The pass condition for the per-block row: a delta
     /// costs the **last block**, not the message. A 3,000-character reply
     /// has a hundred paragraphs already laid out; redrawing one delta into it
     /// must cost exactly what the same delta costs in a one-paragraph

app-rust/src/ui/row.rs

@@ -11,8 +11,7 @@
 //! meant a streamed delta re-shaped every paragraph of a long reply
 //! through parley again -- the stream phase was the one place iris trailed
 //! Compose on Iris's phone. [`RowBlocks::apply_delta`] is the other half
-//! of the fix; docs/DECISIONS.md's entry has what the alternative shapes
-//! were and why this one.
+//! of the fix.
 //!
 //! A `TranscriptRow::Tools` (a run of adjacent tool calls, grouped by
 //! `crate::client::transcript_fold::group_tool_runs`) is the row that proves
@@ -127,7 +126,7 @@ fn tool_call_markdown(tool: &str, input: &str, output: &str) -> String {
 /// The per-block text widgets of one row, kept by `TranscriptScreen` for
 /// the row a reply is streaming into, so a delta can replace the block it
 /// lands in instead of re-shaping the whole message
-/// (docs/DECISIONS.md, 2026-09-06). Nothing else needs it: a row that is
+/// (decided 2026-09-06). Nothing else needs it: a row that is
 /// not the tail never changes.
 pub struct RowBlocks {
     /// What each field was built from, in order -- compared against a

app-rust/src/ui/selection.rs

@@ -35,8 +35,8 @@ use std::{collections::BTreeMap, time::Instant};
 
 /// What this selects between: a row's `RowKey` and the index of one
 /// markdown **block** inside it. A row is a column of one text widget per
-/// block since 2026-09-06 (`crate::client::markdown_blocks`, and
-/// docs/DECISIONS.md for why), so the block, not the row, is the unit --
+/// block since 2026-09-06 (`crate::client::markdown_blocks`), so the
+/// block, not the row, is the unit --
 /// `(row, block)` compares lexicographically, which is reading order for
 /// both levels, so every range query below is unchanged.
 pub type SelKey = (RowKey, u32);
@@ -49,7 +49,7 @@ pub struct Selection {
     /// pan wanting the same touch gesture). See `drag` below, and
     /// `iris::sense::DragGesture`'s own doc for the arbitration, velocity
     /// tracking and pointer-capture mechanics this no longer owns itself
-    /// -- Iris's 2026-09-06 ask (`IRIS.md`) that a drag's *mechanics* live
+    /// -- Iris's 2026-09-06 ask that a drag's *mechanics* live
     /// in iris's default input layer, with only the pan-vs-select
     /// *decision* staying here.
     gesture: DragGesture,