ampere: apply lmcp v1.2.1 cutover (tools.d/ migration) #23
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to closed issue #22. ampere (CoolPi GenBook RK3588) still runs the pre-1.2.1 fork-and-drift pattern: a local
/opt/lmcp/server.luaoverride that hand-mergedfetch+web_searchtools instead of using the packaged copy. After v1.2.1 cutover the tools migrate totools.d/plugins, override goes away, futureapt upgrade lmcpdeliveries land cleanly.Pre-staging needed (when ampere is up)
/opt/lmcp/for existing overrides + identify ampere-specific tools to migrate (likely justfetch+web_search, but check)/opt/lmcp/tools.d/ampere.luaplugin shape (analogous to hertz.lua, 9756 bytes)lua5.4 -e "dofile(/opt/lmcp/tools.d/ampere.lua)"syntax checkCutover sequence (mirror of hertz, ~1 minute hands-on)
Blocker
ampere is a laptop without remote wake (no WoL/IPMI/smart-plug power-cycle on the ampere DECT outlet). Needs physical lid-open + login. Last verified powered-off 2026-05-18 ~03:00 (per shutdown sequence after the data + nuccies poweroff).
Low priority — fetch/web_search are now available via hertz-tools (closes the user-facing symptom). ampere just runs lmcp internally; clean-up is for pattern hygiene + future-proofing against override drift.
References: issue #22 (closed 2026-05-18 by hertz cutover), marfrit-packages PR #25 (lmcp 1.2.1, merged).