@hongmaple0820/med-scale-research-os 0.43.0

package/docs/start/workflow-upgrade.md

@@ -0,0 +1,198 @@
+# SCALE 工作流升级指南
+
+本文是已有仓库安装、更新、适配 SCALE 工作流资产的短路径。
+
+适合三类人：
+
+| 角色 | 关注点 |
+| --- | --- |
+| 项目维护者 | 如何把 SCALE 接入已有仓库，并避免覆盖本地规则 |
+| 普通开发者 | 拉取仓库后如何检查或安装正确的 SCALE 版本 |
+| Agent 使用者 | 哪些步骤可以命令化，哪些必须人工或 Agent 审阅 |
+
+## 哪些可以自动化
+
+SCALE 把更新分成三层：
+
+| 层级 | 命令支持 | 默认行为 |
+| --- | --- | --- |
+| SCALE CLI | `npm install -g @hongmaple0820/scale-engine@latest` | 用户显式安装或升级 |
+| 生成的工作流文件 | `scale upgrade check/plan/apply/rollback` | 先安全检查和生成计划；干净的受管文件可自动刷新，有本地改动则进入人工审阅 |
+| 项目级验证 | 仓库 `make` 目标和 `scripts/workflow/*` | 必须保留项目语义；SCALE 不猜业务路由、凭据和服务拓扑 |
+
+这意味着工作流适配不是 Codex-only。Codex 可以帮助审阅和处理 `manual-review`，但常规路径应该是命令驱动。
+
+## 首次安装
+
+```bash
+npm install -g @hongmaple0820/scale-engine
+scale --version
+```
+
+已有项目可以用交互式初始化选择最接近的 governance pack：
+
+```bash
+scale init --interactive
+```
+
+也可以直接指定：
+
+```bash
+scale init --governance-pack standard
+scale init --governance-pack project-scaffold
+scale init --governance-pack scale-engine-repo
+scale init --governance-pack moe-workspace
+scale init --governance-pack go-service-matrix
+scale init --governance-pack node-library
+scale init --governance-pack frontend-app
+```
+
+不确定时先用 `standard`。仓库形态明确时再用更具体的 pack。`scale-engine-repo` 是 `scale-engine` 仓库自身的自托管 pack，不是普通业务仓库默认选项。
+
+## 更新已有工作流
+
+默认使用升级向导：
+
+```bash
+scale upgrade --dir .
+scale preflight --dir . --service all --preflight-profile quick
+```
+
+向导会生成计划和 HTML 报告；如果计划可安全应用，会在交互式终端询问是否立即应用。需要 CI 或精确控制时，再使用分步命令：
+
+```bash
+scale upgrade check --dir .
+scale upgrade plan --dir . --html
+scale upgrade apply --dir . --confirm
+scale preflight --dir . --service all --preflight-profile quick
+```
+
+如果升级计划提示 AI OS runtime 尚未接入，优先使用一键接入命令。它会创建运行态目录、生成首个 `dry-run` 运行报告、写入 benchmark，并用 doctor 复核就绪状态：
+
+```bash
+scale ai-os adopt \
+  --dir . \
+  --task "接入 AI OS runtime 并生成首份治理证据" \
+  --files "README.md,AGENTS.md" \
+  --lang zh
+```
+
+接入完成后会写入 `.scale/ai-os/adoption.json`。后续真实任务再使用 `scale ai-os run --mode guarded` 生成受治理的执行证据。
+
+默认输出是中文。需要英文命令提示或英文 HTML 计划时加 `--lang en`：
+
+```bash
+scale upgrade check --dir . --lang en
+scale upgrade plan --dir . --html --lang en
+```
+
+给人看的升级输出会使用当前语言生成下一步命令，例如中文场景会推荐 `scale ai-os adopt --task "接入 AI OS runtime" --lang zh`。只有脚本、CI 或 Agent 集成需要稳定结构时才使用 `--json`。
+
+如果仓库已有本地封装，优先使用本地命令，因为它们编码了项目默认值：
+
+```bash
+make workflow-upgrade-check
+make workflow-upgrade-plan
+make workflow-upgrade-apply
+make workflow-aios-adopt
+make workflow-upgrade-verify
+```
+
+回滚只撤回最近一次 SCALE 管理的安全应用：
+
+```bash
+scale upgrade rollback --dir .
+```
+
+## 如何读取结果
+
+| 结果 | 含义 | 下一步 |
+| --- | --- | --- |
+| clean | 生成的工作流集合和 lock 文件一致 | 运行项目级验证 |
+| missing | 生成文件缺失 | 通常可用 `apply --confirm` 恢复 |
+| updates-available | SCALE 版本、governance pack 或受管文件存在可应用更新 | 审阅计划，确认安全后应用 |
+| manual-review | 生成文件已有本地修改 | 检查 diff，不要自动覆盖 |
+
+`manual-review` 是有意设计。SCALE 不应该抹掉本地项目知识、服务命令或 Agent 规则。
+
+## 自动升级边界
+
+`scale upgrade apply --confirm` 现在覆盖三类安全场景：
+
+- 受管文件缺失：从当前 governance pack 恢复缺失文件。
+- SCALE CLI 版本变化：刷新 `.scale/governance.lock.json`，让项目记录当前 CLI 版本。
+- governance pack 版本变化：如果受管文件内容仍与 lock 哈希一致，自动刷新这些干净文件，让新模板、新门禁、新脚本和新文档入口落到旧项目。
+
+下面场景不会自动覆盖：
+
+- 文件相对 lock 已有本地改动。
+- 缺少 `.scale/governance.lock.json`，无法判断哪些文件由 SCALE 管理。
+- 第三方 skills、MCP、浏览器、桌面自动化或外部 CLI 需要新增、升级、执行安装脚本。
+
+这些情况会进入 `manual-review`，由维护者或 Agent 先看计划和 diff，再决定合并、保留本地改动，或重新初始化。
+
+## 项目级适配
+
+生成文件更新后，再按真实仓库适配这些文件：
+
+- `.scale/verification.json`: service matrix, required checks, optional UI or E2E checks.
+- `.scale/workspace.json`: branch model, protected branches, monorepo or workspace boundaries.
+- `AGENTS.md` and `CLAUDE.md`: short agent entry rules.
+- `docs/workflow/README.md`: human-readable workflow and verification commands.
+- Repository wrappers such as `Makefile` and `scripts/workflow/verify.ps1`.
+
+对 `netdisk-project` 这类多服务产品，不能把 `/health` 当作充分验证。验证必须覆盖本次变更影响的真实产品路径，例如 gateway 路由、`/api/v1/*` 请求、OAuth callback、存储驱动、UI 调用和数据持久化。
+
+## Agent 本地产物忽略规则
+
+工作流资产和团队协作规则可以提交；Agent 平台的本地状态、临时 worktree、缓存、日志和会话产物不应提交。已有项目接入或升级 SCALE 时，检查根 `.gitignore` 是否至少覆盖这些本地产物：
+
+```gitignore
+.claude/worktrees/
+.claude/tmp/
+.claude/local/
+.codex/worktrees/
+.codex/tmp/
+.codex-tmp/
+.cursor/tmp/
+.continue/
+.aider*
+.gemini/tmp/
+.omc/
+.roo/tmp/
+.cline/tmp/
+.windsurf/
+.playwright-mcp/
+```
+
+不要为了省事直接忽略所有协作配置目录。像 `AGENTS.md`、`CLAUDE.md`、`.cursor/rules/`、团队共享的 `.claude/settings.json`、`.scale/governance.lock.json` 这类稳定规则可以进入版本库。
+
+## 推荐仓库封装
+
+接入 SCALE 的仓库建议暴露这些命令：
+
+```makefile
+workflow-upgrade-check:
+	scale upgrade check --dir . --lang zh
+workflow-upgrade-plan:
+	scale upgrade plan --dir . --html --lang zh
+workflow-upgrade-apply:
+	scale upgrade apply --dir . --confirm --lang zh
+workflow-upgrade-rollback:
+	scale upgrade rollback --dir . --lang zh
+workflow-upgrade-verify:
+	scale preflight --dir . --service all --preflight-profile quick
+workflow-aios-adopt:
+	scale ai-os adopt --dir . --task "$(TASK)" --files "$(FILES)" --level "$(LEVEL)" --budget "$(BUDGET)" --lang zh
+```
+
+如果 Windows 环境没有 `make`，提供等价 PowerShell 脚本，或在文档里写清原始 `scale` 命令。
+
+## 完成检查
+
+- `scale --version` 输出预期版本。
+- `scale upgrade check --dir .` 没有非预期 drift。
+- 有变更时，`scale upgrade plan --dir . --html` 能生成可审阅计划。
+- `scale upgrade apply --dir . --confirm` 只在审阅计划后使用；干净受管文件可自动刷新，本地改动必须人工审阅。
+- 项目级验证通过，或记录清楚已知失败。
+- `README.md`、`AGENTS.md`、`CLAUDE.md`、`docs/workflow/README.md` 指向同一组工作流命令。

