P2-Knowledge-Base

End-to-end release of a P2 manual to the public deliverables area — VERIFY the generated PDF is complete (page count, outline, key sections, compile-log; guards against silent content-drop), promote the CHANGELOG + update the deliverables README release index (add new manuals, force-download links), record the Platform Freshness Ledger PUBLISH line + roster status, then surface the commit/tag/push. Use when the user says "release the <manual>", "publish the <manual>", "promote <manual> to deliverables", "get <manual> released", or invokes /release-manual. Assumes the PDF was generated by PDF Forge and placed in deliverables/documents/DOCs/. Suggests git commands but does NOT execute them. Handles a single manual or a multi-manual release wave.

Prepare a P2 manual for PDF Forge generation — refresh workspace from opus-master, escape LaTeX characters, and stage only changed files to outbound. Use when the user says "prepare/build/stage the <manual> for PDF", "get <manual> ready for the Forge", or invokes /prepare-manual. Works for any manual under engineering/document-production/workspace/. Does NOT generate the PDF itself (PDF Forge does that); produces the outbound bundle that the user moves to Forge.

Audit a P2 manual against the current YAML/KB HEAD and itself, at a chosen depth, producing a consolidated findings report — and, at release depth, ENFORCE the publish gate. Use when the user says "audit the <manual>", "re-audit <manual> against the KB", "is <manual> ready to release", runs a periodic/quarterly audit, re-audits after a YAML change-set lands, or invokes /document-audit. This is the central, manual-agnostic audit body; per-manual specifics (sources, code-line budget K, doc-class, fragile areas) come from that manual's MANUAL-DESCRIPTOR.md overlay, resolved from the active_element pointer. Owns the YAML-HEAD drain gate (no publish while actionable YAML corrections are pending) and the changeset- integrity (delta-since-last-published) audit. Finds and reports; resolving findings is document-finalize, releasing is release-manual.

Ingest a source document into the P2 knowledge base — the INGESTION head's front-to-back process. Use when the user says "ingest <doc>", "re-study the <doc>", "add a new source", "do the next ingestion", or supplies an updated edition of an already-ingested source (e.g. Spin2 v55 superseding v51). Orchestrates all passes a complete document needs — content, code examples, images/visual catalog, post-processing, validation, cross-source Q&A + conflict detection, and dashboard registration — at CURRENT tooling capability (DOCX-primary, pnut_ts-validated code, image-tools-mcp). Routes any P2KB content conflict it surfaces to the corrections register. Does NOT edit deliverables/ai/P2/ YAML directly (that is yaml-knowledge-base-maintenance).

Edit and validate P2 knowledge base YAMLs in place. Use when applying any change to deliverables/ai/P2/ — a single fix or a sweeping cross-data-set update from a P2KB Update Request document. Enforces Sacred Rule #7 (never delete cross-references; redirect to where content IS documented). The engineering/knowledge-base/ tree is transient and NOT touched by this skill.

Round-trip a document/template through the PDF Forge interactive watch daemon and inspect the result YOURSELF — stage files, submit a test request, wait for the PDF, then read the compile log and render any page to verify images/layout/template behavior. Use when the user says "test the <template/doc> on the forge", "round-trip this", "does the layout/diagram look right", "generate a test PDF and check it", or invokes /forge-test. This is for INTERACTIVE TESTING ONLY (nailing down template/layout/feature behavior); production deliverables still use prepare-manual → manual copy-to-Forge.

Audit a P2 manual's CHANGELOG.md latest entry for release readiness — verify it conforms to the manual's changelog-style-guide.md (voice/structure) AND that its claims are traceable to actual commits since the last public release. Use when the user says "audit the <manual> changelog", "is the changelog ready to release", or invokes /audit-changelog. Reports findings; does NOT auto-edit the CHANGELOG. Supports --deep flag for diff cross-reference (default is headline-level).