Repository navigation
Record read-only production smoke evidence - #143
Conversation
Refs: LVT-347
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
🚅 Deployed to the lovat-pr-143 environment in lovat
2 services not affected by this PR
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Lovat AI reviewStatus: completed · Model: Reviewed commit: Critical: 0 · High: 0 · Medium: 0 · Low: 0 Overall assessmentThis PR adds a read-only public smoke script, a workflow to run it manually on main, tests, and documentation. The script performs anonymous bounded GET requests with manual redirects, capped body reads, one retry for transient failures, and no logging of response contents or secrets. The retry, deadline, truncation, and redirect-validation logic are consistent with the tests, and the workflow uses pinned actions with minimal permissions and a short timeout. No concrete correctness, security, or data-integrity defect is evident in the changed lines. No high-confidence issues were found in the reviewed changes. Review details
Limitations
|
What changed
Adds a manually triggered, main-only GitHub Actions workflow and a matching local command to check fixed public Website, Learn, Dashboard, and API routes. Records HTTP status and timing with bounded retries, without credentials, response-body logging, or changes to live configuration. This is the first slice of LVT-347.
Areas affected
Contracts and data
Verification
Node 22.20.0: 18 smoke and CI tests passed, including six new smoke cases. Structure, static workflow YAML assertions, and diff checks passed. Live
node scripts/deployment-smoke.mjs: six of seven checks passed. The Learn root currently returns HTTP 404; the Welcome guide itself returns 200. The smoke correctly reports this as a failure. Full workflow policy/actionlint run in GitHub CI.Deployment
No provider changes or deployment triggers. This workflow does not make alerts, rollbacks, or production promotions automatic. Dependency readiness checks, authorized synthetic operations, and alerting remain separate follow-ups.