Notify actionable branch drift once

[efraespada]

Branch synchronization now keeps a localized status card as the source of truth and emits a single linked action notification only when an aligned branch becomes stale again. The change preserves existing synchronization safety while reducing repeated timeline noise.

What changed

• Added transition-only notifications with canonical source-head fingerprints and replay protection.
• Reused the shared semantic publication flow to reconcile notifications and compact exact duplicates.
• Added English and Spanish branch-sync messages with sanitized branch references and status links.
• Updated observer tests, coverage budgets, architecture records, specifications, and user documentation.

Validation

• git diff --check origin/develop...origin/codex/branch-sync-action-notifications

Review notes

• Initial stale detection creates only the status card; a later aligned-to-stale transition is required for an action notification.
• Notification publication requires a canonical source head and trusted bot identity; publication failure preserves the updated status card without replaying branch work.

[docs-page]

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/copilot~387

Documentation is deployed and generated using docs.page

[vypbot]

Bugbot: review incomplete

Current status: The review of cc24a22 has partial coverage and cannot declare the whole pull request clean.

Action: Inspect the omitted items or reduce the pull request scope. Rerun the review only after changing the scope, limits, or access.

Incomplete coverage

• selection: complete; retained=1
• pull-request-comments: complete; retained=0
• review-threads: complete; retained=0
• diff: partial; retained=14, omitted=5, truncated=1
• previous-findings: complete; retained=0
• human-conversation: complete; retained=0
• rules: complete; retained=0

Pull request · Verified commit · Workflow run

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.99%. Comparing base (274db40) to head (cc24a22).
⚠️ Report is 772 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #387      +/-   ##
===========================================
+ Coverage    90.94%   92.99%   +2.04%     
===========================================
  Files          135      656     +521     
  Lines         6251    17443   +11192     
  Branches      1338     4481    +3143     
===========================================
+ Hits          5685    16221   +10536     
- Misses         172      473     +301     
- Partials       394      749     +355     

Files with missing lines	Coverage Δ
...pplication/policies/branch_sync_message_catalog.ts	100.00% <ø> (ø)
...cation/policies/branch_sync_notification_policy.ts	100.00% <100.00%> (ø)
...n/usecases/actions/observe_branch_sync_use_case.ts	100.00% <100.00%> (ø)
...pplication/usecases/push_single_action_contexts.ts	98.95% <100.00%> (ø)
...ure/composition/main_run_route_composition_root.ts	93.22% <ø> (ø)
...tion/push_single_action_capability_port_binding.ts	100.00% <ø> (ø)

... and 712 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.