Skip to content

docs(upstream): re-audit the six drifted upstream pages by agent, owner only for design changes - part 2 of 2 #16488

Closed

Description

@melodic-automation-lanes

Part 2 of 2 of #16486, split at intake (owner Q93). The done-when below is copied from #16486 as written.

Done when

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 16, 2026
  2. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    Size: Large
    Complexity: Medium
    Uncertainty: Known
    Flags: none
    Blocked by: none

    Decision recorded. #16502 did one of the six re-audits (t3dotgg/tstack, #16405, pin moved to 11e37a7). This issue is not done: the other drift issues among #16403-#16408 still need their own PRs, one per upstream, each moving its pin and recording take, adapt or reject for every changed row, under the owner's Q190 (a) decision (D346). Only a take or adapt that changes a skill's design goes to the owner. Send it back through intake for the next one.

    #16488 (comment)

    That decision settles the open questions, so I'm asking nothing new. What's left is the remaining upstream re-audits among #16403-#16408, other than #16405, which #16502 already did. Each gets its own PR that moves the pin and records take, adapt or reject for every changed row. Any take or adapt that changes a skill's design is listed in the PR body and raised to the owner, not applied. This is docs-only work. The earlier run was refused for patch size, so one PR per upstream is the sensible unit. I found no other open issue or merged PR that covers this beyond #16502.

    Automated triage. A maintainer reviews it.

  3. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 16, 2026
  4. melodic-automation-lanes commented on Nov 16, 2026

    @melodic-automation-lanes
    ContributorAuthor

    Not admitted to the issue lane: its last run's patch was over the scan job's size cap (scan-refused-patch), and a size-split sub-issue never splits again (owner Q93), so a builder session takes it. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  5. melodic-automation-lanes commented on Nov 16, 2026

    @melodic-automation-lanes
    ContributorAuthor

    {"v":1,"actor_id":337595936,"title_sha256":"2e2d8345a662edf06b03ce2b40776a62da1ae6fbf88f3e2e742ef3b781b5a44e","body_sha256":"de1e2209d0a16afe0f38ca636c652b56076afe7c2f2c279fa2335ff65f319ace"}

  6. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor
    No description provided.
  7. melodic-automation-lanes commented on Nov 16, 2026

    @melodic-automation-lanes
    ContributorAuthor

    Pull request #16502 merged with Refs:, so this issue stays open and nothing starts the lane on it again. work-unblock removed status: ready and agent-ready, so the hourly triage sweep sends it back to intake triage. Admission then parks it at status: confirmed for a check of what that pull request left, until a **Decision recorded.** comment says what is left or someone closes it.

  8. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    The triage sweep dispatched intake triage for this issue (dispatch 1; 2 runs that reach intake, or 6 dispatches, hand it to a maintainer).

  9. 2 remaining items

  10. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    Member

    Decision recorded. #16502 did one of the six re-audits (t3dotgg/tstack, #16405, pin moved to 11e37a7). This issue is not done: the other drift issues among #16403-#16408 still need their own PRs, one per upstream, each moving its pin and recording take, adapt or reject for every changed row, under the owner's Q190 (a) decision (D346). Only a take or adapt that changes a skill's design goes to the owner. Send it back through intake for the next one.

  11. melodic-automation-lanes commented on Nov 16, 2026

    @melodic-automation-lanes
    ContributorAuthor

    {"v":1,"actor_id":337595936,"title_sha256":"2e2d8345a662edf06b03ce2b40776a62da1ae6fbf88f3e2e742ef3b781b5a44e","body_sha256":"de1e2209d0a16afe0f38ca636c652b56076afe7c2f2c279fa2335ff65f319ace"}

  12. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor
    No description provided.
  13. melodic-automation-lanes commented on Nov 16, 2026

    @melodic-automation-lanes
    ContributorAuthor

    The work-resolve-issue lane stopped on this issue (scan-refused-patch): the scan job refused the run's patch for its size, and the run job's scan of it found no credential shape or binary hunk: the work is too large for one patch, so admission parks it for intake's split (owner Q93) at whatever Size it was triaged (admit.mjs patchCapStopped), and the split files its sub-issues, as for split-required; a size-split sub-issue never splits again, so admission parks it at status: confirmed for a builder session.
    It set Work status to needs-triage, so the hourly triage sweep sends it back through intake triage, and it waits on no decision from a person.

    In the run's words:

    The scan job refused the run's output, so nothing was published: too-large: the patch was over its 262144-byte cap. The run's log names its size.

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/43813659307

  14. added
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 16, 2026
  15. kyle-sexton commented on Nov 16, 2026

    @kyle-sexton
    Member

    Part 2 is delivered: #16403, #16404, #16406, #16407 and #16408 are closed by merged pull requests #16526, #16525, #16527, #16529 and #16530, each moving its pin with a disposition per changed row. No take or adapt changed a skill's design. The full record is on #16486.

  16. removed
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 16, 2026
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

    Fields

    Work status

    confirmed

    Priority

    low

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions