ImYourBoyRoy Site Readiness
Run before material work when current readiness evidence is absent or stale.
Preflight
Resolve the active client repository, read its applicable instructions, and preserve unrelated work. Confirm the toolkit link and site profile belong to this client before running commands.
Command
node ./Web_Toolkit/site_readiness/bin/site-readiness.mjs run --project-root . --site-profile ./<name>.site-profile.json
Shortcuts: npm run readiness | npm run readiness:fix
An ordinary readiness request may write its diagnostic reports but does not
apply project fixes. Do not use readiness:fix or any mutation flag without
separate authorization for the proposed fixes.
Flags
| Flag | Effect |
|---|---|
--apply-safe-fixes |
Authorized project-init apply-safe (never overwrites) |
--install-deps |
Separately authorize dependency installation |
--build |
Run the repository-authorized build and create its artifacts |
--skip-network |
Offline/sandbox — skip integration |
Modes (auto)
sandbox | local | full (network + CF .env)
Outputs
output/site-readiness-*.json— agents read this firstoutput/site-readiness-*.md— human summary- Exit: 0 pass, 2 warn, 1 fail
Workflow
- Run readiness
- Read
nextSteps+recommendedFixesin JSON - Propose fixes; apply only the authorized set, then re-run
- Then portable-web-toolkit for deploy
- site-doctor only when site is live
Record the toolkit version as context. A newer toolkit version is a separate finding, not permission to pull source or reinstall skills. Use toolkit-update when comparison or migration is requested.
Never auto-applied
Deploy, DNS, cf-agent --apply, cache purge, registrar.