[P1][Plan 5] SF-028 — Standardize Hacker News identifier as `hackernews`

[Ankit6149]

Confirmed problem

The main product uses hackernews, while social status and ZIP paths use hn in places. Status, connection reason, generation, export, and UI lookups can disagree or omit Hacker News-specific data.

Scope

• Define hackernews as the only canonical internal identifier.
• Add a temporary migration/compatibility adapter for saved data or API payloads using hn.
• Update platform metadata, provider prompts, quality checks, social status, persistence, exports, tests, and documentation.
• Prevent new code from introducing alternate aliases.

Acceptance criteria

• Every active internal contract uses hackernews.
• Legacy hn saved/API data migrates safely where required.
• Hacker News status, drafts, quality data, exports, and UI cards connect correctly.
• A full repository search finds no active conflicting identifier.
• Other platform IDs are also documented in one canonical registry.

Required verification

• Identifier registry tests.
• Legacy migration test.
• Generation/status/export integration test for Hacker News.
• Repository-wide alias search.