Skip to content

[beta.2.3] Reduce root deno task surface to meaningful repository capabilities #1331

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] Reduce root deno task surface to meaningful repository capabilities

Part of #1322. Release: beta.2.3.

Problem

Root deno.json exposes 114 tasks — every internal function is a first-class developer command.

Target

Conceptual top-level actions (not an exact required list): dev / build / check / test / test:e2e / test:browser / lint / fmt / pack / release / benchmark.

Moves

  • Package-owned implementation tasks move to their owners.
  • Scenario variants merge behind parameterized harnesses (e.g. fixture:* 9 tasks for 2 fixtures).
  • Delete aliases and retired operational tasks (v044:*).
  • Do not touch example-specific tasks for aesthetics; task count is not a hard KPI.

Release

beta.2.3.

Accepted upstream-contribution priority — 2026-09-08

Reduce task wrappers as runner/tool migrations qualify. Preserve Deno-specific public export/type coverage until an equivalent TS7 path is proven. Deno test is not self-built and need not be replaced for uniformity.

Use docs/architecture/infrastructure-reduction.md and VERSION_PLAN as scope. Prepare useful generic fixes for contribution through normal authorization; no invented bugs, cosmetic PR quota, or upstream-response release dependency. No migration is completed by this update.

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