Skip to content

Fix HIGH priority v2.8 version references (semantic classification)#4

Open
gmelli wants to merge 1 commit into
mainfrom
fix-v2.8-semantic-refs
Open

Fix HIGH priority v2.8 version references (semantic classification)#4
gmelli wants to merge 1 commit into
mainfrom
fix-v2.8-semantic-refs

Conversation

@gmelli
Copy link
Copy Markdown
Member

@gmelli gmelli commented Nov 11, 2025

Summary

Fixes 5 HIGH priority version references that signal current version to users.

Root Cause (v2.8 Gap 4)

Classification by location (footers, content) instead of semantics (current vs historical):

  • Wrong: Footers = HIGH, Content = MEDIUM
  • Right: Current examples = HIGH, Historical facts = LOW

Changes

GETTING_STARTED.md (3 tutorial examples):

  • Line 245: Project Context section template: v2.7.0v2.8.0
  • Line 332: Git commit message example: v2.7.0v2.8.0
  • Line 371: Expected wake-up response: v2.7.0v2.8.0

TEMPLATE_SELECTOR.md (2 current migration examples):

  • Line 246: Supervisor use case: v2.6 → v2.7v2.7 → v2.8
  • Line 637: Example 4 migration: v2.6 → v2.7v2.7 → v2.8

Impact

Before: Version confusion

  • Footer: "v2.8.0" ✅
  • Tutorial examples: "v2.7.0" ❌
  • Users confused: "Which version is current?"

After: Consistency

  • Footer: "v2.8.0" ✅
  • Tutorial examples: "v2.8.0" ✅
  • Migration examples: "v2.7 → v2.8" ✅

Semantic Classification Framework

Priority Semantic Meaning Fix?
HIGH Current version signals (tutorials, migration, "Current Version") ✅ YES
MEDIUM Historical progression (timelines, feature notes) ⚠️ OPTIONAL
LOW Historical facts (extraction dates, changelog) ❌ NO

Related

  • Analysis: private-supervisor-AGET workspace/V2.8_PHASE8_SEMANTIC_GAP_ANALYSIS.md
  • Learning: v2.8 Gap 4 - Semantic Classification Error
  • Remaining: 10 HIGH priority refs in template READMEs (separate PR)
  • v2.9 Enhancement: Semantic validation added to Gate 8.3

Verification

# No HIGH priority refs should show v2.7 in current examples
gh api repos/aget-framework/.github/contents/profile/GETTING_STARTED.md | jq -r '.content' | base64 -d | grep -E "v2\.7\.0.*tutorial|commit.*v2\.7|wake.*v2\.7"
# Should return empty

# Migration examples should show v2.7 → v2.8
gh api repos/aget-framework/.github/contents/profile/TEMPLATE_SELECTOR.md | jq -r '.content' | base64 -d | grep "migration"
# Should show "v2.7 → v2.8"

🤖 Generated with Claude Code

Fixes 5 HIGH priority version references that signal current version:
- GETTING_STARTED.md: 3 tutorial examples (v2.7.0 → v2.8.0)
  - Line 245: Project Context section template
  - Line 332: Git commit message example
  - Line 371: Expected wake-up response
- TEMPLATE_SELECTOR.md: 2 current migration examples (v2.6→v2.7 → v2.7→v2.8)
  - Line 246: Supervisor use case bullet
  - Line 637: Example 4 fleet migration scenario

Classification: HIGH priority (tutorial copy-paste + current migration examples)
Root Cause: v2.8 Gap 4 - classified by location (footers) instead of semantics (current examples)
Impact: Version confusion - users saw v2.8.0 footer but v2.7.0 examples

Semantic Framework Applied:
- HIGH: Current version signals (tutorials, migration, "Current Version")
- MEDIUM: Historical progression (timelines, feature notes)
- LOW: Historical facts (extraction dates, changelog)

Related: v2.8 Phase 8 Gap 4, workspace/V2.8_PHASE8_SEMANTIC_GAP_ANALYSIS.md

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
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