Skip to content

Retire the singleton lint export and finish catalogue ownership #731

Open

Description

@devantler

🤖 Generated by the Agentic Engineer

Objective

Finish the workflow-ownership cleanup by retiring the whole-repository lint export once its last production consumer owns that job locally. Keep the shared Go pipeline's actual scanners, signed-fix isolation and regression coverage intact, and make the catalogue accurately describe its remaining interfaces.

Details

The complete workflow census identifies World at Ruin as the only production caller of lint.yaml. Internal smoke fixtures are coverage, not independent product reuse. World at Ruin PR #1494 moves its read-only lint job into the product. Deleting the export before that PR is delivered would break the live caller.

Checklist

  • Refresh the full caller census and verify the World migration is merged before removing the export.
  • Remove the retired export and unreachable export-only fixture/signing machinery, without dropping the real Go scanner or credential-boundary controls.
  • Preserve native clean/finding/malformed/root-configuration controls against the remaining production MegaLinter source and its read-only projection.
  • Keep complete CI selector, reducer, credential, source-pin and documentation parity checks fail-closed.
  • Present actions and genuinely reusable workflows consistently, with separate required-source and internal-fixture indexes and correctly bounded collapsibles.
  • Independently review, protected-merge, publish the breaking interface retirement, verify the normal signed publication/reconciliation, and repeat the portfolio ownership audit.

Dependencies

World at Ruin PR devantler-tech/world-at-ruin#1494 must merge before this retirement merges. The remaining World trusted-admission cutover stays separately tracked by #693. Part of #164 and #287.

Notes

Priority: High — finishes already-started cleanup. Effort: Medium. Existing immutable release pins remain historical compatibility, not active exports. No paid service, new GitHub identity or live ruleset bypass is needed.

Activity

  1. added theissue type on Oct 23, 2026
  2. coderabbitai commented on Oct 23, 2026

    @coderabbitai
    🔗 Related PRs

    #724 - docs: clarify catalogue ownership and references [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Oct 23, 2026
  4. moved this from 🏃🏻‍♂️ In Progress to 🫴 Ready in 🌊 Project Boardon Oct 23, 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

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions