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

这个提交包含在:
2026-05-26 10:08:06 +08:00
父节点 e7baa6c234
当前提交 1b5c7527b7
共修改 24 个文件,包含 361 行新增和 161 行删除
@@ -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."}
@@ -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.
@@ -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."}
@@ -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.
@@ -0,0 +1,6 @@
# TRELLIS1 Pilot Design
TRELLIS1 proved Trellis could be introduced without changing OA business code.
Its original design intentionally bound a Trellis task to Issue CSV evidence.
TRELLIS2 supersedes that dual-track rule and keeps this task as historical
migration evidence.
@@ -27,3 +27,8 @@ binding to Issue CSV and project documentation.
- The task contains issue binding and redacted scope.
- `implement.jsonl` and `check.jsonl` include real spec context entries.
- Trellis governance check passes.
## Test Plan
- `python3 ./.trellis/scripts/task.py validate 05-26-trellis1-pilot`
- `node scripts/qa/check-trellis-governance.mjs`
@@ -0,0 +1,3 @@
{"file":".trellis/spec/hyb-oa/project-governance.md","reason":"Check that task-first governance supersedes mandatory Issue CSV binding."}
{"file":".trellis/spec/hyb-oa/docs-and-evidence.md","reason":"Check documentation registration and evidence boundaries."}
{"file":".trellis/spec/hyb-oa/security-privacy.md","reason":"Check sensitive-data exclusions in Trellis governance files."}
@@ -0,0 +1,21 @@
# TRELLIS2 Design
## Decision
Use the official Trellis task directory as the single execution contract for
new work. Issue CSV remains available as historical evidence or an optional
export format when a tabular external audit packet is needed.
## Contract Shape
- `task.json`: metadata, status, scope, related files and optional commit/PR.
- `prd.md`: goal, scope, out-of-scope, acceptance and test plan.
- `design.md` or `implement.md`: required for complex process, API, migration,
permission, deployment or workflow-governance changes.
- `implement.jsonl` / `check.jsonl`: stable spec or research context only.
## Compatibility
Existing Issue CSV files stay in place. Existing Trellis tasks can mention
their old Issue CSV bindings as historical metadata, but new task validation
must not require those bindings.
@@ -0,0 +1,3 @@
{"file":".trellis/spec/hyb-oa/project-governance.md","reason":"Defines the hyb-oa development governance contract to update."}
{"file":".trellis/spec/hyb-oa/docs-and-evidence.md","reason":"Defines docs fact-source and evidence registration rules."}
{"file":".trellis/spec/hyb-oa/security-privacy.md","reason":"Defines redaction boundaries for Trellis tasks, docs and reports."}
@@ -0,0 +1,49 @@
# TRELLIS2 Official Task Contract
## Goal
Adopt official Trellis task-first usage for hyb-oa development governance.
Future non-trivial work starts from `.trellis/tasks/*`; the task directory
holds the PRD, implementation context, verification context and finish record.
## Scope
- Make Trellis task the execution contract for new work.
- Keep `docs/` as the business fact source.
- Keep historical `issues/*.csv` files for audit and legacy lookup only.
- Update AGENTS, Trellis workflow, project governance spec, governance check,
project documentation and the hyb-oa delivery skill.
## Out Of Scope
- No backend or frontend business-code changes.
- No deployment or public OA verification.
- No database, Enterprise WeChat, payment, production config or real-data write.
- No deletion, migration or bulk rewrite of historical `issues/*.csv` files.
## Acceptance
- New governance text says non-trivial work requires a Trellis task, not an
Issue CSV.
- `scripts/qa/check-trellis-governance.mjs` validates task contract quality
without requiring Issue CSV bindings.
- Current active Trellis tasks have PRD/test/scope information sufficient for
the new check.
- Documentation and the project skill agree on Trellis task-first operation.
## Test Plan
- `python3 ./.trellis/scripts/task.py validate 05-26-trellis2-official-task-contract`
- `python3 ./.trellis/scripts/task.py list`
- `node --check scripts/qa/check-trellis-governance.mjs`
- `node scripts/qa/check-trellis-governance.mjs`
- `node scripts/qa/audit-docs.mjs --check-registry`
- `python3 /home/shunli/.codex/skills/.system/skill-creator/scripts/quick_validate.py .agents/skills/hyb-oa-delivery`
- `git diff --check`
- `bash scripts/check-minimal.sh`
## Privacy
Do not store passwords, token, Secret, real invoice originals, contract bodies,
bank materials, full accounts, complete local paths or raw payloads in Trellis
tasks, docs, reports or chat.
@@ -0,0 +1,38 @@
{
"id": "trellis2-official-task-contract",
"name": "trellis2-official-task-contract",
"title": "TRELLIS2 official task contract",
"description": "Migrate hyb-oa development governance from Issue CSV binding to official Trellis task contracts.",
"status": "in_progress",
"dev_type": "docs",
"scope": "trellis-governance",
"package": "docs",
"priority": "P2",
"creator": "shunli",
"assignee": "shunli",
"createdAt": "2026-05-26",
"completedAt": null,
"branch": null,
"base_branch": "main",
"worktree_path": null,
"commit": null,
"pr_url": null,
"subtasks": [],
"children": [],
"parent": null,
"relatedFiles": [
"AGENTS.md",
".trellis/workflow.md",
".trellis/spec/hyb-oa/project-governance.md",
"scripts/qa/check-trellis-governance.mjs",
"docs/Agent开发交付实践.md",
"docs/文档索引.md",
"docs/文档事实源状态矩阵.md",
".agents/skills/hyb-oa-delivery/SKILL.md"
],
"notes": "No business code, no deployment, no public OA data writes. TRELLIS2 intentionally creates no Issue CSV.",
"meta": {
"contractMode": "trellis_task",
"supersedesPolicy": "TRELLIS1 dual-track Issue CSV binding"
}
}