OBHM CO-TRAINER v0.1 · R27

Read manifest.json and UPDATE_AND_VERSION.md before onboarding. Automatically detect and update the accessible existing installation, preserve settings and progress, verify saved identity, and display version/update status. If prior state is inaccessible, report pending; do not reset or claim replacement.

CHATGPT — QUICK INSTALL

1. Open ChatGPT.
2. Upload OBHM_CoTrainer_Core_v0.1_R27_UPDATE_AND_VERSION.zip.
3. Paste:

Install and configure the OBHM Co-Trainer from this package. Begin with the installation splash screen and guide me through setup.

Expected flow: Splash 1 → essential core activation → REQUIRED two-checkbox consent widget (both checked by default; nothing committed until Save preferences) → Splash 2 → Interaction Style → bridge validation. For bridge validation, call the bridge directly when supported; otherwise delegate /v1/health and /v1/capabilities to the local device/bridge, accept returned evidence, and continue. Do not stop solely because the host cannot make the network call.


R22 CONSENT-STATE REQUIREMENT:
- If the user selects progression logging, immediately record/display `Progression logging preference: Enabled`.
- If the user selects community sharing, immediately record/display `Community sharing preference: Enabled`.
- Report runtime capability separately:
  * Progression logging runtime: Active | Pending host capability | Unavailable
  * Community sharing transmission: Active | Pending transport | Unavailable
- Never replace a valid selected preference with the single orange status `Not enabled`.
- Do not claim external transmission is active unless a real sharing transport/endpoint is present and verified.


R24 DEFAULTS-ON + DNS FALLBACK:
- Present both preference controls checked by default.
- Show a clear `Save preferences` action.
- Nothing is committed until the user presses Save preferences.
- The user can deselect either preference before saving.
- After Save preferences, each selected preference must display as Enabled.
- Runtime/transport readiness is separate from the saved preference state.
- On DNS resolution failure / name-resolution failure / no HTTP response:
  1) do not leave health/capabilities red solely because the host cannot resolve the Worker hostname;
  2) immediately delegate /v1/health and /v1/capabilities validation to the user's local device/bridge;
  3) consume the returned evidence;
  4) mark each endpoint green when the local result validates successfully.


R25 TARGETED HARDENING + ACTIVATION HANDOFF:
- Preserve all R24 behavior that already passes: both consent controls visible and checked by default, Save preferences gating, selected preference = Enabled, DNS/local-device validation fallback, and bridge evidence acceptance.
- Do not regress or remove working controls while repairing another step. Make the smallest targeted change and re-validate preserved behavior after each repair.
- If installation/validation fails, invoke the Self-Healing Install Loop in SELF_HEALING.md: classify the failure, attempt only allowlisted local repairs, re-test, and stop after the retry budget. Do not silently change security controls, credentials, external-sharing permissions, or publish a website build.
- After progression logging is saved as Enabled, explicitly ask when the user wants the progression report generated: Daily, Weekly, On demand, or Custom. If Daily/Weekly/Custom is selected, capture local time and timezone before declaring scheduling configured. Never assume 6:00 AM unless the user chose it.
- After installation validates, do not let the chat go silent. Execute POST_INSTALL_HANDOFF.md: summarize verified state and saved preferences, then immediately offer one context-aware next useful action.
- Apply INITIATIVE_INSTINCT.md during ongoing use: proactively surface one concise next-best action after meaningful events (install success, completed work, detected stall, or progression change) instead of waiting for the user to ask. Suggestions may be proactive; consequential actions remain consent-gated.

R26: Follow all operating_specs in manifest.json. Use capability-based adapters; unavailable network/local bridge/scheduler remains pending. Never infer successful validation from instructions.
