@zibby/skill-ids 2.0.3 → 2.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zibby/skill-ids",
-  "version": "2.0.3",
+  "version": "2.0.5",
   "description": "Single authoritative Zibby skill-id map (zero-dep leaf). The one source of truth for well-known skill ids — every consumer (agent-workflow, core, skills, backend, templates) imports it, so the ids can never drift.",
   "type": "module",
   "main": "src/index.js",

package/src/index.js

@@ -89,7 +89,9 @@ export const SKILL_IDS = Object.freeze({
   // `doc_source` — INTEGRATION-GATE MARKER (like `circleci`), not a runtime MCP
   // skill: no skill registers under this id (the resolver warns + skips it).
   // Declaring it gates deploy on a document source via the OR-group
-  // {any:[google, notion, lark]}. Used by the prd-review template.
+  // {any:[google, notion, lark-docs]} — Lark Docs ("Lark App"), never plain
+  // Lark Chat (that credential can't read a Lark doc). Used by prd-review
+  // and product-owner.
   DOC_SOURCE: 'doc_source',
   // `linkedin` — publish to the connected PERSONAL LinkedIn profile
   // (linkedinSkill → linkedin_publish_post).
@@ -158,13 +160,21 @@ export const SKILL_IDS = Object.freeze({
   // (the flaky-test-fixer pattern).
   CIRCLECI: 'circleci',
   // `vikunja` — INTEGRATION-GATE MARKER (same shape as `circleci`): no skill
-  // registers under this id. board-runner's vikunja tracker resolves the
-  // instance + token deterministically via resolveIntegrationToken('vikunja')
-  // and calls the Vikunja REST API itself, so the agent gets no vikunja tools.
-  // Declaring it surfaces Vikunja on the deploy modal — as an OPTIONAL row, not
-  // a gate: board-runner picks one of three tracker backends at run time, so a
-  // Jira-only user must not be blocked on a Vikunja connection.
+  // registers under this id (a vikunja tracker resolves the instance + token
+  // deterministically via resolveIntegrationToken('vikunja') and calls the
+  // Vikunja REST API itself, so the agent gets no vikunja tools). Mapped
+  // OPTIONAL in the backend — declaring it surfaces a non-blocking Vikunja
+  // connect row. board-runner no longer declares it: its tracker requirement
+  // moved to the REQUIRED one-of `board_tracker` group below (founder ruling,
+  // 2026-08-21).
   VIKUNJA: 'vikunja',
+  // `board_tracker` — INTEGRATION-GATE MARKER (the `doc_source` shape): no
+  // skill registers under this id. The backend maps it to the REQUIRED
+  // OR-group {any:[jira, vikunja]} (+ a trigger-time gate with a PingCode env
+  // alternative), so a board-driving template declares it to mean "at least
+  // ONE board tracker must be available". Declared by board-runner's poll +
+  // writeback nodes (as a literal string — see the 0.x-caret note there).
+  BOARD_TRACKER: 'board_tracker',
   // LLM-provider admin/billing skills (paste-token integrations). See
   // @zibby/skills' llm-billing.js + backend/src/handlers/llm-billing.js.
   OPENAI_BILLING: 'openai_billing',