WEFT_OS/.github/ISSUE_TEMPLATE/decision.yml
Marco Allegretti dcc09f319d
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-09 08:34:48 +00:00

58 lines
2.1 KiB
YAML

name: Decision
description: Request a maintainer decision on a material change of direction, compatibility, trust boundaries, support scope or data policy.
body:
- type: markdown
attributes:
value: |
This form requests a decision before implementation; opening it does not approve the change.
Ordinary implementation of an accepted BLUEPRINT.md boundary does not need this form.
Search existing decisions and issues first.
- type: textarea
id: observed
attributes:
label: Observed
description: The current problem and the concrete affected user, caller or contract.
validations:
required: true
- type: textarea
id: direction
attributes:
label: Accepted direction affected
description: The BLUEPRINT.md section, public contract or support promise this would change, and how.
validations:
required: true
- type: textarea
id: evidence
attributes:
label: Evidence
description: Commit, source references, executed checks and the selected dependency revisions that establish the problem. Separate verified facts from assumptions.
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Alternatives and trade-offs
description: Viable options including keeping the current direction, with their costs for ownership, security, data, compatibility and schedule.
validations:
required: true
- type: textarea
id: decision
attributes:
label: Decision requested
description: The specific decision needed and the work it unblocks. Independent authorized work continues meanwhile.
validations:
required: true
- type: textarea
id: acceptance
attributes:
label: Acceptance criterion
description: The independently evaluable outcome an accepted option must satisfy.
validations:
required: true
- type: textarea
id: proof
attributes:
label: Expected proof
description: The fixtures, measurements or integration evidence that will show the chosen option works.
validations:
required: true