chore(message-parser): tracking issue for parser correctness, performance, and test hardening

[Shreyas2004wagh]

Description:

Create a single tracking issue for all message-parser findings and PRs so maintainers can follow progress in one place, while keeping individual fixes in small mergeable PRs.

Steps to reproduce:

1. Check message-parser issues/PRs opened over the last few days.
2. Notice each finding is tracked as a separate issue without a parent tracker.
3. It is harder to see overall progress, remaining scope, and rewrite readiness in one view.

Expected behavior:

A single umbrella issue exists with a checklist of all parser findings, each linked to its issue/PR and marked as done/in progress/pending.

Actual behavior:

Findings are currently spread across multiple separate issues/PRs, making consolidated progress tracking harder.

Server Setup Information:

• Version of Rocket.Chat Server: N/A (tracking/process issue)
• License Type: N/A
• Number of Users: N/A
• Operating System: N/A
• Deployment Method: N/A
• Number of Running Instances: N/A
• DB Replicaset Oplog: N/A
• NodeJS Version: N/A
• MongoDB Version: N/A

Client Setup Information

• Desktop App or Browser Version: N/A
• Operating System: N/A

Additional context

Tracking checklist:

Tracking checklist:

• Ordered list index 0 lost in LIST_ITEM AST: issue Ordered list items with index 0 lose number field in message parser AST #39051, PR fix(message-parser): preserve ordered list index 0 in LIST_ITEM nodes #39052 (merged)
• Hot-path allocation reductions in parser helpers: issue Performance bug: message parser hot-path helpers allocate excessive temporary arrays #39074, PR refactor: reduce hot-path allocations in message parser utils #39075 (merged)
• Timestamp test oracle decoupling from internals: issue Test bug: message-parser tests are oracle-coupled to production helpers #39085, PR test(message-parser): decouple parser tests from production helpers #39086 (merged)
• Related perf improvement (reducePlainTexts): issue Performance: reducePlainTexts causes excessive allocations in message parser hot path #38900, PR refactor: make reducePlainTexts linear and allocation-light #38901 (merged)
• ASTNode union completeness/type narrowing: issue Message parser ASTNode types are incomplete and break type narrowing for valid parser output #39057, PR chore(message-parser): align ASTNode union with parser output #39058 (open)
• Invalid absolute URL protocol-duplication handling: PR fix(message-parser): avoid protocol duplication for invalid absolute URLs #39293 (open)
• Simplify Any fallback URL/phone parsing path: PR refactor(message-parser): simplify Any fallback to reduce URL/phone parse attempts #39294 (open)
• Parse-local skip flags refactor: PR refactor(message-parser): make skip flags parse-local #39477 (open)
• Tighten parser test assertions (toMatchObject -> stricter structure): PR test(message-parser): tighten AST assertions #39438 (open)

Relevant logs:

N/A (tracking/process issue; no runtime logs required).

[Shreyas2004wagh]

@ggazzo as requested, I created this single tracking issue for message-parser findings and linked the current PRs here. I’ll keep adding future parser findings/PRs to this thread.

[Shreyas2004wagh]

@ggazzo as requested, I’m tracking message-parser work in this umbrella issue now. I’ve also opened two new related PRs: #39293 and #39294 . Could you please review them?

[Shreyas2004wagh]

Hi @ggazzo , I’ve finished the remaining message-parser findings and opened the related PRs. Could you take a look when you have time? I’ve linked everything in this tracking issue for easier follow-up.

[Shreyas2004wagh]

Hi @ggazzo , could you please review these issues and the linked pr's when you get time??