Repository navigation
Runtime lock selects OctoScript-Makepad b1596d9c, which is not on main (current shared runtime is 463e3da8) #4
Description
native-runtime.lock.json (and the octoscript-render git rev in the Cargo manifest) select OctoScript-Makepad b1596d9c2cee6e80cca9d27b1b0c2d57b9d28dd8 ("Include the current Android Home and build-tool support in the shared release", 2026-09-16). That commit is not on OctoScript-Makepad main: the GitHub compare API reports b1596d9c...463e3da8 as diverged, main 190 commits ahead.
Every other consumer is on the current shared runtime: OctoScript-App-Design-Flow's native-runtime.lock.json and the App Hub build select OctoScript-Makepad 463e3da8 (makepad cd812acd, Octoscript 68f6a9df). The README says this repository shares the one runtime with the other OctoSense applications; with this pin, tools/setup-native.py here and in App-Design-Flow disagree about the sibling checkouts, so they cannot share one workspace.
Suggested fix: bump the lock (and the matching Cargo revs) to 463e3da8ac170a987e34552a1f96551d2a2cc6ea and rerun python3 tools/setup-native.py --check --cargo-manifest …. Not done in the docs audit because it is a build change that needs a device check.
Found during the hackathon docs audit.
Activity
Docs: note the off-main runtime lock (#4); date the e1c2164b constrai…
Merge pull request #6 from OctoSense-org/docs/hackathon-audit2
ymote commentedon Sep 27, 2026
Fixed by #7 (merge 32cf526): the lock and octoscript-render revs now select Octoscript-Makepad main 297ff0bb (makepad cd812acd, Octoscript 68f6a9df). b1596d9c was the pre-history-rewrite hash of Octoscript-Makepad main f4acc6c (only scrubbed home-directory paths differ), so nothing needed porting. Host check, setup-native --check and the host route probe (42 routes, 0 suspicious) pass; no NDK build or device run was done.