fix(run): remote-state scope resolves intent-declared project slugs - #606
Merged
Conversation
…o prj_… ids An intent that declares `project: <slug>` outranks both the repo link and the OIDC exchange's bound scope in resolveScope — and state routes take prj_… ids only, so every CI lane 404'd, which resource-hiding reported as 'this repo isn't connected' (hit live on the first CI run after the intent heal). - CI: adopt the OIDC exchange's bound project when the local value is empty OR a slug — the exchange's binding is authoritative there. - everywhere else: resolve a non-id project via the projects list (configsurface.ResolveProjectID), leaving the OSS backend's fixed _local scope alone. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
adampullely
added a commit
that referenced
this pull request
Aug 2, 2026
…ped intents (#607) Two silent ways the catalog (and its docs) never reached the platform: - The auto-publish gate keyed on scope precedence, where tag outranks branch: a release workflow that tags every main head disabled auto-sync FOREVER, with no output (hit live — a repo's Docs library stayed empty because each merge commit was immediately tagged). The gate now takes the snapshot and accepts a clean main head that is also tagged; dirty/detached/PR states stay excluded. Every silent precondition return now says why under ORUN_VERBOSE. - The push scope adopted the intent-declared project SLUG; state routes take prj_… ids, so the object sync 404'd ('Route not found: …/projects/<slug>/state/objects/missing', warn-only in autosync). Same resolution as run/#606: OIDC-bound id wins in CI, projects-list resolution elsewhere. Also: `orun catalog push` resolves the backend URL from intent.yaml (passed nil before — the explicit verb demanded --backend-url even inside a configured repo). Co-authored-by: Rahul Varghese <rahul.varghese@sourceplane.ai> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First CI run after a product intent declares
project: <slug>(lumen#66): the slug outranks the OIDC exchange's bound scope in resolveScope, state routes 404 on slugs, and resource-hiding collapses that into 'this repo isn't connected' — all 8 infra lanes failed on ambient run 30742748771.prj_…when the local scope is empty or a slug (the exchange's repo-binding is authoritative).configsurface.ResolveProjectID(same hop the secrets surface uses since feat(secrets): resolve intent-declared project slugs to prj_… ids #603). OSS_localscope untouched.🤖 Generated with Claude Code