Skip to content

[beta.2.3] Audit repository file lifecycle and remove redundancy islands #1328

Description

@SisyphusZheng

ADR-0152 / #1341 scheduling amendment: execute cleanup alongside every Beta.2.1/Beta.2.2 replacement; Beta.2.3 is the residual closure checkpoint, not the start of cleanup. Remove displaced owners and their callers/checkers/docs together with regression evidence.

[beta.2.3] Audit repository file lifecycle and remove redundancy islands

Part of #1322. Release: beta.2.3. Excludes examples/**.

Method

Classify suspicious files KEEP / MERGE / DELETE / HISTORICAL. For each: What does it own? Is it canonical? Who consumes it? Is the consumer independently legitimate? What is its lifecycle? Why can it not be merged? What retires it?

Audit surface: root; .agents; .github; packages; package fixtures; tools; docs; www; root evidence; benchmarks (where active governance inputs); release machinery; generated artifacts.

Known inputs from the 2026-09-05 redundancy audit

  • www/e2e visual baselines: 272 PNG / ~30.5MB — evaluate lossy format or viewport-matrix convergence (adjudicate together with the carried visual-drift risk; do not silently normalize).
  • v0.44 stage tooling (~3.4k LOC) — sunset per constitution rule 4.
  • zod + valibot double dependency — nearly suspended; consolidate to one.
  • docs/release historical evidence — safe to prune from HEAD only after verifying release:evidence:check reads tag trees and the CURRENT version chain stays intact.

The census lives in an issue comment / PR description / generated CI artifact. Do not commit a permanent file registry.

Release

beta.2.3.

Activity

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

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions