Skip to content

Before listing: the review-bot footer still publishes the box, the routing, the spend and the plan type #390

Open

Description

@dinndev2

What to build

The review bot's footer still publishes internal state on every review it posts, and the platform's
2026-11-10 sanitisation did not reach it.

The narration footer and the pull-request body footer were cleaned — they no longer print the box,
the cost, the run URL or the funding mode. The review footer was left as it was, and it now
carries more than it used to: the machine the review ran on, the provider and model that served it,
the token counts, the account's plan type, a dollar figure, and an internal review identifier.

A review posted on 2026-11-10 still reads, in one line: the box it ran on, which provider and model
served it, how many tokens it used, that the account is on a flat-rate plan, what that cost, and
its review id.

Across this repository: 38 reviews carry the box and the routing, 11 posts carry a dollar figure,
and the newest ones carry the plan type and the review id. Twelve distinct machine names appear,
three of which embed a team member's name or handle.

Acceptance criteria

  • The review footer prints the brand line and nothing else — no box, no provider or model, no
    token counts, no cost, no plan type, no internal identifier.
  • The same holds for the narration footer and the pull-request body footer, so a new footer
    cannot reintroduce them.
  • The old posts are dealt with by the same decision as the other repositories in this audit.

Notes

  • The fix point is the footer template, not the 38 posts.
  • This is not a historical problem: the newest review in this repository still carries all of
    it, which is why it is filed against the template rather than against the posts.
  • The same footer class was filed against the other public repositories in this audit; one template
    change covers all of them.

Activity

  1. added this to the Public hygiene milestone on Nov 11, 2026
  2. developerz-ai commented on Nov 13, 2026

    @developerz-ai
    Contributor

    Triage stopped on this request: triage could not settle it on its own.

    The platform will not retry it on its own. Adding the missing detail here, or narrowing the request, lets it be judged again; reopening a closed issue does the same.

  3. dinndev2 commented on Nov 14, 2026

    @dinndev2
    ContributorAuthor

    Status, 2026-11-14, measured on the newest reviews (#417 to #421):

    • Review footer: the visible footer is now the brand line and a "What is this?" link only. No box, provider, model, token counts, cost or plan type. One internal identifier remains, in a hidden marker comment at the end of each review. Removing it is a platform change, in progress.
    • Narration and pull-request body footers: they still carry the internal task identifier in hidden markers, tracked in Before listing: the platform's internal task identifier is still published on every new post #395. Same platform change.
    • Old posts: part of the same decision as the other repositories, with the maintainers.
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions