feat: open Ask Agent cited posts onto Event Lineage (v2.16.0)

[seonghobae]

Summary

Stacked on #262. Opening an Ask Agent cited post uses the same Event Lineage focus contract as Weekly VOC, Calendar, and Customer master.

• After an authorized answer, cited posts are named as current and can be opened onto Event Lineage (ADR 0096).
• The opened post is marked current, with Keyman and evaluation as the next read.
• A Board home-list open does not gain Ask-origin focus or copy.
• No TEPP theta, cutoff body, or cited post is invented.

Correctness repair

When a buyer submitted a second question, the previous answer and its cited-post next action remained visible while the new request was pending. Those stale citations were still clickable and labelled as current even though they belonged to the prior question.

A bounded one-shot RED→GREEN workflow now submits one completed question and a deferred second question, proves the previous answer and Next action remain visible before the fix, clears superseded answer state as soon as the new Ask begins, then runs the focused and full frontend suites, lint, production build, and Storybook. It publishes only from the exact tested head and removes itself before the production commit.

No passing result is claimed while that exact-head workflow remains queued, running, or failed.

Merge safety

• Keep this PR Draft until the one-shot workflow has published its production commit and removed the repair workflow.
• Re-check the exact head and current base after publication; concurrent restacking has moved this branch.
• Required current-head checks and a qualifying independent approval must be terminal-success.
• Do not self-approve, force-merge, or reuse the earlier 121 passed evidence as current-head evidence.
• Issues Milestone 2: port verified direct-PostgreSQL analysis into the protected product architecture #79 and Milestone 2.1: add normalized runtime-analysis schema bridge after v0.77 #87 remain open.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: abc337bc-1818-4d6d-baac-176904219ba6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[seonghobae]

Cycle 2026-08-19T16:31 KST. Exact head 0aaf992. Frontend 121 passed, oxlint clean, production build succeeded. Independent exact-head APPROVE required. Do not self-approve. Issues #79 and #87 stay open.

[seonghobae]

Cycle retry 2026-08-19T14:08Z: exact head remains 0aaf992fab65a2e1ad6d41d5de8a7cad1825e04c (v2.16.0). Independent exact-head APPROVE still required. Do not self-approve. Next buyer gap after this Event Lineage focus contract is Keyman/evaluation landing under that focused heading (v2.17.0), stacked on this branch, not mixed into #92.

[seonghobae]

Cycle 2026-08-19T14:10Z: exact head remains 0aaf992 (v2.16.0 Ask Agent → Event Lineage). Independent exact-head APPROVE still required — do not self-approve. Next buyer increment is v2.17.0: preserve GNB focus flags when opening a linked Event Lineage DAG node from a focused popup so the Keyman/eval next-action contract stays on the walk. Issues #79 and #87 stay open. Do not mix into #92.

[seonghobae]

v2.17.0 stacked as #264 @ 3e5bfca on this exact head 0aaf992. Independent exact-head APPROVE still required on this PR — do not self-approve.