feat: export host findings for an external package

[voku]

What changed

Implements #144 on top of released voku/agent-learning 0.13.0.

• bump voku/agent-learning to ^0.13.0;
• expose agent-loop learn finding-export --target-package PACKAGE --source-repository OWNER/REPO [--root PATH];
• bind the command to the repository's configured Learning root by default;
• call the package-owned FindingExporter API directly;
• render missing options and exporter failures as normal CLI failures rather than raw stack traces;
• advertise the umbrella extension in agent-loop learn help and top-level help.

Ownership boundary

agent-loop does not parse, validate, filter, or reshape Finding records. agent-learning owns all Finding/export semantics. The umbrella only resolves its local root and CLI options, then prints the package-owned deterministic JSON result.

There is no ToolingFinding, second store, copied run_id, generic provenance model, or automatic upstream write path.

Reduction check

The consumer-side production delta is deliberately small: Dispatcher.php is +41/-3 and the dependency constraint is a one-line change, for roughly +38 net production lines. The larger added file is focused integration coverage.

The practical acceptance test remains outside this repository: replay the real voku/httpful#34 dogfood feedback as governed Findings and remove docs/agents/agent-loop-findings.md. If that handoff still needs a parallel feedback document, this feature has not earned its complexity.

Validation

The focused integration test verifies exact package filtering through the real .agent-loop/learning default root and confirms the command is discoverable through learn help. Full repository CI remains authoritative.

[coderabbitai]

Warning

Review limit reached

@voku, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 28 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7b8b2189-68b8-463c-8248-67803eea1d03

📥 Commits

Reviewing files that changed from the base of the PR and between 39d16f3 and eeb972d.

📒 Files selected for processing (3)

• composer.json
• src/Dispatcher.php
• tests/FindingExportDispatcherTest.php

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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