WEFT_OS/.github/pull_request_template.md
Marco Allegretti 39869a2a38
docs: add engineering contract, contributor toolkit and templates
Add AGENTS.md as the single engineering contract: sources of truth,
evidence and proof requirements, ownership, working modes, the reviewed
change loop, maintenance isolation, decision authority, dependency and
fork rules, the 0.0.x to 0.1.0 release progression, and branch and
publication rules.

Add .agents/ with scope, implement, verify, maintenance and release
procedures; reviewer, architecture debt scout, simplicity and refactoring
roles; skills for the compositor, Servo rendering, runtime capabilities,
appd sessions, packages and data, Linux deployment, integration
verification and documentation; and verify.py, which runs the existing
check profiles with --locked from any directory, stops on the first
failure and supports --dry-run.

check_toolkit.py validates local links and heading anchors, metadata,
catalog coverage and issue forms. A new contributor-toolkit CI job runs
both. The structure follows the Resina Design System toolkit at
1e768064f57a1e403ab271822383e732795905a6, adapted to WEFT.

Validation, against the committed lockfiles:
- verify.py toolkit: checker passes, 28 runner/checker tests pass
- verify.py portable, demos, packages: pass
- verify.py linux, runtime, servo-embed: fail on existing defects
  (clippy collapsible_if in the winit backend, three clippy lints in
  weft-runtime with wasmtime-runtime, and an E0308 in the selected Servo
  revision's servo-layout); the runner reports the failing status

Add CONTRIBUTING.md, issue forms for defects and changes, maintenance
problems and decisions of direction, and a pull request template asking
for ownership, proof and the validation actually performed. README.md
links the contribution guide.
2026-10-08 23:40:08 +00:00

29 lines
1.7 KiB
Markdown

## Problem and scope
<!-- The concrete problem and its present impact. Link the issue (Closes #...) or the accepted scope. For a material change of direction, link the decision that approved it. -->
## What changed
<!-- The resulting behavior or structure, for a reader without access to your working notes. State relevant exclusions. -->
## Ownership
<!-- The owning component and the public contracts touched (wapp.toml, WIT, shell protocol, IPC types, package format). Explain how ownership and compatibility are preserved, or how an approved change keeps them coherent. -->
## What proves it
<!-- The test, component fixture, integration fixture, pixel check or measurement that fails without this change and passes with it. Explain any changed expectation, fixture or signature. Compilation and mocks do not prove rendering, native input, isolation or persistence. -->
## Validation performed
<!-- Actual commands and results, e.g. python .agents/scripts/verify.py portable linux. Name the environment for integration evidence (backend, GPU or virtual device, VM). List checks not run and why. -->
## Manual verification
<!-- What automation cannot establish, the environment and scenario used, and the observed result. If none is needed, say why automated evidence covers the scope. -->
## Limitations and related issues
<!-- Limitations that affect evaluation or use. Link separately actionable problems as issues; do not store future work here or leave a supported path knowingly incomplete. -->
<!-- Keep this text about the project problem, change and evidence. No model or provider attribution, co-author or generated-by trailers, reviewer counts or personas, prompts or process narration. -->