WEFT_OS/.agents/skills/weft-linux-deployment/SKILL.md
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

2.8 KiB

name description
weft-linux-deployment Use for the Nix flake and reference VM, systemd units, native dependencies, installed paths, endpoints and service activation.

Linux deployment

Owner: Linux and systemd own the seat, session substrate, service lifecycle and process and resource boundaries. The installed closure must carry the real feature-enabled product. Read the blueprint's release profile, installed session and developer workflow.

Where things live

Concern Source
Flake, toolchain, dev shell flake.nix, flake.lock
Package derivations and features weft-packages.nix
VM configuration configuration.nix
VM build and run build.sh, run.sh
Service units infra/systemd
Native build dependencies building.md, CI
Environment variables architecture.md and the std::env reads in each crate

Working rules

  • Keep one authoritative Nix and systemd configuration; make development units and scripts consistent with it.
  • The closure includes the feature-enabled binaries (servo-embed for both shells, wasmtime-runtime for the runtime), the shell HTML and UI assets at installed paths, reference packages with an explicit trust configuration, the binary paths appd needs, and explicit activation and dependencies.
  • Pass the real compositor display and daemon endpoints; never guess names such as wayland-1. Keep persistent data and ephemeral runtime storage separate.
  • Fill fixed-output hashes, including Servo's git outputHashes, from an actual build, never by copying an unrelated value.
  • Never fabricate pkg-config files or library versions to satisfy a build. Repair the environment or exclude the feature explicitly. Do not commit machine-specific usernames or checkout paths.
  • Record the exact VM machine, graphics device, kernel, Mesa, CPU and memory used for evidence. A headless VM or a successful evaluation is not graphical acceptance.

Evidence

The runner has no Nix or VM profile. Build with bash infra/vm/build.sh and run with bash infra/vm/run.sh where Nix with flakes is available, and record the environment. Installed-system claims need a fresh graphical boot that starts the complete system without checkout paths or manual repair, plus persistence across reboot and update. A missing Nix installation or virtualization support is unavailable evidence.