3.3 KiB
captured, source
| captured | source |
|---|---|
| 2026-08-06 | session task list (session-scoped, persisted here so a fresh session inherits it) |
Open operational tasks as of 2026-08-06 evening
Phase 13 itself: 14/15 plans complete, only 13-15 (device-close, autonomous: false)
remains. Everything below is outside the plan graph unless stated.
Blocking 13-15 (needs the operator, in a browser)
Four checks on archi-dev-box in the real embedded Chat iframe (not dev:mock), hard-reload
first. These close AIUI-06:
- Renders — AIUI appears in the Chat iframe, not a black page. Repeat on mobile
(reach the node by IP or Tailscale name;
.localhttps does not resolve on Android). - Content grid — BLOCKING GATE — real peer/owned files render (not fixtures, not model-invented rows); playing audio goes to the bottom bar, never the lightbox.
- Share regression — share a video and a document from the cloud view; each still gets its correct type and files where it always did (the music track edited that MIME map).
- CSP boundary — in the AIUI frame's devtools console a POST to the RPC endpoint is blocked; from the top-level frame the same call succeeds.
Then: write 13-UAT.md, fill 13-VALIDATION.md's map, close 13-15, close the phase.
Known gaps to record rather than fix: music view (D-13 independent track), Routstr live paid
request (protocol unverified, zero allowance), E-09 naive-user comprehension study.
Node/infra tasks (not phase 13)
- Gated-app iframe login (
session timeoutin-frame, works in a tab). Mechanism confirmed: https dashboard + hardcodedhttp://iframe URL => schemeful-same-site =>SameSite=Laxcookie withheld on the subrequest. Two fixes ruled out: the appgate has NO TLS (verified:https://127.0.0.1:8334refuses), and/app/<id>/path-prefix proxying is rejected by the operator ("never works ever, breaks all the websites historically"). Remaining: TLS on app ports (gate or an nginx TLS front) vs. enforcing one dashboard scheme per node. Needs a decision before code. - App health UX — a container that is up but not yet answering its probe renders as
"Unreachable" instead of "Starting…". Hit today by both LND and bitcoind (
-28warm-up). Fix the status mapping with a grace window. - .228 mempool — NOT down (API serves live data; ElectrumX is rebuilding its index from
genesis after being recreated, ~24h, address lookups only). The tx-link half is fixed
(
24a34a37) but only reaches .228 when a release ships there — decide: normal release, or push the frontend to .228 sooner. - Unreachable node app-gate — operator to OTA it to .125 from its own UI, then retest.
Follow-on phases (proposal written)
See ../phases/13-.../FOLLOW-ON-SCOPE-PROPOSAL.md, pushed. Shape:
A finish declared-but-unbuilt AIUI-02 (conversational settings) + AIUI-05 (delivery/build);
B outbound brokered, driven by the web-search setting (operator decision: the toggle must
change what is possible — move it node-side, derive the CSP from it, allowlist not wildcard);
C Nostr first-class + zaps (wallet tool category behind the 13-08 confirm gate).
B before C.
Other captured todos in this directory: Routstr funding UX; web-search through node chat.