Skip to content

chore(strip): drop this repository's process machinery in every strip variant - #258

Merged
koniz-dev merged 1 commit into
mainfrom
chore/strip-process-artifacts
Sep 26, 2026
Merged

koniz-dev merged 1 commit into
mainfrom
chore/strip-process-artifacts

Conversation

@koniz-dev

@koniz-dev koniz-dev commented Sep 26, 2026 •

Copy link
Copy Markdown
Owner

Why

A measurement of what this template actually ships: lib/ is 1.0 MB, docs/verification/ alone is 31 MB. 97% of the documentation an adopter inherits is evidence about issues closed in this repository. Two of the guards they inherit do not merely take up space, they fail outright in a fork.

Two changes, both requested directly by the repository owner.

There is no issue for this work. The owner asked for it directly and asked that no issue be filed just to have something to reference, so the commit carries no Refs koniz-dev/flutter-starter#N. Consequence, stated plainly: the Issue refs check on this PR is red for exactly that reason, and for no other — check_issue_refs.sh has no exemption path. There is no auto-closing keyword anywhere in the commit or this body; the failure is the missing Refs line only. See "Open question" at the bottom.

Change 1 - the strip drops process-only artifacts

The test applied to every candidate is the owner's: would an adopter notice if this were missing?

Stripped, with reasoning per item

Item Reasoning
docs/verification/ 31 MB of acceptance evidence about issues closed here. An adopter inherits an archive of work they never saw. scripts/test/run_acceptance.sh survives and recreates the directory for their issues. Strip.
tool/check_epic_coverage.dart + test/tooling/epic_coverage_test.dart Asserts every tracked directory maps to exactly one epic:* label. An a

Refs #259

@koniz-dev
koniz-dev force-pushed the chore/strip-process-artifacts branch from 42679ec to 1b09b3c Compare September 26, 2026 15:28
… variant

The template shipped 31 MB of docs/verification against 1 MB of lib/, plus
guards that enforce this repository's own issue workflow. A fork inherits
neither epics nor these issue numbers, so issue-refs.yml would reject every
pull request the adopter opens and check_epic_coverage would fail their first
flutter test.

Strip now drops those in all three variants, marks process-only sections in
place rather than in a second list that can rot, and strip-smoke.yml asserts
the removals happened - analyze and test stay green if the strip silently
stops. CLAUDE.md gains the scope test that produced this change.

Nothing is deleted from this repository; only the stripper learns to drop it.

Refs #259
@koniz-dev
koniz-dev force-pushed the chore/strip-process-artifacts branch from 1b09b3c to 7ac259e Compare September 26, 2026 15:33
@koniz-dev
koniz-dev merged commit 8b80f2d into main Sep 26, 2026
6 checks passed
@koniz-dev
koniz-dev deleted the chore/strip-process-artifacts branch September 26, 2026 15:37
koniz-dev added a commit that referenced this pull request Sep 26, 2026
…ss-only artifacts (#260)

Verification phase for 8b80f2d (PR #258), which was merged without evidence, so
gate G4 did not hold and the issue stayed open.

All eight criteria were driven here; nothing routed to needs-uat. The three
strip variants were run against pristine exports of 8b80f2d and each stripped
tree passes pub get, analyze, test and check_docs with zero broken links.

Two counterfactuals back the claims that an assertion alone cannot:
strip-smoke.yml's assertion step, extracted verbatim, exits 1 on an unstripped
tree while audit_template.sh exits 0 on that same tree; and an unbalanced
process-only marker aborts the strip with exit 2 before any deletion, with
before/after sentinels showing all 1003 docs/verification files intact.

Refs #259

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant