Repository navigation
Audit and Traceability
publish-wiki.mjs validates and mirrors the maintained onboarding, operation,
API, build, contributor, acceptance, and backlog sources to the repository
Wiki. Inspect the page plan first:
node Tools\Audit\publish-wiki.mjsGenerate the complete branded Home, sidebar, 23 source-backed pages, banner,
and product icon under the ignored .build/wiki-preview directory and validate
every generated Wiki link without contacting or changing the Wiki remote:
node Tools\Audit\publish-wiki.mjs --previewAfter GitHub's one-time first wiki page has been created, publish with:
node Tools\Audit\publish-wiki.mjs --applyThe publisher uses a verified temporary directory, generates the branded
Home.md and _Sidebar.md, rewrites source-relative links to their Wiki page
or canonical repository target, commits only when content changed, and leaves
repository Markdown as the canonical source. Repository identity is resolved from
GITHUB_REPOSITORY in automation or the authenticated gh repo view result
locally; the publisher and issue synchronizer contain no checkout-specific
owner/repository fallback.
extract-user-turns.mjs reads one or more Codex rollout JSONL files and merges
the extracted human-authored user messages chronologically. It removes exact
text duplicated across continuation files belonging to the same root session,
while preserving repeated human turns within one source or between distinct
root discussions as separate timeline events. Generated
<environment_context> and <codex_delegation> user envelopes are excluded by
default. Supplying every continuation file is important when one long project
conversation spans multiple rollouts. Use --include-generated only when an
audit intentionally needs those generated envelopes.
Keep generated transcripts under the repository's ignored .cache directory;
they can contain local paths or other private conversation context and must not
be committed to the public project. The canonical publishable acceptance
artifact is ../../docs/Project-Checklist.md.
node Tools/Audit/extract-user-turns.mjs SESSION.jsonl CONTINUATION.jsonl \
--json .cache/user-turns.json \
--markdown .cache/user-turns.mdsync-github-requirements.mjs contains the normalized public requirements
catalog. It validates the existing repository labels, creates or updates issues
by stable requirement-id markers, links every item to its epic as a true
GitHub sub-issue, synchronizes evidence-based states and epic counts, and writes
../../docs/Requirements-Backlog.md.
It never reads or uploads the private extracted transcript.
Run it without a flag for a read-only plan, then apply the idempotent sync:
node Tools/Audit/sync-github-requirements.mjs
node Tools/Audit/sync-github-requirements.mjs --apply- π Getting started and operations
- πΊοΈ Repository and file map
- ποΈ Front panel and menus
- π§ Hardware initialization and tuning
- βοΈ Host configuration and integrations
- π§ Hosted front-panel menus
- π Portable WebUI
- π Protocol and network API
- π§© C library API
βοΈ Control-surface capability matrix
- ποΈ Build and packaging tool
- πΎ Firmware tool
- π₯οΈ Host Controller
- π§ͺ Virtual Board
- π¦ Dependency maintenance
- π‘οΈ Toolchain bootstrap and safe programming
- π§ Memory and feature tradeoffs
- π¦ CI/CD and releases
- π© Urboot-Custom reproducible fork
- π Audit and traceability tools
- β Project acceptance
- π Requirements backlog
- 𧬠Local-library variant comparison