docs(OMN-12312): Linear handler coverage inventory — 11 call categories mapped, 6 MISSING

[jonahgabriel]

Summary

OMN-8771 T1 inventory. Audited omnimarket/src/omnimarket/nodes/ for backing handlers covering each mcp__linear-server__* call category used by the 9 named skill prompt files in omniclaude (ticket_pipeline, decompose_epic, ticket_work, linear_epic_org/ticketing_epic_org, linear_triage/ticketing_triage, linear_insights/ticketing_insights, auto_merge, compliance_sweep, plan_audit).

The skills express Linear access through a tracker.* ProtocolProvider seam; each tracker.<op> maps 1:1 to an mcp__linear-server__<op> category.

Findings

• 11 distinct Linear call categories across the 9 skills.
• 5 EXIST: get_issue, list_issues, list_children, save_issue (state-write), save_comment — backed by node_linear_triage + node_ticket_query.
• 6 MISSING concrete EFFECT handlers: issue description/parentId write, create_issue, list_issue_labels, list_projects, get_project, list_teams, list_users — currently agent-executed against raw MCP or exposed only as injected protocol ports.
• 3 sub-tickets filed (3 net new Linear EFFECT nodes): OMN-13482 (node_linear_issue_write_effect), OMN-13483 (node_linear_issue_create_effect), OMN-13484 (node_linear_metadata_read_effect).

Inventory doc: docs/audits/2026-06-22-linear-handler-coverage-inventory.md. Docs-only; no code/interface change.

OMN-12312
dod_evidence: docs/audits/2026-06-22-linear-handler-coverage-inventory.md + sub-tickets OMN-13482/13483/13484 filed in Linear
Evidence-Source: d56ec4f6fd09f30295c939eeb9ae1ee0814edabd
Evidence-Ticket: OMN-12312

Paired OCC receipt PR: OmniNode-ai/onex_change_control#2909

[coderabbitai]

Warning

Review limit reached

@jonahgabriel, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 8 minutes and 14 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c53c3b00-8b60-47d7-a976-a436b0fdcb94

📥 Commits

Reviewing files that changed from the base of the PR and between 82b041c and 3feffb7.

📒 Files selected for processing (1)

• docs/audits/2026-06-22-linear-handler-coverage-inventory.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonahgabriel/omn-12312-omn-8771-t1-inventory-handler-coverage-which-node-handlers

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

⚠️ Hostile Reviewer — DEGRADED (informational)

Blocking findings (critical/error): 0
Total findings: 0
Models succeeded: none

Note: All reviewer models failed or were unavailable. Degraded results are informational during the pilot phase (OMN-8524) and do not block merge. Error: cli_review exited non-zero (all models failed or binary error)

---

Gate semantics (pilot phase)

Verdict	Meaning	Blocks merge?
passed	No critical/error findings	No
blocked	CRITICAL or ERROR findings found	Yes
degraded	All models unavailable (infra)	No (pilot)

Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524)