RPS V1 PR1: Naming reconciliation + Wall package re-home#144
Merged
Conversation
…SuspectedCause → Hypothesis rename
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…e fields Patch type was Partial<Hypothesis>, allowing patches to id/createdAt/ deletedAt. Per EntityBase contract these are immutable. Tightened to Partial<Omit<Hypothesis, 'id' | 'createdAt' | 'deletedAt'>> per RPS V1 spec D8 + reviewer flag. Co-Authored-By: ruflo <ruv@ruv.net>
…d compat) D15 commits to clean breaks in design phase. Stored-value migration shim mapping 'suspected'/'not-confirmed' to new HypothesisStatus values contradicts D15 + dev fixtures already reset via pnpm dev:reset (per OQ7). Replaced normalizeHypothesisStatus() with assertHypothesisStatus() that fails loud on unknown status values. Updated the corresponding test from "migrates legacy values" to "throws on unknown values". Co-Authored-By: ruflo <ruv@ruv.net>
jukka-matti
added a commit
that referenced
this pull request
May 13, 2026
…80, log shipment All 10 PRs of Response Path System V1 merged on main 2026-05-09 → 2026-05-13 (#144 / #147 / #148 / #149 / #150 / #151 / #152 / #153 / #154 / #155). This commit syncs tracking docs that the squash merges left stale: - docs/roadmap.md: PR-RPS-9 + PR-RPS-10 SHIPPED rows; flip §3 to "10 of 10"; free up ADR-080 slot from the 8f canvas viewport item (taken by Sustainment) - docs/decision-log.md: pin "2026-05-13 — RPS V1 SHIPPED — full lifecycle live" - docs/07-decisions/adr-080-sustainment-auto-fire-pattern.md (new): document the Sustainment-shaped lifecycle pattern (auto-fire + Inbox prompt + signoff tier gate) as a pattern reference for future response-path lifecycles, per plan §PR-RPS-9 ledger line 2231 - docs/07-decisions/index.md: add rows 078 / 079 / 080 (078+079 also weren't indexed when shipped) - Spec + plan frontmatter: draft/active → delivered, last-reviewed 2026-05-13 Co-Authored-By: ruflo <ruv@ruv.net>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pure refactor implementing PR-RPS-1 per
docs/superpowers/plans/2026-05-09-response-path-system-v1.md:SuspectedCause->Hypothesisacross live code, persistence surfaces, stores, hooks, apps, UI, and AI contextMechanismBranchStatus+WallStatusinto the 5-stateHypothesisStatussuspectedCauseId->hypothesisIdandSUSPECTED_CAUSE_*actions ->HYPOTHESIS_*InvestigationWallfrom@variscout/chartsto@variscout/uiHypothesis.themeTags?: string[]and WallTagChiprenderingNo deprecated aliases, transition fields, or charts re-export shims were added, per RPS V1 D15/D17.
Test plan
pnpm --filter @variscout/core testpnpm --filter @variscout/charts testpnpm --filter @variscout/ui testpnpm --filter @variscout/hooks testpnpm --filter @variscout/stores testpnpm --filter @variscout/pwa testpnpm --filter @variscout/azure-app testpnpm --filter @variscout/ui buildbash scripts/pr-ready-check.sh