@thiaq/project-skill 0.1.1 → 0.1.2

package/SKILL.md

@@ -197,11 +197,35 @@ Use `get_project_context` first. Then call the smallest useful write operation:
 - `propose_access_profile_changes` for test URL, role, auth, and secret refs.
 - `propose_safety_policy_changes` for safe/unsafe action boundaries.
 - `list_test_ideas` after discovery.
+- `list_operational_state` to inspect the agent-manageable workspace backlog:
+  ideas, groups, issues, journey candidates, runner work, and proposals.
+- `update_test_idea` to soft-triage, archive, restore, or annotate test ideas.
+- `group_test_ideas` to dedupe or collect ideas into scenario, area, or review
+  groups.
+- `merge_test_ideas` to archive duplicate ideas under a primary idea.
 - `propose_test_idea_promotion` to create reviewable promotion work.
 - `list_issue_categories` for UX confusion, selector, driver, assertion, and
   safety gaps.
+- `create_issue_category` to store an operational issue category from evidence.
+- `update_issue_category` to close, reopen, archive, restore, relabel, or
+  reprioritize operational issue categories.
+- `merge_issue_categories` to archive duplicate issues under a primary issue.
 - `create_repair_proposal` when an issue needs product, adapter, selector, or
   assertion repair.
+- `update_journey_candidate` to reprioritize, archive, restore, or annotate
+  candidate journeys without approving executable coverage.
+- `cancel_runner_job` for stale queued/running discovery or scenario work.
+- `retry_runner_job` to clone failed/stale runner work without changing original
+  evidence.
+- `update_proposal_status` to withdraw, archive, restore, or supersede draft
+  proposals. Do not use it for final accept/reject review gates.
+- `bulk_archive_operational_records` to dry-run and then archive large noisy
+  operational backlogs by type, status, source run, and explicit keep IDs.
+- `reconcile_operational_state` to dry-run or apply safe stale runner cleanup.
+
+Use soft mutation statuses instead of deletion. Evidence, run artifacts,
+approved flows, approved journeys, manifests, safety policy, and CI tier changes
+remain review-gated.
 
 For tool schemas and payload examples, read
 `references/mcp-tools.md` only when preparing MCP calls.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thiaq/project-skill",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "type": "module",
   "private": false,
   "description": "ThiaQ project setup skill for Codex and Claude Code agents.",

package/references/mcp-tools.md

