tcw-cli 3.0.0__tar.gz → 3.0.1__tar.gz

{tcw_cli-3.0.0/tcw_cli.egg-info → tcw_cli-3.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tcw-cli
-Version: 3.0.0
+Version: 3.0.1
 Summary: Taxonomy · Capabilities · Work — a storage-abstracted framework for describing and evolving a software project.
 License:                                  Apache License
                                    Version 2.0, January 2004
@@ -724,7 +724,8 @@ A change to the product is followed from the first request to the records:
 In filesystem mode, the agent working `qa` may record the verdict itself, unless
 the project's own instructions for `qa` ask for a person to decide. When they
 do, the agent still writes the round, recording the person's decision. In Jira
-mode, a person accepts or rejects on the ticket.
+mode, a person accepts or rejects: on the ticket, or by telling the agent,
+which then moves the ticket and records who decided.
 
 Work reaches taxonomy through those capabilities: a new capability names the
 vocabulary and feature it involves, and those entries must exist first.

{tcw_cli-3.0.0 → tcw_cli-3.0.1}/README.md

@@ -508,7 +508,8 @@ A change to the product is followed from the first request to the records:
 In filesystem mode, the agent working `qa` may record the verdict itself, unless
 the project's own instructions for `qa` ask for a person to decide. When they
 do, the agent still writes the round, recording the person's decision. In Jira
-mode, a person accepts or rejects on the ticket.
+mode, a person accepts or rejects: on the ticket, or by telling the agent,
+which then moves the ticket and records who decided.
 
 Work reaches taxonomy through those capabilities: a new capability names the
 vocabulary and feature it involves, and those entries must exist first.

{tcw_cli-3.0.0 → tcw_cli-3.0.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "tcw-cli"
-version = "3.0.0"
+version = "3.0.1"
 description = "Taxonomy · Capabilities · Work — a storage-abstracted framework for describing and evolving a software project."
 readme = "README.md"
 requires-python = ">=3.11"

tcw_cli-3.0.1/tcw/__init__.py

@@ -0,0 +1 @@
+__version__ = "3.0.1"

{tcw_cli-3.0.0 → tcw_cli-3.0.1}/tcw/work/procedures/unattended-work.md

@@ -29,7 +29,7 @@ advisor alone.
 
 | The stage asks for          | Do this instead |
 | --------------------------- | --------------- |
-| What the requester wants, at request | Do not ask the advisors: what the requester wants is not theirs to know. Write the request from the evidence available, marking each assumption, as the request prompt says when there is no user to ask. Where the backend keeps the request, as Jira does, post your questions with `tcw work comment <slug>` instead and leave its text alone. Then continue. |
+| What the requester wants, at request | Do not ask the advisors: what the requester wants is not theirs to know. Write the request from the evidence available, marking each assumption, as the request prompt says when there is no user to ask. Where the backend keeps the request, as Jira does, post your questions with `tcw work comment <slug>` instead and leave its text alone, and leave the item at request unless the user's own instruction for this run explicitly said to move it out of request. Then move on to other work. |
 | One agent or several        | Decide yourself. One, unless the parts are truly independent. |
 | An open question in a spec or plan | Ask the advisors, then write the answer into the document with the assumption stated in the text. |
 | Review                      | Run the review stage as its prompt says: a read-only reviewer, never the agent that implemented. Apply what you agree with; write down what you reject and why. |

{tcw_cli-3.0.0 → tcw_cli-3.0.1}/tcw/work/prompts/qa.md

@@ -52,7 +52,7 @@ QA plan scenario as passed, failed or not run, with the evidence for each.
 <!-- /backend -->
 <!-- backend: jira -->
 **Produce** findings, not a verdict. In Jira, qa happens on the ticket, and the
-ticket's status, which people move, is the verdict. You may run the scenarios
+ticket's status, which a person decides, is the verdict. You may run the scenarios
 and post what you found with `tcw work comment <slug>`.
 
 ## Steps
@@ -60,11 +60,15 @@ and post what you found with `tcw work comment <slug>`.
 1. Run each scenario in the QA plan, in the environment it names.
 2. Post one comment listing each scenario as passed, failed or not run, with
    evidence. **No claim without output or an observation from just now.**
-3. Leave the decision to a person. Tell them how to record it: accept by
-   moving the ticket on in Jira, or with
-   `tcw work advance <slug> --to completed --reason "<why>"`; reject with
-   `tcw work advance <slug> --to implement --reason "<what to fix>"`, whose
-   reason becomes the comment implement reads.
+3. A person decides the verdict, never you. Ask them for it. When the person
+   who decides gives you the verdict in this conversation, record it: accepted
+   with `tcw work advance <slug> --to completed --reason "accepted by <name>:
+   <why>"`, rejected with `tcw work advance <slug> --to implement --reason
+   "rejected by <name>: <what to fix>"`, whose reason becomes the comment
+   implement reads. A verdict comes after they have seen your findings: an
+   instruction given before that, such as "accept it if it passes", is not
+   one. They may instead move the ticket in Jira themselves. If they give no
+   verdict, stop at qa and say the item waits for them.
 <!-- /backend -->
 
 ## Exit badly

{tcw_cli-3.0.0 → tcw_cli-3.0.1}/tcw/work/prompts/request.md

@@ -32,10 +32,19 @@ Write it to `tcw work path <slug> request`. Keep any dated `## Added`
 sections already there: they are amendments made after it was written.
 <!-- /backend -->
 <!-- backend: jira -->
-The request is the ticket's description, and Jira owns it: never rewrite it.
-When a section is missing or unclear, post a comment with
+The request is the ticket's description, and Jira owns it: never rewrite it on
+your own judgment. When a section is missing or unclear, post a comment with
 `tcw work comment <slug>` listing what is missing and proposing wording, for
 the requester to adopt.
+
+The requester decides when the request is ready. When they tell you to move
+the item on, in this conversation, do it. If they adopted changed wording,
+first put it into the ticket's description: write it yourself if your harness
+can edit Jira tickets, or ask them to paste it in. Then read it back and
+confirm the description now says what they adopted. Then run
+`tcw work advance <slug> --reason "<who told you to move it>"`. A question,
+such as whether accepting the wording moves the item, is not an instruction to
+move it.
 <!-- /backend -->
 
 ## Steps

{tcw_cli-3.0.0 → tcw_cli-3.0.1}/tcw/work/resolve.py

@@ -450,8 +450,14 @@ def stage_footer(row, external, target: str) -> str | None:
     if row.artifact == NO_ARTIFACT:
         return None              # how an arrival becomes work differs by backend
     if row.name in external:
-        text = ("> **When this stage's work is done, a person moves the item on "
-                "in the backend.** Do not move it yourself.")
+        # A person decides; the agent carries out the move once told (TCW-100).
+        move = (f"`tcw work advance {target} --to <stage> --reason \"<who decided, "
+                f"and why>\"`" if row.verdict else
+                f"`tcw work advance {target} --reason \"<who told you>\"`")
+        text = ("> **When this stage's work is done, a person decides whether the "
+                "item moves on.** Move it only when that person tells you to, in "
+                "this conversation; a question or an implied yes is not that. "
+                f"Then run {move}.")
         if row.verdict:
             text += " The verdict is that move."
         return text

{tcw_cli-3.0.0 → tcw_cli-3.0.1/tcw_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tcw-cli
-Version: 3.0.0
+Version: 3.0.1
 Summary: Taxonomy · Capabilities · Work — a storage-abstracted framework for describing and evolving a software project.
 License:                                  Apache License
                                    Version 2.0, January 2004
@@ -724,7 +724,8 @@ A change to the product is followed from the first request to the records:
 In filesystem mode, the agent working `qa` may record the verdict itself, unless
 the project's own instructions for `qa` ask for a person to decide. When they
 do, the agent still writes the round, recording the person's decision. In Jira
-mode, a person accepts or rejects on the ticket.
+mode, a person accepts or rejects: on the ticket, or by telling the agent,
+which then moves the ticket and records who decided.
 
 Work reaches taxonomy through those capabilities: a new capability names the
 vocabulary and feature it involves, and those entries must exist first.

{tcw_cli-3.0.0 → tcw_cli-3.0.1}/tests/test_shipped_prompts.py

@@ -267,6 +267,26 @@ def test_jira_qa_records_no_verdict():
     assert "tcw work path <slug> qa" not in text and "verdict:" not in text
 
 
+def test_jira_qa_moves_the_ticket_when_the_person_gives_the_verdict():
+    """TCW-100: the person decides; once they give the verdict in the
+    conversation, the agent records it with `advance`, and otherwise stops."""
+    paragraph = _paragraph_with(prompt("qa", "jira"), "gives you the verdict")
+    assert "--to completed --reason" in paragraph
+    assert "--to implement --reason" in paragraph
+    assert "after they have seen your findings" in paragraph
+    assert "stop at qa" in paragraph
+
+
+def test_jira_request_writes_adopted_wording_before_moving():
+    """TCW-100: adopted wording goes into the description, is read back, and
+    only then is the item moved, with a reason naming who said to move it."""
+    paragraph = _paragraph_with(prompt("request", "jira"), "tell you to move")
+    for words in ("description", "paste", "read it back",
+                  "tcw work advance <slug> --reason"):
+        assert words in paragraph, words
+    assert paragraph.index("read it back") < paragraph.index("tcw work advance")
+
+
 @pytest.mark.parametrize("sid", sorted(SHIPPED))
 def test_no_prompt_tells_the_agent_to_ask_what_it_is_reading(sid):
     """`tcw work lifecycle --stage <id>` inside the text that command reports

tcw_cli-3.0.0/tcw/__init__.py

@@ -1 +0,0 @@
-__version__ = "3.0.0"