feat: add constructive-compute-stubs — schema-only DDL for FK resolution

[pyramation]

Summary

Adds database/constructive-compute-stubs/ — a pgpm package containing schema-only DDL (tables, columns, constraints, indexes) for user/auth/infra/membership schemas. Zero behavioral code (no policies, grants, triggers, procedures, views).

Generated by the constructive-db slicer (stubMode: true) from PR #1586.

8 schemas, 50 tables:

Schema	Tables	Examples
services_public	15	apps, apis, api_modules, domains, sites, site_metadata
constructive_memberships_public	20	app_memberships, org_memberships, membership_types, org_members
constructive_auth_private	8	sessions, session_credentials, identity_providers
constructive_memberships_private	3	SPRTs (structural only)
constructive_users_public	2	users, role_types
constructive_infra_public	2	platform_namespaces, platform_namespace_events
constructive_auth_public	0	schema only
constructive_infra_private	0	schema only

Purpose: Provides FK targets so the compute packages (constructive-compute, constructive-compute-fbp) can reference user/auth tables without pulling in the full security machinery. This enables a lightweight database for constructive-functions that has the complete relational model without any auth overhead.

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

[devin-ai-integration]

🤖 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, CI, and merge conflict monitoring

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​pgpm/​stamps@​0.26.0
	npm/​@​pgpm/​inflection@​0.26.0
	npm/​pgpm@​4.28.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @constructive-io/s3-utils is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/pgpm@4.28.1 → npm/@constructive-io/s3-utils@2.18.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@constructive-io/s3-utils@2.18.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @constructive-io/s3-utils is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/pgpm@4.28.1 → npm/@constructive-io/s3-utils@2.18.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@constructive-io/s3-utils@2.18.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/pgpm@4.28.1 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm pgpm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: database/constructive-compute-stubs/package.json → npm/pgpm@4.28.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/pgpm@4.28.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report