mirror of
https://github.com/marcoallegretti/WEFT_OS.git
synced 2026-11-22 08:13:59 +00:00
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.
43 lines
2.3 KiB
Markdown
43 lines
2.3 KiB
Markdown
---
|
|
name: scope
|
|
description: Establish a reported problem or proposal and draft verifiable scope with owner, acceptance criterion and proof.
|
|
---
|
|
|
|
# Establish the scope
|
|
|
|
Input: a defect report, desired behavior or proposal. Read
|
|
[AGENTS.md](../../AGENTS.md), the relevant sections of
|
|
[BLUEPRINT.md](../../BLUEPRINT.md) and the matching
|
|
[skills](../README.md#skills). The result is a draft; this procedure neither
|
|
implements it nor authorizes publication.
|
|
|
|
1. **Inspect.** Read the implemented source, the public contract involved
|
|
(manifest, WIT, shell protocol, IPC types) and the selected dependency source
|
|
when an external API matters. Check whether the blueprint already records the
|
|
problem, for example in its [baseline findings](../../BLUEPRINT.md#32-findings-that-determine-the-implementation-order).
|
|
2. **Reproduce** where practical, with the exact commit, environment, features
|
|
and command. Separate observations from assumptions and say which level of
|
|
[evidence](../../BLUEPRINT.md#111-evidence-levels) each observation reached.
|
|
3. **Name the owner** from the
|
|
[ownership table](../../BLUEPRINT.md#4-architecture-and-ownership) and the
|
|
affected user, caller or contract. If nobody is worse off today, stop: there
|
|
is no issue.
|
|
4. **Check for duplicates** among existing issues and pull requests. If access is
|
|
unavailable, say that duplicate checking is incomplete.
|
|
5. **Decide the path.** Ordinary work within accepted architecture becomes a
|
|
change. A material departure from accepted direction, compatibility, trust,
|
|
support scope or data policy needs a
|
|
[decision](../../AGENTS.md#9-decisions-and-authority): prepare the evidence,
|
|
alternatives and trade-offs and mark implementation as waiting for it.
|
|
6. **Draft** against the matching form:
|
|
[defect or change](../../.github/ISSUE_TEMPLATE/change.yml),
|
|
[maintenance](../../.github/ISSUE_TEMPLATE/maintenance.yml) or
|
|
[decision](../../.github/ISSUE_TEMPLATE/decision.yml).
|
|
|
|
The draft states observed and expected behavior, evidence with file and line
|
|
references, owner and affected boundary, present impact, one acceptance
|
|
criterion, the proof that would fail today and pass afterwards, and relevant
|
|
non-goals. A claim without a verification surface is unfinished scope.
|
|
|
|
Return the draft plus any missing evidence or decision. Create or update an
|
|
issue only when that is part of the authorized task.
|