Skip to content

docs(release-audit): Telegram Android capture pass (2026-07-20) - #54

Merged
ifuensan merged 1 commit into
mainfrom
audit/capture-results-android
Jul 21, 2026
Merged

docs(release-audit): Telegram Android capture pass (2026-07-20)#54
ifuensan merged 1 commit into
mainfrom
audit/capture-results-android

Conversation

@ifuensan

@ifuensan ifuensan commented Jul 21, 2026

Copy link
Copy Markdown
Owner

Registra el pase de captura on-device en Telegram Android contra v0.4.4 (11 capturas, las 13 variantes de listing + las reales del Corsair).

Contenido byte-fiel en todas — escapes resueltos, negrita/cursiva, emoji intactos, banners de edición encima del cuerpo, teclados correctos, price_drop_ping en texto plano. Con esto la columna Android queda completa y se cubre la celda de price_drop_ping que faltaba en Desktop.

Anomalía ! cosmética, NO bloqueante: la fila 💶 hace soft-wrap a dos líneas en Android con el tamaño de fuente del operador (… + 4,82 / Protección = 63,32 €). Es el reflow normal de líneas largas de Telegram — la cabecera de precio y la línea de Confidence también hacen wrap —, no una ruptura de markup: texto idéntico al de referencia, sin escape colado ni emoji corrupto, legible. Falla el invariante literal "💶 en una línea" pero no cumple ningún criterio de bloqueo. Veredicto: limitación documentada, no BLOCKED. Si se quisiera una línea, sería un ticket de diseño post-v1.0 (acortar la fila), no un parche de auditoría (formato FR22-locked).

§2 colorblind (glifos nuevos): 💶/📉 son informativos, no portan señal; el par 🔴/🟢 son los tokens de severidad ya auditados y la palabra del banner (RESERVADO/Disponible/Bajada) lleva el estado. Sin dependencia de color nueva → el contrato UX-DR22 se sostiene por inspección.

Sigue abierto (ambos clientes ya capturados): el vistazo §3 al ciclo de teclado y una edición real in-place — los dos requieren un evento en vivo, no un emit.

Solo docs.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GCRu65gaarXToBMgxJhFep

Summary by CodeRabbit

  • Documentation
    • Expanded the v0.4.4 re-audit with Android capture results for all 13 listing variants.
    • Documented byte-faithful rendering, emoji and keyboard/button behavior, and color-blind considerations.
    • Recorded a non-blocking Android line-wrap limitation for the 💶 row.
    • Updated capture status and clarified remaining open items, including keyboard lifecycle transitions and in-place editing.

All 13 listing variants captured on Android (incl. price_drop_ping, the
Desktop gap) render content byte-faithful. One cosmetic non-blocking
anomaly: the 💶 buyer-total row soft-wraps to two lines at the operator's
Android font size (clean reflow, no markup break) — documented as a
limitation, not BLOCKED; a one-line fix would be a post-v1.0 design
ticket (FR22-locked row). §2 for the new glyphs holds by inspection
(text carries the signal). Still open: §3 keyboard-lifecycle + a real
in-place edit, both needing a live event.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GCRu65gaarXToBMgxJhFep
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The audit summary updates the v0.4.4 capture status, documents Android results for all 13 listing variants and live Corsair evidence, records emoji wrapping and color-blind guidance, and lists remaining lifecycle and in-place edit checks.

Changes

Telegram Android audit

Layer / File(s) Summary
Android capture results
docs/release-audits/v1.0/SUMMARY.md
Updates price_drop_ping, records two live Corsair alerts, and documents byte-faithful Android rendering, emoji handling, and the non-blocking 💶 soft-wrap.
Audit follow-ups
docs/release-audits/v1.0/SUMMARY.md
Keeps keyboard-lifecycle and true in-place edit verification open, and records a transient operational alert outside the audit variants.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

  • ifuensan/salvager#51: Updates the same v1.0 audit summary with Android capture outcomes and related variant invariants.
  • ifuensan/salvager#52: Tracks Telegram v0.4.4 capture statuses for the same variants across Desktop and Android.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: a release-audit docs update documenting the Telegram Android capture pass.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch audit/capture-results-android

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/release-audits/v1.0/SUMMARY.md`:
- Around line 149-150: Update the Desktop status cell for price_drop_ping to use
an allowed checklist marker: leave it blank while retaining the Android-only
explanation in the note, or define — in the documented capture-status vocabulary
before using it.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4dfbc1fd-eb80-4820-8277-3906c6e0e945

📥 Commits

Reviewing files that changed from the base of the PR and between e665c29 and 5be9bcf.

📒 Files selected for processing (1)
  • docs/release-audits/v1.0/SUMMARY.md

Comment on lines +149 to 150
| `price_drop_ping` | — | not in this batch; captured on Android instead (below) |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Use a defined capture-status marker for the Desktop gap.

The checklist below permits only , !, or blank, but this cell introduces without defining it. Either leave the Desktop cell blank and explain the Android-only capture in the note, or add to the documented status vocabulary.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/release-audits/v1.0/SUMMARY.md` around lines 149 - 150, Update the
Desktop status cell for price_drop_ping to use an allowed checklist marker:
leave it blank while retaining the Android-only explanation in the note, or
define — in the documented capture-status vocabulary before using it.

@ifuensan
ifuensan merged commit 51d61aa into main Jul 21, 2026
9 checks passed
@ifuensan
ifuensan deleted the audit/capture-results-android branch July 21, 2026 19:37
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