Skip to content

feat: establish viewer-scoped SQLite and secrecy foundation - #1

Merged
freckle-infra-agent[bot] merged 1 commit into
mainfrom
agent/c-1813-under-wraps-m1-database-boundary-secrecy
Nov 11, 2026
Merged

freckle-infra-agent[bot] merged 1 commit into
mainfrom
agent/c-1813-under-wraps-m1-database-boundary-secrecy

Conversation

@freckle-infra-agent

Copy link
Copy Markdown
Contributor

Cockpit: C-1813

Implements M1 of C-1810 with a single internal SQLite boundary, viewer-scoped typed reads and writes, owner DTOs without coordination fields, query-level surprise exclusion, soft deletion/restore, configured calendar archives, and admin group management without content bypass.

Adds real on-disk database read/permission matrices, complete owner-response differential tests, cross-store claim races, persistence/migration checks, and a full-source structural guard with negative fixtures, transitive API type resolution, approved operation signatures, input-only contexts and checker-only parser tooling. Documents schema, API, migration/rollback and release prerequisites. Adds Conventional Commits/release-please, immutable main images, release images, and PR/merge-queue container build paths.

Local validation: source guard, formatting, vet, real SQLite tests with race detector, repeated claim/differential tests and CGO-disabled binary smoke initialization. Container build and GitHub publishing require CI; no Docker runtime is available locally. Release automation additionally requires owner-provisioned scoped App credentials. No UI, OIDC/MCP runtime or deployment is claimed.

Workflow changes require owner review. Merge only after every check, independent exact-head review and applicable publication/owner approval gates pass.

@freckle-infra-agent
freckle-infra-agent Bot force-pushed the agent/c-1813-under-wraps-m1-database-boundary-secrecy branch from 453676b to efc2584 Compare November 11, 2026 16:14

@nicolerenee nicolerenee left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed at exact head efc2584 (via Claude Code, on Nicole's instruction "yes, fix it first" and her standing review delegation). One-line delta from the previously reviewed 453676b: the build-stage FROM now pulls through mirror.gcr.io and is digest-pinned (golang:1.27.3@sha256:e519d3b0..., same tag as go.mod); runtime stage and every other byte unchanged, same parent. Independent prepared-publication approval on this exact object (private anchor 08c0f12, authorization read via review_evidence); CI test and image green; merge state clean. My earlier full read of the tree still stands: no private identifiers, SHA-pinned actions, read-only top-level permissions, release credential only on pushes to main. Not covered / still pending on Nicole: provisioning the release GitHub App credentials (RELEASE_APP_CLIENT_ID variable, RELEASE_APP_PRIVATE_KEY secret); until then the release job fails on pushes to main.

@freckle-infra-agent
freckle-infra-agent Bot merged commit a9cb148 into main Nov 11, 2026
4 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