Update to Spera

{
  "description": "Deliver a verified Spera strategy across authoring, exact-revision backtesting, project knowledge, and artifact documentation through the remote Spera MCP server. Use when Claude Code, Codex, or Cursor must complete a strategy handoff with durable cross-client continuity and evidence receipts. Composes the dedicated Spera skills and stops before deployment or bot lifecycle actions.",
  "included_files": [],
  "name": "spera-deliver-strategy",
  "skill_md_contents": "---\nname: spera-deliver-strategy\ndescription: Deliver a verified Spera strategy across authoring, exact-revision backtesting, project knowledge, and artifact documentation through the remote Spera MCP server. Use when Claude Code, Codex, or Cursor must complete a strategy handoff with durable cross-client continuity and evidence receipts. Composes the dedicated Spera skills and stops before deployment or bot lifecycle actions.\nmetadata:\n  spera-contract: \">=1.0 <2.0\"\n---\n\n# Deliver a Spera strategy\n\nRead and follow `spera-foundations`, `spera-build-strategy`, `spera-run-backtest`,\n`spera-update-project-knowledge`, and `spera-write-documentation`. Use only the parts required by the\nuser's delivery request.\n\n## Deliver through one durable workflow\n\n1. Establish the explicit project, exact strategy ID, workflow ID, and granted scopes. Resume an existing\n   workflow after a client change or reconnect; never recreate a successfully persisted artifact.\n2. Build or repair one strategy draft in place until its exact revision has an `artifact_compiled`\n   receipt. When the requested delivery names a pair, market, and timeframe, pass that intended\n   workspace context as create-time `chartSettings`. Stop on the builder's typed budget or terminal rule.\n3. If requested, run a bounded backtest for that exact compiled commit. Deep starts still pass the full\n   pair and explicit market/timeframe; the first accepted deep job fills missing chart context but later\n   jobs do not overwrite it. Preserve settings, dataset, job,\n   pagination, and `backtest_completed` receipt. Do not imply live or forward performance.\n4. Research the manifest before project content. Apply ordinary knowledge once, or propose and obtain\n   explicit acceptance for `STRATEGY.md`. Keep revision-pinned citations and receipts.\n5. Read then apply exact artifact documentation once. Include compile/backtest statements only when the\n   same workflow contains the matching receipts and the document names their receipt IDs.\n\n## Handoff and stop\n\nReturn exact project/artifact IDs, branch and commit, workflow ID, document and documentation revisions,\nbacktest job/configuration when used, citations, and every persistence/compile/backtest/documentation\nreceipt. State any unverified claims or omitted steps plainly.\n\nDelivery ends at a documented, optionally backtested strategy. Never start, stop, pause, resume, or\ndeploy a bot; operate Fleet; access exchange credentials; or perform paper/live trading lifecycle work.\n"
}