Session Handoff [rv3028-eeprom]: No upstream movement; cleanup deferred, every PR waits on maintainers

[ptr727]

Next steps, in priority order

1. Watch for replies to the 2026-10-05 triage comments on #3545 and #3421. Link Session Handoff [rv3028-eeprom]: All Copilot rounds answered; every upstream PR waits on maintainers #21, step 1 has the handling, including the parity rule if someone names a real "BSF handling" path.
2. Sweep every upstream PR and issue authored by ptr727. The commands are in link Session Handoff [rv3028-eeprom]: All upstream PRs answered; watch for maintainer review #18, step 1. Anything with updatedAt after 2026-10-06T01:00Z is new. Watch #3434 for a maintainer verdict.
3. Keep MeshCore, ZephCore and Zephyr in sync (project memory cross-firmware-parity-policy). ZephCore's current handoff is now ptr727/liquidraver-ZephCore#47, track hw-cli. Base class for companion radios meshcore-dev/MeshCore#46 is closed.
4. The two new MeshCore bugs are still ON HOLD until the RTC work lands. These are the CLI reply overrun and ClientACL out_path_len. Details are in link Session Handoff [rv3028-eeprom]: Two RTC PRs re-pushed with cross-firmware fixes; triage Copilot headlines #19, step 4.
5. If upstream dev moves, or a PR merges or is declined: follow link Session Handoff [rv3028-eeprom]: Three MeshCore PRs upstream; watch and respond to review #17, steps 3 and 4. Adopt an RTC only if its time registers read like that chip 🤖🤖 meshcore-dev/MeshCore#3544, Store RV3028 backup switchover and trickle charger config in EEPROM 🤖🤖 meshcore-dev/MeshCore#3545 and Read and write the RV3028 clock atomically, and reject switchover-garbled transfers 🤖🤖 meshcore-dev/MeshCore#3421 all touch AutoDiscoverRTCClock.cpp.
6. Cleanup is deferred at Pieter's choice (2026-10-06): "Watch only". Keep board 1CAB on the Read and write the RV3028 clock atomically, and reject switchover-garbled transfers 🤖🤖 meshcore-dev/MeshCore#3421 test build, and keep the -hw-3545, -hw-3421, local/rv3028-probe-* and local/rtc-probe-test worktrees, so a maintainer-requested re-test needs no rebuild. Ask again only once a PR merges or is declined.

External blockers

• MeshCore maintainers: review and merge of Adopt an RTC only if its time registers read like that chip 🤖🤖 meshcore-dev/MeshCore#3544, Store RV3028 backup switchover and trickle charger config in EEPROM 🤖🤖 meshcore-dev/MeshCore#3545, Write and read the RX8130CE WEEK register as one-hot 🤖🤖 meshcore-dev/MeshCore#3550, Read and write the RV3028 clock atomically, and reject switchover-garbled transfers 🤖🤖 meshcore-dev/MeshCore#3421, Do not feed an invalid GPS time into the RTC 🤖🤖 meshcore-dev/MeshCore#3422, Make GPS status reporting say what was actually checked 🤖🤖 meshcore-dev/MeshCore#3423, Treat the GPS enable pin as a pin number, not a truth value 🤖🤖 meshcore-dev/MeshCore#3425 (draft), Reject a negative sensor list start index 🤖🤖 meshcore-dev/MeshCore#3433 and Pass TELEM_RAK12500_ADDRESS to the RAK12500 I2C probe 🤖🤖 meshcore-dev/MeshCore#3434. Nothing is owed from our side.
• A Copilot re-request after any future push still needs Pieter, in the web UI.
• Zephyr: its BSF guard (local 67fda87) waits on Pieter in that session. zephyrproject-rtos/zephyr#121252 is still REVIEW_REQUIRED at 51fb6e72.
• ZephCore: liquidraver/ZephCore#101 (RX8130CE + YSN8900 weekday) is waiting on its owner's review.

Internal dependencies

