datatug / backend / 38185932364

84%

Build Type

push

github

Committed by web-flow

Commit Message

fix: preserve SQL query connections on GitHub revision reads (#40)

Saved GitHub SQL queries with `connectionId` were returned read-only with a fallback revision, even though the Core save contract persists that field. Allow that supported field so reads preserve the connection and return the canonical writable revision; retain strict rejection of unknown or malformed metadata.

Validation: the new regression failed on the baseline, then passed with the one-line fix. `wb run -- go test ./githubstore4datatug -count=1`, `wb run -- go vet ./githubstore4datatug`, and `git diff --check` passed. Regression coverage uses the real save codec and checks the exact connection, query contents, branch head, canonical revision, and save support; unknown metadata alongside a connection and invalid connection types remain read-only.

Independent review and landing are owned by the coordinating launch agent.

Source commits:

- 0cb061ebd2c4 fix: preserve SQL query connections on GitHub revision reads

Pull request: datatug/backend#40
Review: /Users/alex/projects/handover-datatug-launch-2026-10-05/reviews/receipts/business-github-query-connection-reader-independent-sol-r1-20261012.md

Coverage Stats

1 of 0 new or added lines in 0 files covered. (NaN%)

5 existing lines in 2 files now uncovered.

7836 of 9328 relevant lines covered (84.01%)

0.84 hits per line