PULL_REQUEST_TEMPLATE.md
September 19, 2026 · View on GitHub
Goal And Delivered Outcome
- Goal/source and gap:
- Observable before → after, with the validation row that proves it:
- Issue/task and intended base:
Scope And Continuation
- Completed scope and remaining work:
- Slice boundary / successor:
Validation
Public-safe summaries only, including in HTML comments. Do not paste raw logs, private data or prompts, private screenshots, credentials, internal URLs, connection strings, or local paths. Use repository-relative commands without sensitive arguments, aggregate results, and already-public CI links. If evidence is private, report its category and limitations only; do not upload it to prove a claim.
- Tested revision:
- Run state:
- Input classes:
| Check kind | Result | Public-safe evidence / limitation |
|---|---|---|
unit | not_run | Example only: repository-relative test path; behavior checked; aggregate outcome or generic reason not run. |
- Coverage and gaps:
See validation disclosure guidance.
Frontend / Visual Evidence
- UI impact:
- Before:
- After:
- States and viewports shown:
- Source data:
- Attention review:
Type of Change
- Bug fix
- New feature
- Breaking change
- Refactoring (no functional changes)
- Documentation update
- Test update
LoopX Area
- Control plane (goals, todos, quota, scheduler, registry, runtime)
- Benchmark boundary (adapters, runners, verifiers, scoring, evidence)
- Capability or extension (providers, adapters, skills)
- Public docs or presentation surface (README, protocols, dashboard)
- Build, packaging, installer, or CI
- Host or runtime integration
Technical Direction
- Direction / acceptance reference, when applicable:
Shared-authority RFC fixture impact
- Production-scale fixture schema:
- Semantic dimensions changed, or reviewed no-impact rationale:
- Provider conformance arms run:
- Read-only legacy/file/PostgreSQL three-arm rehearsal (required for promotion, runtime-routing, or compatibility-projection changes):
Boundary Checklist
- Neither the diff nor this PR body/comments/attachments disclose private state, credentials, raw traces or verifier output, internal links, or local machine paths (including
.loopx/,.codex/goals/, and liveACTIVE_GOAL_STATE.md). - I did not duplicate maintainer-owned benchmark work unless a maintainer split out a public issue for it.
- I kept the change scoped to the linked issue/task.
- I completed the visual evidence section for UI changes, or marked UI impact
none. - Every commit includes a DCO
Signed-off-bytrailer (git commit -s).