Repository navigation
Description
Summary
Feature request from Discord #feature-requests (reporter: nickywilks6405): Power-loss autostop (VBT-style) — auto-end a set when power drops X% below the set's best rep, as an alternative to a fixed rep target.
Request details
Core
Auto-end set when power drops X% below the set's best rep, as alternative to fixed rep target.
Why power, not velocity
Standard VBT assumes fixed load. Echo holds speed and varies resistance, so fatigue shows as force drop. Power (F×v) covers both: fixed-load modes reduce to velocity loss (matches research thresholds), Echo reduces to force loss. One setting, all modes.
Metric — per-rep Mean Concentric Power (MCP)
Sample-wise Σ(F×v) across cables, averaged over concentric phase (velocity crosses small positive threshold → top turnaround). Reference = best MCP among working reps (warm-ups excluded), not necessarily rep 1. Trigger when 1 − MCP_n/MCP_best ≥ threshold. Echo: trigger concentric only; log eccentric separately.
Thresholds (research-backed)
~10% power, ~20% strength (≈RPE 7–8), 20–30% hypertrophy, avoid >35%.
Guards
- ≥2 working reps before trigger
- Reps <85% of reference ROM count as triggering (short reps hide power loss)
- Max-reps backstop
- Optional 2-consecutive-reps requirement
UX
Config: Rep target | Power-loss target. Presets 10/20/30%, custom 5–40% (warn >35%). Live % loss per rep + audio cue at threshold−5%; end behaves like existing rep auto-stop. Summary: "Stopped at rep 9 — 21% power loss (best: rep 2)" + per-rep MCP.
Scope v1
In scope: Old School, Pump, Just Lift, Echo. Out of scope: TUT/Eccentric-Only (tempo changes power meaning).
Logging
Per rep: MCP, % loss, ROM, con/ecc split. Per set: threshold, trigger/best rep. Richer export data.
Maintainer questions (from the reporter)
- Per-cable force + velocity sampled fast enough?
- Echo: eccentric load derived from concentric force?
- Interplay with stall countdown / VBT voice?
Expected behavior
A configurable "Power-loss target" alternative to the fixed rep target that auto-ends the set when per-rep mean concentric power drops by the configured percentage below the set's best working rep (warm-ups excluded), with live per-rep % loss display, an audio cue at threshold−5%, and a set summary such as "Stopped at rep 9 — 21% power loss (best: rep 2)" plus per-rep MCP.
Actual behavior
Not applicable — this is a feature request; no power-loss-based auto-stop alternative to the fixed rep target exists today.
Impact / notes
Applies to the mobile app workout modes Old School, Pump, Just Lift, and Echo. The request deliberately excludes TUT/Eccentric-Only because tempo changes what power means. Echo specifics: trigger on concentric only, log eccentric separately. The request also anticipates richer export data (per-rep MCP, % loss, ROM, con/ecc split; per-set threshold and trigger/best rep).
Attachments
None recorded on the Discord message.
Original Discord Report
**Feature request: Power-loss autostop (VBT-style) — <@&1509574103043145931>**
**Core:** Auto-end set when power drops X% below the set's best rep, as alternative to fixed rep target.
**Why power, not velocity:** Standard VBT assumes fixed load. Echo holds speed and varies resistance, so fatigue shows as *force* drop. Power (F×v) covers both: fixed-load modes reduce to velocity loss (matches research thresholds), Echo reduces to force loss. One setting, all modes.
**Metric — per-rep Mean Concentric Power:** sample-wise Σ(F×v) across cables, averaged over concentric phase (velocity crosses small positive threshold → top turnaround). Reference = best MCP among working reps (warm-ups excluded), not necessarily rep 1. Trigger when `1 − MCP_n/MCP_best ≥ threshold`. Echo: trigger concentric only; log eccentric separately.
**Thresholds (research-backed):** ~10% power, ~20% strength (≈RPE 7–8), 20–30% hypertrophy, avoid >35%.
**Guards:** ≥2 working reps before trigger; reps <85% of reference ROM count as triggering (short reps hide power loss); max-reps backstop; optional 2-consecutive-reps requirement.
**UX:** Config: Rep target | Power-loss target. Presets 10/20/30%, custom 5–40% (warn >35%). Live % loss per rep + audio cue at threshold−5%; end behaves like existing rep auto-stop. Summary: "Stopped at rep 9 — 21% power loss (best: rep 2)" + per-rep MCP.
**Scope v1:** Old School, Pump, Just Lift, Echo. Out: TUT/Eccentric-Only (tempo changes power meaning).
**Maintainer questions:** 1) Per-cable force + velocity sampled fast enough? 2) Echo: eccentric load derived from concentric force? 3) Interplay with stall countdown / VBT voice?
**Logging:** Per rep: MCP, % loss, ROM, con/ecc split. Per set: threshold, trigger/best rep. Richer export data.
Discord-Message-ID: 1569561696542920725
Activity
9thLevelSoftware commentedon Nov 10, 2026
Feasibility assessment — ACCEPT (high confidence), phased
Repo ownership:
project-phoenix-mp(mobile). All four in-scope modes are mobile; portal involvement is data display only.Key finding: the expensive part already exists.
RepMetricData(RepMetrics.kt) already captures per-sample per-cable loads (A/B, kg) + concentric velocities at notification rate (documented 50 Hz curves) and computes per-repavgPowerWatts= mean(force × velocity) over the concentric phase — exactly the requested per-rep Mean Concentric Power.isWarmup,rangeOfMotionMm, and the auto-stop coordinator inActiveSessionEngine(with an existing warm-up gate) cover the trigger formula, ROM guard, and "≥2 working reps" requirement.Maintainer questions:
eccentricOverload% in the BLE Echo frame today (not derived from measured concentric force). Fine for v1: trigger is concentric-only and eccentric is logged separately from already-captured samples.VbtPreferences.velocityLossThresholdPercentis the UX precedent.Assumptions: per-exercise opt-in setting ("Rep target | Power-loss target", default = Rep target); trigger policy = best working rep as reference, ROM <85% counts as triggering, max-reps backstop, optional 2-consecutive-reps flag; v1 modes Old School/Pump/Just Lift/Echo only.
Risks: trigger-policy correctness (mitigate: pure-logic module + tests first); persistence ripple across backup/sync/CSV for the new config field (same path as
stallDetectionEnabled).Effort: 4–6 bounded packets (~1–2 weeks): trigger policy + tests → engine wiring → config UX/HUD/summary → logging/export ripple → polish. Next stage: architecture + integration modelling, then UI prototype (config selector, live % loss, set summary) before signoff.
9thLevelSoftware commentedon Nov 10, 2026
Architecture for #1392 is complete; implementation has not started. Opt-in Power-loss target for Old School/Pump/Just Lift/Echo, with 10/20/30% presets, custom 5–40% (>35% warning), mandatory max-reps backstop and optional two-consecutive rule.
Important feasibility correction: existing power analytics use summed loads times the faster cable velocity, not exact paired-cable MCP; the design adds a versioned validated per-cable signal and leaves historical metrics unchanged.
Best valid working rep excludes warmups; evaluate from second working attempt; <85% ROM on any active cable counts as a separate trigger. Invalid signal shows unavailable, never fabricated fatigue.
One execution target plan keeps firmware/app max reps aligned; centralized leased completion preserves safety and avoids competing velocity auto-end/duplicate stops. Local history/export preserve per-rep and trigger evidence; cloud payloads change only after verified server support.
Next: integration model, then actual-UI prototype and model signoff. Hardware/phase validation is a release gate, not evidence already obtained.
9thLevelSoftware commentedon Nov 10, 2026
#1392 integration model is complete and parent-reviewed. Mapped routine/template/ad-hoc configuration, validated paired-cable samples, the pure power-loss policy, one execution target plan, and leased one-winner completion into existing mobile paths. Pending concentric attempts remain distinct from bottom-confirmed completed reps.
Local history durability, atomic frozen completion facts, backup, and versioned export are mandatory v1 work. Remote feature fields remain deferred: legacy power semantics and payloads stay unchanged, with no new wire keys; local metadata must survive legacy pull/merge. Existing sync is not a backup of these new fields.
The model includes implementation dependency packets and a future test/fixture matrix, not passing test results. Next: an actual-UI-grounded Android/iOS prototype, then escalated-model signoff, with no human-wait gate. This is not implementation authorization or final merge approval; no build, runtime, device, or server-contract proof is claimed.
Artifact: /Users/christopherwilloughby/.hermes/phoenix-enhancements/issue-1392-1569561696542920725/integration-model.md
9thLevelSoftware commentedon Nov 10, 2026
#1392 prototype update: the integration model is complete, but the actual-app visual gate is blocked; no prototype screenshots or implementation are being claimed.
A clean current-main checkout was tested with the prescribed Phantom launcher. It refused before build/launch because its required pinned simulator fixture is absent from current main. The current PhoenixApp iOS host is present; this is not the old host-rename issue. The required config/HUD/history screens also now live in phoneMain, outside this prototype card's authorized edit paths; the launcher clean-tree requirement also needs a supported temporary-mock workflow.
Next: restore a supported current-main capture contract and authorize the current UI paths, then render configuration, live loss/quality/pending-attempt states, and summary/history in the actual app. The visual gate stays incomplete; no feature implementation or merge approval is unlocked. No additional reporter details or human approval are needed for this tooling blocker.
9thLevelSoftware commentedon Nov 13, 2026
Power-loss prototype progress (#1392): the old launcher and edit-scope blockers are superseded by the coordinator's capture authorization. The current PhoenixApp simulator framework and native host now build successfully.
Capture reached a different blocker: the app shows “Local data preserved / STARTUP_INITIALIZATION_FAILED” before the proposed UI appears, including after relaunch. The built app has empty required Supabase URL/anonymous-key configuration; native logs show dependency resolution blocked after database initialization. The redacted diagnostic does not prove that configuration is the only cause.
The draft and native startup logs/screenshots are retained, but those screenshots are diagnostic—not the power-loss prototype. The visual gate remains incomplete; no implementation or signoff is authorized. Next: supply the standard local build configuration securely (or a sanctioned offline capture recipe), then capture the proposed setup, HUD and history on iOS/Android. No reporter action is needed. No production branch was changed or pushed; the test installation was removed.
9thLevelSoftware commentedon Nov 14, 2026
Prototype stage progress — corrected interactive prototype delivered; native in-app capture still blocked at app startup
Done this run (2026-11-13):
prototype/frontend/screenshots/.//comment semantics truncatedSUPABASE_URLtohttps:— fixed viaSLASHindirection + xcodebuild overrides (built Info.plist now carries the full placeholder URL); (2) simulator Keychain -34018 (unsigned build) KoinMainViewModel → PortalTokenStorageabort — fixed with a simulator-only fallback to NSUserDefaults (devices rethrow).Still blocked: the app continues to show
STARTUP_INITIALIZATION_FAILEDafter both fixes (presence=UNAVAILABLE; underlying exception intentionally redacted). Zero accepted native prototype PNGs;prototype_gate_completestays false. Android not captured — no emulator/device on this host.Representative corrected interactive-prototype frames (simulated design data, no trainer control):



Unblock needed: a way to see the redacted underlying startup exception (diagnostic build/flag), or a sanctioned offline native capture recipe. Evidence:
prototype/native-screenshots/capture-receipt.json,prototype/native-startup-after-keychain-fallback.log.9thLevelSoftware commentedon Nov 14, 2026
In-app prototype — native visual evidence delivered (prototype gate complete)
The power-loss autostop UI rendered in the actual Phoenix app (current
iosApp/PhoenixAppsimulator host, built with xcodebuild from the disposable prototype branch, committed locally and never pushed) on the dedicated iOS 27 simulator, captured headless per the sanctioned capture contract (XCUITest/launch-argument scene routing +simctl io screenshot). Simulated design data only — no trainer control, no BLE, no live sensor feed, no hardware or efficacy validation.Startup blocker resolved (no guards bypassed): the prior
STARTUP_INITIALIZATION_FAILEDwas cleared by fixing the xcconfig//comment truncatingSUPABASE_URLand the simulator Keychain -34018 Koin abort (simulator-only fallback); the suspected SQLite duplicate-column migration errors proved non-fatal — schema reconciliation reports267 ops … 0 failed,Initialization complete, and the app renders normally.Configuration
Rep target (default) · config-rep-target
Power-loss target 20% · config-power-20
Custom threshold 36% with the >35% caution · config-custom-caution-scrolled
Unsupported mode → explicit REP fallback, POWER config preserved dormant · config-dormant-rep-fallback
Live HUD
Near-limit cue (16% ≥ cue from 15% = threshold−5) · hud-near-limit-cue
Trigger stop (21% ≥ 20% — "Set ended · power-loss target reached") · hud-trigger-stop
History / set summary
"Stopped at rep 9 — 21% power loss (best: rep 2)" with per-rep MCP table (★ best / ! trigger, eccentric "Not recorded", 8 completed reps vs attempt 9 semantics) · history-stopped-summary
Notes
prototype/native-screenshots/capture-receipt-run-1994.json; gate artifact:prototype/prototype-gate.md.9thLevelSoftware commentedon Nov 14, 2026
#1392 — Power-loss autostop design signoff
Decision: APPROVED for implementation specification and subsequent development, with the binding corrections below. Not release, hardware-readiness, or merge approval.
1569561696542920725; cardt_78609abf.phoenix-rca; actual model:gpt-6-astra(openai-codex).1. Reviewed inputs and evidence
Read the complete canonical ticket including original request/reply, feasibility.md, architecture.md, integration-model.md, prototype/prototype-gate.md, prototype/design/ui-spec.md and capture-receipt-run-1994.json. Read live GitHub issue/body/comments: OPEN, enhancement, not deferred. Read all 10 Discord thread messages available at review; newest was 1570999215885394021. No new reporter scope change or explicit human approval was present in those messages/GitHub comments. Decision is independent model review, not inferred consent from bot posts.
Independently viewed all 8 native PNGs and verified their hashes against the capture receipt; full hashes in signoff-audit-receipt.json. These show REP default, POWER20, custom selection and scrolled36 caution, dormant TUT fallback, near-limit/terminal HUD, and history. They are simulated design-state visuals, not executable feature acceptance. Source references in architecture/integration are historical inspected-baseline evidence; this signoff did not rerun source analysis, builds, native capture, app tests, audio or trainer tests.
2. Rationale and approved scope
The design matches the request: opt-in per-exercise POWER alternative for Old School/Pump/Echo and Just Lift style; paired-cable concentric power, best valid working reference, warmup exclusion, second-observed-attempt minimum, ANY active cable short-ROM guard, mandatory cap and optional two-consecutive qualification. Presets10/20/30, custom integer5–40, >35 caution, once-only near-limit cue, honest attempt/completed summary and per-attempt data are covered.
Architecture corrects feasibility's central error: legacy average power is not the required paired signed MCP. A new versioned ordered control signal, single execution target plan, leased completion arbitration and frozen durable companion facts are appropriate boundaries. V1 local history, backup and versioned export are mandatory; remote POWER settings/results are explicitly deferred with unchanged legacy wire payloads. No efficacy, RPE-equivalence, guaranteed sampling cadence or firmware internal force-algorithm claim is approved.
The eight real-host iOS captures are sufficient for design direction with the bounded corrections in this document. I explicitly amend the earlier requirement to capture both platforms/light-dark/large-text before this design signoff: uncaptured Android and accessibility variants move to mandatory implementation acceptance, not a claim they passed or a release waiver. This is a stage sequencing decision, not equivalent Android evidence. No further product-intent question is needed.
3. Binding decisions and corrections (override conflicting upstream text)
A. Control policy and deterministic reasons
B. Native UI corrections, required in implementation specification
These are visible limitations, not successful acceptance results:
Reps 12with POWER selected. UseSaved reps: 12and adjacent POWER-active indication, as ui-spec already requires; do not rely on an offscreen disclosure.10from%andCustomintoCus/tom. Use adaptive rows/stacking and nonbreaking numeric-unit labels; no intra-word wrapping. Preserve reachable Apply/Cancel under small height, keyboard and large text. Dormant fallback capture does not prove its footer is reachable in all states.REPlabel with no visible count/attempt, and the lower card runs behind the bottom load panel. Render authoritative completed count plus working-attempt/pending identity and ensure essential status/Stop remain unobscured using real inset/height constraints. Do not fill counts from fixture loss or nominal target. Preserve existing Metrics/Demo/Stats pager and safety controls.Set endedwhile retaining a live STOP surface. Production must distinguish committedEnding set…from actual completed transition, then use existing summary/navigation. A candidate or sent command is not proof physical resistance released. No new confirmation or delay.ROM A/B · mmEccentricheadings run together. Implement the specified compact core rows with expandable details, not this crowded wide table. Use text best/trigger labels and screen-reader semantics, not only star/exclamation symbols. Include reference-at-decision, units, per-cable ROM/trust, phase durations, separate eccentric quality and pending/completed state. Missing data stays unavailable; no invented eccentric zero.Stopped at rep 9headline is approved ONLY with the adjacent8 completed reps / lifting attempt9clarification shown. Actual completed count is never promoted to match headline. The first row's zero loss is relative to its own decision-time reference, not retrospectively to final best.C. Capture and security provenance correction
The capture receipt explicitly records a simulator-only NSUserDefaults substitution for secure token storage plus placeholder Supabase configuration. Therefore prior blanket wording 'no secure-store check was bypassed' / 'no guards bypassed' is not accepted as proof of ordinary startup or production security. These are disposable capture accommodations, not a production Keychain remediation. This signoff neither authorizes transplanting them nor certifies their scope was security-audited. No real credentials may enter that fixture store. Production implementation starts from supported main and preserves real secure storage/startup guards; exclude launcher routing, diagnostics, placeholder settings, capture fixtures and storage substitution. Reverify normal signed startup independently. SQLite duplicate-column/nonfatal reconciliation is a parent-log finding, not a fresh RCA by this reviewer.
4. Mandatory acceptance before release/enablement
Implementation specification must copy these as gates, not optional follow-ups:
5. Handoff
Proceed through bridge-managed
implementation_specand user instructions, then bounded implementation. Priority of authority: this signoff's corrections > architecture/integration contracts > UI spec > visual fixtures; feasibility is historical and superseded where inconsistent. No new tasks created here; no app code modified. Attach this signoff to the downstream packets and carry every acceptance hold through final review. Re-review material scope/algorithm changes rather than silently broadening approval.Confidence: high for design scope and documented integration approach; medium for final layout fidelity; runtime/sensor/physical-stop correctness unverified. Approval is a reviewed design decision with explicit constraints, not a completion claim for the feature.
9thLevelSoftware commentedon Nov 14, 2026
Implementation plan — power-loss autostop (spec complete)
Implementation spec + user instructions are written from the approved design (signoff.md binding corrections carried through). This is a development plan, not implementation authorization, release approval, or merge approval.
Scope: opt-in per-exercise Power-loss target (REP | POWER) for Old School, Pump, Just Lift, Echo — paired-cable Mean Concentric Power (MCP V1), best-valid-working-rep reference, warm-up exclusion, short-ROM guard (<85% on any active cable; trusted short ROM may qualify with missing power), mandatory max-reps backstop, optional 2-consecutive. Local-only data + versioned export; no new wire keys; legacy average power/payloads unchanged; remote feature data deferred. Off by default behind a capability gate.
Bounded packets (P0–P8):
ExecutionTargetPlan: deterministic reducer incl. SHORT_ROM-over-POWER_LOSS tie-break, unrounded threshold equality, unknown-ROM no reference promotionMandatory gates copied from signoff §4: pure signal/policy fixtures · production engine race tests · durability/compatibility · Android+iOS UI incl. accessibility · physical trainer phase/sign/cadence/stop evidence · security/release (no capture-only accommodations, exact-head CI, fresh PR review).
Full packet map, allowed/forbidden scope, test anchors, visual QA protocol and acceptance criteria:
implementation-spec.md; user-facing behavior + release-note draft:user-instructions.md(both in the ticket artifact directory).9thLevelSoftware commentedon Nov 15, 2026
🚀 Implementation in progress — PR opened
PR: #1401
Phase 1 of the signed-off implementation (spec packets P1 + P2 + P3-seam) is committed, tested, and open for review:
9.81/1000 × Σ(load × max(v,0))W, idle cable zero, no cross-cable substitution, signed lowering excluded) with enumerable quality reasons, ordered accumulator, and a sealing concentric phase normalizer.PowerLossPolicyreducer carrying signoff corrections SD1–SD4 as hard requirements (frozen reference-at-decision facts, unrounded threshold equality, trusted short-ROM qualification surviving missing power, SHORT_ROM-over-POWER_LOSS tie-break with both facts persisted, unknown-ROM no reference promotion, cap independence), plusExecutionTargetPlanand the capability gate.SetEndReasonMAX_REPS_BACKSTOP / POWER_LOSS / SHORT_ROM, per-set controller in the engine, POWER-only velocity auto-end/voice suppression, once-per-set near-limit cue, and a non-blocking stop path (SD5).Verification at exact head: targeted powerloss + end-reason suites green (
:shared:iosSimulatorArm64Test). Zero regressions proven by A/B against baselinemain@4d4de558: both baseline and branch show the identical 1105 tests / the identical 14 pre-existing failures (4 test-harnessreadProjectFilesource-resolution failures + 10 set-summary lifecycle assertion failures — present onmain, untouched by this PR).Remaining packets (P3-remainder engine completion races, P4 storage/export, P5 UI, P6 tests, P7 visual QA, P8 trainer validation) land on this branch before the merge gate. Feature ships off by default behind the capability gate. Full plan: implementation-spec.md; user guide + release notes: user-instructions.md.
feat(power-loss): frozen P3/P4/P5 evidence contract (#1392)
feat(power-loss): frozen power-history export v1 facade (#1392)
feat(power-loss): P5 UI state, copy, config draft, HUD/summary/histor…
feat(power-loss): P4 tier-1 companions + migration 64 + atomic eviden…
5 remaining items
feat(power-loss): P3 one-winner evidence latch, WORKOUT_COMPLETE cap …
test(power-loss): golden no-new-wire-keys guard for mobile-sync-push (#…
9thLevelSoftware commentedon Nov 17, 2026
🚀 Implementation progress — P3 core + P4 tier-1 + P5 main UI landed on PR #1401
PR: #1401 (head
5a6ff36b, basemain, MERGEABLE)Since the phase-1 slice, the following bounded packets are committed, tested, and pushed:
PowerLossEvidence+WorkoutExitSnapshot): the winning end reason and its frozen evidence latch before claim/teardown; rawWORKOUT_COMPLETEon a finite POWER plan normalizes toMAX_REPS_BACKSTOP(neverTARGET_REPS_REACHED, never inferred fatigue); live HUD facts feed; POWER-only velocity-auto-end/voice suppression; once-per-set near-limit cue with terminal/safety supersession; non-blocking stop path (SD5).SchemaManifest/MigrationStatementsupdated together;validateSchemaManifestgreen: 812 columns / 68 tables), atomic evidence commit (attempt-only trigger rows survive), and power-history export v1 (codec + exporter + Koin wiring + null-vs-zero-preserving roundtrip).ExerciseConfigModalSet-target section (presets 10/20/30 + Custom 5–40 with persistent 36–40 caution, max-reps dynamic bound, two-consecutive SD1 helper, short-ROM safeguard copy, Echo concentric-only note),WorkoutHudpower-loss readout + attempt identity (8 completed reps · attempt 9 not confirmed complete),SetSummaryCardheadline + completed/attempt clarification,HistoryTabcompact rows — SD6 corrections applied.PowerLossNoNewWireKeysTestpins the exact 55-path serialized wire surface of sessions + rep telemetry (pre-feature contract: the wholedata/syncchain is byte-identical tomain@4d4de558on this branch), asserts no power-loss identifier reachesmobile-sync-push, and guards the legacypowerWatts = avgPowerWattsmapping.Verification at exact head
5a6ff36b::shared:iosSimulatorArm64Testincl.PowerLossPolicyTest32,PowerLossConfigDraftTest17,PowerLossAcquisitionTest14,PowerLossHudUiStateTest12; 45:shared:testAndroidHostTestincl.SchemaParityTest35,PowerHistoryExportRoundtripTest).main@4d4de558(same harness:shared:iosSimulatorArm64Test): baseline 4230 tests / 252 failed; branch 4348 tests / 229 failed — zero failures unique to the branch (all 229 are pre-existing on main; 23 baseline-only failures are flaky sync-suite tests that pass on the branch). New tests account for the +118 test delta.Remaining packets (on this branch before merge): P3 remainder (single-target propagation + production race tests), P4 remainder (backup v7 sections, versioned routine CSV / lossy-export block, runtime snapshot codec + restart/rebaseline), P5 remainder (bottom-sheet/JustLift/set-ready surfaces + routine propagation + export UX), P6 cross-cutting hardening, P7 implementation-branch visual QA (merge gate), P8 trainer evidence (release gate). Feature stays off by default behind the capability gate; no merge authorized.
fix(power-loss): pin QA schema-head contract markers to user_version …
test(media): move Phase-1 schema gate baseline to 64.sqm (#1392 lande…
feat(power-loss): propagate one effective execution target plan throu…
feat(power-loss): backup v7 companion sections + versioned routine CS…
feat(power-loss): bottom-sheet/JustLift/set-ready surfaces + config p…
fix(power-loss): pin QA schema-head doc markers to user_version 68 (#…
fix(power-loss): wire live HUD power facts into the active workout HUD (
fix(power-loss): render the full ui-spec §4 power panel in the HUD re…
fix(power-loss): render the ui-spec §6 summary block + per-attempt ta…
fix(power-loss): render the E04 uncertain-reference HUD state (#1392)
fix(power-loss): reset the live power HUD at set boundaries (#1392)
fix(power-loss): keep the committed cap winner in set summary + evide…