[2217173240]

Settings sheets with fixed minimum widths clipped content on phones. Make the model, agent and tool sheets fill narrow viewports, stack the skills panes with a scrollable file tree and usable editor, and allow traffic headers to wrap. Preserve desktop sizing and existing application actions.

Fix the documented local Docker preparation command for fresh checkouts and repeated copies. Keep scratch artifacts ignored while project documentation and frontend shell scripts remain eligible for tracking; contributor guidance retains source attribution and reflects the completed archive cleanup.

Pin Next.js to 16.4.1 and synchronize its lockfile packages to address GHSA-2464-fhr4-w9xw, GHSA-p3m5-59mp-jv5r and GHSA-673q-mjm6-r5xr. This is the common minimum patched release; the resolved Sharp dependency is 0.35.5.

Sources: jubeater's RuoJi6/ARTEX PR37, 303620638f03c3df27afed82714bb10ddf698d62, and xingchuan / chu0119's mobile layout commit, both AGPL-3.0. These are adaptations to current components; the mobile source's common Git ancestry remains unverified. Attribution and adoption boundaries are recorded in docs/fork-integrations.md.

Validation:

• Actual filesystem execution covers missing directories, repeated replacement, hidden/nested assets and output directory structure.
• Chromium with the existing local synthetic-data UI at 390×844 and 1280×800: complete phone settings panels, preserved desktop widths, an expanded skills tree with an actual wheel scroll and a 354px mobile editor.
• TypeScript, dependency audit (zero reported vulnerabilities) and git diff --check pass locally. Git ignore inclusion/exclusion cases and tracked-file eligibility checked.
• Independent review passes the responsive layout and dependency patch. Targeted Biome retains existing diagnostics; this PR does not claim a clean lint audit.
• GitHub quality and CodeQL checks must pass against the final PR HEAD before merge.

Browser verification covers layout using synthetic data; live backend, model and real-target behavior are outside that verification. Useful dependency/build caches remain available.