Skip to content

README: replace outdated hosted key-isolation limit; note MySQL port - #4

Merged
PradipNichite merged 1 commit into
mainfrom
docs/readme-hosted-key-limits
Oct 22, 2026
Merged

PradipNichite merged 1 commit into
mainfrom
docs/readme-hosted-key-limits

Conversation

@PradipNichite

Copy link
Copy Markdown
Contributor
  • Known limits still said "broader hosted provider-key isolation … remain separate work". Hosted accounts now have an explicit own-or-platform key source. An account on its own keys uses them everywhere and fails clearly, with no platform fallback, when its key is missing. The new text gives the scope of the verification: one bounded hosted journey, not a load or multi-tenant security assessment.
  • It also documents a constraint the README never mentioned: validate_database_request accepts MySQL only on port 3306 (PostgreSQL accepts any port). This was hit on the hosted service today with a MySQL fixture on 3307.

Docs only.

🤖 Generated with Claude Code

…cope

Hosted accounts now have an explicit own-or-platform key source; the README
still listed provider-key isolation as separate work. State what was verified
(one bounded hosted journey) and what was not (load, multi-tenant security).
Also document that MySQL connections are accepted on port 3306 only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@PradipNichite
PradipNichite merged commit 48335d0 into main Oct 22, 2026
4 checks passed
@PradipNichite
PradipNichite deleted the docs/readme-hosted-key-limits branch October 22, 2026 15:37
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