# Decision needed on #49/#267 and #302 (doyle, 2026-09-14, for operator review via lia)

## What these requests are
- #49 and #267: "refresh freeze". When the daemon refreshes or updates itself, an attached terminal can freeze. Same bug reported twice.
- #302: "console hitch". A remote console session stutters for a moment now and then.

## What v0.70.0 (the #304 candidate) actually does about them
- #49/#267: adds two log events that will tell us WHERE the freeze happens. No fix. The observation run that uses those events has not been done.
- #302: adds a diagnostic switch (SPT_RC_HITCH_DIAG) that reports what the network pump is doing during a hitch. No fix. There are two candidate causes; a remedy is designed for one of them, but we cannot pick until the probe is run on YOUR box during a real hitch.

So the candidate ships instruments for these three, not repairs.

## Why you must decide now
The rules for a golden release run say the milestone must match what you greenlit. These three requests are in #304 but are not fulfilled by it. A request cannot be quietly dropped: it must be moved to another milestone or sent back to evaluation, with the reason written on the issue, BEFORE golden runs. Everything else in #304 is done and verified (both OS test legs green, hand-off ready). The only thing holding the release is this decision plus the #297 field check.

## Your options
A. RELOCATE (recommended). Move #49/#267 and #302 into a new "fast-follow" milestone. #304 ships now with the diagnostics inside it. The fast-follow milestone then does the observation run and the #302 probe on your box, chooses the remedy, builds it, and ships it next. Draft milestone body already written.
   Cost: one more release cycle for the real fixes.
   Benefit: the eight other fulfilled requests ship today, and the diagnostics have to be in your hands before the fixes can even be chosen, so shipping them IS the next step.

B. HOLD. Keep them in #304 and do not release until they are fixed. That means: observation run, probe on your box, pick remedy, build, test, new candidate, new golden. Realistically weeks, and all the finished work waits.

C. BACK TO EVAL. Least useful: we already know what the next steps are.

## What I need from you
One word: RELOCATE or HOLD. If RELOCATE, I create the fast-follow milestone through alchemy and record the move on #304 myself.

Separate, smaller question also pending: for #300 (remote console input fix, core part done), do you want its two-node field test AFTER publishing v0.70.0 (recommended, it needs two real machines) or BEFORE?