Implement software-change-delivery@1.0.0 TeamPlaybook and deterministic transitions

[shenjiecode]

Scope

First closed, versioned TeamPlaybook software-change-delivery@1.0.0 and deterministic transition policy.

Package

• Layout: manifest.json, PLAYBOOK.md, schemas/ (project/task/result/transition-binding), transition-policy.mjs, tests/transition-truth-table.json.
• Closed resolver + playbooks.lock.json (playbookId/version/contentDigest, policy digest, schema digests, compatible RoleProfile digests, AgentTeams/TeamTaskPort contract versions).

Binding + transitions

• Immutable ProjectPlaybookBinding on Project creation (via a Tiangong-owned manifest + path/digest ref, or a tag-verified upstream metadata extension — decided by the v1.2 oracle).
• Per Task/Result binding { playbookStepId, taskKind, revisionIndex, completionContractDigest, inputRefs }.
• Fixed DAG design → implement → assess → release; revision via new nodes; maxRevisionWaves=2; timeout/blocker → BLOCKED; no PlaybookRun competing with AgentTeams Project status.
• Transition key { projectId, playbookDigest, sourceTaskId, decision, revisionIndex }; replay returns saved result without re-dispatch/accept/report.
• Task kinds: design, implement, assess, release with minimal completion contracts.

Tests

• Transition truth table; illegal role/step/digest/result/revision rejections; replay idempotency.
• explicit_subject approval policy with positive, negative, and adjacent-subject tests.

Exit gate

Playbook binding validates; illegal transitions fail closed; replay is idempotent; approval negatives fail closed.

References

• AGENTS.md, docs/rules/worker-runtime.md, docs/rules/security-and-evidence.md