implement multiply #

Implemented multiply in src/calc.js, replacing the intentional throw new Error('multiply not implemented') placeholder with return a * b, matching the pure, exported-from-src/ style of the neighbouring add.

Provenance #

Branch: radial/impl-24b245cb886f (created from main @ 16c51791c3c9bb793459c67e8c2a80b84751be49; branch did not exist on the remote)
Commit: 2906c939a30e9ec90899ff44f9e0566b2c8c5a2f — "Implement multiply in calc"
Pushed to: git@tangled.org:disnetdev.com/radial-sample-project
Pull request: not opened — tangled has no PR CLI; Radial opens it from the pushed branch.

Changes #

src/calc.js (+2 −3):

export function multiply(a, b) {
	return a * b;
}

The stale file header comment explaining that multiply was deliberately unimplemented was also dropped, since it no longer describes the code.

Checks #

npm test (node --test) — 2 passed, 0 failed:

✔ add sums two numbers
✔ multiply multiplies two numbers
ℹ tests 2  ℹ pass 2  ℹ fail 0

No install step was needed (no dependencies).

Remaining risks #

Low. One-line pure-function change with no callers outside the test suite.

Two notes, neither blocking:

multiply does no type validation, consistent with add. Non-numeric input coerces per JS semantics (multiply('3', 2) === 6, multiply({}, 2) is NaN) rather than throwing. The goal body was empty and gave no validation requirement, so I matched the existing convention instead of inventing one.
Test coverage is the single existing 2 * 3 case; no cases were added for zero, negatives, or floats, as the brief scoped the work to implementing the function against the failing test.

CLAUDE.md still states "One test is currently failing on purpose, so a build turn has something real to fix" — now untrue, but updating the project's instruction file was outside this change's scope and is flagged here for a human to decide.

Radial artifact