# Session handoff — 2026-09-16 (LAB / 007)

**For the next chat:** read this file first, then `docs/007-kernelsu-runbook.md`.  
**Prior chat (full context):** Cursor transcript id
`a601104c-c593-45d3-b737-545a7838957d`
(path: `~/.cursor/projects/home-aventura-Workspaces-sunfish-a16-rom/agent-transcripts/a601104c-c593-45d3-b737-545a7838957d/`).

**Rules:** working tree only (no commit / push / MR). LAB only
`11231JEC207477` — never GOLDEN.

---

## Project spine (do not forget)

We did **not** start from abu or from LOS 22 as the product base.

1. **`003`** — LOS **23.2** vanilla on LAB  
2. **`004`/`005`** — microG + patched Play (Phonesky) + restricted spoofing → bacon zip  
3. **`007`** — our ReSukiSU root on **our** `msm-4.14`, then modules / SusFS / banks  

**ROM zip (ours):**  
`.local-artifacts/005-spoofing/20260915-bacon/lineage-23.2-20260915-UNOFFICIAL-sunfish.zip`

**abu / torukk / Downloads `boot-sunfish-resukisu*.img`:** reference only (SusFS / module ideas).  
**Never** treat Downloads abu boots as “ours”.

---

## Our boot images (host + laptop)

| Role | File | Where |
|------|------|--------|
| **Penúltimo (known-good ReSukiSU, no SusFS)** | `boot-resukisu-our-20260915T183729Z.img` | Host `/srv/rom/artifacts/007-kernelsu/` (+ symlink `boot-resukisu-our-latest.img`). Copy to laptop before flash if missing locally. |
| **Último (ReSukiSU + SusFS API bridge)** | `boot-resukisu-susfs-20260916T004038Z.img` | Host + laptop `.local-artifacts/007-kernelsu/boot-resukisu-susfs-latest.img` — sha256 `455a77a6…` |

Earlier same-day builds: `…T172342Z` / `…T172400Z` (superseded by `T183729Z`).

---

## What happened today (facts)

### Kernel / SusFS (host)

- Integrated **ReSukiSU** (not KSU-Next) into our tree; fixed shallow-clone bogus `KSU_VERSION=30701`.
- Built SusFS after bridging non-GKI 4.14 SusFS (`INODE_STATE_*`, etc.) with ReSukiSU GKI-style ioctl `CMD_*` / wrappers — compile+link OK (~18m).
- Pin notes: `.local-artifacts/007-kernelsu/susfs-pin/` (host tree under `kernel/google/msm-4.14`).
- **Process note:** SusFS build ran before US2 hide verification (constitution prefers profiles first). Treat SusFS boot as **trial**, not claimed.

### LAB flash chaos (evening)

- Torukk **22.2 MicroG** was on device temporarily (test/capture); **not** our product path.
- Attempted restore to **our 23.2 bacon** + SusFS boot.
- `fastboot -w` erased userdata **without** formatting (`File system type raw not supported`) → “Can't load Android system / data may be corrupt”.
- Wrong boot paths (`~/Downloads/boot-sunfish-resukisu.img`) = **abu/torukk**, not ours — caused confusion.
- Sideload of our 23 zip from old recovery: signature / **downgrade** prompts (recovery compares timestamps/patch, not “22<23” marketing). Accept install-anyway / downgrade when intentional.
- End of session: operator reported **sideload of our 23 finished and device booted**. Confirm with:
  `adb shell getprop ro.lineage.version` → expect `23.2-20260915-…`.
- Next flash after that sideload: **our penúltimo** boot (`boot-resukisu-our-20260915T183729Z`), then later trial SusFS if needed.

### What is *not* done

- SusFS boot **not** proven stable on our 23.2 (earlier bootloop / corrupt-data episode with SusFS + messy slots).
- US2 hide verification, modules (TEESimulator-RS / Zygisk / PIF), Island banks — still open.
- microG **Location UI** gap on our 23.2 (see urgent next).

---

## Urgent next (new chat)

1. **Confirm LAB identity:** `ro.lineage.version` = our 23.2 bacon; slot; serial `11231JEC207477`.
2. **Flash our penúltimo boot** (if not already):  
   `fastboot flash boot …/boot-resukisu-our-20260915T183729Z.img` then reboot.
3. **URGENT — Location options (`005`/`004` follow-up):**  
   On `23.2-20260915` + microG 0.3.16, operator saw **no usable microG Location UI** (no remember-from-GPS / request-from-online / hotspot-style controls vs richer UI on community 22.2).  
   Re-check on restored stack: screenshots + `dumpsys`; decide if packaging/overlay/settings gap.  
   Docs: `docs/004-lab-selfcheck.md` § “LAB observation (follow-up — 2026-09-16)”.
4. Reinstall manager (matching `KSU_VERSION`) + modules; resume `007` US2 → SusFS trial → attestation / Yuh+Swissquote.
5. Do **not** re-introduce abu ROM/kernels into the flash path; keep abu trees as SusFS/reference only.

---

## Spec / doc touchpoints updated this handoff

- `docs/007-kernelsu-runbook.md` — our boots, SusFS trial status, abu archived as reference
- `specs/007-kernelsu-sunfish/tasks.md` — T018 build done; T019 pending proof
- `specs/README.md` — `007` active
- `docs/004-lab-selfcheck.md` — Location marked urgent for return to our stack