chore: prepare final Codex ops foundation PR

.agents/skills/cross-repo-boundary-guard/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: cross-repo-boundary-guard
+description: Use when a task touches MPLP, Cognitive OS, SoloCrew, Validation Lab, website, docs, runtime, protocol, evidence, publication, or brand surfaces. Prevents boundary drift.
+---
+
+# Cross-Repo Boundary Guard
+
+## Authority Map
+
+MPLP owns:
+
+- protocol objects
+- schemas
+- invariants
+- conformance vocabulary
+- protocol docs
+
+Cognitive OS owns:
+
+- runtime substrate
+- execution semantics
+- DTOs
+- evidence pipeline
+- protocol bindings
+
+SoloCrew owns:
+
+- product UX
+- founder console
+- secretary/cell interaction
+- projection-safe workflow views
+
+Validation Lab owns:
+
+- evidence packs
+- deterministic adjudication
+- pointer resolution
+- failure cases
+- public validation UI
+
+JearonWong.com owns:
+
+- articles
+- essays
+- white papers
+- brand narrative
+- publication pages
+- social distribution assets
+
+## Required Boundary Check
+
+Before implementation, classify every changed file:
+
+```yaml
+boundary_check:
+  file:
+  repo_layer:
+  allowed_semantics:
+  forbidden_semantics:
+  risk:
+```
+
+## Forbidden Drift
+
+- MPLP must not contain product UI language.
+- SoloCrew must not claim protocol authority.
+- Cognitive OS must not redefine MPLP semantics.
+- Validation Lab must not become certification authority.
+- Website must not claim regulator approval or official standard status.

.agents/skills/docs-minimalism-governance/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: docs-minimalism-governance
+description: Use when creating, editing, or reviewing governance docs, release records, audit records, baselines, checklists, README files, or protocol documentation. Prevents document sprawl.
+---
+
+# Documentation Minimalism Governance
+
+## Rule
+
+Do not create new governance documents unless existing documents cannot be reused.
+
+## Required Before New Docs
+
+Codex must report:
+
+```yaml
+doc_reuse_check:
+  existing_candidate_docs:
+  can_update_existing:
+  why_not_reuse:
+  new_doc_needed:
+  proposed_doc_path:
+  document_budget_impact:
+```
+
+## Preferred Actions
+
+1. Update existing baseline.
+2. Append to existing audit record.
+3. Add one index entry.
+4. Only then create a new document.
+
+## Forbidden
+
+- Duplicate release records.
+- Duplicate governance baselines.
+- New checklist if an existing checklist can be extended.
+- Marketing language in protocol docs.
+- Certification, official standard, regulator approval, or vendor ranking claims.

.agents/skills/mplp-schema-v2-invariant-intake/SKILL.md

@@ -0,0 +1,85 @@
+---
+name: mplp-schema-v2-invariant-intake
+description: Use for MPLP schemas/v2 primitive intake, invariants, negative fixtures, object schemas, profiles, conformance manifests, and validator gates.
+---
+
+# MPLP Schema v2 Invariant Intake
+
+This skill governs schemas/v2 work.
+
+## Hard Order
+
+Codex must follow this order:
+
+1. Inspect existing schemas/v2 assets.
+2. Inspect existing validators and fixtures.
+3. Define or update invariants.
+4. Add negative fixtures bound to invariant IDs.
+5. Add kernel object schemas.
+6. Add positive fixtures.
+7. Add validator tests.
+8. Update conformance manifest or inventory.
+9. Update governance record only if necessary.
+
+## Required Principle
+
+Invariant -> Negative Fixture -> Object Schema -> Positive Fixture -> Validator -> Governance Record
+
+## v1.0 Frozen Boundary
+
+v1.0 module schemas may reference v2 objects only through pointer-only refs.
+
+Allowed:
+
+```yaml
+active_context_version_ref:
+  ref_id: "ctxv-..."
+  ref_type: "ActiveContextVersion"
+  protocol_version: "2.0.0"
+  schema_version: "2.x"
+  profile_marker: "required"
+```
+
+Forbidden:
+
+```yaml
+active_context_version:
+  context_id: "..."
+  validity_state: "active"
+  superseded_by: "..."
+```
+
+## Forbidden Imports Into Protocol Core
+
+Do not add these to MPLP protocol core:
+
+- RCCS-M
+- ALCS
+- AARM
+- audit score
+- insurance score
+- procurement score
+- certification
+- legal compliance proof
+- regulator approval
+- vendor ranking
+- SoloCrew UI objects
+- Cognitive OS runtime internals
+- Coregentis commercial validation service language
+
+## Required Output
+
+For every schema primitive, report:
+
+```yaml
+primitive:
+  name:
+  module_mapping:
+  invariant_mapping:
+  positive_fixture:
+  negative_fixture:
+  validator_rule:
+  conformance_profile:
+  v1_pointer_refs_if_any:
+  files_changed:
+```

