Skip to content

docs: coordinate private static query and relationship capabilities - #91

Open
Dastari wants to merge 15 commits into
mainfrom
docs/gema-capability-coordination-20260930
Open

Dastari wants to merge 15 commits into
mainfrom
docs/gema-capability-coordination-20260930

Conversation

@Dastari

@Dastari Dastari commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner

Current outcome

Keep the remaining static joined/computed queries, SQL Server summaries/pages and private generated views open. Record the independent #96/#98/#99/#102 implementation contracts, combined executable examples and backend evidence; none completes the full consumer migration or requires dynamic runtime GraphQL.

Coordinate the immutable AI-only .2 baseline and reserved subsequent .3 ORM release. Reconcile aligned package versions and distinguish proposed A–D interfaces from implemented static fixes. A remains under corrected FK/ownership review and B–D stay gated; independent fixes do not wait for those capabilities.

This documentation checkpoint follows committed static predecessors; once they merge its diff is documentation-only. It does not add application changes or authorize deployment/database access. Exact merge/tag metadata will be recorded in the final handoff.

Validation: documentation governance passes for 192 files, local links resolve to committed runnable examples, and the matrix retains every open requirement and verification gate. Combined core/group/projection execution passes 45 SQLite tests, 33 PostgreSQL tests plus an owned aggregate test; six generated relationship regressions execute on each backend. MSSQL library/profile/compilation evidence remains explicitly separate from live execution.

Documentation impact

  • Documentation updated: active plan, requirement/dependency matrix, release coordination and source/example references.

@Dastari
Dastari changed the base branch from main to fix/policy-aware-projections-20261001 October 1, 2026 07:16
@Dastari
Dastari marked this pull request as ready for review October 1, 2026 07:17
@Dastari
Dastari changed the base branch from fix/policy-aware-projections-20261001 to main October 1, 2026 07:56
@Dastari

Dastari commented Oct 2, 2026

Copy link
Copy Markdown
Owner Author

Portable group enumeration and ordinary SQL-visible aggregates are implemented for review in #111 (0.38.0 proposal, head 09915d1), independently of A–D and timestamp opt-in. PostgreSQL and SQLite execute >1,300-group parity with ASCII-only ordering/byte tie-break, authorization/nullable/metrics/cursor fixtures and a no-query-SQL consumer collecting 1,225 events in 100-group batches. Ordinary fetch accepts current Unrestricted/Complete visibility and rejects residual policies; nonowner PostgreSQL RLS is executed. MSSQL pages explicitly remain unsupported; no live MSSQL execution claimed.

Keep joined/computed queries, SQL Server summaries/pages and private generated views open here. This is event-name enumeration/ordinary aggregate authorization only, not completion of the remaining GEMA migration. #111's tiny dependency #110 repairs expired documentation review dates blocking publication. A protected-environment human release review is still required; no unpublished PR head is an adoptable GEMA release. Release handoff will identify the immutable tag/source when published.

@Dastari

Dastari commented Oct 3, 2026

Copy link
Copy Markdown
Owner Author

PR #111 merged at 3bff96b90ce19efa2bfc9cc71d3c95f45cad8c39 (tested head c7d564ffab8105e67c6f1932cc99a572c347313a; all 12 checks green), aligning ORM/macros 0.38.0. PostgreSQL complete single-text event enumeration and ordinary aggregates under complete SQL read visibility now have disposable execution evidence and a standalone private repository example. SQLite behavior/SDL/cursors are retained; MSSQL group pages reject explicitly.

Joined/computed queries, SQL Server summaries/pages and private generated views remain open here. This does not complete the GEMA migration or implement runtime A–D.

Authorized source-only release workspace-2026.10.03.1 is validating exact merged source: https://github.com/Dastari/graphql-orm/actions/runs/37080240446 . GEMA should adopt only after immutable publication and matching manifest/commit verification; no release is published yet.

@Dastari

Dastari commented Oct 3, 2026

Copy link
Copy Markdown
Owner Author

Published immutable workspace-2026.10.03.1, ORM/macros 0.38.0, exact source 3bff96b90ce19efa2bfc9cc71d3c95f45cad8c39 (merged #111; tested head c7d564ffab8105e67c6f1932cc99a572c347313a). All 12 PR checks and all 20 release jobs passed.

Release: https://github.com/Dastari/graphql-orm/releases/tag/workspace-2026.10.03.1
Manifest: https://github.com/Dastari/graphql-orm/releases/download/workspace-2026.10.03.1/workspace-2026.10.03.1.json

Workspace/core/macro tags resolve to the exact merge source. Published manifest/notes match the deterministic preview; checksums, package trees and lockfile hash verified. Complete SQLite/PostgreSQL text-group enumeration and SQL-visible ordinary COUNT/SUM are now published. Remaining joined/computed queries, MSSQL summaries/pages and private generated views stay open in #91. Runtime A–D and host timestamps are not included; pending branch versions must advance above actual main before merge. No downstream files or application databases were changed.

This branch has not been deployed

No deployments
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