Consent and client context move into the coaching workflow

What changed on the branch

Client review now has a clearer data boundary. Coach can show assigned-plan performance and attention context while optional personal Training history remains athlete-owned, explicitly granted, revocable, and visually separate.

Training gained invitation review and Coaching settings where the athlete can accept plan-only coaching, choose optional sharing, inspect current relationships, and revoke access. Coach gained relationship-scoped client views for Overview, Performance, Plans, and Shared context.

The decision behind the controls

Consent cannot live in a paragraph nobody sees after onboarding. It belongs beside the relationship and the data it controls.

An athlete may want a coach to assign a plan without exposing unrelated personal history. Another athlete may choose to share a bounded range of prior sessions because it changes the next programming decision. Both are valid, and the default remains the smaller grant.

When a relationship is deactivated, optional grants suspend immediately. Reactivation does not silently restore them. A coach sees whether context is currently shared, never the athlete's private decline reason or behavior.

What Coach can infer

Assigned-plan analytics remain actual-only and lineage-aware. Exercise performance groups compatible work without silently merging substitutions, and optional history never changes adherence or performance totals for the assigned plan.

The software prepares evidence such as completed work, missed work, substitutions, and observed performance. The coach still owns the interpretation and the final call.

Availability

These controls are implemented and tested on the Coach branch. Protocol Coach remains in development and invite-only, with no claim of public availability.

Next

Finish entry, recovery, profile, trial, and application flows so access to the professional workspace follows the same explicit lifecycle as the data inside it.