update
Paved command paved.update. Plan and apply a compatible local Paved Core, adapter or input update. Use when the user asks to update initialized Paved state.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- update
- description
- Paved command paved.update. Plan and apply a compatible local Paved Core, adapter or input update. Use when the user asks to update initialized Paved state.
03 SKILL.md 正文
<!-- Generated by Paved plugin paved@2.29.0 from paved.update; edit Paved Core instead. -->
Paved update command (paved.update)
Plan and apply a compatible local Paved Core, adapter or input update. Use when the user asks to update initialized Paved state.
Input: No arguments. Output: Compatibility result, planned changes, lock result, and diagnostics. Required lifecycle: INITIALIZED, RESOLVED, GENERATED, VALIDATED, READY, STALE, INCOMPATIBLE, BROKEN Required context: .paved/manifest.yaml, .paved/paved.lock Required capabilities: none declared Allowed side effects: Paved lock through update transaction, affected generated context and proposals Host side effects: refresh only the initiating host's installed Paved marketplace/plugin on an explicit update request; no host writes in dry-run.
Host plugin refresh
An explicit request to update Paved includes refreshing its installed plugin in the initiating host before updating this repository. Do not update another host, install a missing plugin, add a marketplace or change the installation scope.
For --dry-run, skip all marketplace and plugin writes; report the refresh steps and run only the existing launcher's local update --dry-run --json. Automatic lifecycle repairs and retries update local project state only; do not repeat this host refresh.
- Check the current host's plugin inventory with
claude plugin list --json. Confirmpaved@pavedis already installed in the current scope and note its version and path. If it is not installed, explain that plugin refresh is unavailable and stop before updating project state; do not install it. - Run
claude plugin marketplace update paved, and only if it succeeds runclaude plugin update paved@paved. Respect host permissions and keep the existing installation scope; if the host needs an explicit scope option, use the one reported by its inventory. Never update all marketplaces. - Locate the newly installed plugin's
scripts/paved.mjsfrominstallPathin a freshclaude plugin list --jsonresult. Do not use the old launcher, a cached environment path or the project shim for this first update. Quote the discovered path when invoking Node; do not guess it. - Use that launcher for the repository update below, preserving the user's supported arguments and explicit
--projecttarget. Verify the outcome with the same launcher'sruntime status --jsonandstatus --json. Report the installed plugin version separately from the project's pinned runtime version. If refresh, installation or path discovery fails, stop and report the failed stage before updating project state. A host refresh is not part of the project's rollback transaction: report any completed host steps, do not claim that nothing changed, and never bypass runtime integrity or compatibility checks. If the host needs a session restart to load refreshed hooks or skills, tell the user; do not claim those are already active.
Execution contract
- Invoke
node "<newly discovered plugin>/scripts/paved.mjs" update --jsonfrom the repository root after host refresh, passing the user's supported inputs. When refresh is skipped as described above, use the existing launchernode "${CLAUDE_PLUGIN_ROOT}/scripts/paved.mjs" update --jsoninstead. Always run it from the repository being worked on, never from the plugin directory. The launcher verifies the runtime and applies the transactional repository update. - Follow the structured result's status, diagnostics, evidence, and next action. When
data.remediationnames a Paved command, run it right away, present any decisions it returns, then repeat the original command. Stop only when the runtime blocks on something it cannot remediate.
Failure behavior
- Unknown compatibility, migration requirements, and ownership conflicts stop before unsafe writes.
- Remote updates remain unsupported.
- When the plugin carries a newer runtime than paved.lock pins, update verifies and activates it inside the update transaction and rewrites the lock;
runtime rollbackrestores the previous runtime and lock. The same or an older plugin runtime never changes the pin. - If a required ToolImplementation or runtime is unavailable, stop and explain the missing prerequisite. Never infer or execute a command from repository scripts.
- Do not edit human-owned Paved state or bypass lifecycle, ownership, approval, or verification gates.
Conversational contract
- Invoke the command. If it returns
"status": "awaiting_input", it is waiting on the user. - Present every decision in
decisions[]to the user: what Paved detected, what remains to decide, why it matters, the options, Paved's recommendation and its evidence. - Collect the user's answer. Do not answer on their behalf.
- Resume the same command with
--answer <decision-id>=<value> --answered-by <identity>, repeating--answeronce per value for a multi-choice decision. - Present the result.
Follow core.decisions.decisions for the full interaction protocol and its prohibitions.
04 同仓库更多 Skills
sample-skill
Does a sample task. Use when a sample is needed.
unexplained-contract
Does a sample task. Use when a sample is needed.
shell-block
Does a sample task. Use when a sample is needed.
project-identifier
Does a sample task. Use when a sample is needed.
oversized
Does a sample task. Use when a sample is needed.
no-activation
Does a sample task.