.agents/skills/release-gate-and-seal-discipline/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: release-gate-and-seal-discipline
+description: Use before declaring any task, PR, release, RC, seal, deployment, or merge complete. Requires commands run, pass/fail evidence, remote truth, and remaining risk.
+---
+
+# Release Gate and Seal Discipline
+
+Codex must not declare completion without verification.
+
+## Required Report
+
+```yaml
+completion_report:
+  branch:
+  starting_head:
+  final_head:
+  files_changed:
+  commands_run:
+  pass_fail_results:
+  tests_added_or_updated:
+  governance_records_changed:
+  remote_truth_checked:
+  final_git_status:
+  remaining_risks:
+  exact_verdict:
+```
+
+## Common Checks
+
+Use repo-specific commands if available. Otherwise inspect package scripts first:
+
+```bash
+cat package.json | sed -n '1,160p'
+```
+
+Then run available gates:
+
+```bash
+git diff --check
+pnpm run build
+pnpm run lint
+pnpm run test
+```
+
+If commands differ, explain why.
+
+## Forbidden
+
+- Do not say "done" without command output summary.
+- Do not tag release without owner approval.
+- Do not create seal record without owner approval.
+- Do not claim live deployment unless repo truth, build truth, remote truth, and live truth are checked.

.agents/skills/repo-truth-first-audit/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: repo-truth-first-audit
+description: Use before any implementation, refactor, release, schema, docs, or governance task. Inspect branch, HEAD, remote, dirty status, existing files, reusable assets, and why new files are needed.
+---
+
+# Repo Truth First Audit
+
+Before making changes, Codex must inspect repository truth.
+
+## Required Commands
+
+Run or equivalent:
+
+```bash
+git branch --show-current
+git status --short
+git rev-parse HEAD
+git rev-parse --verify origin/main || true
+git log --oneline -5
+```
+
+## Required Investigation
+
+Identify:
+
+- current branch
+- current local HEAD
+- remote HEAD if available
+- dirty files
+- relevant existing directories
+- relevant existing tests
+- reusable assets
+- missing assets
+- why new files are necessary
+
+## Output Format
+
+Before implementation, report:
+
+```yaml
+repo_truth:
+  branch:
+  local_head:
+  origin_main_head:
+  dirty_status:
+  relevant_existing_files:
+  reusable_assets:
+  missing_assets:
+  why_new_files_needed:
+  proposed_change_surface:
+```
+
+## Rules
+
+- Do not create new files before this audit.
+- Do not rewrite existing architecture without explaining why extension is insufficient.
+- Prefer update over new document.

.codex/agents/package_surface_auditor.toml

@@ -0,0 +1,27 @@
+name = "package_surface_auditor"
+description = "Audits npm/PyPI package publication surfaces, package metadata, README footers, LICENSE/NOTICE files, owner statements, and registry-readiness blockers."
+model_reasoning_effort = "high"
+sandbox_mode = "workspace-write"
+
+developer_instructions = """
+You are a package publication surface auditor.
+
+Inspect package-facing files only:
+- packages/npm/**
+- packages/pypi/**
+- package.json
+- README.md
+- LICENSE
+- NOTICE
+- governance/release/** when package release readiness is relevant
+
+You must not publish, upload, deprecate, yank, tag, or bump versions.
+
+Return:
+- files inspected
+- exact problematic strings
+- active publication surface vs historical record classification
+- recommended replacement
+- post-edit verification command
+- blocker verdict
+"""

.codex/agents/product_boundary_reviewer.toml

@@ -0,0 +1,28 @@
+name = "product_boundary_reviewer"
+description = "Reviews SoloCrew product UX changes for user-facing clarity and prevents protocol/runtime jargon leaking into founder-facing UI."
+model_reasoning_effort = "high"
+sandbox_mode = "workspace-write"
+
+developer_instructions = """
+You are a SoloCrew product boundary reviewer.
+
+User-facing UI should express:
+- what needs your decision
+- company status
+- secretary brief
+- continue from here
+- evidence behind this
+- system details only when necessary
+
+Block:
+- internal protocol jargon as primary UI copy
+- direct approve/reject/dispatch/execute unless explicitly scoped
+- runtime authority in product UI
+- provider/channel send behavior unless explicitly authorized
+
+Return:
+- UI files inspected
+- copy issues
+- authority boundary risks
+- recommended user-facing wording
+"""

.codex/agents/protocol_schema_reviewer.toml

@@ -0,0 +1,25 @@
+name = "protocol_schema_reviewer"
+description = "Reviews MPLP schemas/v2 invariants, negative fixtures, object schemas, conformance profiles, and v1 pointer-only refs."
+model_reasoning_effort = "xhigh"
+sandbox_mode = "workspace-write"
+
+developer_instructions = """
+You are an MPLP protocol schema reviewer.
+
+Rules:
+- invariant-first
+- negative fixture second
+- object schema third
+- positive fixture fourth
+- validator/conformance last
+- v1 module refs must be pointer-only
+- no RCCS-M, ALCS, AARM, certification, vendor ranking, product UI, runtime-private, or commercial validation service language in protocol core
+
+Return:
+- schema files inspected
+- invariant mapping
+- fixture mapping
+- missing negative tests
+- v1/v2 boundary risks
+- blocking findings
+"""