6459c9fcf0
* wip: the diagnosis of #10181 (the bug reproduces on current main) sketch.project has .enabled(in_sketch) (crates/engine/src/cmd/sketch_project.rs:24) and in_sketch (crates/engine/src/cmd/mod.rs:285) answers 'no sketch is being edited'. Pressing P outside a sketch goes keymap::press -> sketch_tool_for (crates/ui-egui/src/keymap.rs:451-457) -> app.start("sketch.create") with d.then_start = Some("sketch.project"): the sketch IS created, but the Project dialog opens and the command is refused, so the dialog shows the red row and the 'Create Issue...' button, which opens the Report a bug form over the viewport. The probe here reproduces the bug on the CURRENT main (two variants). It is a diagnostic probe, not the regression test: it must be replaced before a PR. * test: a context error offers no Create Issue button (#10181) The Project panel showed the red row for a CONTEXT error ('sketch.project is not available right now: no sketch is being edited') and offered the 'Create Issue...' button, which opens the Report a bug form over the viewport. A context error is not something to report, so the panel must not offer it. RED: the test fails with the exact message of the issue. * fix: a context error is not something to report (#10181) The Project panel offered "Create Issue..." for the error the engine raises when the command is not available in the current context ("`sketch.project` is not available right now: no sketch is being edited (Create Sketch or Edit Sketch first)"). That refusal is guidance about the context, not a failure of the design, so there is nothing to report: ending the sketch under an open Project panel should not invite the user to file a bug. error_rows already spared the missing-pick errors ("select ...", "pick ...") the same way. It now spares the context refusals too, using the engine's own kind rather than the message text: CommandSpec gains disabled_refusal, which is the engine's own Disabled refusal for the command in the current session, and the UI matches the dialog's error against it. A real failure of the command (an invalid face, say) still shows the red row with "Create Issue...". * style: rustfmt the test of #10181 The formatter joins the two asserts of the test onto one line (the repository sets max_width = 150 and use_small_heuristics = Max). The tokens of the file are unchanged: the diff is the line breaks of the asserts and nothing else.