https://projectious-work.github.io/aibox/v0.x/v0.34.3/docs/contributing/Reproducible AI workspaces from one aibox.toml.enMon, 01 Jan 0001 00:00:00 +0000https://projectious-work.github.io/aibox/v0.x/v0.34.3/docs/contributing/maintenance/Mon, 01 Jan 0001 00:00:00 +0000https://projectious-work.github.io/aibox/v0.x/v0.34.3/docs/contributing/maintenance/Maintenance#Internal procedures for building, testing, documenting, and releasing aibox. The canonical step-by-step release note remains in context/notes/; this page is the public contributor summary. Development Checks# bash Copy cd cli && cargo fmt -- --check cd cli && cargo clippy --all-targets -- -D warnings cd cli && cargo test The helper script wraps the same checks:https://projectious-work.github.io/aibox/v0.x/v0.34.3/docs/contributing/e2e-tests/Mon, 01 Jan 0001 00:00:00 +0000https://projectious-work.github.io/aibox/v0.x/v0.34.3/docs/contributing/e2e-tests/E2E Test Catalogue#aibox deliberately has no container-runtime bridge from its development container. Tests are placed according to the product behavior they prove, not according to the historical runner that happened to execute them. Execution surfaces# Surface Where it runs Contracts Local Development container, unique temporary directories CLI parsing, init/apply, generated files, preservation, …https://projectious-work.github.io/aibox/v0.x/v0.34.3/docs/contributing/version-line-porting/Mon, 01 Jan 0001 00:00:00 +0000https://projectious-work.github.io/aibox/v0.x/v0.34.3/docs/contributing/version-line-porting/Version-line porting#aibox maintains the v0.x and v1.x lines in parallel. A fix landing on either line must be reconciled with the other line when applicable. The release gate compares both maintained branches after the recorded enforcement baselines in .github/version-line-port-baselines.toml. Every non-merge source commit must have a matching port on the target line or an explicit not-applicable …