Skip to content

Let a recipes-only PR name writers:<provider> #277

Closed

Description

@ericlitman

Current scope

Unfret on PR #276's merged head (v1:56f146a8…, verdict-changing): the shared-recipe expansion in .claude/skills/verify-open-pstack/scripts/core.ts adds the aggregate writers feature for a features/recipes.ts change, but not the per-provider writers:<provider> features, so verify.sh refuses --feature claude:writers:amp on a PR that changes only recipes. Such a PR must then run every writer case, against Eric's 2026-11-06 instruction to live-gate only what changed.

Acceptance: a recipes-only change reaches every writers:<provider> feature as well; the existing reach table test gains the case, failing before and passing after. Live gate: one writers:<provider> case plus the mandatory --self-test.

Introduced by: #276

Activity

  1. ericlitman commented on Nov 6, 2026

    @ericlitman
    OwnerAuthor

    PR: #278

  2. added a commit that references this issue on Nov 6, 2026
  3. ericlitman commented on Nov 6, 2026

    @ericlitman
    OwnerAuthor

    Batch 262 closeout for this issue (full record: https://github.com/mobilyze-llc/docs/blob/main/projects/open-pstack/records/2026-11-06-batch-262/closeout.md):

    #277: let a recipes-only PR name writers:

    Fix-forward for #276 (Unfret 56f146a8). PR #278, merged head 60c05c7 approved; reach test fails before, passes after. Done differently: the live gate ran the self-test only (2 sessions), not one writers:<provider> case, because the change touched only the verifier's classification. Eric answered "Accept".

  4. added a commit that references this issue on Nov 6, 2026
    60c05c7
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

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions