feat: name Weekly VOC and focus Event Lineage (v2.13.0)

[seonghobae]

Summary

Stacked on current #258. Weekly VOC is a Board ISO-8601 week list filter; opening a filtered Voice of Customer post focuses Event Lineage.

• Weekly VOC keeps voc posts for the latest ISO week in the loaded list (UTC Thursday rule). Other VOC types and older weeks drop out.
• The Board names the next action: those posts are current; open one to read Event Lineage (ADR 0070).
• Opening that filtered post focuses the Event Lineage heading and names Keyman and evaluation next (ADR 0071).
• A home-list open does not steal focus or add that copy.
• Localizes the new copy in Korean, English, Chinese, Japanese, and Vietnamese.
• No TEPP theta is invented. No cutoff body is invented.

Evidence

• Frontend: 97 passed (isoWeek, i18n, App including both Weekly VOC tests).
• Synthetic fixtures only.

Merge safety

• Independent exact-head APPROVE required. Do not self-approve.
• Do not squash-merge without that approval.
• 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 stay open.
• PR feat: name Weekly VOC on Board as an ISO-week list filter (v2.12.0) #259 was closed as superseded (stale select-based type filter).

[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: de96a9b2-6f3f-4a73-9d24-2f5ae3a03afd

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]

Next buyer increment stacked as #261 (03a1167, v2.14.0): opening a Calendar commitment focuses Event Lineage. Independent exact-head APPROVE required on #258, this PR, and #261. Do not self-approve. Issues #79 and #87 stay open.

[seonghobae]

@opencode-agent Restack this existing PR only onto current #258 exact head 1dbace2. Preserve #260's Weekly VOC behavior and its RED/GREEN frontend tests, but do not bring the stale parent snapshot or the old parent-level migration/test failures forward. Current #258 already owns ADR 0070-0089, so renumber this PR's two Weekly VOC ADRs from 0070/0071 to 0090/0091 and update every in-repo reference/changelog pointer consistently. Keep #260 at v2.13.0 (parent is now v2.12.6). Resolve conflicts semantically: parent auth/migrations/embedding/Buyer fixes win unless this one-commit Weekly VOC delta intentionally changes the same line. Re-run focused isoWeek/i18n/App tests, full frontend tests, lint, Storybook build, production build, and the repository Python suite against the new exact head. Do not touch #258 or #261-#265, do not merge, and do not claim old checks as current-head evidence.

[seonghobae]

@opencode-agent Parent exact head moved during reconciliation. Use #258 current exact head ea77f76 as the only restack base; the earlier 1dbace2 instruction is stale. Keep all other constraints from comment 5349017533: Weekly VOC-only semantic delta, ADR 0090/0091, v2.13.0, parent fixes win on overlap, full exact-head verification, no merge and no edits outside #260.

[seonghobae]

@opencode-agent Parent moved again because the browser/API OIDC verifier was hardened after the earlier restack instruction. Use #258 current exact head a9165c6 as the restack base. Preserve those new parent auth changes (kid fail-closed, API audience validation, local Keycloak audience mapper, auth/config regressions) unchanged. All prior #260 constraints remain: Weekly VOC-only delta, ADR 0090/0091, v2.13.0, full exact-head validation, no merge, no edits outside #260.

[seonghobae]

@opencode-agent #258 is now stable at f805afc after the OIDC audience Compose pass-through was minimized to the intended two-line config delta. Restack #260 onto this exact head. If #258 moves again before you write, refetch the live #258 head first and use that exact SHA rather than any earlier comment. Preserve all prior constraints: Weekly VOC-only delta, ADR 0090/0091, v2.13.0, parent fixes win on overlap, exact-head full verification, no merge.

[seonghobae]

@opencode-agent Final parent pin for this restack: use #258 exact head d101b18 as the only base. Earlier parent-SHA comments are stale. Preserve the current #258 OIDC/JWKS hardening unchanged, including explicit external resource audience, strict RS256/RSA signing-key metadata, and one-time JWKS refresh on rotated kid. Reapply only #260's Weekly VOC semantic delta, renumber its ADR 0070/0071 to 0090/0091 with every in-repo reference updated, keep v2.13.0, and do not carry the obsolete parent snapshot. Run focused Weekly VOC tests plus full frontend tests, lint, Storybook build, production build, and repository Python tests on the new exact head. Do not merge and do not edit #258 or #261-#265.