feat: complete M2 content workspace and inspector

This commit is contained in:
Rbanh committed 2026-07-17 23:40:49 -04:00
1 parent 931f561e7f
commit cf6eaba534
438 files changed
+59749 -19043

No files matched your search

@@ -0,0 +1,17 @@
---
name: blacksite-release-candidate
description: Nominate and verify one Blacksite candidate tree or commit, reuse still-valid selective verification evidence, run the remaining full release gates once, produce an evidence manifest, and hand results to Gitea synchronization.
---
# Blacksite release candidate
Read `.codex/workflow.toml` and [the release gates](references/release-gates.md). Require stable scope, no pending major delta, and `Candidate-ready` session state.
1. Record the candidate SHA or dirty-tree digest.
2. Read the verification ledger and reuse every gate whose relevant input digest and lane signature remain valid.
3. Run only missing/invalid release gates via `verify.py candidate` and managed candidate/package lanes.
4. Preserve final binaries/package output and required native evidence before disposable-lane pruning.
5. Write `.codex/session/candidate-evidence.json` with commands, digests, results, artifacts, screenshots, and documentation status.
6. Run documentation integrity and hand a dry-run/authorized candidate update to `blacksite-gitea-sync`.
Do not push, close, or change tracker scope outside direct or configured authority. Run full workspace/all-feature tests and strict lint only once per candidate code digest.
@@ -0,0 +1,14 @@
# Candidate release gates
A nominated Blacksite candidate requires, when relevant:
- Full workspace/all-feature tests.
- Strict all-target/all-feature Clippy with warnings denied.
- Deterministic content processing and read-only check parity.
- Level/sample/project validators and migration idempotence.
- Packaging, packaged artifact validation, and launch.
- Named native editor/runtime scenarios against candidate binaries.
- Documentation authority/contradiction audit.
- Clean candidate-tree or nominated dirty-tree digest evidence.
Do not precede workspace tests with a redundant workspace check unless a target is otherwise uncovered. Documentation-only changes do not invalidate code gates when recorded inputs are unchanged. Closure additionally requires every issue criterion, epic checklist synchronization, and configured Gitea evidence.