package/docs/workflow/GATES_AND_SCORE.md

@@ -0,0 +1,89 @@
+# Gates and Task Score
+
+This document records the first deterministic optimization layer for gate visibility, architecture conformance, and task scoring.
+
+## Gate Status
+
+Use `scale gates status` to inspect the active gate catalog.
+
+```bash
+scale gates status --json
+```
+
+The report separates four concepts that were previously easy to confuse:
+
+- Core gates: `G0-G8`, used by workflow verification, preflight, and product smoke profiles.
+- Meta-governance gates: `G9-G15`, used by `scale meta-governance`.
+- Enhanced gates: `G16-G22`, covering commit discipline, doc hygiene, runtime evidence, code review, supply chain, context budget, and session health.
+- Extension gates: policy-backed checks such as engineering standards, product smoke policy, and tool evidence.
+
+`scale gates status` is intentionally read-only. It does not execute checks; it explains which checks exist and which policies are blocking.
+
+## Architecture Standards Gate
+
+Architecture and engineering standards are driven by project configuration:
+
+- `.scale/verification.json` controls whether `engineeringStandardsGate` is `off`, `warn`, or `block`.
+- `.scale/engineering-standards.json` controls standards rules and baselines.
+- `.scale/frameworks.json` records project-specific framework and architecture conventions.
+
+Preflight now uses changed-file standards scope when the target is inside a Git worktree. Non-Git projects keep the old full-scan behavior so bootstrap and fixture projects still get complete feedback.
+
+## Enhanced Gates (G16-G22)
+
+Added in v0.41.0, these gates cover commit discipline, runtime quality, and session hygiene:
+
+| Gate | Name | Blocking | Description |
+| --- | --- | --- | --- |
+| G16 | Commit Discipline | ✅ | Uncommitted file count (warn=10, block=25), time since last commit (warn=60min, block=180min), staged files >1MB, whitespace errors |
+| G17 | Documentation Hygiene | — | Changed markdown files must have valid internal links |
+| G18 | Runtime Evidence | ✅ | Task must have recorded runtime evidence with matching exit codes |
+| G19 | Code Review | ✅ (L/CRITICAL) | L and CRITICAL tasks require reviewed changes with resolved findings |
+| G20 | Supply Chain | ✅ | No CRITICAL/HIGH vulnerabilities; lock file must be consistent |
+| G21 | Context Budget | — | Advisory check on context token usage against configured budget |
+| G22 | Session Health | — | Advisory check on stale worktrees and session state consistency |
+
+Run enhanced gates individually:
+
+```bash
+bash scripts/gates/G16-verify.sh   # Commit Discipline
+bash scripts/gates/G17-verify.sh   # Documentation Hygiene
+bash scripts/gates/G18-verify.sh   # Runtime Evidence
+bash scripts/gates/G19-verify.sh   # Code Review
+bash scripts/gates/G20-verify.sh   # Supply Chain
+bash scripts/gates/G21-verify.sh   # Context Budget
+bash scripts/gates/G22-verify.sh   # Session Health
+```
+
+Or run all gates including enhanced:
+
+```bash
+bash scripts/gates/all.sh --all
+```
+
+## Task Score
+
+Use `scale score task` to produce an algorithmic completion score.
+
+```bash
+scale score task --changed --json
+scale score task --task-id TASK-123 --level L --changed-files src/api/foo.ts,src/workflow/bar.ts
+```
+
+The score is computed from evidence, not from a model:
+
+- Verification: recent gate pass rate.
+- Architecture standards: deterministic standards doctor result.
+- Evidence completeness: persisted gate evidence records.
+- Context and memory: CodeGraph/code intelligence readiness and memory provider readiness.
+- Cost efficiency: governance ROI and cache/context savings.
+- Risk control: task level, blocking standards, and blocking extension gates.
+
+Default thresholds:
+
+- `S`: 65
+- `M`: 75
+- `L`: 85
+- `CRITICAL`: 90
+
+Use `--warn-only` when the score should be reported without failing the command.

