Create an unusually complete desktop operating-system simula...

Prompt

Create an unusually complete desktop operating-system simulation as a single self-contained HTML file. Treat this as a one-shot software-engineering benchmark, not a visual mockup challenge. Return only the finished index.html in one code block. Do not include explanation, pseudocode, TODO comments, placeholders, fake screenshots, or descriptions of functionality that has not been implemented. HARD CONSTRAINTS * One HTML file only. * Vanilla HTML, CSS, and JavaScript. * No frameworks. * No external libraries. * No network requests. * No external assets. * Must run directly from a local file in Chrome/Edge/Firefox. * Use localStorage and/or IndexedDB for persistence. * Every major application described below must perform meaningful operations. An application that merely opens a decorative window does not count. * Features must share underlying system state rather than being disconnected demonstrations. DESKTOP ENVIRONMENT Build a polished desktop environment containing: * boot sequence; * login screen; * desktop; * wallpaper; * icons; * dock or taskbar; * launcher/start menu; * notification area; * clock/calendar; * quick settings; * notifications; * context menus; * keyboard shortcuts. WINDOW MANAGER Implement a real window manager supporting: * open; * close; * minimize; * maximize; * restore; * focus; * z-order; * dragging; * resizing from edges/corners; * snapping to screen edges; * multiple simultaneously visible windows. Applications must retain their internal state while minimized. VIRTUAL FILE SYSTEM Implement a persistent virtual hierarchical filesystem. Support: * folders; * text files; * JSON files; * simple image documents created by the paint application; * create; * rename; * duplicate; * move; * delete; * trash; * restore from trash; * file metadata; * sorting; * search. Changes must immediately become visible to every relevant application. Persist the filesystem across browser refreshes. FILE MANAGER Create a functional graphical file manager with: * folder navigation; * breadcrumbs; * list and icon views; * selection; * double-click opening; * rename; * create folder; * delete; * drag-and-drop or equivalent move operation; * sorting; * search. TEXT EDITOR Create a multi-document text editor. Implement: * open files from the virtual filesystem; * edit; * save; * Save As; * unsaved-change indicator; * line/character statistics; * find and replace; * basic keyboard shortcuts; * multiple open documents or tabs. TERMINAL Implement an interactive terminal backed by the SAME virtual filesystem. At minimum provide working versions of: help clear pwd ls cd mkdir touch cat echo write cp mv rm tree find date whoami history open Commands that modify files must immediately affect the graphical File Manager. Commands that open supported files should launch the appropriate graphical application. PAINT APPLICATION Implement a usable paint program using Canvas. Support: * drawing; * eraser; * color; * brush size; * line tool; * rectangle; * ellipse; * undo; * redo; * clear; * save document into the virtual filesystem; * reopen saved artwork later. CALCULATOR Implement: * ordinary arithmetic; * parentheses; * keyboard input; * calculation history; * several scientific functions. SYSTEM MONITOR Display live simulated system information based on actual activity within the desktop simulation. Include: * running applications; * window count; * storage usage of the virtual filesystem; * uptime; * animated CPU/memory-style graphs. Allow terminating a running application from the process list. SETTINGS Provide settings that actually affect the environment: * wallpaper/theme; * dark/light mode; * accent; * clock format; * reduced motion; * desktop icon size. Persist settings. WEB BROWSER SIMULATOR Because network access is forbidden, create an internal offline browser application. Give it: * address/search bar; * tabs; * back/forward; * refresh; * bookmarks; * browsing history. Provide several internal pseudo-sites rendered from local data, such as: * documentation/wiki; * news; * weather simulation; * system manual; * an app store/catalog. Navigation and history must actually function. INTEGRATION REQUIREMENTS The important part of this challenge is cross-application integration. Examples that MUST work: 1. Create a text file in Terminal → it appears in File Manager. 2. Open that file in Text Editor → edit and save it → cat in Terminal shows the modified content. 3. Draw an image in Paint → save it → it appears in File Manager → double-clicking opens it again. 4. Delete a file → it enters Trash → restore it → it returns. 5. Change a theme in Settings → all currently open applications update. 6. Kill an application through System Monitor → its windows close. 7. Refresh the browser → persistent files and settings survive. POLISH Use a coherent original visual design rather than directly reproducing Windows or macOS. Include: * transitions; * hover/focus states; * icons made from CSS/inline SVG; * keyboard accessibility where practical; * subtle sounds via Web Audio if useful; * responsive handling for smaller screens. QUALITY REQUIREMENTS Do not create fake controls that do nothing. Do not use alert() as a substitute for an application. Do not pre-render fake terminal output instead of implementing commands. Do not represent the filesystem merely as visible HTML items; use a coherent data model. Do not intentionally pad the code with useless repetition, but do not shorten the implementation by dropping requested functionality. Use the available response budget aggressively for complete implementation. Before producing the final answer, mentally check the interactions between applications and correct obvious inconsistencies. OUTPUT Return ONLY one complete executable HTML document in a single code block.

A system prompt was added to support web rendering