docs: name the iPhone boot project

docs/tasks/63-d10-second-body.md

@@ -133,7 +133,7 @@ two candidates are both in the parts that were *guessed* rather than derived:
 boot. **The pipe is not the daily path until a pixel is seen on it.**
 
 Kernel work is committed on archdev as `2e349ddf2` and exported to
-`hoolock/d10-port/patch/`. That commit also captured the 141-line `t8010-d10.dts`
+`souveraine-iphone/d10-port/patch/`. That commit also captured the 141-line `t8010-d10.dts`
 port, which had been uncommitted against the 14-line mainline stub.
 
 ## The session is real now
@@ -151,7 +151,7 @@ absolute targets**, so moving it between homes needs all 432 links repointed, no
 just a copy. Shell tree parity against blueline was verified file-by-file — 1056
 files, one difference, and it is a file the *Pixel* lacks.
 
-`hoolock/boot.sh` is the whole boot: waits for DFU, runs checkm8 → m1n1 → kernel
+`souveraine-iphone/boot.sh` is the whole boot: waits for DFU, runs checkm8 → m1n1 → kernel
 handoff, then prints kernel/touch/spi/drm/adp/deferred/session. `./boot.sh` for
 everything, `1`/`2`/`3` for one stage, `-l` to list staged kernels, `-k` to pick.
 
@@ -280,4 +280,5 @@ TASK-43/51 (viewtop; the render path and the tearing are new lanes),
 TASK-08 (`Blank`/`Unblank` are its actuators),
 `DEVICE-STATE-MACHINE.md` §0 (lockhint drift, reproduced),
 `SESSION-AUTHORITY-DOCTRINE.md` §13 (three layers refused the unlock),
-`souveraine-iphone7-d10` (the boot path Hoolock provides and nothing else).
+`souveraine-iphone` (the D10 boot path; Hoolock is its upstream provenance,
+not the project's identity).

docs/tasks/64-one-iphone-build.md

@@ -1,12 +1,15 @@
 # TASK 64 — one SouveraineOS build for the iPhone
 
-**Status: scoped 2026-08-10, not started.** Casey, 2026-08-10: *"we're going to
+**Status: scoped 2026-08-10; repository foundation landed, build work not started.** Casey, 2026-08-10: *"we're going to
 OWN the PIPELINE from BOOT to OS. Gutting ALL the iBoot extra we don't need,
 Gutting all the hoolock whatever. I want ONE SOUVERAINEOS BUILD for the
 IPHONE."*
-**Repos:** `hoolock` (not a repo yet — that is part of the work),
+**Repos:** `souveraine-iphone` (the D10 boot path and device artifacts),
 `Pixel3Arch`, `SouveraineOS`.
 
+`souveraine-iphone` was renamed from `hoolock-d10` on 2026-08-10. Hoolock
+remains upstream bring-up provenance, not this project's identity.
+
 TASK-63 made the d10 a body. This task makes it a **build**. Today the iPhone
 boots through a rescue-distro loader carrying an iPad's name, a kernel tree that
 is not a repository, and a laptop-side shell script — none of which is a package
@@ -14,8 +17,9 @@ and none of which CI has ever built.
 
 ## Why now
 
-`hoolock/` is a vendored rescue environment plus m1n1 plus pongoOS plus an IPSW
-scratch area. The parts we use are small:
+`souveraine-iphone/` is the D10 project checkout. It still contains a vendored
+Hoolock rescue environment plus m1n1 plus pongoOS plus an IPSW scratch area.
+The parts we use are small:
 
 | kept | what it does |
 |---|---|
@@ -30,7 +34,7 @@ tutorials — is bring-up scaffolding for a device that now boots off `nvme0n1p1
 
 The kernel tree is the sharper problem. `linux-pauli` lives on archdev, is not a
 git remote anywhere, and today carried **nine dirty files** with no commit. Its
-work reaches the phone by `scp` of `Image.gz` into `hoolock/out/`. That is the
+work reaches the phone by `scp` of `Image.gz` into `souveraine-iphone/out/`. That is the
 "second secret road to success" the working agreement forbids, and it is the only
 road this device has.
 
@@ -165,7 +169,7 @@ smithay's `failed to create signaled syncobj` was a symptom rather than a cause.
 - `pacman -S` installs the d10 kernel, DTB and loader as owned packages.
 - The kernel tree has a Gitea remote and the d10 commits are on a branch.
 - CI builds the kernel; no `Image.gz` reaches a phone by `scp`.
-- `hoolock/` contains only what boots this device.
+- `souveraine-iphone/` contains only what boots this device.
 - `boot.sh` consumes packaged artifacts, not `out/`.
 - A second T8010 joins by installing a package.