docs: v5 API notes + implementation plan#12
Open
daniel-lynch wants to merge 1 commit into
Open
Conversation
Phase 0 discovery for v5 (encrypted metadata) support, validated end-to-end against Passbolt CE 5.12.0: - v5-api-notes.md: confirmed endpoints, payload shapes (metadata, metadata_key_id, metadata_key_type), resource-type ids, the shared metadata key workflow, and the read-path implications - V5_PLAN.md: phased implementation plan and Opus/Sonnet split Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Phase 0 deliverables for full v5 (encrypted metadata) support — docs only, no code changes.
docs/v5-api-notes.md— discovery notes validated end-to-end against Passbolt CE 5.12.0 (.devstack/v5/v5_e2e.pyruns a full encrypted-metadata round trip): confirmed endpoints, payload shapes (metadata/metadata_key_id/metadata_key_type), all resource-type IDs, the shared metadata-key workflow, and read-path implications.docs/V5_PLAN.md— phased implementation plan and the Opus/Sonnet model split.Key finding: a stock v5 instance defaults to v4 cleartext, so v5 support is additive, not a rewrite. The main implementation challenge is that v5 resources store
name/username/uriinside an encrypted blob, so lookup-by-name requires decrypting metadata.🤖 Generated with Claude Code