build(bayn): make Effect TSGo the typecheck

[gregkonush]

Summary

• make the existing pinned @effect/tsgo 0.24.3 compiler the normal Bayn tsc path instead of running TypeScript and Effect diagnostics twice
• fail the single compiler boundary on configured Effect warnings and errors and simplify the Bayn PR workflow accordingly
• sequence HTTP/platform dependencies correctly and retain NodeServices.layer for TLS-backed PostgreSQL certificate reads
• inspect startup failure through Exit so an autonomous-loop Effect never enters an Effect error channel
• bind the exact amd64 and arm64 dependency closures produced by the TSGo package contract

Stacked on #13612.

Related Issues

None

Testing

• bun run --filter @proompteng/bayn tsc — Effect TSGo checked 464 files with 0 errors, 0 warnings, and 0 messages, including after restoring the unpatched native TypeScript binary
• focused composition/startup/release tests — 125 passed, 0 failed
• bun run --filter @proompteng/bayn test — 1054 passed, 160 PostgreSQL-environment skips, 0 failed
• bun test packages/scripts/src/bayn — 126 passed, 0 failed
• bun run --filter @proompteng/bayn build
• bun run --filter @proompteng/bayn lint
• bun run --filter @proompteng/bayn lint:oxlint
• bun run --filter @proompteng/bayn lint:oxlint:type
• nix eval --raw .#packages.x86_64-linux.bayn-image.drvPath
• nix eval --raw .#packages.aarch64-linux.bayn-image.drvPath
• git diff --check
• hosted full Bayn, PostgreSQL, amd64/arm64 image, dependency, broker, Effect runtime, release, and repository gates are green

Breaking Changes

None. bun run --filter @proompteng/bayn tsc remains the public validation command and now includes Effect diagnostics in the same compiler pass.

Checklist

• Testing section documents the exact validation performed.
• Screenshots are not applicable; Breaking Changes are documented.
• Documentation and CI contract tests are updated.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 776c4f6a04

ℹ️ 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".

[gregkonush]