Discarded negation of a void call rejects valid JavaScript

When compiling a bundled CLI, the generated debug-ID banner starts an immediately invoked function with !. Its boolean result is discarded. Node runs the banner, but scriptc rejects it before lowering because the function returns void.

This also reproduces without the bundle:

function register() {
  console.log("registered");
}
!register();

Node prints registered and exits successfully. Current scriptc 0.4.9 reports SC0001: An expression of type 'void' cannot be tested for truthiness. The same problem affects !function () { console.log("registered"); }();.

For an expression statement, the result of the negation is unused. Evaluating the operand once and discarding its result preserves the side effects and any exception. The boolean conversion itself does not call user code.

This report is limited to discarded negation statements. A consumed negation, an if condition, or a short-circuit operand still needs a runtime value. Treating every void value as undefined would be unsafe: a callback typed as returning void can return a value at runtime. TypeScript and JavaScript projects that explicitly request type checking should retain their diagnostics.

In the current CLI application entry, five of seven diagnostic sites are this discarded-banner pattern. Removing that refusal exposes two separate late-var require() restrictions; it does not make the full CLI compile yet.