Skip to content

intent: Count runs from disabled selected workflows - #401

Merged
yihanzhu merged 2 commits into
mainfrom
ystack/intent/disabled-workflow-run-counting
Sep 22, 2026
Merged

yihanzhu merged 2 commits into
mainfrom
ystack/intent/disabled-workflow-run-counting

Conversation

@yihanzhu

Copy link
Copy Markdown
Owner

The quota preflight currently omits runs when a selected workflow becomes disabled. This intent defines the remaining repair: include those runs in the existing count while preserving selection, thresholds, exclusions and error handling.

Tracks #132.

Current intake acceptance: #132 (comment)

review_size: standard

Only work/disabled-workflow-run-counting/intent.md changes. The original 60-line draft and its branch are preserved; a normal merge refreshes its base. No implementation, workflow, installation or activation is included.

Validation: exact intent blob and merge parents verified, clean checkout and whitespace check. Required quick CI and fresh independent G1 review are pending; this is not implementation acceptance.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

Deploying ystack with  Cloudflare Pages  Cloudflare Pages

Latest commit: 34dfb97
Status: ✅  Deploy successful!
Preview URL: https://4ebc2375.fabrica-6yx.pages.dev
Branch Preview URL: https://ystack-intent-disabled-workf.fabrica-6yx.pages.dev

View logs

@yihanzhu

Copy link
Copy Markdown
Owner Author

Independent G1 review — PR #401

Reviewer: /root/package_rebinding_intent_author, independent of the original #132 intent author. Requested model/effort: gpt-6-astra / high; actual runtime identity is not independently exposed.

Repository: yihanzhu/ystack
PR: #401
Stage: G1 intent only
Branch: ystack/intent/disabled-workflow-run-counting

Reviewed-head: 34dfb97
Reviewed-base: 1756573
Intent-blob: d9bd79f672384b5b97d43ab96e9165038fb5d3c3
Intake-title-sha256: 8d8797714fd0b602d816d0e6fb9ad3499faa3b10e797104f4486dfbec12629d5
Intake-body-sha256: 628e11bfe6ede8a92d47bef7a7953cbe7b67610d90dfa87c235a23b057012809

Evidence and review boundary.

I read the complete 60-line intent, complete PR diff and description, applicable G1 stage criteria, current working/review rules and program authorization. I checked the intent against the current quota helper, its complete existing hermetic test, and the already implemented run-attempt identity behavior.

Before and after substantive review, independently fetched API values showed the same head, base, PR title/body and intake hashes above. Hashes cover the issue’s exact non-null UTF-8 title/body without normalization or added newline. PR #401 remained open with no labels, so merge-ready was absent. Issue #132 remained open with only roadmap-step-4.

Current acceptance is comment 5772185718, independently read from the API and verified as authored by yihanzhu. It binds the current intake, scope and same-attempt recovery under the named manager’s directly supplied September 21 handback. I did not substitute the historical September 14 comment for current authority.

Bugs pass — no Important findings.

The intent identifies the remaining source defect accurately. The helper queries selected workflows without --all; installed GitHub CLI help confirms that disabled workflows are excluded without that flag. The artifact correctly describes this as a source-level counting gap, not an observed account overrun.

The intended behavior is precise: eligible runs from a disabled selected workflow contribute to the existing window and combined threshold decision. Selection, threshold comparison, exclusions, fetch-limit scaling, missing-workflow treatment, error handling and configuration precedence remain unchanged.

The proposed behavioral proof is appropriate for G1. It requires a hermetic regression showing that previously omitted runs affect the actual count and threshold result, rather than merely matching a command string. Fixture details and boundary-case selection remain explicit design questions for G2.

The original run-attempt identity requirement is already implemented and is correctly retained as a constraint. No duplicate repair or workflow change is proposed.

Security pass — no Important findings.

The prospective concern stays within the existing quota helper and its existing test. Global listing failures, unexpected per-workflow failures and invalid numeric counts remain failures; errors cannot silently become zero usage.

The intent excludes workflow changes, probe publication, permissions, executable selection, quota-policy changes, credentials, provider operations, installation, activation and target execution. It grants no new operational authority. Hermetic behavioral evidence does not require enabling, disabling or invoking a real workflow.

Compliance pass — no Important findings.

Only work/disabled-workflow-run-counting/intent.md differs from the reviewed base: 60 added lines, mode 100644. No implementation, accepted upstream artifact, constitution path or unrelated file changes.

The artifact follows the G1 template, states the problem and bounded outcome in plain language, identifies affected systems, preserves safety constraints and leaves implementation details to design. It tracks #132 without closing it. It contains no review-round history or premature implementation-success claim.

The PR description records one review_size: standard token and accurately describes the preserved draft and base refresh. The concern fits the currently accepted independent Roadmap work; this PR does not resume any expressly parked issue or depend on the blocked step-7 attempts.

G2 must still accept the design and explicit risk classification. The applicable independent plan gate, implementation proof and required reviews remain necessary before code or completion.

Preserved history verified.

The reviewed head is a normal two-parent merge:

  1. Preserved intent head: 58ab0fb850a383ed56255a63171b3b4c99a308ed
  2. Reviewed current base: 17565733df166fcf939bfee5d7dd50d2f986c395

The original intent commit has parent fefa82e10a163c6570b8eb8581e7fbab776ed7f6 and changes only the intent path. The merge preserves its exact intent blob. The restored worktree was clean, and the diff whitespace check passed. No replacement attempt or rewritten history appears.

Source blobs used for comparison:

  • Quota helper: 806f23e6612c2db01b2dd61701c8f20d146425f8
  • Existing test: 114bee10c47d66807d3133f53654f7476196c33d
  • Plumbing workflow: ca9be78eea08ad36f89a2cd0d5da3461a258a6ca
  • Probe helper: a286dd19f5f675255b031ae8a61e11c58bef6476
  • Program decision: 712fc135b1b2f845776466e54e1b938c4c9be101

CI and conclusion.

The API reports quick-CI run 35695455155 completed successfully at the reviewed head. This reports the observed automatic run, not full-suite or implementation proof. The manager must still verify required checks and unchanged identities immediately before any protected merge.

No Important findings or nits. Accept this exact intent at G1. This is not G2, plan, implementation or merge authorization.

This reviewer made no file, ref, worktree, comment, label or other state changes and executed no tests or targets.

Review-verdict: ACCEPT

@yihanzhu
yihanzhu merged commit ca7daca into main Sep 22, 2026
4 checks passed
@yihanzhu
yihanzhu deleted the ystack/intent/disabled-workflow-run-counting branch September 22, 2026 06:42
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