Instrument the command-line LLM summarizer

Instrumentation should explain behavior without collecting the raw material unnecessarily. For this artifact, record enough to calculate contract-test pass rate, latency, retry count, output length, and success on a small fixed prompt set. Include version or configuration identifiers so two runs can be compared. A log line is useful only if it answers a debugging question; dumping entire inputs creates noise and may create a privacy problem.

The artifact's user-facing goal is specific: send one system message and one user message through an HTTP-shaped client and return a bounded one-sentence summary. Its accepted input is a non-empty text string, model name, timeout, and API key loaded from the environment. Those statements are intentionally narrower than “build an AI system.” Narrow scope lets us inspect every input and expected result, and it prevents a toy result from being presented as a production claim. The sample emits a compact metric record that a test or dashboard could aggregate.

Save this as lesson.js and run node lesson.js. It uses only the language standard library, so the example is reproducible offline.

const event={ok:true,latency_ms:84,retries:0,model:'demo',input_chars:42};
console.log(JSON.stringify(event)); if(event.latency_ms>1000) process.exitCode=1;

Expected output: one JSON metrics event. Exact floating-point formatting may vary slightly, but the asserted behavior must not. Read the output as evidence about this stage, not merely proof that the interpreter started.

Separate request construction, transport, and response parsing. Test each with a fake transport before contacting a provider. For a malformed response, print the status and safe structural fields, never the API key or full prompt. Retry only explicit transient statuses such as 429, cap attempts, and preserve the final error. A missing choices array is a contract failure, not an empty successful summary.

At the testing and observability stage, save the smallest failing fixture beside the expected result. Change one cause at a time and rerun the exact command printed above; that makes the repair reviewable and keeps this chapter's progressive artifact reproducible.

Run a fixed set of short prompts through the fake contract and, when credentials are intentionally available, through the real adapter. Measure latency, retries, output length, and whether the one-sentence constraint holds. Save expected properties rather than exact prose because model wording can vary. Contract tests must remain deterministic and runnable offline.

For this testing and observability page, preserve the fixture and result as evidence for the next page. Label observations separately from conclusions: a passing assertion establishes the behavior it names, while broader usefulness requires the chapter's full evaluation set and stated operating limits.