Skip to content

Source instance - #197

Open
davidabram wants to merge 5 commits into
mainfrom
source-instance
Open

Source instance#197
davidabram wants to merge 5 commits into
mainfrom
source-instance

Conversation

@davidabram

Copy link
Copy Markdown
Member

No description provided.

davidabram and others added 4 commits August 10, 2026 13:18
Repository-scoped databases previously identified only their logical repository, leaving no stable identity for an individual physical database. Add an additive migration and typed metadata to assign a generated identity once per database, with an atomic claim that makes concurrent initialization converge without overwriting valid values.\n\nCover fresh, repeated, reopened, independent, concurrent, mismatch, and baseline-migration cases with tests, and record the logical-versus-physical identity contract.\n\nPlan: agent-trace-source-instance-id (T01)

Co-authored-by: SCE <sce@crocoder.dev>
Storage resolution previously discarded metadata returned while verifying the repository database, preventing callers from accessing source_instance_id from the same initialization call that opened the database. Preserve the typed metadata through concurrent-safe opening and expose it on ResolvedAgentTraceStorage, with assertions for stable identity across repeated resolution.

Plan: agent-trace-source-instance-id
Task: T02

Co-authored-by: SCE <sce@crocoder.dev>
Hook runtime previously used the setup/lifecycle resolver, which could run repository migrations during high-frequency hook execution. Split storage opening by caller so hooks use a no-migration path that preserves setup guidance for missing or incomplete schemas while still validating repository metadata after setup.\n\nUpdate the agent-trace storage context and plan evidence to document the separate contract and cover missing, baseline-only, and initialized database behavior.\n\nPlan: agent-trace-source-instance-id T03

Co-authored-by: SCE <sce@crocoder.dev>
Setup diagnostics previously omitted the source-instance identity even though storage resolution already returned it. Include the ID in the lifecycle setup payload and rendered message, with coverage for configured and absent remotes, so setup output exposes the complete repository identity without changing workspace or ingestion behavior.\n\nPlan: agent-trace-source-instance-id.md (T04)

Co-authored-by: SCE <sce@crocoder.dev>
@vercel

vercel Bot commented Aug 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sce-config-json Ready Ready Preview Aug 10, 2026 11:47am

Request Review

Distinguish the logical repository ID from the physical database lineage ID and preserve the migration, concurrency, and setup/runtime resolution contracts. Record the accepted decision and mark the implementation plan complete with its validation evidence.\n\nPlan: context/plans/agent-trace-source-instance-id.md (T01, T02, T03, T04, T05)

Co-authored-by: SCE <sce@crocoder.dev>
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