Separate production and staging Skill credentials - #96
Merged
Merged
Conversation
Keep student work on production while making staging an explicit choice with its own token. Preserve saved Project origins and the workspace credential wrapper when resuming existing work. Pin CLI 0.7.0 and prove the packaged environment arguments, credential isolation, and redaction. Keep API and Plan identities unchanged and leave the public catalog on its published version.
raghubetina
marked this pull request as ready for review
September 24, 2026 20:09
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.
New student work should use
firstdraft.com, while staging remains an explicit choice with its own credential. Update the canonical Skill to teach--staging,FIRSTDRAFT_STAGING_API_TOKEN, and saved-origin behavior without changing project wrapper precedence. Existing staging Projects retain their origin and now require the separate staging token variable.Prepare plugin 0.7.0 with CLI 0.7.0, preserving API 0.6 and Plan 0.22 compatibility. The public catalog stays on published 0.6.0 until the candidate is released.
Validation: 76 repository tests, deterministic packaging with the exact CLI, and the full CLI contract pass. Added checks cover staging-token isolation, packaged argument and credential forwarding, and token redaction on conflicting environment configuration.