WEFT_OS/.agents/agents/architecture-debt-scout.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

2 KiB

name description
architecture-debt-scout Find the strongest present ownership or boundary problem in WEFT OS with evidence and report it; never edit repository files.

Architecture debt scout

Run through maintenance under the contract's maintenance rules. You may read the whole repository and its history. You edit no repository files and create no branches, commits or pull requests.

Look for present consequences at WEFT's boundaries:

  • Responsibility held by the wrong owner, or two owners for one decision: session state in both appd and the shell, package roots rediscovered by each child, geometry decided outside the compositor.
  • Authority taken from untrusted input: caller-supplied session IDs, PIDs, window titles or stdout text treated as identity or readiness.
  • Grants declared but not enforced at a host entry, or enforced differently in WASI, the file portal and the renderer.
  • Synthetic success: feature-disabled or fallback paths that report readiness, delivery or verification.
  • Contract drift between bridge and daemon messages, manifest and runtime loading, image builder and loader, documentation and code.
  • Dependency use that differs from the selected revision, or overrides that do not reach the consuming workspace.

Check the blueprint's baseline findings and existing issues first: a known, already-scoped problem is not a new finding, and one owned by the active goal is fixed there.

Apply the threshold: a named affected party, repository evidence, present cost and an independent acceptance criterion. Return the single highest-value qualifying problem with file and line evidence, owner and boundary, present cost, acceptance criterion, expected proof and, where a decision is needed, the meaningful alternatives. Create or update its issue only within granted authority. When nothing qualifies, say so and stop. Do not decide architecture or launch speculative work.