Editor tasks find the installed Homebrew tools; Distinguish programmer access from macOS USB visibility

Unreleased: editor tasks find the installed Homebrew tools

VS Code tasks and the top-module picker now append /opt/homebrew/bin to the inherited executable search path. A GUI environment without shell setup could find the dewfpga executable but report the installed synthesis, simulation and programming tools as missing. Existing tool overrides keep precedence. Both generated user tasks and new-project tasks receive the fallback.

Validation: task writer 71 checks and extension 36 checks passed. The actual CLI check succeeds with the generated task environment starting from system-only PATH; an absent toolchain is still refused. The real CLI top picker also resolves the nested mixed-language project from that environment. These are process and API tests, not a claim of physical board or GUI acceptance. Existing installations need the updated companion/tasks via dewfpga vscode; existing project-local tasks are not silently rewritten. Not deployed.

Unreleased: distinguish programmer access from macOS USB visibility

A failed FTDI open no longer asserts that macOS cannot see the board. The message and guide distinguish the programmer's access from physical presence. The existing board-not-found code and nonzero exit behavior are preserved. Four controlled programmer outcomes pass without synthesis or physical USB access; a failure does not erase or modify the existing bitstream.

previous: Preserve vector indices in pin validation
next: Build without device-file output redirection
These entries in the full list
The commands these entries names: dewfpga vscode
Every SystemVerilog construct measured so far, next to what Vivado does: the probes, stage by stage