Skip to content

BAZ-016: enforce harness runtime boundaries#31

Merged
rullopat merged 1 commit into
mainfrom
codex/baz-016-harness-runtime-boundaries
Jul 11, 2026
Merged

BAZ-016: enforce harness runtime boundaries#31
rullopat merged 1 commit into
mainfrom
codex/baz-016-harness-runtime-boundaries

Conversation

@rullopat

Copy link
Copy Markdown
Owner

Summary

  • enforce current harness policy at HTTP and Telegram ingress/egress boundaries
  • make scheduler trigger and inbox claims atomic under lifecycle leases
  • add the disabled contract-version release gate, health signals, migration, and exhaustive boundary tests
  • document the as-built result and move BAZ-016 to done

Verification

  • pnpm vitest run apps/daemon/test/core/runtime-boundaries.test.ts apps/daemon/test/lib/harness-contract.test.ts apps/daemon/test/lib/telegram-routing.test.ts apps/daemon/test/lib/telegram-mirror.test.ts apps/daemon/test/routes/communication.test.ts apps/daemon/test/routes/misc.test.ts apps/daemon/test/core/triggers.test.ts
  • pnpm test (91 files, 714 tests)
  • pnpm typecheck
  • pnpm --filter @bazilion/web typecheck
  • pnpm lint (existing warnings only)
  • pnpm build
  • pnpm --filter @bazilion/web build
  • git diff --check

Enforcement remains off and compiled management contract version remains 0 pending BAZ-017.

@rullopat
rullopat merged commit a8b8508 into main Jul 11, 2026
1 check passed
@rullopat
rullopat deleted the codex/baz-016-harness-runtime-boundaries branch July 11, 2026 12:07
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