feat!: only use uncertain transfer risk

[reidzeibel]

Good news, impossible or unlikely state is now dropped, so then the rule is simpler!
Bad news? it is a breaking change. 😅

TransferRisk.Unlikely and UNLIKELY_TRANSFER_LIMIT_IN_SECONDS are removed. Any gap equals to or below zero now classifies as TransferRisk.Uncertain, so getTransferRisk(-300) returns 'uncertain' where it previously returned 'unlikely'.

May this PR simplifies everything! 🙏🏼

[Copilot]

🟢 Approval recommended

Behavioral changes are consistent across implementation, exports, and tests, with only a small documentation wording nit noted.

Pull request overview

This PR simplifies the transfer-risk model by removing the unlikely state and its threshold, leaving a single uncertain risk for any non-positive (missed or zero-slack) transfer gap, and updates exports/tests accordingly.

Changes:

• Remove TransferRisk.Unlikely and the UNLIKELY_TRANSFER_LIMIT_IN_SECONDS threshold constant.
• Update getTransferRisk to classify any finite seconds <= 0 gap as TransferRisk.Uncertain.
• Update public exports and unit tests to reflect the single remaining risk level.

File summaries

File	Description
src/transfer-risk/types.ts	Removes Unlikely and updates TransferRisk shape/docs for the simplified model.
src/transfer-risk/transfer-risk.ts	Simplifies getTransferRisk to return only Uncertain (or undefined).
src/transfer-risk/index.ts	Removes re-export of the deleted threshold constant; keeps TransferRisk export.
src/transfer-risk/tests/transfer-risk.test.ts	Updates test expectations and removes references to the deleted constant/state.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.