D-10 closure runbook v2: lab build + lab infocheck driven workflow #105
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_proc#105
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Why this issue
hero_proc#102 tracks D-10 closure (every demo-set repo passes
lab build+lab infocheckcleanly). The per-session "manual sweep" playbook we refined across s101–s107 has been superseded by thelab build --release --install --workspace+lab infocheckdriven flow. This issue is the canonical runbook for closing the remaining work under the new tooling.Current state (2026-05-17 session, after live
lab infocheckinventory + 6 rebuild probes)lab build --release --install --workspace(no source changes).service_base!(), noservice.tomlon disk; need full canonical-base bootstrap).mycelium_networkis not a Rust workspacelab infocheckcan audit; out of scope.The 17 effective-clean break down: T1 = 6/6, T2 from prior manual sweeps = 6/6 (hero_slides, hero_books, hero_biz, hero_collab, hero_office, hero_foundry), plus the 6 stale-install confirmations = hero_compute, hero_proxy, hero_codescalers, hero_whiteboard, hero_memory, hero_embedder. Live tracker #102#33220 carries the full per-session history.
The 15 remaining wholesale-shape repos (D-10 real work)
Source state: 0 of N main.rs files have
service_base!(), noservice.tomlon disk. Each needs full canonical-base bootstrap.hero_os— s12270f627d(5 binaries: cli + server + admin + app + web; service_base!() macro wholesale + lesson #19 forward_env_if_set on both spawned ActionSpecs + PATH_ROOT env block added to server+admin service.tomls; smoke 6/6 met)hero_osis— s1237d8b3a2hero_livekit— s11401e48e7(4 binaries: server + admin + lk-backend + hero_do_hero_livekit)hero_logic— s110 ba74b2bhero_indexer— s109 e60eca8hero_voice— s119f8503b3(4 binaries: cli + server + admin + voiced; first end-to-end validation of transcribe + TTS branches of herolib_ai v0.6.0 API + pairedsrc/bin/hero_voice.rs → src/main.rsrestructure, 5/5 met)hero_agent— s120a141d48(3 binaries canonical + herolib_ai v0.6.0 transcribe-surface migration — last AI-rename ripple absorbed, 5/5 met)hero_code_indexer— s111 95ccdadhero_lib_rhai— s121b4d138ahero_matrixchat— s115635619b(3 binaries canonical + web.sock→admin.sock pair, 5/5 met)hero_planner— s116bdfbfb4hero_researcher— s118ee3431b(2 binaries: cli + server; herolib_ai v0.6.0 migration paired + web.sock→admin.sock rename, 5/5 met)hero_wallet— s11242cb6393hero_webbuilder— s1175f726af(4 binaries: cli + server + admin + web; herolib_ai v0.6.0 migration paired with D-10 sweep, 5/5 met)hero_website_framework— s1136c88a34Per-repo runbook (safe-by-default variant)
This variant adds two checkpoints to the standard flow — it doesn't fork from it. Same commands, same destination, just two extra pauses to confirm no broken state ships.
Release pipeline (linux-x86_64 binaries)
Once a repo is clean (D-10 acceptance), publish via:
Uploads to a rolling
lab-latestForgejo release on the repo. Other machines fetch vialab build --download --install <repo>.Methodology notes
lab infocheckmeasures local install state, not just source. If$PATH_ROOT/bin/<name>exists, it runs the installed binary's--info --json. So a repo can read "dirty" on a stale machine and "clean" on a fresh one. Alwayslab build --release --installbefore reading the inventory for an authoritative count.lab buildexits 0 even when targets fail. Parse~/hero/var/build_report.md("targets: N built, M failed") for the truth, not the exit code.lab build -uauto-pushes the working branch. Under the no-PR workflow used here, skip-uand pull manually. Kristof's parallel agent fleet uses the-upath with auto-push; that's also fine — different gate position, same destination.lab build --repaironly fires on cargo compile failures, not on pre-build--info-gate failures. Wholesale-shape repos (noservice_base!()wiring) must be hand-bootstrapped or driven vialab agent; the build repair loop won't bootstrap them.Related
mik-tf referenced this issue from lhumina_code/hero_demo2026-05-18 00:10:28 +00:00
mik-tf referenced this issue from lhumina_code/hero_demo2026-05-18 23:31:36 +00:00