[wukongnotnull]

This PR MUST target the main branch. Active work is developed on
focused branches and merged directly into main after review.

Tracking: #61

Who is submitting this PR? (required)

Field	Value
Your model + version	Cursor Grok 4.7 (originalModelName: grok-4.7)
Harness + version	Cursor cloud agent
All plugins installed	none beyond the Cursor cloud-agent environment (MCP namespaces present: cursor-cloud, cursor-subscriptions, Gmail; cursor-cloud was used only to read this run's model id; the others were unused)
Human partner who reviewed this diff	悟空非空也g — asked to 发版. origin/main already contains merged #60

What problem are you trying to solve?

Manifests on main still say 6.6.0 while PR #60 is already merged. Users who install by version, and bug reports that cite 6.6.0, cannot distinguish the recording-qa-to-issues skill from the tagged release. RELEASE-NOTES.md has no dated section for that commit. 悟空非空也g asked to 发版 on current origin/main (tag v6.6.0 plus #60).

This is the same problem #57 solved for 6.6.0, #54 solved for 6.5.0, and #39 solved for 6.4.0: ship the version number and notes together so harness install paths and the changelog match main.

What does this PR change?

Runs scripts/bump-version.sh 6.7.0 on the seven declared files (package.json, Claude/Cursor/Codex/Kimi plugin manifests, Claude marketplace plugin version, product-design.lock.json wukong_code_version). Adds ## v6.7.0 (2026-10-14) describing only PR #60. Updates the README Product Design version line and the docs/prd.md current-version line so the snapshot matches the tag.

Is this change appropriate for the core library?

Yes. This is core plugin release metadata and notes, not a new skill, not a third-party dependency, and not a rewrite of behavior-shaping skill text. The skill already landed in #60. The lock-file wukong_code_version field is outside the hashed Product Design import boundary (same as #39, #54, and #57).

What alternatives did you consider?

• Patch 6.6.1. Rejected: feat(skills): record questions and replies as GitHub issues #60 is a user-visible new skill (feat: recording-qa-to-issues), not a broken-install fix or a docs-only typo. Same reasoning as Release v6.6.0 #57 rejecting 6.5.1 for the grilling HANDOFF change.
• Major 7.0.0. Rejected: no harness install incompatibility or removals. A new skill is additive. This repo shipped new skills inside 6.x minors (for example the grilling spec handoff in 6.4.0). A new skill is not an automatic major.
• Leave feat(skills): record questions and replies as GitHub issues #60 out of the notes. Rejected: it is the only commit range after v6.6.0 (256c535, merge 7ec3304).
• Invent extra features in the notes. Rejected by the release request.
• Rewrite docs/prd.md so it counts 27 skills. Not in this PR. feat(skills): record questions and replies as GitHub issues #60 updated the five READMEs to 27 and left the PRD sentence at 26. Release v6.6.0 #57 only changed the PRD version line; this PR does the same. The stale count is noted on Ops: release v6.7.0 from current main #61.
• npm publish or a Codex portal zip in this PR. Out of scope. registry.npmjs.org/wukong-code is HTTP 404 (re-checked 2026-10-14). The v6.6.0 GitHub Release has no assets. scripts/package-codex-plugin.sh is maintainer-side and was not attached to Release v6.6.0 #57's release. After merge, the follow-up is an annotated v6.7.0 tag and a GitHub Release whose body is the dated notes.

Does this PR contain multiple unrelated changes?

No. Every file is the version bump, the release-notes heading for that bump, or the two version strings the previous release PR also updated (README Product Design line and docs/prd.md).

Existing PRs

• I have reviewed all open AND closed PRs for duplicates or prior art
• Related PRs: Release v6.6.0 #57 (Release v6.6.0 — same path; this is the next cut, not a redo), Release v6.6.0 notes: product commits are #55 #58 (v6.6.0 notes range correction), Release v6.5.0 #54 (Release v6.5.0), Release v6.4.0 #39 (Release v6.4.0), docs: add Unreleased release-notes entry for #37–#45 #46 (Unreleased notes, already consumed by Release v6.5.0 #54), Release v6.2.0 #4 / Release v6.2.1 #10 (older release PRs), feat(skills): record questions and replies as GitHub issues #60 (content being dated, not re-landed). No open duplicate release PR. No open or closed PR titled for 6.7.0.

Difference from #57: that PR dated only #55. This PR dates only #60. It does not change skills or tests.

Environment tested

Harness (e.g. Claude Code, Cursor)	Harness version	Model	Model version/ID
Cursor cloud agent (this checkout)	Cursor cloud agent Linux VM, Oct 2026	Cursor Grok 4.7	grok-4.7

Local: bash scripts/bump-version.sh --check — all seven files at 6.7.0; audit found no undeclared 6.7.0 strings. bash tests/skills/test-gemini-retirement.sh — PASS including ## v6.7.0 in release notes. npm run test:extended — PASS after installing host rsync (preflight needs it; not a new plugin dependency). bash scripts/lint-shell.sh --all — PASS with shellcheck 0.9.0; this PR does not change shell scripts. CI on this PR is the extended suite plus ShellCheck.

New harness support (required if this PR adds a new harness)

Not applicable. This PR does not add a harness.

Clean-session transcript for "Let's make a react todo list"

N/A — not a new harness integration.

Evaluation

• What was the initial prompt you (or your human partner) used to start the session that led to this change? 悟空非空也g asked to 发版 on current origin/main, which includes v6.6.0 and merged feat(skills): record questions and replies as GitHub issues #60.
• How many eval sessions did you run AFTER making the change? Zero skill-behavior evals. This PR does not change skill or hook text. feat(skills): record questions and replies as GitHub issues #60 already landed the skill.
• How did outcomes change compared to before the change? Version check and the Gemini retirement notes gate now see 6.7.0; the extended suite still passes. No new agent-behavior claim.

Language-pack evidence

• Language and support status: n/a (no language pack change)
• Real failure generic methodology handled incorrectly: n/a
• Project markers and toolchain versions: n/a
• Official sources: n/a
• No-guidance repetitions and failures: n/a
• With-guidance repetitions and results: n/a
• Monorepo, unsupported-language, and docs-only controls: n/a
• Human reviewer familiar with the language: n/a
• Frameworks or third-party preferences introduced: none

Rigor

• If this is a skills change: I used wukong-code:writing-skills and completed adversarial pressure testing (paste results below)
• This change was tested adversarially, not just on the happy path
• I did not modify carefully-tuned content (Red Flags table, rationalizations, "human partner" language) without extensive evals showing the change is an improvement

Not a skills change. Adversarial here means: bump-version.sh --audit reports no undeclared 6.7.0 hits; the Gemini retirement test requires the dated ## v6.7.0 heading; the extended suite and ShellCheck were run, not only --check.

Human review

• A human has reviewed the COMPLETE proposed diff before submission

悟空非空也g explicitly asked to 发版 this repo, authorized a release PR targeting main, and #60 (the only post-6.6.0 product change) is already merged. The diff in this PR is version metadata and notes for that already-merged history. The human should still glance at RELEASE-NOTES.md wording on GitHub before relying on the GitHub Release object.