Skip to content

fix: address issues #153-#156 (App wf fallback, e2e hardening, ruleset strict=false, test additions)#157

Merged
SebTardif merged 3 commits into
mainfrom
fix/strong-guard-release-pr
Jun 22, 2026
Merged

fix: address issues #153-#156 (App wf fallback, e2e hardening, ruleset strict=false, test additions)#157
SebTardif merged 3 commits into
mainfrom
fix/strong-guard-release-pr

Conversation

@SebTardif

@SebTardif SebTardif commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Batch fix for open issues #153 and up (tech debt from anti-rationalization audit after #147+ and strong guard work).

Changes

Verification

  • npm run check (compile + unit tests + coverage gate + package) green multiple times.
  • Ruleset confirmed via gh api.
  • Subagent reviewer (general-purpose as reviewer) performed full inspection: mostly ready, no criticals; followed all process suggestions (full gate, explicit staging, DCO, draft/ready flow consideration, Closes refs).
  • Double-checked with greps, git diff, issue bodies, timeout semantics, token fallback conditions.
  • No regressions to existing guards, DI, relative .js imports, or DCO.

Closes #153
Closes #154
Closes #155
Closes #156

Checklist

  • DCO signed
  • npm run check passes
  • Docs updated
  • Followed owned repo + new branch/PR discipline (draft first recommended for future)

This PR itself touches workflow file; auto-merge enabled via fallback path (as designed).

- Add label-based release guard step in auto-approve.yml (autorelease: pending)
- New scripts/guard-no-release-merge.sh hard-fail script for agents/humans
- Document 'Release PRs - Strong Guard' procedure + ask_user_question requirement in AGENTS.md
- Update tracking in patchloom-vscode-contrib skill (local only)

Prevents recurrence of agent running gh pr merge --auto on release-please PRs without explicit user yes.

All changes pass npm run check (259 tests, package ok).

Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
@SebTardif SebTardif enabled auto-merge (squash) June 22, 2026 20:29
…et strict=false, coverage tests)

- #153: auto-approve now falls back to GITHUB_TOKEN for auto-merge on wf-touching PRs (conditional App token creation); removes hard dependency on workflows:write grant.
- #154: added normalize/CRLF test case exercising pure helper in initializeProject.
- #155: bumped e2e managed/MCP timeouts to 60s for cold-start robustness.
- #156: updated live ruleset strict_required_status_checks_policy=false; release PRs now merge reliably when green.

Closes #153
Closes #154
Closes #155
Closes #156

All via npm run check (clean), double-checked, subagent reviewer passed (mostly ready, followed suggestions for full gate + draft PR flow).

Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
@SebTardif SebTardif changed the title chore: add strong guard against unauthorized release PR merges fix: address issues #153-#156 (App wf fallback, e2e hardening, ruleset strict=false, test additions) Jun 22, 2026
…h for #154)

Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
@SebTardif SebTardif merged commit d2dfe21 into main Jun 22, 2026
19 checks passed
@SebTardif SebTardif deleted the fix/strong-guard-release-pr branch June 22, 2026 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment