sys-lib 0.2.0

System facts for Rust services: OS, CPU, memory, disks, network, host, this process, virtualization, power, and device identity, container-aware by default, plus build info, instance info, and a process guard. No subprocesses, zero third-party dependencies.
Documentation
# sys-lib v0.1.0 - Scaffold

**The repository and the plan.** v0.1.0 set up the crate in the portfolio template and wrote down the design before any code. There is no functional code in this release; it also claimed the name on crates.io.

## What is sys-lib?

<strong>sys-lib</strong> answers the questions a program asks about the machine it runs on, with one plain function call each, on Linux, macOS, and Windows: the operating system, the CPU, memory, disks, network interfaces, the host, this process, virtualization and containers, power, and an application-scoped device id. It also carries the boot kit a long-running service needs in its first milliseconds: build info, instance info, and a process guard. It is container-aware, reports unknown facts as unknown, never runs another program, never starts a thread, and has no third-party runtime dependencies.

## What's in 0.1.0

- The crate manifest: edition 2024, MSRV 1.89, no dependencies, `Apache-2.0 OR MIT`, features `instance` and `guard` (default) and `device-id` (opt-in) declared ahead of their code.
- The crate root: `VERSION`, `unsafe_code` denied at the root (to be lifted only inside the per-platform OS modules), missing docs, undocumented unsafe blocks, and `unwrap`/`expect`/`panic` in library code denied.
- CI on Linux, macOS, and Windows, each on x86_64 and aarch64, on stable and 1.89; cross-target checks for musl, 32-bit Windows, Android, and iOS; documentation built with default and all features; `cargo package`; `cargo audit` and `cargo deny`; a job that fails if `src/` can start a subprocess outside the build helper.
- `dev/PLAN.md`: purpose, scope, requirements, the design, the API outline with item ids, sixteen threats with their attack tests and costs, the architecture, dependencies, competitors, performance targets, the testing plan with one hundred edge cases, open decisions, ideas, and the decision log.
- `dev/DIRECTIVES.md` (engineering law and definition of done) and `dev/ROADMAP.md` (phases 0.2 to 1.0 with exit criteria).

## What's next

`0.2.0` locks the public API in `docs/API.md`, writes `docs/SOURCES.md` and the reviewed OS declaration lists with struct layout assertions, and captures the first fixture machines. `0.3.0` ships the boot kit: build info, instance info, the process guard, OS identity, CPU counts and name, and the host name.