Skip to content

(standardize-repo): Report Renovate health and apply the release's toolchain floors per repo #1689

Open

Description

@evanharmon1

Problem

Dependency updates stay out of a standardize run for scope: a dependency bump inside a template-application PR makes the review scope impossible to state. Two things belong in the run because the template dictates them. First, the toolchain floors a release requires (pnpm major, Node, copier, task, the devcontainer tool pins) are part of the template update and land in the same PR, and nothing else dependency-shaped does. Second, a Renovate-health row in the reconcile report: the Dependency Dashboard issue exists (its absence means Renovate is inert; sommerlawn-zoho had none on 2026-10-26) and the rendered renovate.json matches the template render (harmon-devkit#1677). Everything else about dependency maintenance changes under harmon-init#1345, separately from this run.

Surface

ai/skills/repo/standardize-repo/assets/ (guarded update asset, report renderer), the classified item list shared with harmon-init.

Acceptance criteria

  • [CI] The guarded update's discover step lists the toolchain floors the target release raises for the repo, apply includes them in the update PR, and the PR body's review scope names them.
  • [CI] The reconcile report has a Renovate-health row per repo: dashboard issue present or absent, renovate.json matches the template render or drifts, and the class (human-only when the dashboard is absent, agent-apply when only the render drifts).
  • [CI] A test proves that an open Renovate PR or an outdated lockfile entry never changes the update PR's diff.

Verify

Re-read the ADR and spec named under Provenance for the current design, and re-establish every path, task name or observation above with git grep in the target checkout (and gh for GitHub state) before acting; a renamed path means the claim needs re-checking, not that the problem is gone.

Out of scope

Merging Renovate PRs, fleet-wide dependency runs, and the Renovate preset or grouping work under harmon-init#1345.

Provenance

Filed from the 2026-10-26 standardize-repo redesign session (harmon-devkit, worktree/clear-river-0602). Design record: harmon-devkit ADR docs/decisions/2026-10-26-fleet-standardization-runs.md and spec specs/standardize-repo-fleet.md.

Activity

  1. added
    featureNew feature or request
    ai-generatedCreated or authored by an AI agent
    layer:integrationExternal boundary: webhooks, API clients, credentials
    tier:economyModel tier: cheapest qualified hosted model first; escalation allowed
    domain:standardizationKeeping repos current with conventions: standardize-repo, drift audits, adoption
    area:standardize-repoThe standardize-repo skill and its standards catalog
    impact:mediumImpact: clear benefit to a meaningful share of users or goals
    risk:lowRisk: a mistake is contained, caught quickly, and cheap to undo
    complexity:sComplexity: small and local; a clear approach across a few files
    on Oct 27, 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

    ai-generatedCreated or authored by an AI agentarea:standardize-repoThe standardize-repo skill and its standards catalogcomplexity:sComplexity: small and local; a clear approach across a few filesdomain:standardizationKeeping repos current with conventions: standardize-repo, drift audits, adoptionfeatureNew feature or requestimpact:mediumImpact: clear benefit to a meaningful share of users or goalslayer:integrationExternal boundary: webhooks, API clients, credentialspriority-ai:p2Priority (AI): worth doing, not blockingrisk:lowRisk: a mistake is contained, caught quickly, and cheap to undotier:economyModel tier: cheapest qualified hosted model first; escalation allowed

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions