diff --git a/data/backlog.json b/data/backlog.json index 34e606c..6cc9d1e 100644 --- a/data/backlog.json +++ b/data/backlog.json @@ -173,7 +173,7 @@ {"project":"linux-phone-oco/lab-tools","id":"test-hold-parallel-flake","title":"hold::tests::the_phone_is_held_by_one_change_at_a_time fails in a parallel workspace run, passes alone","status":"open","note":"Sign (coordinator, 2026-11-18): failed once in a parallel workspace run, passes alone. Likely a shared lease file or lock path across tests; give each test its own.","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"cargo test --workspace passes 20 runs in a row with default parallelism","rank":10,"about":null} {"project":"linux-phone-oco/lab-tools","id":"sxmo-utils-lab-apk-deliver","title":"Build, sign and publish the sxmo-utils lab apk as the sxmo-utils@lab repository","status":"done","note":"Delivered 2026-11-18. Conveyor v1.2.1 (v1 moved; PRs conveyor 19, 20): alpine.yml copies the APKBUILD's whole folder, keeps the live repository's other packages in the one signed APKINDEX, derives the front page and verify from it, installs the APKBUILD's makedepends in the signing container before the key, and refuses a deploy that would lose a live package; its own test (tests/alpine/run.sh, CI job alpine) runs the steps on two fixture packages. lab-tools PRs 168 (packaging/sxmo-utils/conveyor.toml, second packages job, tag sxmo-utils-v1.18.1_p20261118 pushed by hand), 169 (APKBUILD build()), 172 (restored 168/169 after #170 put the files back). Proof: lab-tools Packages run 44322521483: 19 packages verified against the committed key, https://linux-phone-oco.github.io/lab-tools/ offers lpoco-health 0.15.1 and sxmo-utils 1.18.1_p20261118-r0 (every subpackage listed), both installed in a clean Alpine 3.24 aarch64 from the page's own lines. Next: the phone takes it (apk add sxmo-utils from that repository tagged @lab) - the phone proof suspend-retry-backs-off.","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"suspend-retry-backs-off","rank":4,"about":"sxmo-utils-lab-apk"} {"project":"linux-phone-oco/lab-tools","id":"phone-pieces-drift-in-lab","title":"lpoco lab names a stale phone-side piece at every change's end, from the report it reads back","status":"done","note":"2026-11-18, lab-tools-builder: done (lab-tools #170, main 27bd466). lpoco-lab test and health name a stale phone piece after the run, from the report just read back, judged by lpoco_host::stale_lines (shared with lpoco host check). Proof: host/tests/phone_pieces.rs the_lab_names_a_piece_off_main_from_the_report_it_reads_back (seen failing first) and the_lines_name_a_package_off_its_pin. Not tested end to end against a phone: devlab's wiring (health.rs name_stale_pieces) has no test of its own. Note: the commit named is now the oldest holding the stale blob (changes host check output). Report-name ordering checked: names are YYYYMMDD-HHMMSS, so the greatest sorts newest.","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"a test in lab-tools lpoco/tests (to write, failing first): after a change the lab output names a piece off main","rank":6,"about":"phone-pieces-drift-named"} -{"project":"linux-phone-oco/lab-tools","id":"host-plan-unreadable-not-new","title":"lpoco host records each root file it installs, so plan reads an unreadable one as up to date","status":"open","note":"Coordinator, 2026-11-18: when lpoco-host installs a root file, it records the staged content's hash in user state (~/.local/state/lpoco-host, or ~/.cache/lpoco-host). Plan then treats a root file it cannot read as up to date when the staged hash matches the recorded one and its check passes (for 50-lpoco.rules: the share check), and as changed only when the staged content differs. Sign: planning 0.15.0 named /etc/polkit-1/rules.d/50-lpoco.rules '(new)' though the author's 0.14.2 prepare installed it at about 15:00 and the share check passed - the directory is root-only. The same limit applies to NetworkManager keyfiles (part 6b). Bootstrap: the lab has no record yet. Consider recording without root once a check proves the file in place (e.g. lpoco host check passing the share check writes the record for the staged hash), so no sudo is asked for an unchanged file. Then orchestration runs the 0.15.0 prepare itself, with 0 root commands.","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"host plan tests from fixtures: (1) a root file under an unreadable directory, whose staged content hashes to the hash recorded at its last install, is planned up to date with 0 root commands; (2) changed staged content is planned as a root install; (3) with no record, it is named as unreadable and not known, never '(new)'; (4) prepare now records the hash after each root install it runs","rank":5,"about":"lpoco-host-rest"} +{"project":"linux-phone-oco/lab-tools","id":"host-plan-unreadable-not-new","title":"lpoco host records each root file it installs, so plan reads an unreadable one as up to date","status":"done","note":"2026-11-18, lab-tools-builder: done (lab-tools #173, main a4d4a3e). prepare records the git blob id of each root file it installs in ~/.local/state/lpoco-host/installed (lines 'HASH DST'), after every root command succeeded; plan reads a file under a folder the lab user may not enter (PermissionDenied) by that record: up to date when it matches, else planned as an install and worded 'unreadable, not known yet', never '(new)'. Proof: host/tests/plan.rs a_root_file_the_lab_user_cannot_read_is_judged_by_the_hash_recorded_at_its_last_install (seen failing first). Not done, now host-record-from-check: the lab has no record until the next prepare, so the first plan on it still names 50-lpoco.rules 'not known yet' and the first prepare reinstalls it (one sudo); a passing lpoco host check does not write the record; plan does not tie 'up to date' to the share check passing. The test assumes the suite does not run as root (mode 000 does not stop root).","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"host plan tests from fixtures: (1) a root file under an unreadable directory, whose staged content hashes to the hash recorded at its last install, is planned up to date with 0 root commands; (2) changed staged content is planned as a root install; (3) with no record, it is named as unreadable and not known, never '(new)'; (4) prepare now records the hash after each root install it runs","rank":5,"about":"lpoco-host-rest"} {"project":"linux-phone-oco/device-template","id":"template-classifies-its-files","title":"device-template names every file it has: generic (followed) or made-once (laid at creation); the skeleton followed, the hardware files left to idealkb","status":"open","note":"Decision 2026-11-18-device-template-follows-by-release, step 1. Add a made-once list (device.toml, oco.toml, README.md, devicebase.toml, idealkb.toml, provision/packages.txt, .oco/uncommitted, data/); move Makefile, bin/install-tad.sh, tad.yml, gather.yml, .gitignore, tests/health/README.md and the .gitkeep files into generic; split the script check into a workflow a lab does not extend; a template:begin/end part in AGENTS.md for the general conventions; drop records/hardware.sql, records/hardware-status.sql, queries/hardware.sql from generic (idealkb 0.15.0 gives them). Owner: orchestration (device-template).","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":null,"device":null,"proof":"docs research/device-template/2026-11-18/template-drift.sh device-template ideal-knowledge-base: its classified and one-source lines say ok (today 18 unclassified files, 3 with two sources)","rank":null,"about":"device-template"} {"project":"linux-phone-oco/device-template","id":"template-releases","title":"device-template releases by release-please from v0.1.0, and a lab's devicebase.toml names the release it follows","status":"open","note":"Step 2. release-please as in idealkb; devicebase.toml template = \"X.Y.Z\" with own = [...] for template files a lab keeps; the template's own devicebase.toml comment says how a new lab sets it. The date pin (2026-11-17) is retired.","opened":"2026-11-18","waits":null,"blocked_by":"template-classifies-its-files","hardware":null,"needs":null,"device":null,"proof":"gh release list -R linux-phone-oco/device-template shows v0.1.0, and template-drift's pin line reads it for a lab pinned to it","rank":null,"about":"device-template"} {"project":"linux-phone-oco/device-template","id":"template-drift-in-ci","title":"template-drift runs in CI: the template's (classified, one-source) and each lab's (pin, equal, no-copy), from a generic bin/template-drift.sh","status":"open","note":"Step 4. The failing test in docs research/device-template/2026-11-18/ becomes a generic file of the template; a lab's workflow clones the template at its pinned tag and idealkb at its pin, read-only. Like cruft check plus cruft diff --exit-code.","opened":"2026-11-18","waits":null,"blocked_by":"template-releases","hardware":null,"needs":null,"device":null,"proof":"a test PR to a lab that edits a template-generic file fails CI with a line naming the file; main of the template and both labs pass","rank":null,"about":"device-template"} @@ -191,3 +191,4 @@ {"project":"linux-phone-oco/lab-tools","id":"bringup-steps-helpers","title":"The helper map: lpoco bringup steps reads docs' chain and names, per step, its lpoco command or the gap","status":"open","note":"Today: image pack/check/swap/bisect, initramfs build, lab fastboot, flash, provision, suite. Gaps: UART, banner, shell, dmesg map, PMIC, charger, storage. Each gap filled becomes its own item.","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-seed","hardware":null,"needs":null,"device":null,"proof":"a test in lab-tools: every helper named in docs' bringup_steps is a subcommand lpoco --help lists at the pinned release, and lpoco bringup steps --device google-walleye prints the gaps","rank":null,"about":"bringup-steps"} {"project":"linux-phone-oco/lab-tools","id":"bringup-step-runner","title":"Research: a runner that walks a device's ready steps - helper, then proof, then the claim in its base; a step that changes the phone queued to its keeper","status":"open","note":null,"opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-helpers,feed-device-steps","hardware":null,"needs":null,"device":null,"proof":"a research row and a decision with what was rejected, and its failing test: the runner on a made-up device with two ready steps runs each helper and proof and writes two claims","rank":null,"about":"bringup-steps"} {"project":"linux-phone-oco/docs","id":"milestones-step-terms","title":"Milestones name steps: step:ID@device in criteria, read from step_status by milestone-readiness","status":"open","note":null,"opened":"2026-11-18","waits":null,"blocked_by":"feed-device-steps","hardware":null,"needs":null,"device":null,"proof":"milestone-readiness counts a step term done only when step_status says done for that device; a walleye milestone 'reaches a shell' over step:shell-on-console@google-walleye reads ready","rank":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/lab-tools","id":"host-record-from-check","title":"lpoco host check writes the install record for a root file it proves in place, so the first plan after 0.15 asks no sudo","status":"open","note":"From host-plan-unreadable-not-new (#173). Also: plan words 'up to date' only while the file's check passes (share check for 50-lpoco.rules).","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"host plan test from fixtures: with no record and an unreadable rules folder, a passing share check records the staged hash and the next plan lists 0 root commands for it; a failing check records nothing","rank":null,"about":"lpoco-host-rest"} diff --git a/data/session_log.json b/data/session_log.json index f5e24eb..37ee3c0 100644 --- a/data/session_log.json +++ b/data/session_log.json @@ -117,3 +117,4 @@ {"project":"linux-phone-oco/lab-tools","id":"2026-11-18-lab-names-stale-phone-pieces","entry_date":"2026-11-18","title":"lab names stale phone pieces","done":"lpoco-lab test/health print which phone-side piece the run's report holds off origin/main; logic moved to lpoco_host::stale_lines and shared with lpoco host check (#170).","considered":"Printing from run_checks; judging only the report's JSON rows since phone stdout can carry noise; naming the oldest commit holding the blob.","rejected":"Reading device.toml from the manifest dir (a --device file of another name would be misjudged): the given file path is used. Printing before the pass/fail table: now printed after.","date":null,"about":"phone-pieces-drift-named"} {"project":"linux-phone-oco/device-template","id":"2026-11-18-template-research","entry_date":"2026-11-18","title":"Research: device-template, its children and drift","done":"Asked by the author through orchestration. Read the template's, labs' and idealkb's history and PRs (no phone, no lab changed); measured drift by blob id and manifest keys; a researcher read cruft, copier, GitHub templates, actions-template-sync, Yeoman, Nix, projen, Renovate at source. Recorded research device-template-drift-measured and device-template-follow-world, decision 2026-11-18-device-template-follows-by-release, six backlog items unranked, the hand-over device-template-how-it-stands, the subject's summary, and the failing test template-drift.sh (exit 1 today) in research/device-template/2026-11-18/.","considered":"Landing the test in device-template or a lab: neither has a failing-test convention and the labs are not this session's, so it lives in the research material and each item's proof names it. Checking device.toml's shape in the test: left to the schema decision (optional tables would give false failures).","rejected":"Re-recording device-template-follow (orchestration's, in progress): its rank would drop; the decision is tracked by it instead.","date":null,"about":"device-template"} {"project":"linux-phone-oco/docs","id":"2026-11-18-research-bringup-steps","entry_date":"2026-11-18","title":"Research: bring-up steps as data","done":"bringup-steps-research.r1 (research lead, from orchestration). Mined google-walleye-lab (161 backlog items, 120 session logs, the bring-up order plan), surya-lab and docs' surya records, lab-tools' lpoco-bringup and lpoco-health tests (a researcher subagent), and docs' tables (components, features, feature_support, support_status, milestones, tests, the parts feed). Looked around at 22 outside sources (a researcher subagent). Drafted the tables, records, query, seed and failing test and ran them in a scratch clone of docs. Recorded 18 sources, the research, the decision, 11 backlog items unranked, the hand-over row; landed data and the material only.","considered":"Landing the schema myself; steps as components; status typed in docs; edges as a list field; an issue tracker; per-driver probe steps; a 30-day expiry","rejected":"Landing tables.toml, records and queries here: AGENTS.md sends them to the owner, orchestration. The rest: see the decision's rejected.","date":null,"about":"bringup-steps"} +{"project":"linux-phone-oco/lab-tools","id":"2026-11-18-host-records-the-root-files-it-installs","entry_date":"2026-11-18","title":"host records the root files it installs","done":"Built host-plan-unreadable-not-new (lab-tools #173): Seen {Absent, Text, Unreadable} in FileChange, install record, plan wording. Programmer review: two findings fixed (only PermissionDenied counts as unreadable; no diff printed for an unreadable file).","considered":"Recording at check time (kept as host-record-from-check); a record keyed per file vs one file (one file, lines HASH DST).","rejected":"Treating every read error as unreadable: a non-UTF-8 readable file would be called up to date unread.","date":null,"about":"host-plan-unreadable-not-new"} diff --git a/docs/backlog.md b/docs/backlog.md index e0fdcad..ef66e71 100644 --- a/docs/backlog.md +++ b/docs/backlog.md @@ -4338,10 +4338,10 @@ Project : linux-phone-oco/lab-tools Status -: open +: done Note -: Coordinator, 2026-11-18: when lpoco-host installs a root file, it records the staged content's hash in user state (~/.local/state/lpoco-host, or ~/.cache/lpoco-host). Plan then treats a root file it cannot read as up to date when the staged hash matches the recorded one and its check passes (for 50-lpoco.rules: the share check), and as changed only when the staged content differs. Sign: planning 0.15.0 named /etc/polkit-1/rules.d/50-lpoco.rules '(new)' though the author's 0.14.2 prepare installed it at about 15:00 and the share check passed - the directory is root-only. The same limit applies to NetworkManager keyfiles (part 6b). Bootstrap: the lab has no record yet. Consider recording without root once a check proves the file in place (e.g. lpoco host check passing the share check writes the record for the staged hash), so no sudo is asked for an unchanged file. Then orchestration runs the 0.15.0 prepare itself, with 0 root commands. +: 2026-11-18, lab-tools-builder: done (lab-tools #173, main a4d4a3e). prepare records the git blob id of each root file it installs in ~/.local/state/lpoco-host/installed (lines 'HASH DST'), after every root command succeeded; plan reads a file under a folder the lab user may not enter (PermissionDenied) by that record: up to date when it matches, else planned as an install and worded 'unreadable, not known yet', never '(new)'. Proof: host/tests/plan.rs a_root_file_the_lab_user_cannot_read_is_judged_by_the_hash_recorded_at_its_last_install (seen failing first). Not done, now host-record-from-check: the lab has no record until the next prepare, so the first plan on it still names 50-lpoco.rules 'not known yet' and the first prepare reinstalls it (one sudo); a passing lpoco host check does not write the record; plan does not tie 'up to date' to the share check passing. The test assumes the suite does not run as root (mode 000 does not stop root). Opened : 2026-11-18 @@ -4797,3 +4797,31 @@ Proof About : bringup-steps + + + +### lpoco host check writes the install record for a root file it proves in place, so the first plan after 0.15 asks no sudo + +Project +: linux-phone-oco/lab-tools + +Status +: open + +Note +: From host-plan-unreadable-not-new (#173). Also: plan words 'up to date' only while the file's check passes (share check for 50-lpoco.rules). + +Opened +: 2026-11-18 + +Needs +: build + +Device +: xiaomi-surya + +Proof +: host plan test from fixtures: with no record and an unreadable rules folder, a passing share check records the staged hash and the next plan lists 0 root commands for it; a failing check records nothing + +About +: lpoco-host-rest diff --git a/docs/index.md b/docs/index.md index a38eff4..a8a9df9 100644 --- a/docs/index.md +++ b/docs/index.md @@ -4,7 +4,7 @@ The memory of linux-phone-oco, whose goal is Linux phones as good as Android for everyday use, and better: which phone supports which hardware, how we know, why decisions were made, and what is next. Plain versioned data; see AGENTS.md. The plan, and where Linux phones stand against Android and iOS: [the grand picture](picture.md), and the main screen, [features against Android and iOS](feature_support.md). -- [Backlog](backlog.md): 193 +- [Backlog](backlog.md): 194 - [Components](components.md): 21 - [Concepts](concepts.md): 10 - [Decisions](decisions.md): 72 @@ -22,7 +22,7 @@ The memory of linux-phone-oco, whose goal is Linux phones as good as Android for - [Platforms](platforms.md): 7 - [Problems](problems.md): 17 - [Research](research.md): 59 -- [Session Log](session_log.md): 119 +- [Session Log](session_log.md): 120 - [Shell Releases](shell_releases.md): 2 - [Sources](sources.md): 259 - [Summaries](summaries.md): 9 diff --git a/docs/session_log.md b/docs/session_log.md index 384933e..3de2b5c 100644 --- a/docs/session_log.md +++ b/docs/session_log.md @@ -2648,3 +2648,27 @@ Rejected About : bringup-steps + +--- + + + +### host records the root files it installs + +Project +: linux-phone-oco/lab-tools + +Entry date +: 2026-11-18 + +Done +: Built host-plan-unreadable-not-new (lab-tools #173): Seen {Absent, Text, Unreadable} in FileChange, install record, plan wording. Programmer review: two findings fixed (only PermissionDenied counts as unreadable; no diff printed for an unreadable file). + +Considered +: Recording at check time (kept as host-record-from-check); a record keyed per file vs one file (one file, lines HASH DST). + +Rejected +: Treating every read error as unreadable: a non-UTF-8 readable file would be called up to date unread. + +About +: host-plan-unreadable-not-new