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.
2.7 KiB
2.7 KiB
| name | description |
|---|---|
| release | Prepare a 0.0.x or 0.1.0 candidate's evidence and recommend promotion without promoting it automatically. |
Prepare a release stage
Input: the milestone scope, the target version and stage, and the exact
candidate commit. Read versions and releases,
the blueprint's version progression
and, for stable 0.1.0, the stable release gate.
- Inventory. List existing tags, published releases and the versions in
Cargo.toml, crate manifests and package manifests. Choose the next unused0.0.xfor an accepted milestone scope; never reuse, move or rewrite a published tag or release. Record how the unreleased workspace value0.1.0is reconciled. - Check the stage contract.
alpha.Nneeds defined scope, ownership and fixtures with incompleteness stated.beta.Nneeds the declared scope implemented, relevant integration and failure paths passing and interfaces, support scope and budgets frozen.rc.Nneeds the exact candidate complete for its scope, the required matrix passing, independent technical review and ready artifacts and migration behavior. Final, released as the plain version without a-finalsuffix, needs every scoped promise to pass. - Collect candidate evidence for that exact commit with verify: every applicable runner profile plus the blueprint fixtures and target environments in scope. Record commit, environment, features, commands, results and artifact digests. A missing environment leaves the gate incomplete.
- Obtain independent technical review of the candidate with the reviewer, aimed at showing it is not ready. A self review does not satisfy a release gate; an unavailable reviewer leaves the gate pending while other authorized work continues.
- Resolve or scope. Blocking findings prevent promotion. Corrections after review invalidate the affected evidence: rebuild the candidate, rerun the affected checks and re-review. Unsupported features are excluded explicitly, not left as silent success paths.
- Prepare release notes for maintainers: scope, support matrix, known limitations, compatibility and migration notes, commit and artifact digests, and the evidence actually executed.
- Recommend. Return the evidence, open findings and a recommendation. Promotion, tagging and publication happen only under granted release authority, and publish the artifact that was tested. If final metadata requires a rebuild, verify that rebuilt artifact before publishing it.