package/docs/workflow/PROMPT_OPTIMIZATION.md

@@ -0,0 +1,44 @@
+# Prompt Optimization
+
+`scale prompt optimize` is the deterministic pre-execution prompt rewrite layer for coding tasks. It turns a raw user instruction into a structured, professional, executable prompt before the workflow asks an agent to plan or implement.
+
+## Why It Exists
+
+- Reduce model ambiguity before expensive model calls.
+- Preserve the user's real intent instead of inventing a new requirement.
+- Add missing execution structure: objective, context, boundaries, acceptance criteria, validation, deliverables, and risks.
+- Make `scale define` start from a higher-quality requirement, so downstream planning and verification have clearer input.
+
+## CLI
+
+```bash
+scale prompt optimize --input "Build a CLI prompt optimizer that rewrites raw coding requests" --json
+```
+
+Useful options:
+
+- `--language auto|zh|en`: choose output language. `auto` detects Chinese vs English.
+- `--title "Prompt Optimizer"`: add a task title to the optimized objective.
+- `--files "src/api/cli.ts,src/prompts/PromptOptimizer.ts"`: add known file scope.
+- `--service "api,workflow"`: add known service scope.
+- `--success-criteria "structured prompt,preserves intent,validation evidence"`: seed acceptance criteria.
+
+## Workflow Integration
+
+`scale define` now runs prompt optimization before ambiguity scoring and spec creation:
+
+```bash
+scale define "Prompt Optimizer" \
+  --description "用户输入后自动整理成专业 coding prompt，要保留真实意图" \
+  --success-criteria "生成结构化提示词,保留用户原始意图,输出验收标准" \
+  --json
+```
+
+The JSON result includes `promptOptimization`, and `spec.payload.what` stores the optimized prompt used by the rest of the workflow.
+
+## Governance Rules
+
+- The optimizer is algorithmic and does not call a model.
+- It must not silently change the user's scope.
+- It may add generic execution standards, validation requirements, and clarification questions.
+- Vague input is still accepted, but the `quality.missingInfo` list must expose missing acceptance criteria, affected scope, or constraints.

package/docs/workflow/README.md

@@ -0,0 +1,123 @@
+# SCALE Engine 仓库工作流
+
+这里描述的是 `scale-engine` 仓库自身的工程化工作流，不是终端用户如何使用 `scale` CLI。
+
+## 入口
+
+- 新维护者先读 [GETTING_STARTED.md](../guides/GETTING_STARTED.md)
+- 日常开发读 [DEVELOPMENT_WORKFLOW.md](../guides/DEVELOPMENT_WORKFLOW.md)
+- 机器可读分支策略看 [../../.scale/workspace.json](../../.scale/workspace.json)
+
+## 最小命令面
+
+```bash
+make preflight
+make new-task NAME=workflow-adaptation LEVEL=M
+make plan NAME=workflow-adaptation LEVEL=M
+make explore FILES='AGENTS.md CLAUDE.md README.md package.json' MSG='main contradiction'
+make gate-workflow
+make gate-quality
+make verify PROFILE=default
+scale gates status --json
+scale score task --changed --json
+scale prompt optimize --input "raw coding request" --json
+```
+
+### SCALE 2.0 引擎命令
+
+```bash
+# Scale Shield — 钩子拦截
+scale shield compile          # 编译策略 + 安装 hook
+scale shield status           # 验证 hook 注册 + .scale/ 完整性
+scale shield test             # 运行 allow/block 测试
+
+# Scale Orchestrator — 编排守护进程
+scale orch start              # 启动 daemon
+scale orch status             # 查看状态 + workspace 列表
+
+# Scale Cortex — 持续进化
+scale cortex evolve           # 完整进化周期
+scale cortex extract          # 提取 Instincts
+scale cortex inject --minimal # 预览 SessionStart 注入
+scale cortex metrics --days 30 # 治理 ROI 报告
+```
+
+PowerShell:
+
+```powershell
+powershell -NoProfile -ExecutionPolicy Bypass -File scripts/workflow/verify.ps1 -Profile default
+```
+
+See [GATES_AND_SCORE.md](GATES_AND_SCORE.md) for gate catalog visibility, architecture standards gate scope, and deterministic task scoring.
+
+See [PROMPT_OPTIMIZATION.md](PROMPT_OPTIMIZATION.md) for the deterministic prompt rewrite layer used by `scale prompt optimize` and `scale define`.
+
+## 门禁说明
+
+SCALE 2.0 共 23 个门禁，分三层：核心门禁（G0-G8）、元治理门禁（G9-G15）、增强门禁（G16-G22）。
+
+### 核心门禁（G0-G8）
+
+| Gate | 作用 | 默认 | 阻断 |
+| --- | | --- | --- |
+| G0 | 构建命令或配置的验证命令必须通过 | ✅ | ✅ |
+| G1 | 探索是否记录到状态文件，且至少读了 3 个文件 | ✅ | — |
+| G2 | 计划是否包含边界、异常、回滚、现实校验 | ✅ | — |
+| G3 | `src/` 行为改动是否伴随测试改动 | ✅ | ✅ |
+| G4 | lint 命令必须通过 | ✅ | ✅ |
+| G5 | 测试命令必须通过 | ✅ | ✅ |
+| G6 | 覆盖率、任务证据和 diff hygiene 必须满足当前 profile | profile | ✅ |
+| G7 | 安全和依赖风险检查必须通过 | profile | ✅ |
+| G8 | 产品冒烟命令必须通过 | profile | ✅ |
+
+### 元治理门禁（G9-G15）
+
+| Gate | 作用 | 默认 | 阻断 |
+| --- | | --- | --- |
+| G9 | 知识库和 recall 能力是否被使用 | ✅ | — |
+| G10 | 改进候选是否有证据支撑 | — | — |
+| G11 | 护栏结果是否可见且可操作 | ✅ | — |
+| G12 | 工作流阶段和制品是否完整 | ✅ | — |
+| G13 | 多 Agent 协作是否有协调证据 | — | — |
+| G14 | 必需 skill 是否被选择和验证 | — | — |
+| G15 | 经验教训是否安全进入学习循环 | — | — |
+
+### 增强门禁（G16-G22）
+
+| Gate | 作用 | 默认 | 阻断 |
+| --- | | --- | --- |
+| G16 | 未提交文件数量和大文件阈值检查 | ✅ | ✅ |
+| G17 | 变更的文档链接有效性检查 | ✅ | — |
+| G18 | 运行时证据记录和退出码匹配 | ✅ | ✅ |
+| G19 | L/CRITICAL 任务需要代码审查记录 | profile | ✅ |
+| G20 | 无 CRITICAL/HIGH 漏洞；lock 文件一致性 | ✅ | ✅ |
+| G21 | 上下文 token 预算检查（advisory） | ✅ | — |
+| G22 | 会话健康检查：worktree 泄露和状态一致性 | ✅ | — |
+
+## 分支策略
+
+当前仓库采用 GitLab Flow 风格：
+
+```text
+feature/fix/docs/chore/codex -> dev -> master
+```
+
+约束：
+
+- `dev` 是集成分支。
+- `master` 是生产基线。
+- `release/*` 只在必须从生产基线隔离发版时使用。
+- `hotfix/*` 用于生产紧急修复，并要求回流 `dev`。
+
+## 升级入口
+
+如果要把仓库工作流继续升级到更新的 `scale-engine` 版本，先跑：
+
+```bash
+make bootstrap-scale
+make workflow-upgrade-check
+make workflow-upgrade-plan
+make workflow-aios-adopt
+```
+
+先审计划，再决定是否 `make workflow-upgrade-apply`。如果计划提示 AI OS runtime 尚未接入，使用 `make workflow-aios-adopt` 生成运行态目录、首份 dry-run、benchmark 和 doctor 报告。

package/docs/workflow/node-library.md

@@ -0,0 +1,52 @@
+# Generated by scale-engine governance pack: node-library@2
+# Edit policy: prefer editing the pack in scale-engine; local overrides should be documented.
+
+# Node Library Workflow
+
+This repository uses the latest SCALE repository workflow for Node/npm package delivery.
+
+## Command Entry Points
+
+```bash
+bash scripts/preflight/all.sh
+bash scripts/gates/all.sh --dry-run
+bash scripts/workflow/new-task.sh
+bash scripts/workflow/resume.sh
+bash scripts/workflow/verify.sh --preflight-profile quick
+```
+
+PowerShell:
+
+```powershell
+powershell -NoProfile -ExecutionPolicy Bypass -File scripts/preflight/all.ps1
+powershell -NoProfile -ExecutionPolicy Bypass -File scripts/gates/all.ps1 --dry-run
+powershell -NoProfile -ExecutionPolicy Bypass -File scripts/workflow/new-task.ps1
+powershell -NoProfile -ExecutionPolicy Bypass -File scripts/workflow/resume.ps1
+powershell -NoProfile -ExecutionPolicy Bypass -File scripts/workflow/verify.ps1 --preflight-profile quick
+```
+
+## Default Verification Matrix
+
+- quick loop: `npm run build`, `npm run lint`, `npm test`
+- release loop: run `npm run release:check` when available; otherwise add `npm run typecheck`, `npm run smoke:setup`, `npm audit --omit=dev`, `git diff --check`, and `npm pack --dry-run`
+- product smoke: enable a real probe in `.scale/product-smoke.json` instead of treating a health endpoint as completion proof
+
+## Branch Policy
+
+This repository follows a GitLab Flow variant:
+
+```text
+feature/fix/docs/chore/codex -> dev -> master -> tag/publish
+```
+
+Use short-lived branches for governed work. Direct governed commits on `dev`, `master`, or `main` are blocked by SCALE ship rules.
+
+## Release Expectations
+
+Before a package release or demo handoff:
+
+1. Run `bash scripts/preflight/all.sh` or the PowerShell equivalent.
+2. Run `scale preflight --preflight-profile full --json`.
+3. Run `npm run release:check` when the package exposes it, or run the equivalent build/test/smoke/audit/pack commands explicitly.
+4. Run `git diff --check` if it is not already included in the release command.
+5. Confirm runtime evidence and review artifacts for M/L/CRITICAL work.

package/docs/workflow/templates/api-contract.md

@@ -0,0 +1,29 @@
+# API Contract
+
+## Endpoint Or Interface
+
+TBD
+
+## Request
+
+TBD
+
+## Response
+
+TBD
+
+## Errors
+
+TBD
+
+## Permission Rules
+
+TBD
+
+## Compatibility Notes
+
+TBD
+
+## Acceptance Criteria
+
+- [ ] TBD

package/docs/workflow/templates/architecture-review.md

@@ -0,0 +1,23 @@
+# Architecture Review
+
+## Scope
+
+- Modules touched:
+- Public contracts touched:
+- Data flow touched:
+
+## Boundary Checks
+
+- [ ] API/controller layer does not bypass service/usecase layer
+- [ ] Domain layer is not coupled to infrastructure details
+- [ ] Repository/ORM usage follows project conventions
+- [ ] Shared framework components are reused instead of duplicated
+- [ ] New abstractions remove real complexity
+
+## Risks
+
+- TBD
+
+## Decision
+
+- Approved/changes required:

package/docs/workflow/templates/db-change-plan.md

@@ -0,0 +1,20 @@
+# DB Change Plan
+
+## Schema Or Data Change
+
+TBD
+
+## Backward Compatibility
+
+TBD
+
+## Migration Steps
+
+TBD
+
+## Rollback Plan
+
+TBD
+
+## Verification
+TBD

package/docs/workflow/templates/docs-impact.md

@@ -0,0 +1,17 @@
+# Docs Impact
+
+## Code Changes Requiring Docs
+
+- TBD
+
+## Documentation Updated
+
+- TBD
+
+## No-Docs-Needed Rationale
+
+TBD
+
+## Links Checked
+
+- TBD

package/docs/workflow/templates/e2e-plan.md

@@ -0,0 +1,20 @@
+# E2E Plan
+
+## User Paths
+
+TBD
+
+## Browser Coverage
+
+TBD
+
+## Test Data
+
+TBD
+
+## Assertions
+
+TBD
+
+## Evidence
+TBD

package/docs/workflow/templates/explore.md

@@ -0,0 +1,16 @@
+# Explore - {{TASK_ID}}
+
+Date: {{DATE}}
+Level: {{LEVEL}}
+
+## Files Read
+
+- TBD
+
+## Main Contradiction
+
+- TBD
+
+## Constraints
+
+- TBD

package/docs/workflow/templates/github-actions-scale-preflight.yml

@@ -0,0 +1,32 @@
+name: SCALE Preflight
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+      - master
+
+jobs:
+  preflight:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Install project dependencies when present
+        shell: bash
+        run: |
+          if [ -f package-lock.json ]; then
+            npm ci
+          elif [ -f package.json ]; then
+            npm install
+          fi
+
+      - name: Run SCALE preflight
+        run: npx @hongmaple0820/scale-engine@latest preflight --service all --preflight-profile ci

package/docs/workflow/templates/mini-prd.md

@@ -0,0 +1,16 @@
+# Mini PRD - {{TASK_ID}}
+
+Date: {{DATE}}
+Level: {{LEVEL}}
+
+## Goal
+
+- TBD
+
+## Non-Goals
+
+- TBD
+
+## Acceptance Criteria
+
+- TBD