[trinity-ability]

Summary

Fresh installs now seed the bundled community skills catalog (abilityai/trinity-skills) at v0.5.0 (was v0.3.0). This tracks the catalog's releases the same way #3123 did.

• v0.4.0 adds project-status and moves the six project-* skills onto one lineage.
• v0.5.0 adds update-status and fixes two skills that fail on current dev:
  • project-status filed its asks under an id the platform refuses (invalid_request_id), so none was ever raised.
  • add-pipeline taught a 300-character escalation title cap. The real cap is 120, so a longer escalation is refused and never filed.

Checked against the upstream tag:

• refs/tags/v0.5.0 exists and is an annotated tag, which the sync's annotated-tag handling covers (bug(skills): a tag-pinned source is refused as moved on every sync after the first when the tag is annotated #2550).
• 40 skills (38 at v0.3.0), including project-status, update-status and update-dashboard. Nothing was dropped.
• The six non-markdown files that changed since v0.3.0 were reviewed. They rename the Gemini model id (-preview removed), add word counts to the microsite checker, add an unquote import in the epub extractor and change a validator. No new network endpoints.

The seed is fresh-install only, so existing instances keep their source row (ent#529). The user doc already has the steps for moving an existing row to a newer tag.

Files

• src/backend/config.py: DEFAULT_SKILL_SOURCE_REF default is now v0.5.0, and the history comment is updated.
• .env.example: the documented TRINITY_DEFAULT_SKILL_SOURCE_REF is now v0.5.0.
• docs/user-docs/automation/skills-and-playbooks.md: the pin sentence and the post-move "Check" step (project-status, update-status, 40 skills).
• docs/memory/feature-flows.md and docs/memory/feature-flows/skills-library-sync.md: history and index rows.
• tests/unit/test_2545_skill_source_pin.py: the minimum pin rises to v0.5.0 with the reason given, and the upstream membership-check command now covers the new skills.
• tests/registry.json: the entry for that test is updated.

Test evidence

• With only the test file changed, the pin was still below the new minimum and the minimum-pin check failed: 1 failed, 3 passed.
• After the bump: unit/test_2545_skill_source_pin.py: 4 passed.
• Related suites (test_2545_skill_source_pin.py, test_2550_annotated_tag_pin.py, test_ent237_skill_source_env_packaging.py, test_ent237_skill_sources.py): 126 passed.

Pre-merge checklist

• Live fresh install (not run yet; Docker was down). On a fresh-install stack:
  • The seed note shows @ v0.5.0.
  • Syncing the default source succeeds against the tag, with no moved_tag.
  • The Library lists 40 skills, including project-status and update-status.
  • One of the two fixed skills (project-status or add-pipeline) runs end-to-end on an agent.

Release note

bundled community skills catalog now v0.5.0

Target: 1.0.0

Fixes #3430

🤖 Generated with Claude Code

[vybe]

merge-train: pushed one mechanical commit to this branch (90de94029). The pin-floor assertion in tests/unit/test_2545_skill_source_pin.py had lost its f prefix on one line, so a failure printed a literal {_PIN_FILES}. Assertion logic unchanged; 4/4 pass. Validation found nothing else blocking. Notes for the release: the bump only affects fresh installs (existing instances keep their source row), and upstream tagged v0.5.1 today, which would need its own review.

[vybe]

merge-train: batch validated on train PR #3781 (all Tier 1 + Tier 2 checks green).