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>

core/src/icon.rs

@@ -2,7 +2,7 @@
 //!
 //! **Why a bundled font rather than ordinary Unicode**: the disclosure
 //! mark used to be U+25B8/25BE/25B4 out of whatever face the platform
-//! resolved, and once iris stopped bundling fonts (DECISIONS.md,
+//! resolved, and once iris stopped bundling fonts (decided
 //! 2026-09-07) Iris's phone drew an empty box for them and this VM drew a
 //! dot. UI_RULES' answer is not to avoid glyphs but to ship them, which is
 //! also what the Compose app has always done for its icons

core/src/primitive/text.rs

@@ -18,7 +18,7 @@ use swash::{
 ///
 /// This is the one font bundled here, and it is not a text font: body and
 /// monospace text still come from the platform's own collection
-/// (DECISIONS.md, 2026-09-07). An icon is the opposite case -- a small,
+/// (decided 2026-09-07). An icon is the opposite case -- a small,
 /// closed set of codepoints no system font is guaranteed to have -- which
 /// is the same division the Compose app makes.
 const NERD_ICONS: &[u8] = include_bytes!("../../assets/fonts/nerd_icons.ttf");
@@ -92,7 +92,7 @@ impl Default for TextData {
     /// `SansSerif`/`SystemUi` to `["Roboto Flex", "Roboto", "Noto Sans"]`
     /// and `Monospace` to the platform's `"monospace"` alias; the desktop
     /// build's backend is fontconfig. No font is bundled or registered
-    /// here -- see DECISIONS.md's 2026-09-07 entry for why (matching what
+    /// here -- see the 2026-09-07 decision for why (matching what
     /// the Compose app does: it takes body/monospace text from
     /// `FontFamily.Default`/`FontFamily.Monospace`, i.e. Android's Roboto
     /// and its platform monospace face, and ships no text font of its own,
@@ -137,7 +137,7 @@ fn register_icon_font(font_cx: &mut FontContext) -> Option<String> {
 /// `GenericFamily::Monospace` (confirmed against
 /// `fontique-0.11.1/src/backend/android.rs`'s `SystemFonts::new`, and still
 /// present on `linebender/parley`'s `main` as of 2026-09-07, so there is no
-/// released fix to bump to yet -- see DECISIONS.md's 2026-09-07 entry,
+/// released fix to bump to yet -- see the 2026-09-07 decision,
 /// "Platform fonts," for the full account). Two bugs stack, not one:
 /// `DEFAULT_GENERIC_FAMILIES` looks up the name `"monospace"` *before*
 /// `fonts.xml` is parsed into that same name map, and even after parsing,

examples/message_list.rs

@@ -2,7 +2,7 @@
 //! wrapped text, one in twelve carrying a small image, scrollable with the
 //! mouse wheel. Run headless with `iris/run-headless.sh message_list --shot
 //! /tmp/message_list.png` -- there is no display on this machine, so that
-//! is the only way to see it rendered; `run-tests.sh`/`cargo test` never
+//! is the only way to see it rendered; `scripts/run-tests.sh`/`cargo test` never
 //! touch this file.
 //!
 //! Rows alternate two background tints so a screenshot can show the

src/sense.rs

@@ -1191,7 +1191,7 @@ pub enum GestureOutcome {
 /// terminal release -- keeps reaching the same widget even after the
 /// finger has moved off whatever hit region first noticed the press. Iris
 /// asked for this to live here rather than in `transcript-ui::Selection`
-/// (2026-09-06, recorded in `IRIS.md`): "dragging should be part of the
+/// (2026-09-06): "dragging should be part of the
 /// default input system ... anything that provides good performance and
 /// can be generalized well is part of iris rather than the app." A caller
 /// still decides what a committed pan or a completed selection *means*

tests/mask_sdf.rs

@@ -283,7 +283,7 @@ fn run_shader(gpu: &Gpu, radius: f32) -> Vec<f32> {
 /// longer mapped. libtest runs every `#[test]` on a spawned thread, so a
 /// test that opens and closes an instance segfaults *after* printing its
 /// result, which reads exactly like the test failing. Measured
-/// 2026-09-08 with `rigs/gpu-probe`'s `teardown` bin: it
+/// 2026-09-08 with `scripts/rigs/gpu-probe`'s `teardown` bin: it
 /// needs no wgpu (raw `ash` does it too), no GPU work, and no device --
 /// an instance created and destroyed on a spawned thread is enough, and
 /// keeping any one instance alive is enough to prevent it.