Skip to content

fleet-schedule-registry: reconcile stale systemd timer inventory #5661

Closed

Description

@dezren39

Evidence (2026-11-04)

Found during the current-roster recheck for #2131. On main 8de9292, doc/fleet-schedule-registry.md labels the laptop systemd section as 37 timers, but its table has 39 rows. A fresh comparison found 38 loaded timers from systemctl --user list-timers --all; all live timers have rows, with one registry-only row: oc-sumauto.timer. systemctl --user show oc-sumauto.timer reports LoadState=not-found and no fragment path, so it is stale rather than merely disabled.

There is a separate installed but disabled opencode-quota-freshness-summary.timer (LoadState=loaded, UnitFileState=disabled, ActiveState=inactive), not listed in the current registry or live timer list.

Request

Reconcile the Surface 2b inventory against the laptop source of truth: remove or explain the stale oc-sumauto.timer row, correct the section count, and decide/document whether installed disabled timers belong in the registry (including the quota freshness timer). Preserve full timer calendar specs for active entries.

Acceptance criteria

  • doc/fleet-schedule-registry.md Surface 2b inventory matches the laptop source of truth: the stale oc-sumauto.timer row is removed or explained, and the section count matches the table.
  • The registry's policy for installed-but-disabled timers is decided and documented, and opencode-quota-freshness-summary.timer is listed or excluded per that policy.
  • Active entries keep their full timer calendar specs.

Activity

  1. added
    kind/docsDocumentation improvement or addition
    task/triageQueue packet kind: verify, reproduce, and route this item
    priority/normalOrdinary priority (the default)
    on Nov 4, 2026
  2. developing-today commented on Nov 4, 2026

    @developing-today
    Contributor
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 4, 2026
  4. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: queued
    queue: repo-health-code-pilot
    task: 9751 (small_fix, priority 20)
    by: repo-worker-code, OpenChamber scheduled lane 1a180ae5-384f-4e71-8d77-08f7b1652c75
    at: 2026-11-04T22:13:44Z

    Enqueued the Surface 2b inventory correction as task 9751. Evidence: 39 registry rows/37 header versus 38 loaded timers; is not found. Resume from the packet and recheck live timer states.

  5. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    Correction to the queued note: the registry-only unit is oc-sumauto.timer. A fresh systemctl show reports LoadState=not-found; it is not merely a disabled timer.

  6. added
    effort/sSmall: expected under 2 hours of work
    source/humanFiled directly by a human
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Nov 4, 2026
  7. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    Intake review

    • Related: found during the current-roster recheck for issue Fleet roles: Make / Do / Tend — Tend owns the micro (keep everything moving) and the macro (alignment with projects, roadmaps, priorities) #2131; registry doc/fleet-schedule-registry.md on main 8de9292.
    • Notes: Counts in the evidence disagree three ways (37 claimed, 39 rows, 38 loaded timers) — the reconciliation is the work, and the disabled-timer policy is a small documentation decision that should be recorded in the registry itself.
    • Risks: Minimal; docs-only. Do not treat registry rows as authority over the laptop — the laptop's systemctl --user output is the source of truth this doc mirrors.
    • Suggested approach: One pass over the registry against a fresh timer listing: drop/explain the stale row, fix the count, add the policy line.

    Intake by fleet monitor (repo-fleet-monitor), 2026-11-04 run.

  8. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  9. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    event: picked_up
    task: 9751
    worker: repo-worker-code (lane code-f)
    stage: claimed
    summary: Worker lane code-f claimed task 9751 to reconcile Surface 2b of doc/fleet-schedule-registry.md against the live laptop user-timer inventory (remove/explain stale oc-sumauto.timer row, correct count, document disabled-timer policy). Revalidating against fresh GitHub state first; no competing PR for #5661 found.

  10. added a commit that references this issue on Nov 5, 2026
  11. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    event: done
    task: 9751
    worker: repo-worker-code (lane code-f)
    stage: bookkeeping_complete
    summary: Fixed and merged via PR #5714 (merge commit 9ddb919). Surface 2b of doc/fleet-schedule-registry.md reconciled against a fresh live laptop read: stale oc-sumauto.timer row removed (LoadState=not-found), installed-but-disabled opencode-quota-freshness-summary.timer added and marked (disabled) with the inclusion policy documented in the section intro, heading count corrected 37 -> 39 rows (38 enabled + 1 disabled). Table timer-name set diffed against live systemctl --user list-unit-files --type=timer — exact match. Codex review on PR #5714 completed with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort/sSmall: expected under 2 hours of workkind/docsDocumentation improvement or additionmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)source/humanFiled directly by a humanstatus:done

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions