chore(skills): bump the bundled community-catalog pin to trinity-skills v0.5.0 (lockstep with the library release) #3430

What

Fresh installs seed the bundled community skills catalog (abilityai/trinity-skills) at v0.3.0, but the library has since shipped v0.4.0 (2026-10-07) and v0.5.0 (2026-10-09). The pin should follow the catalog to v0.5.0 — the default ref moves in lockstep with catalog releases (last bump: #3123).

Why

Instances only ever see tagged states of the catalog, so every fix and addition since v0.3.0 reaches zero fresh installs until the pin moves:

• v0.4.0 — adds project-status (daily per-project operator status with a projected finish date) and brings the six project-* skills onto one lineage, configured from the agent's own project standard
• v0.5.0 — adds update-status (the agent's STATUS.md), and refreshes project-status, project-steward, add-pipeline and create-playbook to the current ask and dispatch contracts. Two of those are fixes for behaviour that fails today on current dev:
  • project-status filed asks under an id the platform refuses (invalid_request_id), so none was ever raised
  • add-pipeline taught an escalation title cap of 300 characters; the cap is 120, so a longer escalation is refused and never filed

Release notes: https://github.com/Abilityai/trinity-skills/releases/tag/v0.5.0

Acceptance criteria

• Default bundled catalog ref = v0.5.0; the seed note on a fresh install shows v0.5.0
• Fresh-install sync of the default source succeeds against the tag (no moved_tag), and the Library lists 40 skills including project-status and update-status
• Every other place the default ref is written (env examples, user docs, feature flows, pin tests) says v0.5.0 in the same PR
• Release note line: "bundled community skills catalog now v0.5.0"

Scope note

The seed is fresh-install only by design, so this does not move existing instances — that gap is tracked as its own feature issue. The tag exists (annotated, CI green on its commit); this is ready now.