Production checklist¶
Use this checklist to review a customer deployment without adding
unsupported CLI steps. It applies to the reduced npm-launcher journey; items
that mention the full product's .pkg or protected runtime do not apply to
this CLI.
Before deployment¶
- Obtain Aegis through the approved distribution.
- Complete local account setup.
- Confirm the GitHub origin.
- Review the manifest and source.
- Commit the reviewed files.
- Run local HTTP checks.
During deployment¶
- Use the default repository and committed source unless automation requires a repository, ref, or commit selector.
- Record the deployment result.
- Record the repository and commit with the result.
- Keep ordinary source control under the operator's GitHub authority.
- Confirm the Forge GitHub App is installed, granted the repository and associated with this profile, agent and repository before expecting an accepted deploy; 0.9.4 prints no setup URL.
After deployment¶
- Compare the result with the source and manifest.
- Record the failure stage when the result is unsuccessful.
- Avoid claiming hosted availability without accepted evidence.
- Do not add a repository workflow to the app.
Read Deploy and Deployment results and proof for the connected procedure.