trellis2-official-task-contract 采用官方 Trellis 执行合同

.trellis/tasks/00-bootstrap-guidelines/check.jsonl

@@ -0,0 +1,2 @@
+{"file":".trellis/spec/hyb-oa/index.md","reason":"Verify project-specific specs are discoverable."}
+{"file":".trellis/spec/hyb-oa/project-governance.md","reason":"Verify bootstrap remains compatible with current governance."}

.trellis/tasks/00-bootstrap-guidelines/design.md

@@ -0,0 +1,5 @@
+# Bootstrap Design
+
+This is the generated Trellis bootstrap task. hyb-oa keeps it as historical
+setup evidence, while project-specific rules live in `.trellis/spec/hyb-oa/`.
+TRELLIS2 supersedes the old Issue CSV binding requirement for new tasks.

.trellis/tasks/00-bootstrap-guidelines/implement.jsonl

@@ -0,0 +1,2 @@
+{"file":".trellis/spec/hyb-oa/index.md","reason":"Project-specific hyb-oa spec entry after bootstrap."}
+{"file":".trellis/spec/hyb-oa/project-governance.md","reason":"Project governance supersedes generated bootstrap placeholders."}

.trellis/tasks/00-bootstrap-guidelines/prd.md

@@ -6,6 +6,32 @@
 `.trellis/spec/hyb-oa/`; the generated backend/frontend scaffolds remain
 secondary.
 
+## Goal
+
+Capture project-specific Trellis specs so future agents follow hyb-oa
+conventions instead of generic generated placeholders.
+
+## Scope
+
+- Bootstrap project-specific Trellis specs and confirm hyb-oa conventions.
+- Treat this task as historical setup evidence after TRELLIS2.
+
+## Out Of Scope
+
+- No OA business-code changes.
+- No deployment, database write, Enterprise WeChat write or public data write.
+
+## Acceptance
+
+- hyb-oa project specs exist under `.trellis/spec/hyb-oa/`.
+- Future work can use task PRDs and JSONL spec context instead of generic
+  agent memory.
+
+## Test Plan
+
+- `python3 ./.trellis/scripts/task.py validate 00-bootstrap-guidelines`
+- `node scripts/qa/check-trellis-governance.mjs`
+
 **You (the AI) are running this task. The developer does not read this file.**
 
 The developer just ran `trellis init` on this project for the first time.