Session Handoff [hw-cli]: liquidraver/ZephCore#101 awaiting owner review; #98 worktrees retired, shared Zephyr tree re-homed to r6-base #48

Next steps, in priority order

1. Monitor rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101 and answer the owner's feedback.
   • rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101 is the RX8130CE and YSN8900 weekday fix: clean branch rx8130ce-week-one-hot at 2621782, fork iteration PR rtc: write the RX8130CE weekday one-hot #45 at 44ed7e3.
   • List everything posted on rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101 and rtc: write the RX8130CE weekday one-hot #45 after 2026-10-05T19:36Z: issue comments, review comments and reviews.
   • Fix on the dirty branch first and run local review. Then re-squash and force-push the clean branch with a lease, on Pieter's go-ahead.
   • Before any rebuild in rx8130ce-week, delete its stale build folders (see What not to repeat). Rebuild every board a reply names at the exact head.
   • Done means the owner has merged rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101 or asked for nothing more.
2. When rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101 merges:
   • Close fork rtc: write the RX8130CE weekday one-hot #45 unmerged, and close RTC save writes the weekday in binary; the RX8130CE's WEEK register is one-hot #39 (it was fixed on both boards).
   • On Pieter's go, delete work/rx8130ce-week-one-hot and rx8130ce-week-one-hot, and remove the rx8130ce-week and rx8130ce-week-clean worktrees.
   • Keep r6-base. It now holds the shared Zephyr git worktree.
3. Hold companion: mark a CLI reply cut to the app frame (iteration branch) #27-companion: never treat an over-the-air CLI command as local (iteration branch) #32 until Pieter says go (his answer of 2026-10-04 on Session Handoff [hw-cli]: liquidraver/ZephCore #98 and #99 upstream; monitor them, reconnect with MeshCore and Zephyr sessions #41).
4. hw CLI on hardware (Add hw hardware-report CLI command (iteration branch) #1, Add the hw hardware-report CLI command (rebased, hw CLI only) #16). It has not been re-run since it was separated out.

External blockers

• Pieter's go-ahead is needed for any force-push of a clean upstream branch, any new upstream PR, any branch deletion, and any write to meshcore-dev/MeshCore or zephyrproject-rtos/zephyr.
• liquidraver's review of rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101.
• CodeRabbit on the fork allows one review an hour and must be requested. Copilot reviews upstream PRs on its own.

Internal dependencies

• Step 2 waits on rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101 merging, because the iteration PR and its branches are the working copy until then.
• RV3028 rules are shared with MeshCore (#3545, #3421) and Zephyr (#121252). Agree any change to them across the three sessions first.

State (re-derive: git worktree list, gh pr list, git -C <zephcore-hw>/zephyr worktree list)

• Fork dev = upstream dev = 108b96d. rak4631: use a fitted RAK12002 RTC, and keep its backup switchover enabled liquidraver/ZephCore#98 merged as cdd6cc6, cli: reject a negative sensor list start index liquidraver/ZephCore#100 as d1cc647.
• Open upstream PRs from this track: rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101 only, with no owner activity yet.
• Fork PRs: rtc: write the RX8130CE weekday one-hot #45 is at 44ed7e3. Add hw hardware-report CLI command (iteration branch) #1, Add the hw hardware-report CLI command (rebased, hw CLI only) #16, Elecrow ThinkNode M7: board, CH390 ethernet driver, wired TCP companion (iteration branch) #17 and companion: mark a CLI reply cut to the app frame (iteration branch) #27-companion: never treat an over-the-air CLI command as local (iteration branch) #32 are unchanged. rak4631: use a fitted RAK12002 RTC, and keep its backup switchover enabled (iteration branch) #35 and cli: bound sensor list's start index and its pages #44 are closed and their branches deleted.
• Worktrees: rx8130ce-week (dirty) and rx8130ce-week-clean belong to rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101. r6-base is detached at d1cc647. It holds the RAK4631 restore build and the real Zephyr git worktree at the manifest revision with ZephCore patches applied. rx8130ce-week/zephyr symlinks to it. Every rak4631: use a fitted RAK12002 RTC, and keep its backup switchover enabled liquidraver/ZephCore#98 worktree is removed.
• Build: export ZEPHYR_BASE to the real r6-base/zephyr path. rx8130ce-week/build-rak-rep was rebuilt there at 44ed7e3.
• Hardware: this session's RAK4631 (the one without the extra sensor modules) runs the r6-base repeater debug build of d1cc647: handle lpxz, 927.875, tx 1, advert.interval 0.
• Sibling sessions: MeshCore (meshcore-dev-meshcore-*) has Reject a negative sensor list start index 🤖🤖 meshcore-dev/MeshCore#3433 matching cli: reject a negative sensor list start index liquidraver/ZephCore#100. Zephyr (zephyrproject-rtos-zephyr-*) is unaffected by rtc: write the RX8130CE and YSN8900 weekday one-hot liquidraver/ZephCore#101.

The parked decision queue

0 issues carry decision on this fork.

What the last round did

• Pieter chose "Close rak4631: use a fitted RAK12002 RTC, and keep its backup switchover enabled (iteration branch) #35, delete branches". Fork rak4631: use a fitted RAK12002 RTC, and keep its backup switchover enabled (iteration branch) #35 is closed, and work/rak4631-rak12002-rtc and rak4631-rak12002-rtc are deleted.
• Pieter chose "Move Zephyr, remove 4". The shared Zephyr git worktree moved out of the rak4631: use a fitted RAK12002 RTC, and keep its backup switchover enabled liquidraver/ZephCore#98 worktree rak-rtc-r6 into r6-base. Then rak-rtc, rak-rtc-r6, rak-rtc-r6-clean and up-rak-rtc were removed (about 2.5 GB, build output only). Proof: a RAK4631 repeater build from an empty folder at 44ed7e3 succeeds.

What not to repeat

• A shared Zephyr tree cannot live in a plain folder. Zephyr's CMake finds modules by running west topdir from ZEPHYR_BASE. Outside a west workspace that finds nothing, and the build stops on Kconfig warnings (HAS_NRFX && 0). The first move went to a neutral folder and failed for this reason. Keep the tree inside a worktree that has .west/.
• Moving the tree strands every build folder configured against it. west build -p always runs pristine.cmake from the old cached path and fails, so delete the folder instead. These are still stale: build-m1-comp, build-x1-comp and build-r1neo-rep in rx8130ce-week, and build-rak-rep-dev, build-m1-comp-dev and build-rak-rep-restore in r6-base. The restore image still flashes; only rebuilding it needs a fresh folder.
• A reply's build claim outran the builds (round 7). Rebuild every board a reply names at the exact head before citing it.

New learnings

• The module-discovery constraint above is recorded in the maintainer's host memory, because it concerns this host's worktree layout and not the repository.