fix: explain print <local path>, ratchet private imports, dev-bump to 0.6.0.dev0 - #137
Draft
DLANSAMA wants to merge 2 commits into
Draft
fix: explain print <local path>, ratchet private imports, dev-bump to 0.6.0.dev0#137DLANSAMA wants to merge 2 commits into
DLANSAMA wants to merge 2 commits into
Conversation
…-HOME first run README: move "Print something" (step 1 = install OrcaSlicer) above "Try it in 30 seconds", retitle the nav link so no "30 seconds" precedes the first OrcaSlicer mention, and say the sim needs neither a printer nor OrcaSlicer while a real print needs both. Anchors unchanged. Tests (tests/test_first_run_path.py, section 6) lock the empty-HOME contract a newcomer hits, so the walk is deterministic without a printer: - `plate preflight` exits 1 and reports config, orca-slicer, and profiles-dir as three separate checks (human and --json), each with its own next step. - `plate setup --sim` with a non-TTY stdin exits 1 with the headless message naming --printer-ip/--serial/--access-code-file, no traceback. - `plate --sim status` with an empty HOME still exits 0 and reports IDLE. No CLI behaviour changed; no protocol code touched.
…to 0.6.0.dev0 - `plate print tests/fixtures/cube.stl` used to fail with "unsafe name". A path with a separator can never be a printer-side name, so the error now says `print` takes the name of a file already on the printer and points at `plate job <path> --confirm` (model file) or `plate upload` then `plate print <name> --confirm` (sliced file); `next_command` carries the same hint in --json. Exit code 3 / failed_step unchanged. - scripts/check_layers.py: budget for cross-unit imports of underscore-private names (measured 104; may only go down). AGENTS.md documents the ratchet. - main was still 0.5.1 after the release; back to 0.6.0.dev0 (uv.lock self-version synced). - docs/quality-roadmap.md: freeze banner from the 2026-09-01 audit and the checkboxes that were already enforced in CI ticked with evidence; ftps coverage (89.8% < 90) and the 88% floor stay honestly open.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes from the 2026-09-01 repo audit.
What changed
plate print <local path>no longer fails with "unsafe name". A path with a separator can never be a printer-side name, so the error now explains thatprinttakes the name of a file already on the printer and points at the fix:plate job <path> --confirmfor a model file, orplate upload <path>thenplate print <name> --confirmfor a sliced 3MF/G-code.--jsoncarries the hint innext_command. Exit code 3 andfailed_step: validateare unchanged; names without a separator keep the old message. 4 new tests.scripts/check_layers.pynow ratchets cross-unit imports of underscore-private names (PRIVATE_IMPORT_BUDGET, measured 104; may only go down). AGENTS.md documents it.0.6.0.dev0on main after the 0.5.1 release (the follow-up bump in docs/releasing.md step 6 was never done); uv.lock self-version synced.Verified locally
ruff check, ruff format, mypy, bandit, check_layers, gen_schemas --check, all six smokes, and the full suite (1537 passed, 91.1% coverage). Two version tests fail only against a stale venv; a fresh
uv pip install '.[test]'of this branch passes them andplate --versionprints0.6.0.dev0.