lfcode: Instructions file for Codex

• To regenerate the JavaScript SDK, run bun run --cwd packages/sdk/js build.
• The default branch in this repo is dev.
• Local main ref may not exist; use dev or origin/dev for diffs.
• Treat .codex/*.md plans as execution-tracking documents, not just notes: before starting plan-scoped work, read the referenced plan and respect its current Status:.
• If the user asks for a plan first, or the task is being tracked in .codex/, create or update the relevant plan file before implementation starts and give it an explicit Status:.
• Keep the plan lifecycle synchronized with reality: use planned/pending before execution, switch to in_progress once implementation actually starts, and leave it non-completed if work is only partially done or verification is still missing.
• When implementing a task from a plan under .codex/, update that plan in the same change flow: adjust scope/details if they changed, record any remaining gaps, and mark the plan's Status: as completed only after the task is fully implemented and verified.
• When a .codex/ plan is completed and its changes affect the desktop app, runtime, settings, MCP/tools, or other behavior the user is expected to test locally, finish the same flow with the pre-release package/sync lane below; do not touch the production use-copy unless the user explicitly asks to “同步到使用版” or “更新使用版”.
• Keep .codex/*.md reserved for plans and execution tracking. Store standalone HTML design mockups, visual replicas, and reviewable static UI drafts under .codex/design-html/ instead of output/ or scattered temp locations.
• When creating a design draft in .codex/design-html/, prefer a self-contained .html file with inline CSS/assets when practical so it can be opened and reviewed directly without extra build steps.

Project Structure

• This repo is a Bun workspace monorepo rooted at package.json.
• Most product code lives under packages/.
• The core runtime and session engine live in packages/lfcode.
• The web UI lives in packages/app, and the Electron host lives in packages/desktop.
• Shared packages such as packages/ui, packages/plugin, packages/sdk/js, packages/shared, and packages/script support the app/runtime layers.
• Cross-repo specs live in specs/.
• User-local project config and content under the repo root belong in .lfcode/ (agent/, command/, skills/, themes/, plugins/, tool/, glossary/, plus opencode.jsonc and tui.json).
• App settings surfaces now include packages/app/src/components/settings-skills.tsx and packages/app/src/components/settings-archives.tsx; skill-management and archive changes should be validated through those settings views, not only through server routes.
• Instance-side skill APIs live under packages/lfcode/src/server/routes/instance/skills.ts; when changing local skill import, discovery, hiding, or deletion flows, keep the app settings UI and this route in sync.