com_r35157_nenjim-hubd-impl_ref/openspec/changes/archive/2026-09-04-83-remove-burner-service-lifecycle-operations/proposal.md

Why

EvelynIOUBurnerService currently contains only start() and stop(), so ordinary service consumers receive process control instead of a domain API. This conflicts with the current Nenjim architecture, where the Hub owns lifecycle through an implementation's separate NenjimProcess view.

What Changes

• BREAKING: Make EvelynIOUBurnerService an empty lifecycle-free typed service contract until external domain operations exist.
• Keep EvelynIOUBurnerServiceImpl.start() solely as its NenjimProcess.start() implementation.
• Remove the implementation's public general stop operation and its now-unused stopping state and termination timeout.
• Preserve startup-failure cleanup, worker scheduling, transaction safety, and Hub startup wiring.
• Replace explicit stop/start reset semantics with process-restart semantics in JavaDoc, OpenSpec, and Nenjim documentation.

Capabilities

Modified Capabilities

• evelyn-iou-burner-service: Separates the empty typed service view from Hub-owned process startup and removes unsupported public stop/restart control.

Impact

• Changes the public com.fanitas.evelyn.service.burner.EvelynIOUBurnerService source contract and public methods of its reference implementation.
• Existing direct lifecycle callers must use Hub process configuration for startup and cannot request shutdown until common process stop semantics exist.
• Adds no Hub shutdown, NenjimProcess.stop(), replacement domain operation, dependency, or automated test.