@@ -240,3 +240,262 @@ flow code.
   }
 }
 ```
+
+## Operational Workspace Mutations
+
+Agents may directly manage living QA workspace state when the operation is
+soft, reversible, and reasoned. Do not hard-delete evidence. Do not accept or
+reject review gates. Do not mutate approved flow code, journey specs, manifests,
+safety policy, access policy, or CI tiers.
+
+### List Operational State
+
+Use this before cleanup work to inspect all MCP-manageable backlog records in
+one bounded payload.
+
+```json
+{
+  "name": "list_operational_state",
+  "arguments": {
+    "projectId": "project-id",
+    "limit": "50",
+    "status": "draft"
+  }
+}
+```
+
+### Update A Test Idea
+
+Use this to triage, annotate, archive, restore, or reprioritize discovery
+findings.
+
+```json
+{
+  "name": "update_test_idea",
+  "arguments": {
+    "projectId": "project-id",
+    "ideaId": "idea.dashboard.create",
+    "status": "archived",
+    "reason": "Covered by scenario group scenario.dashboard.create"
+  }
+}
+```
+
+### Group Test Ideas
+
+Use this to dedupe or collect findings into scenario, product-area, or review
+groups.
+
+```json
+{
+  "name": "group_test_ideas",
+  "arguments": {
+    "projectId": "project-id",
+    "groupId": "scenario.dashboard.create",
+    "groupKind": "scenario",
+    "label": "Dashboard create path",
+    "ideaIds": ["idea.dashboard.create", "idea.dashboard.empty-state"],
+    "rationale": "These findings describe one scenario candidate."
+  }
+}
+```
+
+### Merge Test Ideas
+
+Use this when several findings describe the same coverage need. The primary is
+kept; secondaries are archived with merge evidence.
+
+```json
+{
+  "name": "merge_test_ideas",
+  "arguments": {
+    "projectId": "project-id",
+    "primaryIdeaId": "idea.dashboard.create",
+    "secondaryIdeaIds": ["idea.dashboard.empty-state"],
+    "reason": "Both findings describe the same dashboard create scenario."
+  }
+}
+```
+
+### Create An Issue Category
+
+Use this to persist a new operational gap that the agent found in evidence.
+
+```json
+{
+  "name": "create_issue_category",
+  "arguments": {
+    "projectId": "project-id",
+    "categoryId": "selector-gap.dashboard-create",
+    "categoryType": "selector_gap",
+    "label": "Dashboard create selector gap",
+    "severity": "medium",
+    "sourceIds": ["idea.dashboard.create"],
+    "reason": "No stable role/test-id locator exists for the create action."
+  }
+}
+```
+
+### Update An Issue Category
+
+Use this to close, reopen, archive, restore, relabel, or reprioritize UX,
+selector, driver, assertion, or safety gaps.
+
+```json
+{
+  "name": "update_issue_category",
+  "arguments": {
+    "projectId": "project-id",
+    "categoryId": "selector-gap.dashboard-create",
+    "status": "closed",
+    "reason": "Stable role locator added to the reviewed interaction contract."
+  }
+}
+```
+
+### Merge Issue Categories
+
+Use this when multiple issues describe the same gap. The primary issue remains;
+secondaries are archived.
+
+```json
+{
+  "name": "merge_issue_categories",
+  "arguments": {
+    "projectId": "project-id",
+    "primaryCategoryId": "selector-gap.dashboard-create",
+    "secondaryCategoryIds": ["selector-gap.create-button"],
+    "reason": "Both point at the same missing create-button locator."
+  }
+}
+```
+
+### Update A Journey Candidate
+
+Use this for ranking and triage only. It does not approve executable coverage.
+
+```json
+{
+  "name": "update_journey_candidate",
+  "arguments": {
+    "projectId": "project-id",
+    "candidateId": "journey-candidate-id",
+    "priority": "high",
+    "status": "active",
+    "reason": "Matches release-critical onboarding path."
+  }
+}
+```
+
+### Cancel Runner Work
+
+Use this for queued or running discovery/scenario jobs that are stale or unsafe.
+Completed jobs are immutable.
+
+```json
+{
+  "name": "cancel_runner_job",
+  "arguments": {
+    "projectId": "project-id",
+    "runnerJobId": "runner-job-id",
+    "runnerJobRequestId": "runner-request-id",
+    "reason": "Superseded by discovery run with updated safety boundaries."
+  }
+}
+```
+
+### Retry Runner Work
+
+Use this to clone a failed or stale runner job/request into new queued work. The
+original evidence remains unchanged.
+
+```json
+{
+  "name": "retry_runner_job",
+  "arguments": {
+    "projectId": "project-id",
+    "runnerJobId": "runner-job-id",
+    "reason": "Runner environment is now healthy."
+  }
+}
+```
+
+### Withdraw Or Supersede A Proposal
+
+Use this for draft proposal lifecycle cleanup. Final accept/reject remains a UI
+review gate.
+
+```json
+{
+  "name": "update_proposal_status",
+  "arguments": {
+    "projectId": "project-id",
+    "proposalId": "proposal-id",
+    "status": "superseded",
+    "supersededById": "replacement-proposal-id",
+    "reason": "Merged into a broader repair proposal."
+  }
+}
+```
+
+### Bulk Archive Operational Records
+
+Use this for large discovery-noise resets when thousands of proposals or test
+ideas would otherwise require one call per record. It is dry-run by default and
+returns compact counts plus sample IDs, not full proposal or idea bodies.
+
+By default, it targets only `proposals` and `test_ideas`. Add more record types
+explicitly when clearing groups, issues, journey candidates, or stale runner
+work. It never hard-deletes evidence, never archives accepted/rejected
+proposals, never archives approved/promoted/implemented test ideas, and only
+cancels queued/running runner work.
+
+Preview first:
+
+```json
+{
+  "name": "bulk_archive_operational_records",
+  "arguments": {
+    "projectId": "project-id",
+    "recordTypes": ["proposals", "test_ideas"],
+    "sourceRunIds": ["runner.discovery.ffe22c16"],
+    "proposalTypes": ["coverage-gap", "candidate-pathway", "bug-candidate"],
+    "dryRun": "true",
+    "excludeIds": ["proposal-to-keep", "idea.to.keep"],
+    "reason": "Preview cleanup of superseded discovery noise."
+  }
+}
+```
+
+Apply after reviewing the returned counts:
+
+```json
+{
+  "name": "bulk_archive_operational_records",
+  "arguments": {
+    "projectId": "project-id",
+    "recordTypes": ["proposals", "test_ideas"],
+    "sourceRunIds": ["runner.discovery.ffe22c16"],
+    "dryRun": "false",
+    "excludeIds": ["proposal-to-keep", "idea.to.keep"],
+    "reason": "Archive superseded discovery noise after preserving latest real findings."
+  }
+}
+```
+
+### Reconcile Operational State
+
+Use this to find stale queued/running runner work. It is dry-run by default.
+Only set `dryRun` to `"false"` when the cancellation is safe.
+
+```json
+{
+  "name": "reconcile_operational_state",
+  "arguments": {
+    "projectId": "project-id",
+    "staleRunnerHours": "24",
+    "dryRun": "true",
+    "reason": "Nightly cleanup of stale queued discovery work."
+  }
+}
+```