Conversation
StepPage previously required a manual `/plugin install steppage` before its
deploy tools were available. Provision the built-in StepPage plugin into a
fresh install automatically so `page_deploy`, site/version listing, and
promote/rollback work out of the box, per the StepPage plugin reference.
- plugins.ts: add `ensureBuiltinPluginsInstalled()` (materializes the built-in
marketplace and copies the StepPage manifest into the user plugin root).
Idempotent and once-only via a `.stepcode-preinstalled` marker, mirroring the
`.stepcode-builtin-fingerprint` pattern, so a plugin the user later uninstalls
is not silently resurrected on the next launch. Add a `{ provision }` option
to `installMarketplacePlugin` and export `provisionBuiltinPlugin`.
- mcp.ts: before discovery in session start, copy the manifest (fast, so the
current session's discovery sees it) and fire the `steppage-mcp` installer in
the background so a first launch never blocks on the network. A still-missing
executable surfaces the existing actionable connect-failure remedy.
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
1 participant
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
Pre-install the built-in StepPage plugin into a fresh install so its deploy tools (
page_deploy, site/version listing, promote/rollback, preview links) are available out of the box — no manual/plugin install steppagerequired, per the StepPage plugin reference.How
plugins.tsensureBuiltinPluginsInstalled()— materializes the built-in marketplace and copies the StepPage manifest into the user plugin root. Idempotent and once-only via a.stepcode-preinstalledmarker (mirrors the existing.stepcode-builtin-fingerprintpattern), so a plugin the user later uninstalls is not silently resurrected on the next launch.installMarketplacePlugin(entry, dir, { provision })— new opt to copy the manifest without running the installer.provisionBuiltinPlugin(was the privateprovisionPluginCommand).mcp.ts— in the MCP session-start block, before discovery:await ensureBuiltinPluginsInstalled()(fast manifest copy, so this session's discovery sees StepPage), then fireprovisionBuiltinPluginin the background so a first launch never blocks on thecurl … | shinstaller. A still-missing executable surfaces the existing actionable connect-failure remedy.Behavior notes
steppage-mcpis still auto-supplied by the official installer when absent (guarded bycommand -v, honorsSTEPCODE_STEPPAGE_INSTALLER_URL, skipped on Windows) — unchanged.STEPFUN_API_KEY/ Step-login fallback path unchanged.Verification
tsgo --noEmit(repo-wide, via pre-commit): clean.pre-installs the built-in StepPage plugin once and respects a later uninstall).ensureBuiltinPluginsInstalled()→discoverStepMcpServers()surfacessteppage__steppage(carrying thesteppage-mcpprovision) in the same session; idempotent; respects uninstall.