#1113 — Exact original-task activity lease candidate

Base main3571e3a0d6dd157e6d0f80a9f016e8f03b7afb7b. Scope: Hub nullable last_activity_at and activity_only mode on the existing mark_tasks_consumed protocol; authenticated immutable node/network and existing task/thread/turn, no status/context/consumption overwrite. Genuine Codex owned-turn events feed a throttled reporter (30seconds, one in flight, zero activity-call retries). Scheduler uses valid last activity then existing consumed/start/create fallback and retains the creation-based total cap.

The first isolated cached Docker run passed113 cases but failed14 new fixtures: the old identity suite intentionally clears the shared victim session node ID, and a new test attempted to insert a duplicate session despite the network/alias unique constraint. New activity fixtures are independent and model the conflicting session by its actual unique-row update; no production guard or assertion was weakened. The cached image disappeared before the corrected rerun (reason unknown); that attempted Docker command executed no tests. Fresh exact-tree CI is required before merge or publication. Local first-run logs and the no-image evidence are retained in the private iteration artifacts.

Dedicated tests cover real authenticated HTTP from the production runtime reporter payload, wrong node/network/context, null legacy node, unconsumed/terminal/revoked authority, no partial batch writes and injected second-write rollback on both databases. Clock cases cover long active execution, idle expiry and absolute cap. Runtime integration verifies wrong-task/old-turn events cannot renew. Assertion witnesses remove context/owner/terminal/idle/cap protections and suppress the reporter; only assertion-red outcomes count.

The prior reporter-context-forwarding mutation anchor is updated to the new pending-promise expression with the same meaning. Documentation symbol links move with the existing tools definitions; no skip baseline is widened. No product/runtime/source publication or live canary completion is claimed at this candidate stage. CLI/Node exact-pair and all three exact-main release gates must pass.

First CI identified three new PostgreSQL fixture calls using a scalar instead of the adapter array parameter, corrected in the fixtures; the other69 HTTP cases passed on that backend, including ownership/context/terminal and atomic failure rollback. The optional protocol flag exceeded the existing all-tools byte ceiling by23bytes; shorten only the protocol description, retaining the85500 ceiling and assertions. Failure evidence is preserved; fresh final-head CI remains required.

Final sourceCI:38345127850 SQLite130/PG121/runtime+pair52 and11 assertion witnesses PASS; caller/sender/pair and ten required PASS. Sourcemain47816a61095f196cf726f194f482739bc09f6a82. Verified Hub/Node public evidence, the later documentation-main CLI registry timeout, selectedHub activation and unresolved client canary are recorded in report-test1113-hub135-activation.txt. The local image rebuild was bounded at50seconds and stopped before the node-dependency install completed; it yielded no corrected local functional result. Fresh CI is the functional authority.
