beo-onboard

Purpose

Verify and repair managed beo startup surfaces.

Primary owned decision

Determine whether managed startup is current and repair only the managed onboarding surfaces.

Ownership predicate

• Managed startup freshness is false, missing, or stale.
• AGENTS.md, .beads/onboarding.json, or .beads/beo_status.mjs needs managed repair.
• The user explicitly requests onboarding check or repair.
• The request is not doctrine editing or runtime readiness authorization.

Dependencies

Machine-readable dependency posture lives in frontmatter. Missing br or bv degrades live inspection only; onboarding does not authorize runtime readiness.