Skip to content

feat: add stack contract compliance sections#35

Merged
henrylove0 merged 2 commits into
mainfrom
tom/stack-contracts
Jun 10, 2026
Merged

feat: add stack contract compliance sections#35
henrylove0 merged 2 commits into
mainfrom
tom/stack-contracts

Conversation

@henrylove0

Copy link
Copy Markdown
Contributor

Summary

  • Extend CONTRACTS.md with GoTrue policy, UI section states, progress events, error forwarding docs

Test plan

  • Review documentation accuracy

🤖 Generated with Claude Code

Document GoTrue security policy, UI section state requirements, progress
event schema, and error forwarding compliance per exe-os stack-contracts.json.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d5f87b4ada

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread CONTRACTS.md
Comment on lines +183 to +184
All 5xx backend errors are forwarded to exe-monitor-hub via `ErrorForwardingFilter` and `ErrorForwardingService`.
Configured by `MONITOR_ERROR_URL` and `ERROR_REPORTING_ENABLED` (default: `true`).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document the required monitor URL

This states that 5xx backend errors are forwarded and that reporting is enabled by default, but ErrorForwardingService.forwardError returns without sending anything whenever MONITOR_ERROR_URL is unset. A deployment following this contract can leave the URL out and silently get no exe-monitor-hub reports while believing the default enables forwarding; please qualify this as "when MONITOR_ERROR_URL is configured" or mark that variable required for forwarding.

Useful? React with 👍 / 👎.

Without await, NestJS never runs onModuleDestroy hooks — the open Redis
connection keeps the event loop alive and the container hangs forever
before reaching the main server process. Added 10s safety timeout with
unref() as a backstop if close itself stalls.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@henrylove0 henrylove0 merged commit 2048cfa into main Jun 10, 2026
0 of 3 checks passed
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.

1 participant