LAB12 — Repair an interface proposal

Start CP04 in a fresh exercise folder. Suggested time: 45 minutes. Read Chapter 12 and the primary links in the project hardware reference. Physical hardware is optional and no assembly is required.

Review this flawed proposal: “Any Feather ESP32-S3 variant has equivalent build settings. The BME280 is already populated because a footprint appears in the board guide. A breakout input allowance is the bare chip supply limit. Use the address from another project. A 1000 ms interval means 1000 seconds. A passing host replay validates wiring and accuracy.”

Mark each claim supported, contradicted, or not established. Attach the applicable source section or explicit unit conversion. Write a corrected two-paragraph proposal, a four-to-six-row constraints table, and a connector-level plan labeled documentation-based and physically unverified. Preserve object identity, units, conditions, and meaningful unknowns.

List the evidence needed to resolve the remaining physical revision, address configuration, and optional initialization questions. Do not fill missing pins or aliases from memory. If using the constraints skill, retain its actual response and separately review its facts; a manual source check is not a model-behavior pass.

Submit the reviewed proposal, table, plan, source record, and limitations. Recovery route: preserve a confusing edit and re-extract CP04 into a new folder. The worked explanation and review answers are in Chapter 12; the next chapter uses this plan to keep synthetic software changes bounded.