inline-code: English word "node" (also cd) matched as a shell command, flagging "node from"/"node runs"

inline-code PATTERN[0] treats the common English word "node" (also cd) as a shell command, so an ordinary prose noun followed by any word is flagged as a bare literal.

Reproduction

Login to each node from list below over SSH.
Confirm each node runs the image before finishing.

warning [inline-code]: literal "node from" must be wrapped in backticks
warning [inline-code]: literal "node runs" must be wrapped in backticks

PATTERN[0] is /\b(?:npm|npx|node|git|eslint|mocha|yarn|pnpm|cd|rm|mkdir|chmod|cat|sed|grep|curl|docker)\s+[\w./-]+/. node/git/cd are legitimate command names, but they are also plain English words (a Zold node, cd as an abbreviation, etc.). Here "node" is a noun and "from"/"runs" is the next English word, not an argument — so backticking it would be wrong.

Proposed fix

For the command tokens that double as common English words (node, cd, maybe cat), only match when the following token looks like an argument rather than a bare word — a path, filename, flag, or version ([./-] present, a known extension, or a leading -). A bare node <word> where <word> is plain prose should not fire. The unambiguous tool names (npm, npx, eslint, docker, …) can keep matching a bare following word.

Found while converting an ops skill that talks about Zold "nodes" to house style; every mention of "node <verb/preposition>" tripped.