OpenFace v0.1.0

OpenFace v0.1.0 is the first public release. With no previous release tag, these notes cover the complete shipped history from the initial commit through main.

Highlights

• One self-hosted AI hub: a Next.js portal, Forgejo, PostgreSQL, nginx, and a FastAPI Docker runner are assembled with Docker Compose.
• Repository-backed catalogs: Models, Datasets, Spaces, Characters, Benchmarks, Skills, MCPs, Prompts, Knowledge, and Pages retain real Git files, history, tags, issues, pull requests, and permissions.
• Dockerfile-first applications: CPU-capable Gradio, static HTML, React, Vue, Next.js, Streamlit, FastAPI, and Node.js samples run behind the same gateway. Public Spaces can be started anonymously; runtime management remains protected.
• Flexible delivery: OpenFace supports embedded Docker Spaces, direct external-link Spaces, and static Pages built from gh-pages or repository docs.
• Remote acceleration: optional pull-based GPU workers let an LXC control plane schedule work to LAN-connected RTX 3060 and RTX 4090 nodes.
• Auditable automation: Claude Code /goal, GLM-backed maintenance, specialist accounts, SHA-bound independent review, allowlisted labels, and fail-closed auto-merge keep maintenance visible in Issues and Pull Requests.
• Knowledge publishing: Git-backed Markdown becomes a searchable bilingual library organized by frequently used topics such as news, benchmarks, how-to, and reference.
• Verified presentation: Standard, Solarpunk, and Cyberpunk themes, Japanese/English UI, responsive desktop/mobile layouts, Markdown, Mermaid, and interaction states are covered by repeatable screenshot audits.

Operations and security

• Forgejo remains the source of truth for repositories, identity, organizations, teams, stars, and forks.
• Space views and likes use persisted metrics APIs; unavailable data is shown explicitly rather than fabricated.
• Repository owners can manage runtime Variables and encrypted Secrets. Secret values are not returned after save and are injected only at container runtime.
• nginx provides the single HTTP/HTTPS entry point, while Proxmox LXC, backup, restore, Tailscale, and LAN deployment procedures are documented.
• Release-branch security and documentation audits run independently and return evidence through Pull Requests.

Tooling and quality gates

• GitHub Actions validate the frontend, VitePress docs, OpenFace Navigator Skill, Space runner, and maintenance agent.
• Visual QA captures route, theme, viewport, scroll, organization, interaction, authentication, character, and Space behavior.
• The installable OpenFace Navigator Skill helps choose, scaffold, and validate the smallest supported publishing path.
• Seed sources and tracked Docker samples are documented so a rebuilt environment uses the same catalog inputs.

Documentation

Start with the getting-started guide, then read the v0.1.0 walkthrough. Operators should also review Docker Spaces, automated maintenance, Proxmox LXC, and remote GPU workers.

Upgrade notes

This is the initial release, so there is no earlier OpenFace release to migrate from. Copy .env.example to .env, provide local credentials, and follow the current Docker Compose setup rather than reusing development secrets.

Validation

The release candidate is checked with the repository CI suites, the VitePress production build, SVG validation, and the release QA inventory validator. The final tag and GitHub Release are created only after the documentation deployment is live.