Skip to content

docs: PLAN-v0.2.9 — AI Understanding Layer Refactor - #25

Merged
MedivhStory merged 2 commits into
mainfrom
docs/v0.2.9-plan
Apr 27, 2026
Merged

MedivhStory merged 2 commits into
mainfrom
docs/v0.2.9-plan

Conversation

@MedivhStory

Copy link
Copy Markdown
Owner

Planning document only. No implementation.

Charter

AI 理解层重构 — title, progress, summary become traceable, expirable, correctable, recall-supportive current interpretations of a session.

Locked decisions

  • Manual generation only (no auto-trigger in v0.2.9)
  • Hybrid migration: `understanding.json` read-only, `understanding-v2.json` new
  • Legacy snapshots permanent as "Pre-v0.2.9 baseline"
  • Adopt AI = pointer move + SelectionEvent (no fake manual artifact)
  • Rationale: Path A optional separate LLM call, current-only metadata
  • Desensitization: narrowly extend DesensitizeSession with fail-closed atomic write
  • Real samples: advisory in v0.2.9, not gate-blocking

Internal phasing

P1 (data model) → P2 (edit/regenerate) → P3 (staleness/history) → P4 (evidence) → P5 (long-session input + prompt) → P6 (desensitization + real samples) → P7 (rationale).

Single `v0.2.9` tag at end. Milestone release gate (synthetic fixtures must PASS) required before tagging.

Workspace

`ClaudeSessionHub_V0.2.9/` (new), based on origin/main at `37b50db`.

Charter: AI 理解层重构 - 让标题、进展、摘要成为可追溯、可过期、
可校正、可帮助回忆的当前解释。

Locked decisions:
- Manual generation only (no auto-trigger in v0.2.9)
- Hybrid migration: understanding.json read-only, understanding-v2.json new
- Legacy snapshots permanent as "Pre-v0.2.9 baseline"
- Adopt AI = pointer move + SelectionEvent (no fake manual artifact)
- Rationale: Path A optional separate call, current-only metadata
- Desensitization: extend DesensitizeSession narrowly, fail-closed atomic write
- Real samples: advisory in v0.2.9, not gate-blocking

Internal phasing: P1-P7, single v0.2.9 tag at end.
Milestone release gate required before tag (synthetic fixtures must PASS).
@MedivhStory

Copy link
Copy Markdown
Owner Author

Review checklist

Reviewers, please verify each of the following:

  • Does the plan preserve the v0.2.9 charter: manual generation + versioning + provenance + staleness + evidence layer + editable correction?
  • Does the hybrid migration avoid mutating or renaming `understanding.json`?
  • Does legacy data remain visible without fake provenance?
  • Does the display policy handle Manual / AI / Legacy / Rule precedence clearly?
  • Does "Adopt AI" preserve AI source and record selection/adoption instead of creating fake manual artifacts?
  • Does rationale stay optional and current-only?
  • Are real samples advisory only, not release-gate blocking?
  • Does the pre-tag checklist match PRODUCT-LINE.md milestone release flow?

Merge will not happen until:

  • CI is green (currently green)
  • This checklist has no unresolved objections

- SelectionEvent: add previousVersionID alongside targetVersionID
  for explicit adoption history
- LegacyUnderstandingSnapshot.generatedAt: Date -> Date?
  (legacy data may lack trustworthy generation time)
- UnderstandingArtifact.sessionFingerprint: String -> String?
  (required for .ai/.rule, optional for .manual)
- Pre-tag checklist: CHANGELOG step phrased as "before opening the
  release PR", untethered from gate artifact ordering

PLAN-only. No implementation.
@MedivhStory
MedivhStory merged commit d013734 into main Apr 27, 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.

1 participant