Skip to content

fix: legacy verification への append で Transferable Principles が蒸発する経路を塞ぐ - #10

Merged
penne-0505 merged 1 commit into
mainfrom
fix/legacy-verification-append
Aug 4, 2026
Merged

fix: legacy verification への append で Transferable Principles が蒸発する経路を塞ぐ#10
penne-0505 merged 1 commit into
mainfrom
fix/legacy-verification-append

Conversation

@penne-0505

Copy link
Copy Markdown
Owner

概要

v1.3.0 の初回フィールド観察 (otibo-dev、2026-08-05) で発見された escape path の修正。詳細な診断は #9 を参照。

既存の qa_schema: 2 verification へ新 round を append する経路 (成熟 repo での常態) が「New documents use qa_schema: 3」の字義をすり抜け、さらに記録先 fallback が summary / PR を許していたため、PR を使わない運用では Transferable Principles が session とともに蒸発していた。

変更内容

  • quality_assurance.md: 新 round の append は同じ編集内で qa_schema: 3 へ移行 (リンク / typo のみは legacy 可、intent 側の既存規則と同型)。summary / PR への記録は verification を作らない Fast Track に限定
  • qa-review skill (両 copy): append 時の schema 昇格規則を Rules に追加
  • post-implementation skill (両 copy): Record location の優先順位を反転 — verification が存在する限り常に verification へ。legacy schema は summary へ逃がす理由にならない
  • eval case 追加: legacy-verification-append — この escape path と逆振れ (不要な移行、過去 round の改変) の両方を検査対象に明記

変更しないこと

検証

  • ./scripts/check-docs.sh PASS (validators / hook tests / smoke tests / markdownlint)

Closes #9

🤖 Generated with Claude Code

…e principles

Field observation after the v1.3.0 migration (otibo-dev, 2026-08-05): two
substantive commits appended rounds to existing qa_schema 2 verifications and
left zero durable Transferable Principles records. Two defects converged:

- qa-review only said "New verification documents use qa_schema: 3", so the
  append path — the common case in mature repos — never triggered schema 3.
  The intent side already had the analogous rule ("meaning-adding edits
  migrate"); it was never ported to QA docs.
- post-implementation's record-location fallback sent reflections to the final
  summary / PR when the section was absent. With direct-to-main commits the
  summary evaporates with the session.

Appending a new round now upgrades the document to qa_schema 3 in the same
edit; the summary fallback is restricted to true Fast Track (no verification
exists). Validator is deliberately unchanged: an append event is statically
indistinguishable from legitimate pre-v1.3.0 multi-round documents, so
enforcement stays with skills and review.

Adds the legacy-verification-append eval case covering the escape path.

Closes #9

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@penne-0505
penne-0505 merged commit e7562af into main Aug 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: legacy verification への append で Transferable Principles が蒸発する経路を塞ぐ

1 participant