Remove the ≤2 promotions/cycle cap from feedback_promote (and charter routing-cap language)

Implemented promotion fixes for Brief #132 / Feedback #44 / Feedback #43 in branch flower/132-promotion-fixes, commit 55fc95236b3fee07454f0cdd52c3fa6e85b172cb. Changes: - Removed the feedback_promote per-cycle throttle entirely from FeedbackPromotionService: no guard, no per-cycle Setting writes, no operator/agent cap path remains. - Kept cycle_key only as promotion metadata/correlation and removed cap language from feedback_promote MCP schema plus the CLI option text. - Removed the dead /config promotion-cap setting UI and Livewire save path so the app no longer exposes a nonexistent cap. - Added Feedback::briefLinks(), creates a BriefLink relation from promoted brief to source feedback using relation=seed, backfills that link on deduped brief promotion, and exposes linked feedback in recall_brief links.feedback. - Removed the stale ops charter default sentence "Cap routings at 2 per cycle." PromptTemplateSeeder was not edited, but because DaemonCharterDefaults feeds seeded prompt templates, orchestrator should re-seed prompt templates after merge if the live charter row needs the updated text. Verification: - Focused: MEILISEARCH_KEY=LARAVEL-HERD ANTHROPIC_API_KEY= ~/bin/php artisan test tests/Feature/Feedback/FeedbackPromotionServiceTest.php tests/Feature/Feedback/FeedbackPromoteEntryPointsTest.php tests/Feature/Feedback/ShowTest.php tests/Feature/Config/IndexTest.php --compact passed: 25 tests, 124 assertions. - Full before Pint: MEILISEARCH_KEY=LARAVEL-HERD ANTHROPIC_API_KEY= ~/bin/php artisan test passed: 701 tests, 690 passed, 11 skipped, 4779 assertions. - ~/bin/php ./vendor/bin/pint fixed formatting. - ~/bin/php ./vendor/bin/pint --test passed. - Full after Pint: MEILISEARCH_KEY=LARAVEL-HERD ANTHROPIC_API_KEY= ~/bin/php artisan test passed: 701 tests, 690 passed, 11 skipped, 4779 assertions. Worktree is clean on flower/132-promotion-fixes; not merged or pushed.

**Operator (Mike) directive, 2026-07-03:** remove the ≤2 promotions/cycle cap on feedback_promote. (Operator thought a brief might already exist — recall_briefs found none, so creating this.) ## What `feedback_promote` currently enforces a "≤2 promotions/cycle" cap (keyed by `cycle_key`, defaulting to the current hour). Remove that cap so daemons can promote as many route-worthy items as genuinely warranted rather than being throttled. ## Where (to confirm during implementation) - `app/Services/Feedback/FeedbackPromotionService.php` — the promotion-cap logic (cycle_key counting / the ≤2 guard). Remove the cap check (or make it a very high/again config-gated ceiling if a safety valve is desired — operator's call; default ask = remove). - The MCP tool `feedback_promote` (`app/Mcp/Tools/...`) — drop the `cycle_key`/cap language from its description + params if the cap is gone. - **Charter/template alignment:** the ops + orchestrator daemon charters (v3, seeded from Solo scratchpads e.g. ops charter scratchpad 1023, orchestrator equivalent) say "Cap routings at 2 per cycle" / "Cap routings at 2 per cycle". Remove that cap language so the charters and code agree. Also check the #126 auto_dispatch drain contract (scratchpad 1026) for any matching cap wording. ## Why Operator wants throughput on triage→route without an artificial per-cycle throttle; the daemons already exercise judgment ("route only route-worthy", "if unsure report") so the numeric cap is redundant and can drop genuinely-actionable items on the floor in a busy cycle. ## Verify - feedback_promote succeeds for 3+ promotions in the same hour/cycle with no cap error. - Charter text no longer instructs a 2/cycle cap; code no longer enforces it. - `php artisan test` green; pint clean.