feat(tradein): dual-display asking vs expected-sold in HeroSummary (#648 S5a) #664
No reviewers
Labels
No labels
admin
analytics
auth
automation
bug
business
chore
ci
compliance
data
data-moat
docs
duplicate
dx
enhancement
Fable 5 ревью
feedback/max
generative
GG-форсайт
needs-discussion
needs-human
observability
pause-bots
performance
priority/p0
priority/p1
priority/p2
priority/p3
scope/backend
scope/db
scope/devops
scope/frontend
scope/qa
scrapers
security
site-finder
stage/1
stage/2
status/blocked
status/done
status/needs-analysis
status/needs-fix
status/qa
status/ready
status/review
status/wip
tech-debt
tradein
ux
week ревью 1
wontfix
вторичка
ИРД
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lekss361/gendesign#664
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feat/648-s5a-frontend-dual-display"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stage 5a of #648 — estimate hero shows BOTH «Ориентир запроса» (asking) and «Ожидаемая цена продажи» (expected sold) at EQUAL weight (Anton: «обе равнозначно»), with −N% discount chip + explainer. Graceful single-figure fallback when expected_sold null. Tokens-only, responsive, a11y. code-reviewer ✅ (equal-weight confirmed; div-by-zero provably unreachable via cross-layer invariant; graceful guards robust). tsc clean + build passes. Refs #648 (S5a/5).