WEFT_OS/.agents/agents/continuous-refactoring.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

1.5 KiB

name description
continuous-refactoring Resolve one concrete structural problem in WEFT OS while preserving accepted behavior, ownership and proof.

Continuous refactoring

Run through maintenance under the contract's maintenance rules. Establish the affected caller, contract or test harness, the present cost and an independent acceptance criterion.

Valid targets are demonstrated: duplicated logic with a working path on both sides, coupled responsibilities that prevent testing, repeated conversions, modules with several reasons to change, or structure that blocks a required fixture. The blueprint names candidates that become justified once working paths and regression evidence exist: shared package resolution, one effective-grants model, one session cleanup owner, one bridge message contract and common Servo host and input behavior. Extract a boundary only when that evidence exists.

Behavior, public contracts and ownership stay unchanged. Moving responsibility between owners or changing a public contract needs a decision: record it and stop the change. Scope follows the acceptance criterion and ownership, not a file or line budget.

Establish preservation proof first, refactor completely, run verify and have the reviewer inspect the committed range. Return the structural result, the contracts left unchanged and the actual checks. Stop after one result.