Skip to content

Add spreadsheet completeness stop guard - #1221

Merged
mergify[bot] merged 1 commit into
mainfrom
stack/EdbertChan/pr/spreadsheet-completeness-guard-hook-only-20260929/add-spreadsheet-completeness-stop-guard--913b9181
Sep 29, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
stack/EdbertChan/pr/spreadsheet-completeness-guard-hook-only-20260929/add-spreadsheet-completeness-stop-guard--913b9181

Conversation

@EdbertChan

@EdbertChan EdbertChan commented Sep 29, 2026 •

Copy link
Copy Markdown
Owner

Summary

A stop check now blocks a claim that the sheet is done. The text must say that coverage passed. The check allows three tries. After that, the claim stays blocked and the missing names stay listed.

Review Claim

The stop check blocks a claim that the sheet is done unless the text includes the coverage receipt, and it allows at most three tries.

Review Lane

behavior

Review Unit

engine-runtime

Safety Invariant

A spreadsheet completion claim cannot pass without the exact coverage receipt; incomplete coverage remains blocked after the retry limit.

Slice Rationale

This pull request contains only the engine hook and harness manifests. Schema and derived-estimate validation stay on the product-skill pull request.

Non-goals

  • No changes to Google Sheet contents.
  • No automatic invention of competitor values.
  • No product-skill files.

Test Plan

Test Plan
  • python3 -m unittest discover -s engine/hooks/spreadsheet-completeness-guard/tests -p test_*.py

Revert Plan

Revert Plan
  • Safe to revert? Yes
  • Revert command: git revert 2b204c70
  • Post-revert steps: None
  • Data migration? No

Change-Id: I913b91811835219351c9267075e078ccbe5795d1
@cursor

cursor Bot commented Sep 29, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_f6434a10-6b69-481a-9c13-8f5ebd9eddb6)

@mergify

mergify Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Queued — the merge queue status continues in this comment ↓.

@EdbertChan

Copy link
Copy Markdown
Owner Author

@Mergifyio queue

@mergify

mergify Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 46 minutes 11 seconds in the queue, including 45 minutes 49 seconds running CI.

Required conditions to merge
  • check-success = lint
  • check-success = test
  • check-success = validate

@mergify mergify Bot added the queued label Sep 29, 2026
@mergify
mergify Bot merged commit b150e5d into main Sep 29, 2026
5 of 10 checks passed
@mergify mergify Bot removed the queued label Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant