Project Operating Model

Project Operating Model

Purpose

This model keeps LessJS release work grounded in verified repo state.

The GitHub issue tracker owns execution. GitHub Projects owns planning views and status.

Source Of Truth

Layer	Source
Audit baseline	docs/conversation/20260601/LessJS-审计-校准版-0.27.x-to-1.0.md
Roadmap tracker	#30
Project board	LessJS v0.27.x to v1.0
Version buckets	GitHub milestones
Work items	GitHub issues
Gate evidence	issue comments and CI results

Issue Types

Use these prefixes in issue titles:

• core: renderer, DSD, VNode, event hydration, middleware types.
• www: docs-site shell, search, theme, i18n, sidebar, SEO.
• router: SPA routing and navigation behavior.
• runtime: public authoring facade and export contract.
• protocols: shared build contracts.
• ci: GitHub Actions, Playwright, publish gates.
• security: permissions, token handling, XSS/trust boundaries.
• perf: SSR bundle, client chunks, HTML budgets, route/content cache.
• docs: guides, ADR/SOP, migration docs.

Priority Model

Priority	Meaning	Closure rule
P0	Blocks release or can break core user workflows	Must have regression test and green gate
P1	Important stability, architecture, security, or DX debt	Must have focused test or documented verification
P2	Cleanup, docs, non-blocking ergonomics	Can close with review and lightweight verification

Project Fields

Field	Values
Work Status	Backlog / Ready / In Progress / In Review / Done / Blocked
Release	v0.27.1 / v0.27.2 / v0.27.3 / v0.27.4 / v0.28.0 / v0.29.0 / v0.30.0 / v1.0.0
Area	core / router / runtime / protocols / www / ci / security / performance / docs / architecture / adapter-vite
Priority	P0 / P1 / P2
Gate	typecheck / test / build / e2e / release / graph / docs
Target Date	milestone target date

Recommended Views

View	Group by	Filter
Release Train	Release	open issues
P0 Burn-down	Work Status	Priority = P0
Area Ownership	Area	open issues
Gate Readiness	Gate	Work Status != Done
v1.0 Blockers	Priority	Release = v1.0 or Priority = P0

Release Gate Rules

v0.27.x Patch Releases

Required:

• deno task typecheck
• focused tests for touched packages
• deno task test
• deno task build
• E2E subset for touched docs-site surface

Minor Releases

Required:

• all patch release gates
• deno task graph:check
• deno task docs:check-current
• deno task dist:check-object-object
• full deno task test:e2e or explicit documented exception

v1.0

Required:

• all minor release gates green
• API surface frozen
• migration guide complete
• compatibility matrix complete
• 7 days without a P0 regression after RC

Triage Rules

1. Reproduce from the repo before changing roadmap priority.
2. If docs and code disagree, update docs or issue text immediately.
3. If a P0 is fixed without a test, keep the issue open.
4. Do not close a milestone while any gate issue is still red.
5. Keep architecture changes framework-level unless there is a measured reason to accept local www workaround code.