WEFT_OS/.github/ISSUE_TEMPLATE/change.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

63 lines
2.5 KiB
YAML

name: Defect or change
description: Report a concrete defect or propose an ordinary change within accepted architecture.
body:
- type: markdown
attributes:
value: |
Use a title that states the defect or the behavior that should hold. Search existing issues
and pull requests first. Use the Decision form for a material change of product direction,
public compatibility, trust boundaries, support scope or data policy.
- type: textarea
id: observed
attributes:
label: Observed
description: What happens now, and who or what is affected (user journey, caller, contract, test harness, contributor).
validations:
required: true
- type: textarea
id: expected
attributes:
label: Expected
description: What should hold instead. Cite the implemented contract or the BLUEPRINT.md section, and say which one applies.
validations:
required: true
- type: textarea
id: evidence
attributes:
label: Evidence
description: Commit, environment (host, compositor backend, GPU or VM), enabled features, exact reproduction steps and actual output, with file and line references.
validations:
required: true
- type: textarea
id: owner
attributes:
label: Owner and boundary
description: The owning component (compositor, servo-shell, app-shell, appd, runtime, package tooling, portal, deployment) and any public contract touched (wapp.toml, WIT, shell protocol, IPC types).
validations:
required: true
- type: textarea
id: impact
attributes:
label: Why it matters now
description: The concrete present impact. A hypothetical future need or a stylistic preference is not enough.
validations:
required: true
- type: textarea
id: acceptance
attributes:
label: Acceptance criterion
description: One independently checkable condition that resolves this issue. Keep unrelated work out of scope.
validations:
required: true
- type: textarea
id: proof
attributes:
label: Expected proof
description: The test, component or integration fixture, pixel check or measurement that fails today and will pass afterwards, and the environment it needs. Compilation and mocks do not prove rendering, input, isolation or persistence.
validations:
required: true
- type: textarea
id: scope
attributes:
label: Scope and related work
description: Related issues, pull requests or blueprint findings, and explicit non-goals.