[Noam-Alum]

Required result

Outcome and ownership

Create the shared StateForge documentation presentation package owned by stateforge-docs. Publish one installable Python distribution, stateforge-docs-theme, exposing the MkDocs theme name stateforge and extending Material for MkDocs without forking it.

Required behavior

• Bundle the official StateForge mark, favicon, brand tokens, typography, spacing, responsive layout, light/dark presentation, navigation treatment, repository link treatment, code styling, and accessible focus/contrast behavior.
• Support a common StateForge identity plus explicit component accents for Agent, Provider Python, Protocol, Control Plane, SF-AOP, and future repositories without copying CSS or assets into consumers.
• Keep content, navigation, repository metadata, and repository-specific plugins owned by each consuming repository.
• Provide stable theme configuration for the version selector and historical-version warning used by later publishing work.
• Package templates and static assets reproducibly in wheel and sdist. Do not load branding from a moving branch or remote runtime resource.
• Keep Material-specific overrides minimal and documented so a later centrally managed Zensical migration does not require rewriting repository content.

Acceptance evidence

A clean environment installs the exact wheel and sdist, selects theme.name: stateforge, and builds representative documentation with bundled assets only. Automated tests cover package contents, theme discovery, responsive light/dark rendering, keyboard focus, contrast, logo/favicon resolution, component accents, and absence of consumer-local branding copies.

Non-goals

No repository-specific documentation content, no documentation hosting, no release/version deployment, no StateForge runtime code, and no Zensical migration in this milestone.

Implementation step

D0

Closes #1