Update to Astrofaith

{
  "name": "astrofaith",
  "description": "Use Astrofaith to resolve locations, calculate authoritative Swiss Ephemeris charts, find planet-in-natal-house transit periods, and securely manage the connected member's saved birth profiles. Includes exact MCP payloads, provenance, settings, output selection, and environment data-boundary guidance.",
  "included_files": [
    {
      "relative_path": "references/contracts.md",
      "size_in_bytes": 6118
    }
  ],
  "skill_md_contents": "---\nname: astrofaith\ndescription: Use Astrofaith to resolve locations, calculate authoritative Swiss Ephemeris charts, find planet-in-natal-house transit periods, and securely manage the connected member's saved birth profiles. Includes exact MCP payloads, provenance, settings, output selection, and environment data-boundary guidance.\n---\n\n# Astrofaith\n\nUse the authenticated Astrofaith MCP server for authoritative chart calculation\nand saved birth-data management. Treat returned birth data as private.\n\n## Confirm context first\n\nCall `birthdata_capabilities` before saved-data work. Every result includes\n`astrofaithContext`: staging and production data are separate, and results\nbelong only to the Astrofaith member who approved the current OAuth connection.\n\n## Recommended workflow\n\n1. Use `resolve_location` to obtain a canonical label, coordinates, and IANA\n   timezone. If it returns multiple candidates, ask the user to choose. A\n   returned candidate can be reused unchanged as a calculation birth's\n   `location` object or as a transit location; do not delete or rename its\n   metadata fields.\n2. Search with `birthdata_list` before creating a duplicate.\n3. Create with `birthdata_create`, a unique `idempotencyKey`, canonical\n   `birthData.options`, and structured provenance where known.\n4. Calculate with `calculate_chart` using either `profileId` or explicit\n   `birth`, never both. Saved zodiac and house settings are inherited unless\n   explicitly overridden.\n5. Use basic output for ordinary readings. Use deep output only when the task\n   needs its extra audit detail, eclipses, or complete aspect data. Prefer\n   `output.sections` and `maxAspects` to keep responses focused.\n6. For \"when is planet X in natal house Y?\", call `find_transit_house_periods`\n   once. Do not approximate the answer by sampling several `calculate_chart`\n   results. Resolve and pass a canonical `transitLocation` when the user names a\n   location; otherwise the saved profile location and timezone are used.\n7. For a natal-plus-transit bi-wheel or cross-chart aspect question, call\n   `calculate_transit_comparison`. Use its `inner`, `outer`, and\n   `comparison.aspects` as one authoritative result instead of combining\n   independent chart calls.\n8. Return `links.openInAppUrl` when the user wants to continue interactively and\n   `links.renderUrl` for a deterministic chart-only view. Explain that plugin\n   OAuth and the Astrofaith browser login are separate sessions; a private\n   saved-profile link may ask the user to log in again in the browser.\n9. Read a record immediately before update or deletion and pass its `etag` as\n   `ifMatch`. Confirm destructive deletion with the user.\n\nRead `references/contracts.md` for exact payloads, supported values, source\nprovenance, ranking semantics, and error correction.\n"
}