Add #698 vera shape to ROADMAP Phase 3a (Aver-inspired, paired with vera context)#699
Add #698 vera shape to ROADMAP Phase 3a (Aver-inspired, paired with vera context)#699aallan wants to merge 1 commit into
Conversation
New entry in Phase 3a (Agent integration), placed immediately after #523 vera context — both are Aver-inspired CLI tools for LLM-agent project navigation. Pairing them in the ROADMAP reflects their conceptual relationship: context says what's here, shape says what shape it is. Credit Szymon Teżewski (@jasisz1) / Aver for the proposal — this is the third Aver-inspired addition (after #523 vera context and the broader CLI naming convention). Vera's static information is richer than Aver's (declared effect rows, typed slot references, mandatory contracts) so the archetype classifier has more signal to work with. Docs-only PR — no version bump, no CHANGELOG entry needed (check_changelog_updated.py only fires for vera/ or spec/ changes). Co-Authored-By: Claude <noreply@anthropic.invalid>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR adds a single documentation entry to ChangesPhase 3a vera shape roadmap entry
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related issues
Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #699 +/- ##
=======================================
Coverage 90.92% 90.92%
=======================================
Files 60 60
Lines 23606 23606
Branches 259 259
=======================================
Hits 21464 21464
Misses 2135 2135
Partials 7 7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Adds #698
vera shapeto ROADMAP Phase 3a (Agent integration), placed immediately after #523vera context. The two are conceptual siblings:vera contextsays what's here — token-budgeted public-API export for LLM consumptionvera shapesays what shape it is — per-module histogram of function archetypes (match dispatcher / pipeline / orchestrator / pure helper / HOF wrapper / effect handler / Inference orchestrator / etc.) that maps onto architectural layers (domain / parse / command / AI-strategy / infra / handler)Both directly inspired by Aver creator Szymon Teżewski (@jasisz1) —
vera contextfrom theaver contextcommand shipped earlier;vera shapefrom his 24 May tweet proposingaver shape.Why this is more interesting in Vera than in Aver
Aver derives archetypes indirectly from what its grammar forbids (no if/else → match dispatchers; no loops → structural recursion). Vera permits if/else, loops, and lambdas, but adds three static signals Aver doesn't have:
@T.kfor somekstrictly smaller than its own arity."So Vera's archetype categories are different from Aver's (we have
Inference orchestratorandeffect handler; Aver has neither since it has no algebraic effects).Full design + Vera archetype list + classifier sketch in the issue body.
Why docs-only
Adds one bullet to
ROADMAP.mdPhase 3a. No code change.check_changelog_updated.pyonly fires forvera/orspec/changes, so no CHANGELOG entry needed. No version bump. No release after merge.Test plan
git diff --stat ROADMAP.md— 1 file changed, 1 insertion(+).pre-commit-config.yaml's default behaviour, even though no Python changed)🤖 Generated with Claude Code
Summary by CodeRabbit