Clinical Profile Runtime Audit

1. Identify the current precedence model.
2. List the fields or behaviors affected.
3. Determine whether the change is core, unit-specific, specialty-specific or legacy-compatibility related.
4. Verify that the change does not unexpectedly reactivate or hide unrelated fields.
5. Add or update tests for runtime resolution, flags and visibility.
6. Update docs if profile behavior materially changes.

Files to inspect first

• src/config/profiles/**
• src/config/unitsConfig.ts
• src/lib/profile-runtime.ts
• tests around catalog, runtime, visibility, flags and overlays
• docs on profiles or architecture if present

Minimum checks

Prefer real project commands such as:

• pnpm -w typecheck
• pnpm -w test

Focus on targeted runtime/profile tests when available.

Hard blockers

Block the change if any of these happen:

• whole-form duplication without necessity
• implicit precedence changes without tests
• overlays reactivating hidden fields unexpectedly
• profile aliases collapsing important context incorrectly
• docs and runtime diverging

Definition of done

A change guarded by this skill is only done when:

• precedence is explicit
• compatibility is tested
• field activation is auditable
• runtime behavior remains understandable to future maintainers