Skip to content

CI: PalomarServer#150 rebased - #1

Closed
dcposch wants to merge 1 commit into
mainfrom
codex/infrastructure-retry-docs
Closed

dcposch wants to merge 1 commit into
mainfrom
codex/infrastructure-retry-docs

Conversation

@dcposch

@dcposch dcposch commented Sep 5, 2026

Copy link
Copy Markdown
Owner

Fork-only draft to run CI on the squashed, rebased branch for PalomarRegistry#150. Not for merge.

@dcposch dcposch closed this Sep 5, 2026
@dcposch dcposch reopened this Sep 5, 2026
Companion to PalomarSubmission#130. Palomar-owned verification failures
increased a submitter's exponential backoff, and the agent instructions
did not tell submitters to run the reproducible preflight.

- Refund one backoff step when a submission settles as
  verification-error, and permit an immediate retry of the same commit.
- Add a "Mechanical preflight" section to the submission llms.txt that
  names the exact reusable workflow and the palomar-standard-v1 profile.
- Document verification-error as a settled, Palomar-owned outcome.
- Bring the bundled browser preflight policy forward so the intake page
  accepts "verification_profile" in comparator.json, matching the policy
  PalomarSubmission#130 publishes. Without this the browser preflight
  reports comparator.unknown_key for the new field.

The contract check against PalomarSubmission main passes only once PalomarRegistry#130
has merged; merge that first.
@dcposch

dcposch commented Sep 5, 2026

Copy link
Copy Markdown
Owner Author

Fork workflows do not run here; CI steps were run locally instead.

@dcposch
dcposch force-pushed the codex/infrastructure-retry-docs branch from e389227 to 273e119 Compare September 5, 2026 15:33
@dcposch dcposch closed this Sep 5, 2026
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