• Steps 1 to 3 can run at any time.
• Step 4 waits for the RTC PRs (Adopt an RTC only if its time registers read like that chip 🤖🤖 meshcore-dev/MeshCore#3544, Store RV3028 backup switchover and trickle charger config in EEPROM 🤖🤖 meshcore-dev/MeshCore#3545, Read and write the RV3028 clock atomically, and reject switchover-garbled transfers 🤖🤖 meshcore-dev/MeshCore#3421) to land, at Pieter's decision. The CLI overrun fix touches CommonCLI.cpp bounds next to sensor list, so check Reject a negative sensor list start index 🤖🤖 meshcore-dev/MeshCore#3433 first.
• Step 6 waits for a merge or a decline, since the hardware builds exist to answer a re-test request.

State

Re-derived at the start of this round, 2026-10-06. Nothing changed from link #21's state table except where noted.

Upstream PR	Fix branch @ head (work branch @ head)	Copilot on head
#3544 RTC identity	fix/rtc-probe-identity @ 9d0d5e31 (c36cb9ee)	approval recommended
#3545 RV3028 EEPROM	fix/rv3028-eeprom-config @ 23b23b24 (e74c5c60)	answered
#3550 RX8130CE weekday	fix/rx8130ce-week-onehot @ 8c9c9772 (4cdd5d71)	approval recommended
#3421 RV3028 time read/write	fix/rv3028-atomic-read @ c408f88b (65907457)	answered
#3433 sensor list	fix/sensor-list-paging @ bbacf47a (ec05125f, fork PR #8)	1 wrong finding, answered and resolved

• Upstream dev is still 3e3150c8.
• Upstream activity since link Session Handoff [rv3028-eeprom]: All Copilot rounds answered; every upstream PR waits on maintainers #21: none from anyone else. The only update after 21:25Z was our own Reject a negative sensor list start index 🤖🤖 meshcore-dev/MeshCore#3433 thread reply at 21:46Z. Store RV3028 backup switchover and trickle charger config in EEPROM 🤖🤖 meshcore-dev/MeshCore#3545 and Read and write the RV3028 clock atomically, and reject switchover-garbled transfers 🤖🤖 meshcore-dev/MeshCore#3421 have no comment after our 19:32Z triage replies.
• ZephCore: #98 merged 2026-10-05T21:59Z, after link Session Handoff [rv3028-eeprom]: All Copilot rounds answered; every upstream PR waits on maintainers #21 was written. It's the counterpart of Store RV3028 backup switchover and trickle charger config in EEPROM 🤖🤖 meshcore-dev/MeshCore#3545, so the RV3028 EEPROM behaviour is now upstream in ZephCore and still pending in MeshCore. That's not a parity gap to act on, since the MeshCore code is identical and only waits on review. Feature Request: Graph Traversal & Signal Quality Mapping for MeshCore Networks meshcore-dev/MeshCore#99 and Added Support for the LilyGo TBeam v1.1 and v1.2 with the SX1276 meshcore-dev/MeshCore#100 are merged, and [Feature Request] boot tone for devices with a speaker meshcore-dev/MeshCore#101 is open.
• Hardware: unchanged. Board 1CAB is on the Read and write the RV3028 clock atomically, and reject switchover-garbled transfers 🤖🤖 meshcore-dev/MeshCore#3421 test build, and ZephCore's board 26B9 stays untouched.
• This round's hub worktree (ProjectTemplate-mc-rv3028) is detached at hub origin/main 62f0b33.

The parked decision queue

0 parked. The fork has no open decision issue. The one question this round, cleanup now or watch only, was asked and answered in the session: watch only.

What the last round did

• Resumed link Session Handoff [rv3028-eeprom]: All Copilot rounds answered; every upstream PR waits on maintainers #21 and re-derived the live state: upstream PRs and issues, dev, the ZephCore and Zephyr counterparts, and the peer sessions.
• Found nothing owed. Pieter chose to defer cleanup and keep the hardware builds ready.
• No code, push or upstream write.

What not to repeat

• gh issue view --comments can't be combined with --json. Use --json comments to read a link's comments.
• Everything in the "What not to repeat" sections of links Session Handoff [rv3028-eeprom]: All Copilot rounds answered; every upstream PR waits on maintainers #21, Session Handoff [rv3028-eeprom]: Two RTC PRs re-pushed with cross-firmware fixes; triage Copilot headlines #19, Session Handoff [rv3028-eeprom]: All upstream PRs answered; watch for maintainer review #18 and Session Handoff [rv3028-eeprom]: Three MeshCore PRs upstream; watch and respond to review #17 still holds.

New learnings

• None beyond the line above. A round with no upstream movement only needs the sweep, not a full re-read of the chain.

[ptr727]

Continued in #23, round 8 on track rv3028-eeprom.