docs: decouple workflow diagram from agent-tasks MCP, add README control loop#69
Merged
LanNguyenSi merged 1 commit intomasterfrom May 6, 2026
Merged
Conversation
…rol loop
The workflow lifecycle stateDiagram in for-agents.md now reads
against the four step kinds the workflows: schema actually defines
(branch / review_subagent / ci_gate / merge) instead of agent-tasks
MCP-specific verbs (task_start, open / in_progress / done). A new
"If you use agent-tasks MCP" footnote below the diagram maps the
lifecycle markers to concrete MCP verbs as one example integration.
Other task systems fit the same lifecycle.
Plus: root README gains a control-loop flowchart ("What harness
does": declare, apply, enforce, record, observe, refine) that both
audiences read identically without audience-specific verbs. The
README + docs now ship four mermaid diagrams total.
Refs agent-tasks 051e5d77.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
LanNguyenSi
added a commit
that referenced
this pull request
May 6, 2026
Bump package.json 0.6.0 -> 0.7.0. Roll up CHANGELOG [Unreleased] into [0.7.0] - 2026-05-06 with a one-paragraph headline plus operator note. PR refs (#65, #66, #67, #68, #69) added to each entry. README now references v0.7.0 in the prose and gains a status checklist row for the workflows-as-data + session-export + docs-split set. Two version-pinned tests bumped to match the new binary header. Theme: workflows-as-data and full-session audit forensics. No schema bump (still version: 1); all new manifest fields are additive and parse identically against 0.6.0 manifests. Refs agent-tasks 1fe55885. Co-authored-by: Lan Nguyen Si <nguyen-si@publicplan.de> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/for-agents.mdis now anchored on the four step kinds theworkflows:schema actually defines (branch,review_subagent,ci_gate,merge). Previous version leaked agent-tasks MCP verbs (task_start) and task-status state names (open/in_progress/done) that an agent without that MCP cannot resolve.README.mdgains a control-loop flowchart ("What harness does": Declare → Apply → Enforce → Record → Observe, with a refine edge back to Declare) that both audiences read identically without any audience-specific verbs.Why
User caught the leak right after PR #68 landed: "der workflow lifecycle nutzt agent-tasks mcp. das werden nur agents verstehen, die agent-tasks mcp connected sind oder nicht?". harness does not depend on agent-tasks; the docs should not silently assume otherwise.
Refs agent-tasks
051e5d77.Scope cut
for-humans.mduntouched.for-agents.mduntouched (it never named an agent-tasks verb).Test plan
git diff --stat master..docs/workflow-diagram-decoupleshows exactly 3 files: CHANGELOG, README, docs/for-agents.md.WorkflowStep.kindexactly (src/schema/workflows.ts).