82: Remove lifecycle operations from the TickerService API

This commit is contained in:
2026-09-03 20:34:49 +02:00
parent 461044a998
commit ddbf6f047d
11 changed files with 155 additions and 34 deletions
+5
View File
@@ -181,6 +181,11 @@ nenjim.journal.service</code></pre>
applications. Construction, registration, and startup remain fail-fast without rollback. Earlier successful
snapshot entries remain truthful after a later failure, and the online point plus blocking wait are reached
only after every configured process succeeds.</p>
<p>Ordinary consumers receive the lifecycle-free <code>TickerService</code> view, which exposes only the
latest-price query. The same <code>TickerServiceImpl</code> object separately implements
<code>NenjimProcess</code> so the Hub owns startup. The implementation starts its configured active
<code>PriceSource</code> instances internally and stops those already started if Ticker startup fails; it
exposes no general Ticker stop operation.</p>
<p>The Ticker still explicitly selects the Raydium EVE/USDT source ID while the hardcoded source remains a passive,
registered component. Process Manager continues to poll immutable ordered snapshots of actual successful
startup milestones rather than displaying configured intent or claiming current health.</p>