GitHub Public Readiness Checklist¶
Use this checklist for repository settings that cannot be fully enforced from the checked-in code. Wright is a public alpha; do not present it as production ready.
Repository Profile¶
- [ ] Set repository description to:
Local-first AI mechanical engineering agent orchestrator for CAD, CAE, CAM, and MCP tool workflows. - [ ] Set website URL to
https://burhop.github.io/wright/after Pages is live. - [ ] Configure social preview art from
docs/images/. - [ ] Add repository topics:
ai-agent,mechanical-engineering,cad,fea,local-first,multi-agent,docker,fastapi,llm,offline-first,manufacturing,openscad,python,typescript,engineering-tools,mcp,parametric-design,digital-twin,autonomous-agent,public-alpha.
Discussions, Support, and Issues¶
- [ ] Enable GitHub Discussions before keeping README and issue-template links live.
- [ ] Create categories: Announcements, Q&A, Ideas, Show and Tell.
- [ ] Keep support questions in Discussions and reproducible bugs in Issues.
- [ ] Keep security reports private through
SECURITY.md; do not triage vulnerabilities in public issues. - [ ] Sync labels from
.github/labels.ymlso issue templates can applybug,needs-triage, andalpha.
Branch Protection¶
Protect main with these minimum public-alpha rules:
- [ ] Require a pull request before merging.
- [ ] Require at least 1 approval.
- [ ] Require branches to be up to date before merge.
- [ ] Require status checks:
python-qualityfrontend-qualitypublic-alpha-safetydocsDocker Build CIBackend Tests (Windows),Frontend Tests (Windows), andPlaywright E2E (Windows)only after the Windows workflow is stable enough for blocking branch protection.- [ ] Disallow force pushes.
- [ ] Disallow branch deletion.
- [ ] Require linear history if maintainers want a strictly linear public history.
Pages and Packages¶
- [ ] Enable GitHub Pages from the
gh-pagesbranch because.github/workflows/docs-deploy.ymldeploys withmkdocs gh-deploy. - [ ] Confirm docs do not deploy on pull requests; PRs should build only.
- [ ] Configure the GHCR package
ghcr.io/burhop/wrightas public before publishing alpha releases. - [ ] Configure required Docker Hub secrets
DOCKERHUB_USERNAMEandDOCKERHUB_TOKENat repository scope or in the protecteddockerhubenvironment. Use the raw read/write token value, not its display name.
Security Settings¶
- [ ] Enable Dependabot alerts.
- [ ] Enable Dependabot security updates.
- [ ] Enable secret scanning.
- [ ] Enable push protection.
- [ ] Review code scanning availability for public repositories and enable it when appropriate.
CI Gate Posture¶
- [ ] Keep Python, frontend, docs, public-alpha safety, and Docker smoke checks blocking for pull requests.
- [ ] Mypy is intentionally warning-only during the first public-alpha hardening window. Promote it to blocking after the package typing baseline is fixed and tracked in a dedicated issue.
- [ ] Keep Trivy report collection followed by the blocking vulnerability
policy in both
docker-pr.ymland the reusabledocker-build.yml. Any exception must be explicit, reviewed, and time-bounded indocker/release-policy.json. - [ ] Confirm release-tag candidates publish digest-bound SBOM/provenance and attestation evidence. Release notes must also call out skipped MCP validation and any policy exceptions.
Repository Metadata Notes¶
- [ ] Keep the root
package.jsonmarked"private": true. The root package is an npm workspace coordinator forapps/*, not a publishable package. Public package metadata should be added to individual packages only when maintainers intentionally publish them. - [ ] Confirm
LICENSE,CODE_OF_CONDUCT.md,CONTRIBUTING.md,SECURITY.md,SUPPORT.md,CHANGELOG.md, andROADMAP.mdbefore each public alpha tag. - [ ] Keep
.all-contributorsrcpointed atburhop/wrightand update the README contributors section when contributors are added.
Release Owner Checklist¶
- [ ] Cut the first public alpha as a prerelease tag such as
v0.1.0-alpha.1, not a stable production release. - [ ] Confirm GHCR image publication before adding registry-specific badges.
- [ ] Confirm Docker Hub publication before adding Docker Hub badges or pull count claims.
- [ ] Use
docs/alpha-release-notes-template.mdfor alpha, beta, and release candidate notes.