Reconcile tools/{issue-ready,memory-index}.py with init-workspace upstream without losing the #56 and #63 fixes

[prekabreki]

Context

#63 was closed by #68, but its Constraints section asked for the tools to be re-copied
from the init-workspace skill rather than hand-patched, so this repo would stop drifting
from upstream. The executor hand-patched blocked_by() instead. The bug is fixed; the drift
is not. This issue closes the drift.

Measured 2026-08-30 against ~/git/vibe-skills/petur-skills/skills/init-workspace/assets/tools/:

file	upstream	repo	differing lines
issue-ready.py	245L	266L	21
memory-index.py	79L	67L	24
session-start-context.py	95L	95L	0 (already in sync)

Acceptance criteria

• tools/issue-ready.py and tools/memory-index.py are reconciled with upstream, with no
  capability lost in either direction (see Danger zones for the specific losses to avoid).
• The UTF-8 handling from Fix yt-dlp resolution under --user installs, and the UTF-8 crash hiding ready work #56 still works after reconciliation.
• The ## Blocked by list-item detection from issue-ready.py misses the list form of Blocked by, so blocked issues are offered as ready #63 still works after reconciliation.
• Whatever upstream memory-index.py has that this repo's 67-line copy lacks is either
  carried in, or a one-line comment in the file says why it was deliberately dropped.
• tools/session-start-context.py is left byte-identical (already in sync, do not touch).
• The full test suite is green.

Files / where this lives

• tools/issue-ready.py (266L) - carries the Fix yt-dlp resolution under --user installs, and the UTF-8 crash hiding ready work #56 UTF-8 fix at lines ~90 and ~210, plus the issue-ready.py misses the list form of Blocked by, so blocked issues are offered as ready #63 patch in blocked_by()
• tools/memory-index.py (67L)
• tools/tests/test_issue_ready_blocking.py - the issue-ready.py misses the list form of Blocked by, so blocked issues are offered as ready #63 tests, must stay green
• Upstream: ~/git/vibe-skills/petur-skills/skills/init-workspace/assets/tools/

How to verify

• ./.venv/bin/python -m unittest discover -s tools/tests -v - 14 tests, all green
• ./.venv/bin/python -m unittest discover -s tests - full suite, 257 tests, green
• ./.venv/bin/python tools/issue-ready.py - output format unchanged, and Re-enable the target-resolution + sharpen UI once the feature is ready #41 absent while Verify HDR/10-bit passthrough through libplacebo on real HDR footage #33/Add FSRCNNX-8 neural upscale option via libplacebo custom_shader_path #37 are open
• diff <(cat ~/git/vibe-skills/petur-skills/skills/init-workspace/assets/tools/session-start-context.py) tools/session-start-context.py - must be empty

Constraints

• Use ./.venv/bin/python, not bare python. A bare python is the system 3.14 and makes
  tests/test_tool_resolution.py fail spuriously (it skips under prefix == /usr). That false
  red already happened once, on issue-ready.py misses the list form of Blocked by, so blocked issues are offered as ready #63.
• Do not change issue-ready.py's output format - the SessionStart hook renders it verbatim.
• Do not touch tools/session-start-context.py.
• Reconciliation may well mean patching upstream first and then copying down, rather than
  copying down and re-patching. Either order is fine; losing a fix is not.

⚠ Danger zones (review focus)

• The drift is bidirectional, so a blind cp from upstream is a regression, not a fix.
  Overwriting tools/issue-ready.py with the 245-line upstream file deletes BOTH the Fix yt-dlp resolution under --user installs, and the UTF-8 crash hiding ready work #56 UTF-8
  fix and the issue-ready.py misses the list form of Blocked by, so blocked issues are offered as ready #63 ## Blocked by fix, and the suite may still look green if nothing exercises
  them. Diff in both directions before copying anything.
• issue-ready.py's output is what an autonomous wave treats as "safe to start". Under-detection
  is silent and only shows up later as an executor picking up genuinely blocked work. Re-test the
  list form with blockers partially satisfied, not just present.
• The 24 differing lines in memory-index.py are unexamined. Read them before deciding direction;
  the repo being 12 lines shorter does not mean it is behind.

Out of scope

• Any new parser feature beyond what issue-ready.py misses the list form of Blocked by, so blocked issues are offered as ready #63 already landed.
• The deferred label / held-work concept, unless it comes free with the reconciliation.
• Changing init-workspace itself beyond what is needed to carry a fix upstream.

Notes

• Executor tier: cheap.
• Follow-up to issue-ready.py misses the list form of Blocked by, so blocked issues are offered as ready #63 (closed by Fix issue #63: Detect list form of 'Blocked by' heading #68).