Repository navigation
feat(billing): safely disable unavailable Dodo Payments - #1489
Merged
Merged
Conversation
…dpoint Exposes registered TypeScript engines as live contracts/v1 capability records derived from the sidecar registry and existing per-engine self-checks, so registered metadata is no longer the only runtime discovery surface. - Each capability: contract version v1, runtime kind typescript, display name, required phase, implementation version, dependencies. - availability="available" when the engine's self-check passes, "unavailable" when it fails. - No provider/generation/database/remote/deployment calls made. TDD receipts (docs/plans/selemene-engine/RUNTIME-CAPABILITY-EVIDENCE.md): RED: bun test tests/baseline_registry.test.ts tests/health.test.ts -> 404 GREEN: same command -> 9 pass, 0 fail; full suite -> typecheck clean, 92 tests passed, 0 failed. Also lands on top of the just-synced origin/main security-audit fix (PR #1485, ae3e2ce) with zero file overlap, and updates the next-wave plan + drafts GitHub issue-update packets (not posted) reflecting that sync. Co-Authored-By: Claude Code <noreply@anthropic.com>
…provenance slice Task 3 (Finish Runtime Capability Coverage): - crates/noesis-api: new GET /api/v1/admin/engines/capabilities, reusing the pre-existing EngineCapability/CapabilityAvailability/RuntimeKind contract-v1 types. Same auth gate (admin:system:read) and same bridge readiness self-check data source as the existing /admin/bridge/health route. No new provider/database/remote calls. - python-services: HealthResponse.capability_status (available/degraded/ unavailable) on both sidecars' /health, derived only from each service's existing local self-check booleans. Task 4 (Build the First Engine Truth Batch) -- partial slice against GitHub issue #1461 ([W3E:tarot:07] Expose provenance, confidence, and degradation), scoped per the plan's own Step 1-4 (one missing-state test + minimal truth surface, not the full six-axis acceptance criteria): - ts-engines: ContractProvenance gains optional confidence?: number; TarotEngine.calculate() now populates EngineOutput.provenance (runtime_kind, implementation_version, cached=false, fallback_used= false, confidence=1) reflecting that tarot's interpretations are fully deterministic local data today, with no fallback path. TDD receipts (RED before, GREEN after, all independently re-run this session, not just accepted from the implementing pass): - cargo test -p noesis-api --test capability_route_tests --locked: 3/3 - pnpm run gate:contracts: pass - cargo build --workspace --locked: no regressions - python3 -m pytest python-services/tests -q (via project .venv): 61/61 - bun run typecheck && bun test: 93/93 (was 92/92 pre-slice) Full evidence: docs/plans/selemene-engine/RUNTIME-CAPABILITY-EVIDENCE.md (Slices 2-3). Plan checkboxes updated in GH-ISSUE-NEXT-WAVE-PLAN.md. Stacked on #1486 (codex/selemene-runtime-capability-endpoint) -- no file overlap with it. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sheshiyer
marked this pull request as ready for review
September 8, 2026 17:39
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Final outcome
PR #1489 merged into
mainas561c3e476e134eeac424c77b092b95b9749e0215; the final documentation reconciliation merged afterward asebd97fe940a3454b0425ff60d56003b07337564.Shipped
BILLING_MODE=freeis explicit; free allowance is deterministic.503 BILLING_DISABLED.freeordisabled, but cannot enable Dodo.Production evidence
ee9cb602-d3d3-4db3-a8d6-d06fc75090a8ebd97fe9passed the connected workflow; Railway correctly skipped the docs-only runtime redeploy because watch patterns exclude docs.Explicit holds
Rust SDK/TUI registry receipts, Cloudflare scoped-account verification, Vercel production protection, exact Railway schema/image equivalence, and exercised rollback remain open. No Dodo payment promotion is enabled.