Initialize Development Environment

[kochizufan]

Quyuan: Initialize Development Environment

Project: [OpenSpec: Standardize Quyuan & Chuci]
Implementation Proposal: standardize-quyuan-chuci
Target Repository: code4history/Quyuan

Proposed Changes

1. Package Management:

   • Ensure pnpm (v9+) is used.
   • Remove package-lock.json if present.

2. Build System:

   • Initialize/Update to Vite 6 (LTS).
   • Configure Vitest 3 for testing.

3. Linting:

   • Install ESLint 9.
   • Setup eslint.config.js (Flat Config).

Rationale

Aligning with Maplat Harmony standard development environment.

[kochizufan]

Regarding Git Hooks (husky/lint-staged):

Consistent with the decision for Chuci (Ref: MaplatHarmony#3), we will NOT adopt \husky\ and \lint-staged\ for Quyuan either.

Reasoning:

1. Windows Friction: Avoiding potential execution policy issues and flakiness on Windows.
2. Migration Efficiency: Preventing Pre-commit hooks from blocking progress during the initial migration/standardization phase.

Action: Please rely on CI (GitHub Actions) for linting and formatting checks instead of enforcing them via local git hooks.

[kochizufan]

CORRECTION & DETAILED REQUIREMENTS (Ref: MaplatHarmony#3)

Please disregard previous incomplete instructions. Here is the definitive list of requirements based on Issue #3 feedback:

1. Repository & Branching

• Default Branch: Must be *\master* (not \main, not \dev). Unify all repos to \master.

2. Build & Output (\dist)

• CommonJS: REMOVE it.
• Types: Ensure *\d.ts* files are generated and included.
• Clean Output: \dist/\ should NOT contain dev-server artifacts; only the clean library build.

3. Dev Server & GH Pages

• Dev URL: \http://localhost:5173/\ should work (no 404).
• GH Pages: Content matches \pnpm dev.
• Deployment Rule: Deploy to \gh-pages\ ONLY on pushes to **\master**.

4. CI/CD (GitHub Actions)

• Triggers: Run on ALL commits (test, lint, typecheck, build).
• Node Versions: Test on Node 20 and 22.
• Linting: Use CI for enforcement.