Skip to content

docs: add scope field documentation for blueprint storage#130

Merged
pyramation merged 1 commit into
mainfrom
feat/storage-scope-docs
May 19, 2026
Merged

docs: add scope field documentation for blueprint storage#130
pyramation merged 1 commit into
mainfrom
feat/storage-scope-docs

Conversation

@pyramation
Copy link
Copy Markdown
Contributor

Summary

Updates skill documentation to reflect the new scope field on top-level blueprint storage[] entries. Only 'app' (default) and 'org' are allowed.

Changes across 4 files:

  • blueprint-definition-format.md — rewrites the storage section from a single-object format to an array format with scope field, adds examples for app-scoped, org-scoped, and both-scopes-together
  • storage-policies.md — adds org-level row to the membership policy type table and updates the storage levels description
  • constructive-features/SKILL.md — adds "Org-scoped storage" row to the Storage & Uploads feature catalog
  • constructive-sdk-uploads/SKILL.md — adds scope examples and auto-injection docs to the bucket seeding section

Companion to constructive-db PR #1240 and constructive PR #1195.

Review & Testing Checklist for Human

Low risk — docs only.

  • Verify blueprint JSON examples are valid and match the actual construct_blueprint behavior
  • Verify the org-level membership policy type row is correct (membership_type=2, AuthzEntityMembership)

Notes

No code changes — documentation only.

Link to Devin session: https://app.devin.ai/sessions/c0494871633d4beb91f1e16e53c776d1
Requested by: @pyramation

Top-level storage[] entries now accept scope: 'app' (default) or 'org'.
- Updates blueprint-definition-format.md with scope examples and field docs
- Updates storage-policies.md with org-level membership policy type
- Updates constructive-features catalog with org-scoped storage feature
- Updates constructive-sdk-uploads with scope examples and auto-injection docs
@devin-ai-integration
Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@pyramation pyramation merged commit d052c25 into main May 19, 2026
2 checks passed
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