Skip to content

[codex] add read-only production debug process#216

Closed
debuggerone wants to merge 1 commit into
develop/1.0.8-betafrom
codex/prod-debug-process
Closed

[codex] add read-only production debug process#216
debuggerone wants to merge 1 commit into
develop/1.0.8-betafrom
codex/prod-debug-process

Conversation

@debuggerone

Copy link
Copy Markdown
Contributor

Summary

  • Adds demo/video-chat/scripts/prod-debug.sh as a read-only production diagnostics process for KingRT video-call incidents.
  • Documents the process in README.md and exposes npm wrappers/contracts in frontend-vue/package.json.
  • Adds a contract test that forbids mutating operations and verifies the intended prod-debug probes.

Validation

  • bash -n demo/video-chat/scripts/prod-debug.sh
  • git diff --check
  • cd demo/video-chat/frontend-vue && npm run test:contract:prod-debug
  • cd demo/video-chat/frontend-vue && npm run prod:debug -- --help
  • Live read-only prod probe with VIDEOCHAT_PROD_DEBUG_ENV_FILE=/home/jochen/projects/king.site/king/demo/video-chat/.env.local VIDEOCHAT_PROD_DEBUG_LOG_TAIL=10 demo/video-chat/scripts/prod-debug.sh
  • demo/video-chat/scripts/deploy.sh deploy
  • demo/video-chat/scripts/deploy-smoke.sh

Production notes

  • Deployed after commit 1d1c0e71.
  • Smoke passed against app.kingrt.com and current production service routes.
  • The debug output confirms production is still on the old nested service-domain contract (api.app.kingrt.com, cdn.app.kingrt.com, etc.); that cutover is intentionally handled by the separate domain/registry branch.

@debuggerone

Copy link
Copy Markdown
Contributor Author

Online branch cleanup: current Codex integration continues in #221; local worktree/branch is retained.

@debuggerone debuggerone closed this May 8, 2026
@debuggerone debuggerone deleted the codex/prod-debug-process branch May 8, 2026 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants