refactor(ui): standardize general-purpose icons on Lucide

[kev1n77]

Summary

• Standardize general-purpose icons on Lucide across the Web UI, mobile web, MiniApp and skin markets, installer, and shared component library.
• Preserve the original artwork for the four harness modes, Git branch, logos, mascots, and device overview.
• Remove unused icon assets and update design system documentation, localized descriptions, and tests.
• Add generation and consistency checks for static startup and form icons.

Type and Areas

Type: Refactor / UI/UX

Areas: Web UI, mobile web, installer, MiniApp market, skin market, design system, docs, dependencies.

Motivation / Impact

The interfaces previously mixed custom SVGs, raster icons, and multiple icon libraries. Using Lucide consistently gives general-purpose controls a shared visual style and reduces duplicated asset maintenance.

Existing named icon aliases remain available to component consumers. Distinctive product and device artwork is preserved.

Verification

Completed during implementation:

• pnpm run check:web — passed, including TypeScript and appearance governance checks.
• pnpm run theme:color-audit:all — all 23 selected surfaces passed.
• pnpm --dir src/web-ui run icons:check — passed.
• pnpm --dir src/web-ui run test:run src/app/components/NavPanel/components/DeviceStatusControl.test.tsx src/infrastructure/design-system/IconUsageIntegration.test.tsx src/app/startup/startupPreload.test.ts — 24 tests passed.
• git diff --cached --check — passed before committing.

Manual visual checks and live remote scenario validation were not performed.

Reviewer Notes

• Changes are limited to Web/React surfaces; native mobile clients are outside this migration.
• Device overview retains its original computer/server SVGs and MacBook image.
• The mobile color baseline was lowered after removing an unused SVG asset.
• No persisted data or wire protocol changes are introduced.

Checklist

• This PR is focused and does not include secrets, temporary prompts, generated scratch files, or unrelated artifacts.
• Relevant verification is recorded above, or skipped checks are explained.
• User-facing strings, docs, and locales are updated where applicable.