Skip to content
- Status: Schema/migration work removed; PR now contains only this ADR.
- Why: PR #1347 (ENG-377, ops-mcp auth middleware) landed on
staging first
and shipped its own mcp_tokens schema + migration (0067_bent_moondragon)
with a different design (uuid org_id with FK to organizations,
issuer/description columns, updated_at). After rebasing onto staging,
this PR’s 0066_eager_marauders migration and mcp-tokens.ts schema
conflict with what is already deployed.
- Resolution: Reset branch to
origin/staging and dropped the duplicate
schema/migration commits. The CodeRabbit feedback that prompted the
MCP_TOKENS → mcpTokens rename is moot — staging’s mcp-tokens.ts
already exports mcpTokens (camelCase).
- Follow-up: If the additional columns this PR introduced (
subject,
created_by) or the token_hash_sha256_chk constraint are still wanted,
open a fresh ticket for an ALTER migration on top of staging’s schema.