# Task26 continuous lifecycle observer v6.4

## Append-only scope

V6.4 succeeds sealed v6.3 (`2833428cfab41826a5cb54f90bb51c56f40b2468850d02687f7341c791b7f803`). V6.3 remains immutable. V6.4 rebinds the unchanged lifecycle to deployed service-state bootstrap successor `4a6c7ee54cf9526a30de8bb576c1d71b411938beba33a04914738f6e1b6ed1cb`, core `3374be765c7e53fc431b0c6e48cacbacb09618f77f13ef87016cb0ad2575d060`, Hermes wheel `9d22e89a0b1a14d4eb7f1c2005fc01860bec5f3b4eda6e01bb1390542a90b875`, deployment receipt `fe65b634396aaae2818719d1b34fdaad148b2547290d3a66b3af7803bf93dfca`, candidate inventory `0119beeb46a15ab25a78550da4c432b4cc52e0dc816822d2688dc9009df89d90`, and unchanged profile wheel `f75856d6d986b64d3d2f083aec2f865c7aea19f5950b84ff06e519f2f6505af6`.

The canonical service-state proof is `/home/cube/.hermes/profiles/dualcoachtest/data/owner-actions/customer-service-state.json`, SHA-256 `81c1e581cb84aac6f44044747e0e8e77a2d7498c71d626f1f9b5ec2f9d09a261`, mode `0600`, schema `customer-service-state-v1`, with empty `states: {}` (unpaused). The deployment receipt binds service PID `576011`, connected Telegram, and the exact allowed customer route `(user_id=8527916639, chat_id=8527916639, topic_id=0)` for customer `task26_live_2e_r2_20260815_8527916639`.

Recovery seal `00d44de03e8dde668da8058091751291b13457c8bd086917dfe85e42b3813df8` binds polling offset lower bound `629525117`. Customer remains enabled, bootstrap generation 6 `ACTIVE`, adaptive activation/delivery false, and delivery count zero. Downstream check-in, owner review, explicit send, exactly one delivery, disable, and cleanup validation is unchanged.

## Fresh customer handoff

Arm before customer action. After arming, the customer must send one fresh exact `오늘 체크인`, then use the inline `오늘 체크인 시작`. The message handled at 2026-08-17 12:10 by the predecessor while fail-closed produced no state or card. V6.4 does not replay or accept that pre-arm message and never represents it as replayed.

## Timeout policy

Defaults remain stage `1800` and total `21600` seconds. Explicit stage and total caps remain `21600`; values above either cap fail closed. A six-hour customer wait fits within the existing six-hour global deadline.

## Exact built-in command

The ready and event paths below are fresh and absent. This command was not run:

```bash
/home/cube/projects/richard/hermes-agent/.venv/bin/python '/home/cube/projects/richard/traning coach/.omo/evidence/task26/task26-continuous-lifecycle-observer-v6.4-4a6c7ee5/observer_v64.py' observe --profile /home/cube/.hermes/profiles/dualcoachtest --ready '/home/cube/projects/richard/traning coach/.omo/evidence/task26/task26-continuous-lifecycle-observer-v6.4-4a6c7ee5/live-v64-ready.json' --events '/home/cube/projects/richard/traning coach/.omo/evidence/task26/task26-continuous-lifecycle-observer-v6.4-4a6c7ee5/live-v64-events.jsonl' --stage-timeout 21600 --total-timeout 21600
```

No observer/tmux startup, customer action, network action, service action, Git action, or live authority mutation is part of this evidence package.