Hiro development journal

Legacy Self-Improvement V2 labels and Telegram side effects traced after the continuous-loop cutover

2026.08.11 at 16:10:44 America/Los_Angeles Diagnosed; Telegram delivery disabled; structural cleanup identified Machine-readable JSON

Executive summary

A user report of continued Self-Improvement V2 updates exposed an incomplete architectural cutover rather than a second active promotion authority.

The continuous queue still imports the former Self-Improvement V2 runner as its discovery front end. Candidate construction and promotion use the new queue and governor, but the reused discovery module retains its old console branding and completion-briefing hook.

Telegram delivery is now disabled at the lifecycle marker, the Telegram bot process is stopped, and the notification outbox contains no pending entries.

Two obsolete Stage 6B Windows scheduled tasks also remain enabled. They are distinct from the Self-Improvement V2 discovery call but are stale automation that should be retired in a dedicated cleanup.

Work completed

Telegram shutdown verification

Completed

Removed the runtime notification-enabled marker through Hiro's checked-in lifecycle control.
Stopped the managed Telegram bot process and removed its PID record.
Verified the dynamic notification setting evaluates false while Hiro's local HTTP service remains healthy.
Inspected the sandbox notification outbox and found no pending messages to deliver later.

Self-Improvement V2 update diagnosis

Completed

Confirmed the continuous-loop adapter imports and executes the old Self-Improvement V2 runner in proposal-only mode whenever discovery is due.
Confirmed the old runner still emits Self-Improvement V2 banners, summaries, report names, and a completion briefing through the shared Telegram sender.
The shared sender now fails closed because the notification marker is absent, so future calls from this process cannot deliver Telegram messages.
The old runner is supplying discovery only; the new durable queue, canary, and stable governor remain responsible for candidate decisions and promotion.

Residual scheduler audit

Incomplete cleanup identified

The source scheduler still contains disabled legacy overnight Self-Improvement V2 functions and labels.
Windows Task Scheduler still reports two obsolete Stage 6B tasks as enabled and ready, while two Stage 6B-to-6C bridge tasks are disabled.
No scheduled task was changed during this diagnostic response because the user asked for an explanation rather than broader scheduler mutation.

Decisions and reasoning

Describe the cutover accurately: promotion was replaced, but discovery was reused and therefore the former system was not fully removed.
Keep Telegram disabled through the central runtime gate so every shared sender fails closed regardless of which legacy call site invokes it.
Treat extraction of discovery into a side-effect-free continuous-discovery component and retirement of obsolete scheduled tasks as the proper structural correction.

Validation and evidence

Check	Status	Result
Telegram lifecycle status	passed	Notifications reported disabled and the managed Telegram bot reported not running.
Notification outbox inspection	passed	No pending sandbox review notifications were present.
Hiro availability after Telegram shutdown	passed	The local Hiro HTTP endpoint returned status 200.
Discovery and briefing call-path inspection	passed	The continuous adapter, former discovery runner, briefing hook, and legacy scheduler labels were identified directly in source.

Current state

Hiro remains online.
Telegram notifications are disabled, the Telegram bot is stopped, and no pending outbox messages exist.
The continuous queue still uses the former Self-Improvement V2 module for discovery, which explains the obsolete update label.
The continuous queue and stable governor remain the active candidate and promotion path.
Two obsolete Stage 6B scheduled tasks remain enabled pending explicit structural cleanup.

Next steps

Create a side-effect-free continuous discovery module with current naming and no Telegram briefing behavior.
Point the continuous adapter at that module and remove the former discovery runner from automatic scheduling.
Disable and archive the remaining obsolete Stage 6B scheduled tasks after confirming their exact definitions.
Add regressions proving continuous discovery cannot send Telegram messages and that only the continuous queue is scheduled.