merge(app): bring main into flutter/s1-data candidate

This commit is contained in:
2026-10-21 15:15:49 +01:00
+14 -3
View File
@@ -21,6 +21,10 @@ All work under app/. Existing applications remain running and unchanged.
| R2b | Native cancel-run confirmation | run51 →52 / correction5449370 | manager reran23 action tests + analyze, pass; known refusal now immediate and dismissible while resync pending | merged main; ancestry verified | reusable component only; wiring/browser pending |
| X1 | Native search and result targets | run49 / flutter/x1-search | Code computed success; WAITING truncated2MiB export | held, review not reached | pending |
| I1 | App-owned socket/session + live Runs shell registration | run50 / flutter/r1-native | Code computed success; WAITING truncated2MiB export | held, review not reached | not deployed |
| E1 | Narrow authorized server export-bound fix | run53 / fix/session-export-limit | API v8, Flash; bounded export/repair regressions | pending | no service restart authorized by pipeline |
| R2c | Native retry/restart confirmation | run54 / flutter/r2-retry | Task v6, Flash; small independent action | pending | pending |
| R2d | Native rename-run dialog | run55 / flutter/r2-title | Task v6, Flash; small independent action | pending | pending |
| S1a | Saved schedules repository/revision safety | run56 / flutter/s1-data | Task v6, Flash; nonvisual independent slice | pending | — |
## Next ready work
- P1 pipelines list/detail/source/version; P2 graph and stage/visit selection.
@@ -61,9 +65,16 @@ session identities remain retained. `pipelines repair-session-export 34 1` was
attempted once; it returned `session export repair incomplete: partial` at the
same cap. No full stage reruns, evidence replacement, cancellation or gate bypass
was performed. Remaining waits stay active for eventual export-only recovery.
Server export-cap change is outside the user's explicit app-only authorization;
approval is required before changing server code/configuration/deployment. Do
not burn repeated repair attempts against this deterministic size limit.
User subsequently approved the narrow server export-limit exception and asked
for continued small parallel tasks. Run53 owns ONLY bounded export-limit code,
necessary verification/repair regressions and a focused note. Existing web and
mobile source remain off-limits. Deployment remains a separate operator gate
under internal/server/AGENTS.md; no shared service restart is delegated. After
authorized installation, recover the original exact visits EXPORT-ONLY. Do not
burn repeated repair attempts against the unchanged deterministic size limit.
Parallel work while E1 runs: R2c/R2d/S1a are separate worktrees, each with its own
focused existing Task v6 run and background wait. No new workflow definitions.
At 160ab45: 29 Flutter tests and 6 Node proxy fixtures pass; flutter analyze,
flutter build web and git diff --check pass. Real Chrome phone/desktop captures