feat: complete release readiness work

- consolidate API ownership and remove dead vendor code

- add Stripe billing, learning paths, and public CV hardening

- add migration, recovery, security, audit, and browser gates

docs/career/education.md

@@ -1,3 +1,7 @@
 # education
 
-TODO: Complete documentation.
+Education entries are relational `CareerEducation` children with stable item keys. The Career Profile is
+the editable source of truth; CV variants control only selection, order, labels, and presentation-time
+overrides. Imported CV data is reviewed before it is merged.
+
+See `docs/architecture/career-profile-model.md`.

docs/career/experience.md

@@ -1,3 +1,7 @@
 # experience
 
-TODO: Complete documentation.
+Experience entries are relational `CareerExperience` children owned by one Career Profile. They carry
+stable item keys so CV variants can reference, hide, reorder, or override presentation without copying
+the underlying facts. Career Profile edits update the source; variants resolve the latest source data.
+
+See `docs/architecture/career-profile-model.md`.

docs/career/projects.md

@@ -1,3 +1,6 @@
 # projects
 
-TODO: Complete documentation.
+Projects are structured Career Profile records and can appear in any CV variant. Project facts remain
+in the profile while each variant chooses visibility, order, and presentation overrides. Public CV
+custom sections are the portfolio surface. A separate hosting product is intentionally out of scope
+until a concrete need such as media galleries or custom domains appears.

docs/career/skills.md

@@ -1,3 +1,7 @@
 # skills
 
-TODO: Complete documentation.
+Skills are structured Career Profile records used by CV rendering, deterministic job matching, keyword
+gap analysis, and application readiness. They are never inferred into the profile without review.
+Variant-specific hiding or ordering belongs to `CvVariantSettings`, not the Career Profile.
+
+See `docs/career/career-profile.md` and `docs/architecture/career-profile-model.md`.