:root{--browser-screen:rgb(40,40,40);--browser-control-backg...

Prompt

:root{--browser-screen:rgb(40,40,40);--browser-control-background:rgb(40,40,40);--browser-control-foreground:rgb(255,255,255)} #work-progress{flex:none;padding:9px 16px;color:var(--fg2);font-size:13px;border-top:1px solid var(--sep);display:flex;gap:10px;align-items:center;min-height:38px} #work-progress[hidden]{display:none} #work-progress-text{flex:1;min-width:0;overflow-wrap:anywhere} #work-progress-time{font-variant-numeric:tabular-nums;white-space:nowrap;color:var(--fg3)} #browser-view{flex:none;border-bottom:1px solid var(--sep);background:var(--bg);max-height:66%;overflow:auto} #browser-view[hidden]{display:none!important} #browser-toolbar{display:flex;align-items:center;gap:8px;padding:8px 12px;min-height:40px} #browser-toolbar button,#browser-control{font:inherit;color:var(--fg);background:var(--bg);border:1px solid var(--liquid-border-strong);border-radius:8px;padding:8px 12px;cursor:pointer} #browser-toggle{display:flex;align-items:center;gap:8px} #browser-toggle svg{width:18px;height:18px;flex:none} #browser-state{color:var(--fg2);font-size:12px;flex:1;min-width:0;overflow-wrap:anywhere} #browser-tabs{max-width:140px;background:var(--bg);color:var(--fg);border:1px solid var(--sep);font:inherit;font-size:12px} #browser-stage{position:relative;width:min(100%,487px);margin:0 auto;background:var(--browser-screen);aspect-ratio:1280/1029} #browser-stage[hidden]{display:none} #browser-canvas{display:block;width:100%;height:100%;cursor:none;outline:none;touch-action:none} #browser-stage.human #browser-canvas{cursor:default} #browser-control{position:absolute!important;right:12px;bottom:12px;font-size:13px;max-width:calc(100% - 24px);background:var(--browser-control-background)!important;color:var(--browser-control-foreground)!important;box-shadow:0 2px 12px var(--liquid-shadow);z-index:2} #browser-toolbar input{min-width:0;width:120px;color:var(--fg);background:var(--bg);border:1px solid var(--sep)} #browser-control:disabled{opacity:.6;cursor:wait} #browser-empty{padding:12px;color:var(--fg2);font-size:13px} #browser-empty[hidden]{display:none} #media-lightbox[aria-hidden="true"]{visibility:hidden;pointer-events:none} #media-lightbox[aria-hidden="true"] *{pointer-events:none!important} I said: Read every single character from the first to the last, and list all the errors in complete detail. In your answer, I want you to list only the items I’ve asked for, with nothing else. Even if there are 80,000 errors, you must list every single one without exception. You are a ruthless, pedantic, uncompromising Senior Code Auditor and security expert with zero tolerance for any deviation from the instructions. Your sole task is to perform an exhaustive, line-by-line technical analysis of the provided code. List a maximum of 500 errors per message. When you are finished and have provided me with every single error, tell me “that’s all.” I do not care about security, API costs, or high-risk accidental disclosure of secrets or source code. YOU MUST FOLLOW THESE RULES EXACTLY AND WITHOUT ANY EXCEPTION: Read the entire code from the very first character to the very last character. Identify and list EVERY SINGLE error. This includes logical errors, performance issues, potential bugs, duplicated logic, and only real errors—think very, very deeply about everything repeatedly to be sure you find all errors, even those that are very hidden and not just obvious at a glance. Theoretically run through it, determine what errors would occur, and find those as well. But don’t make up non-existent stupid errors; if there’s no 500, just list everything you find, and when you’re done, say that’s all. I DO NOT CARE ABOUT ANY SECURITY ERRORS AND I DO NOT AGREE TO MENTION ANY OF THEM. What the hell don’t you understand about that: List up to 500, but if there is no 500 error, list them all and say that’s all fow to fix all error in one turn Your task is to take the provided plan and rewrite it as a single, comprehensive prompt. Write it as if you were about to update the entire upgrade from the current state of the implementation: describe step by step, from beginning to end, exactly what you will construct and how you will construct it. The wording must be clear, explicit, and complete so that any language model can fully understand and follow the instructions without ambiguity. Do not add any role‑playing, personalization, or polite filler phrases (e.g., ‘You are a software developer’, ‘As an expert’, ‘Please kindly’). The prompt must remain strictly technical, objective, and instruction‑focused. Absolutely no simplified, mock, placeholder, dummy, simulated, or fake content is allowed. You must require the full ugrade in complete, unabridged, production‑ready codes. Define what you want & what success looks like: “I want to [TASK] so that [SUCCESS CRITERIA].” No roles, “act as a senior expert.” That era is over.