Contribute with evidence

Start from the real boundary

Choose a concrete user outcome and trace it from UI intent through IPC validation, host policy, runtime behavior, event reporting and persistence. A new button is not an implemented feature until its actual host effect, error state and recovery path exist.

Before changing code, reproduce the issue with the exact model, settings and build. Preserve the original failure and identify which layer owns it. Avoid loops of unrelated patches that make the happy path look healthy while obscuring a broken tensor contract or lifecycle race.

A useful change record

• Problem: a concrete trigger and observed incorrect behavior.
• Contract: what the host/runtime/UI should do, including invalid input.
• Scope: the files and boundaries changed, with retained ownership rules.
• Evidence: targeted tests, actual applied settings and meaningful end-to-end proof.
• Limits: unsupported artifacts, unmeasured performance and remaining gates.

Do not fabricate benchmark numbers, support matrices, provider identity, installed integrations or endorsements. Distinguish a source inspection, an estimate, a successful load, completed generation, quality evaluation and performance comparison.

Tests that earn their cost

Use parser and planner tests for corrupt metadata, unknown encodings, incomplete shards, numeric bounds and memory assumptions. Use protocol fixtures for streaming, cancellation, terminal errors and ownership. Use an actual native flow for packaging/security and a real chosen artifact for runtime qualification.

Do not start a second GPU workload while another agent or developer owns the machine’s qualification slot. Isolate test profiles, preserve model bytes and close only the processes the test owns. Keep credentials and private histories out of shared receipts.

Documentation changes

This site lives in docs-site/, with authored Markdown/MDX under src/content/docs/. Its navigation is explicit in astro.config.mjs; Pagefind builds a local search index. Add substantive content, internal links and a status label that matches actual implementation. Planned API pages must not publish imaginary package commands.

Update affected guides when a contract changes. A measured optimization should document the exact artifact, engine, placement and workload before the release-status page changes. Deployment and source publication remain separate actions with their own verified destination and rollback plan.