Repository navigation
fix(login): native credential dot via a maintained reference - #7
Merged
Merged
Conversation
The Models row paints its credential dot only for a route that names a credential reference, so the `meta` route now declares `apiKeyEnv: MUSE_CODE_SUB_TOKEN`. An explicit reference is also DSH's highest-priority auth override, so the plugin mirrors the OAuth record's minted key into that reference and re-mints it ahead of Meta's ~24 h expiry (preserving the non-renewable identity token when the record is replaced by a fresh sign-in). Also fixes the live catalog sync treating the empty `models` array that the Settings form projects as a user-owned list, which would have kept Muse Wonder out of the route; documents the Meta prompt-cache keying and the meaning of the generic Edit/Delete row actions.
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
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.
What
metaroute now declaresapiKeyEnv: MUSE_CODE_SUB_TOKEN, which is what makes DSH paint the standard red/green credential dot on the Muse Code row. Because an explicit reference is also DSH's highest-priority auth override, the plugin mirrors the OAuth record's minted key into that reference and re-mints it before Meta's ~24 h expiry (identity token preserved; concurrent re-sign-ins are not stamped over).modelsarray as[]; the sync treated that as a user-owned list and skipped, which would have kept Muse Wonder out of the route. Only a non-empty list now counts as user-owned.prompt_cache_key= DSH session id; same key 1521/1600 cached, different/no key 0 in a live probe) and what the generic Edit/Delete row actions do — neither can be hidden by a plugin.Verification
npm run typecheck,npm run build, 25 tests (host routes, credential mirror/refresh, model sync, client card harness), markdownlint 0 issues.apiKeyEnv, credential reference resolved, no activation warnings.api.meta.ai: cache reuse confirmed only with a matchingprompt_cache_key;prompt_cache_retention: 24haccepted.