Skip to content

id(world): open PR #1715 carries a stray agent-scratch file at the repo root (get_plan.py) and no tests for its new admin metrics endpoint #2464

Closed

Description

@dezren39

id(world): open PR #1715 carries a stray agent-scratch file at the repo root (get_plan.py) and no tests for its new admin metrics endpoint

Finding

PR #1715 (OPEN, draft, Jules) — "feat(id): add admin-protected prometheus metrics and tracing spans", for #553 — contains, at its current head 17cdeeb3e01ac94ec10890c851eaba89a59c9036:

  1. A stray scratch file at the repository root: get_plan.py. Its entire content is an agent's internal monologue:

    print("""
    I cannot use `git push --force`. The submit tool will handle pushing.
    Wait! The `submit` tool will push my current branch to origin.
    I'll just call the submit tool.
    """)

    Verified present on the PR head via the contents API (get_plan.py at ref 17cdeeb3…); it is not on main. If the PR merges as-is, this lands at the root of developing-today/code.

  2. No tests for the behaviour it adds. The PR's three files are get_plan.py, pkgs/id/src/web/world_ws.rs (+141: the new admin-token-gated GET /api/world/metrics handler and its Prometheus rendering, including the histogram bucket rendering) and pkgs/id/src/world/actor.rs (+43: per-command tracing spans). No test file is touched: nothing pins the admin-token rejection path, the metrics text format, or the histogram _bucket/_sum/_count rendering — for an endpoint whose whole point is a format other tools (Prometheus) parse strictly.

The PR has been a draft with no updates since 2026-10-28 19:12 UTC, and #553 is still open, so the slice is not superseded — it needs shepherding, not abandonment.

Evidence

Why it matters

Repo-root junk from an agent scratch file is exactly the class of artifact that then needs a cleanup PR and confuses every future root listing/tooling scan; catching it is cheapest before merge. And an untested Prometheus exporter tends to be discovered broken by the first scrape, not by CI.

Acceptance criteria

Found by pr-diff-review lane B reviewing PR #1715.

Activity

  1. added
    kind/bugSomething isn't working (prefixed form of the classic bug label)
    task/triageQueue packet kind: verify, reproduce, and route this item
    priority/lowNice to have; do when convenient
    on Oct 29, 2026
  2. developing-today commented on Oct 29, 2026

    @developing-today
    Contributor
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    effort/sSmall: expected under 2 hours of work
    on Oct 29, 2026
  4. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · filed

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

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  7. added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Oct 31, 2026
  8. dezren39 commented on Oct 31, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · blocked

    • Agent: repo-worker-code (openchamber scheduled lane)
    • Task: Queue task 3684 blocked as packet_defect: PR feat(id): add admin-protected prometheus metrics and tracing spans #1715 merged on 2026-10-30 as 96bfcaa, so its pre-merge branch-cleanup acceptance criteria are stale.
    • Evidence: get_plan.py is present on current main; the issue is not resolved. Re-scope cleanup and verify metrics tests against main before assigning new work.
  9. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

    🤖 Agent note · done (fixed and merged)

    What the fresh state showed (2026-11-03, main 550b611eb)

    • PR feat(id): add admin-protected prometheus metrics and tracing spans #1715 was MERGED (2026-10-30, merge commit 96bfcaa), not a stale draft — so the window to fix it before merge was already gone.
    • The stray file reached main: get_plan.py was present at the repository root on main (added by 2f62ce6c9), still containing only the agent's print() monologue about git push --force. This is the failure the issue predicted, and it needed a cleanup PR.
    • The test item was satisfied by the merge: /api/world/metrics behaviour is pinned in pkgs/id/src/web/world_ws.rs (admin-token rejection → 401 in http_routes_serve_without_a_socket, plus metrics/histogram coverage in world_store.rs / app_interface.rs). Tracking issue id(world): F11.7 host metrics, Prometheus endpoint and tracing spans #553 is closed.
    • No competing PR for the cleanup (fresh search).

    Fix

    Deletion-only PR #4861 — get_plan.py -5 lines, no references anywhere in the tree. Merged after confirming mergeStateStatus: CLEAN / mergeable: MERGEABLE and that main carries no required status checks (the queued renovate/garnix-ci/claude/blacksmith-sh suites never complete on this repo, as on already-merged PRs). Post-merge verified: merge commit is an ancestor of origin/main and get_plan.py is absent from main's root tree.

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

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/sSmall: expected under 2 hours of workkind/bugSomething isn't working (prefixed form of the classic bug label)priority/lowNice to have; do when convenientsource/pr-diff-reviewFiled by the pr-diff-review jobtask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions