fix: replace Vite ?raw imports with readFileSync for Node.js compatibility

[Dubworx]

Summary

• Replaces Vite-specific ?raw imports in packages/core/src/frames/index.ts and packages/core/src/design-skills/index.ts with fs.readFileSync, enabling @open-codesign/core to be imported from Node.js/tsx contexts (e.g. headless CLI scripts) without Vite running
• Adds "type": "module" to root package.json to support ESM top-level await in scripts that import from the core package

Problem

The ?raw import suffix is a Vite-only feature. When importing @open-codesign/core from a plain Node.js/tsx script (such as the headless scripts/clone-from-dna.ts or scripts/extract-dna.ts), the import chain fails with:

SyntaxError: The requested module './android.jsx?raw' does not provide an export named 'default'

This blocks any headless/CLI usage of the core generate() function outside of the Vite dev server or Electron app context.

Approach

Replaced all ?raw imports with a readFileSync helper that resolves paths relative to import.meta.url. This works in both:

• Vite context (Electron app / dev server) — Vite's Node.js compat handles readFileSync fine
• Plain Node.js/tsx — standard fs module, no bundler needed

Files Changed

File	Change
package.json	Added "type": "module"
packages/core/src/frames/index.ts	?raw → readFileSync for 5 frame JSX files
packages/core/src/design-skills/index.ts	?raw → readFileSync for 12 skill JSX files

Test plan

• pnpm dev — Electron app starts and renders designs normally
• pnpm build — Production build succeeds
• npx tsx scripts/clone-from-dna.ts --help — CLI script imports core without errors
• npx tsx scripts/extract-dna.ts --help — CLI script imports core without errors
• Frame templates and design skills load correctly in both contexts

🤖 Generated with Claude Code

[github-actions]

Findings

• [Major] Runtime readFileSync() here breaks packaged desktop builds. FRAME_TEMPLATES and DESIGN_SKILLS are imported by the Electron main process (apps/desktop/src/main/index.ts:9, apps/desktop/src/main/index.ts:296), but packaging only ships out/** plus package.json (apps/desktop/electron-builder.yml:15). Replacing ?raw with readFileSync(resolve(__dirname, name)) (packages/core/src/frames/index.ts:19, packages/core/src/design-skills/index.ts:17) means the packaged app now expects the .jsx source files to exist next to the bundled JS, and the current electron-vite build does not emit or copy them (apps/desktop/electron.vite.config.ts:12). That turns a packaged app import into an ENOENT on the first frame/skill load.
  Suggested fix:

  // Keep these starter assets bundled into JS until there is a dual-path
  // solution that also emits/copies the companion .jsx files for packaged builds.
  import iphoneJsx from './iphone.jsx?raw';
  import ipadJsx from './ipad.jsx?raw';
  // ...apply the same revert for the rest of the frame and skill starters

• [Minor] website/public/llms.txt now points to a plan file that is not in the public checkout. website/public/llms.txt:79 references docs/v0.2-plan.md, but that file is not present, and AGENTS.md:16 explicitly says docs/** is mostly maintainer-local. That leaves public readers and LLM consumers with a dead source reference.
  Suggested fix:

  See the [roadmap](/roadmap) for the milestone plan.

Summary

• Review mode: initial
• 2 findings. The main risk is a packaged-desktop regression from swapping bundled starter assets for runtime filesystem reads.
• Existing tests cover starter contents, but I did not find a regression test for the plain-Node import path claimed in this PR or a packaged Electron smoke path.

Testing

• Not run (automation). pnpm is not installed in this runner, so I could not execute the repo test suite.

open-codesign Bot

[github-actions]

[Major] This replaces build-time inlining with a runtime readFileSync, but the packaged desktop app only ships out/** and package.json (apps/desktop/electron-builder.yml:15-17). Because the main process imports FRAME_TEMPLATES / DESIGN_SKILLS (apps/desktop/src/main/index.ts:9-10, apps/desktop/src/main/index.ts:296-300), packaged builds will now look for iphone.jsx-style source files next to the bundled JS and hit ENOENT.

Suggested fix:

import iphoneJsx from './iphone.jsx?raw';
import ipadJsx from './ipad.jsx?raw';
// ...keep the starter bodies bundled until there is a dual-path
// solution that also emits/copies the .jsx assets for packaged builds

[github-actions]

[Minor] docs/v0.2-plan.md is not in the public checkout, and AGENTS.md says docs/** is mostly maintainer-local. This leaves a dead public reference.

Suggested fix:

See the [roadmap](/roadmap) for the milestone plan.