Clarify Issue Designer cold-start readiness guidance #10

Merged
anodyine merged 1 commits from ISSUE-950 into main 2026-11-05 11:35:56 -05:00
Owner

Summary

Update the automatic Issue Designer default to require an attributed cold-start readiness check when marking each item. It covers current issue comments, cited source and tests, target and installed environment observations, non-secret retrieval instructions, and an explicit unresolved question when evidence is missing. The package is versioned 0.6.1; the eight optional Designer methods stay at 0.6.0.

Evidence

  • Before: The 0.6.0 default requested current facts and a cold-start check but did not explicitly cover comments, environment inputs, or retrieval instructions.
  • After: python -m unittest discover -s tests -v passed 13 tests. python -m tools.packages check packages/issue-designer-default validates the exact package bytes and role.

Checks run

  • python -m unittest discover -s tests -v — 13 passed.

Merge Danger

Door: Two-way. The change affects guidance for future Issue Designer Chats after the owner pins the new release. Existing Chats keep their captured bytes.

Blast Radius: Automatic Designer guidance and the public release used by RelayView issue #950. No owner tools or authority change.

Rollback: Revert this PR before tagging; RelayView can continue using the pinned v0.6.0 package.

Reviewer prerequisites

  • Python 3 and a clean checkout of this repository. No provider credentials or paid calls.

Manual Test Plan

  1. Action: Read packages/issue-designer-default/SKILL.md and verify it asks for a specific unresolved question and available evidence when a readiness input cannot be observed.

    Expected: The instruction gives a new Planner enough non-secret retrieval context and does not claim the Designer can inspect a host through an unassigned tool.

Post-Merge Cleanup

After review and merge, publish the immutable v0.6.1 tag at the merged package commit before RelayView pins it as a public release.

## Summary Update the automatic Issue Designer default to require an attributed cold-start readiness check when marking each item. It covers current issue comments, cited source and tests, target and installed environment observations, non-secret retrieval instructions, and an explicit unresolved question when evidence is missing. The package is versioned `0.6.1`; the eight optional Designer methods stay at `0.6.0`. ## Evidence - **Before:** The `0.6.0` default requested current facts and a cold-start check but did not explicitly cover comments, environment inputs, or retrieval instructions. - **After:** `python -m unittest discover -s tests -v` passed 13 tests. `python -m tools.packages check packages/issue-designer-default` validates the exact package bytes and role. ### Checks run - `python -m unittest discover -s tests -v` — 13 passed. ## Merge Danger **Door:** Two-way. The change affects guidance for future Issue Designer Chats after the owner pins the new release. Existing Chats keep their captured bytes. **Blast Radius:** Automatic Designer guidance and the public release used by RelayView issue #950. No owner tools or authority change. **Rollback:** Revert this PR before tagging; RelayView can continue using the pinned `v0.6.0` package. ## Reviewer prerequisites - Python 3 and a clean checkout of this repository. No provider credentials or paid calls. ## Manual Test Plan 1. [ ] **Action:** Read `packages/issue-designer-default/SKILL.md` and verify it asks for a specific unresolved question and available evidence when a readiness input cannot be observed. **Expected:** The instruction gives a new Planner enough non-secret retrieval context and does not claim the Designer can inspect a host through an unassigned tool. ## Post-Merge Cleanup After review and merge, publish the immutable `v0.6.1` tag at the merged package commit before RelayView pins it as a public release.
anodyine added 1 commit 2026-11-05 08:58:23 -05:00
Strengthen Issue Designer cold-start readiness guidance
Check instruction packages / check (pull_request) Successful in 3s
Check instruction packages / check (push) Successful in 3s
e0a10bd418
Author
Owner

Review-loop evidence for PR #10: comparison base 082f225fd522c0c244e0537e6cb2be0b488268e4, reviewed head e0a10bd4189ae1d28feda23ea7ce01579f11f039. Standards: 0 actionable and 0 nonblocking findings. Spec (#950 readiness portion and this PR body): 0 actionable and 0 nonblocking findings.

On that committed head, python -m unittest discover -s tests -v passed 13 tests; python -m tools.packages check packages/issue-designer-default passed with identity 705c597605747d444b037a96664ef77bd95643ddeac88b250482a9a2dc65a150; git diff --check 082f225fd522c0c244e0537e6cb2be0b488268e4...HEAD passed. The worktree is clean. This PR is ready to merge. Publish tag v0.6.1 at the reviewed source commit e0a10bd4189ae1d28feda23ea7ce01579f11f039 after merge, matching RelayView #950's bundle lock.

Review-loop evidence for PR #10: comparison base `082f225fd522c0c244e0537e6cb2be0b488268e4`, reviewed head `e0a10bd4189ae1d28feda23ea7ce01579f11f039`. Standards: 0 actionable and 0 nonblocking findings. Spec (#950 readiness portion and this PR body): 0 actionable and 0 nonblocking findings. On that committed head, `python -m unittest discover -s tests -v` passed 13 tests; `python -m tools.packages check packages/issue-designer-default` passed with identity `705c597605747d444b037a96664ef77bd95643ddeac88b250482a9a2dc65a150`; `git diff --check 082f225fd522c0c244e0537e6cb2be0b488268e4...HEAD` passed. The worktree is clean. This PR is ready to merge. Publish tag `v0.6.1` at the reviewed source commit `e0a10bd4189ae1d28feda23ea7ce01579f11f039` after merge, matching RelayView #950's bundle lock.
anodyine merged commit 0e00dff4ec into main 2026-11-05 11:35:56 -05:00
anodyine deleted branch ISSUE-950 2026-11-05 11:35:56 -05:00
Author
Owner

Merged PR #10 as merge commit 0e00dff4ec4358dd1f0937e59f63a26a4702930d. Published public tag v0.6.1 at its reviewed source head e0a10bd4189ae1d28feda23ea7ce01579f11f039; remote tag readback matches. RelayView #950's npm run verify:first-party-skills-source now passes against that public release and the bundled lock at product head 1411b0053b407f851860d6018345ab29c2600b40.

Merged PR #10 as merge commit `0e00dff4ec4358dd1f0937e59f63a26a4702930d`. Published public tag `v0.6.1` at its reviewed source head `e0a10bd4189ae1d28feda23ea7ce01579f11f039`; remote tag readback matches. RelayView #950's `npm run verify:first-party-skills-source` now passes against that public release and the bundled lock at product head `1411b0053b407f851860d6018345ab29c2600b40`.
Sign in to join this conversation.