docs(pii): land the #154 post-approval polish that missed the squash

[YellowSnnowmann]

Summary

#154's squash was cut at ef1eb19; the post-approval commit bfd2ea2 — addressing @oxoxDev's approval notes — was pushed but never made it into the merge. This re-lands it on main, byte-identical (verified: zero content diff vs bfd2ea2).

Two changes:

• CJK-tier doc corrected to the case the substring tier actually covers (keyword embedded mid-sentence, …信用卡账单 <PAN>) — and why digit-attached 卡号<PAN> was never a candidate at all (CC_RE's leading \b fails on CJK-\w).
• Bare elo and maestro dropped from the standalone keyword list — both networks are covered structurally by the IIN table, and as English words they were the loosest entries.

Docs + one regex literal; no behavior change beyond the two keywords narrowing. Safety suite 82 passed, fmt clean.

Follow-up once this merges: an openhuman vendor/tinycortex re-pin from the now-orphaned bfd2ea2 (a PR-head SHA openhuman main currently points at, reachable only via refs/pull/154/head) to the resulting main SHA — restoring the fresh-clone reachability guarantee and closing the content drift between openhuman's pin and tinycortex main.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Improved credit-card number detection to reduce false-positive redactions caused by standalone “maestro” or “elo” keywords.
  • Existing multilingual and boundary-based matching behavior remains unchanged.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 84c95dc9-326b-4b9d-843b-571592101569

📥 Commits

Reviewing files that changed from the base of the PR and between 0a5eac2 and 5c2d0c7.

📒 Files selected for processing (1)

• src/memory/store/safety/pii.rs

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

📝 Walkthrough

Walkthrough

The credit-card keyword matcher no longer treats maestro or elo as standalone corroborating keywords for bare card-number redaction. Other multilingual substring and boundary matching remains unchanged.

Changes

PII matching

Layer / File(s)	Summary
Credit-card keyword filter src/memory/store/safety/pii.rs	The documentation and standalone keyword alternatives no longer include maestro or elo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk:⚪ Minimal · up to 5c2d0

This change narrows standalone keyword matching while retaining structural detection for Maestro and Elo card numbers; it introduces no actionable merge-blocking risk and is merge-ready after normal checks.

Suggested reviewers:senamakel

Poem

A rabbit checks the card-number trail,
Removes two keywords from the matching rail.
maestro and elo now step aside,
While boundary rules continue to guide.
Hop, hop—the matcher stays precise!

🚥 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 accurately identifies a documentation-focused follow-up related to PR #154, but it does not specify the keyword-list change.
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.

---

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.}

[tinysweeper]

tinysweeper found nothing blocking. Approving.

$0.0000 · 0 in / 0 out · 166 embedded · openrouter/openai/text-embedding-3-small

[tinysweeper]

How this change flows

0 changed behaviours across 7 relationships. 6 surrounding behaviours are shown (60 graph nodes walked). 17 further behaviours left out to keep the diagram readable.

flowchart LR
n0["collect_redactions_inner"]:::impacted
n1["Hit"]:::impacted
n2["push"]:::impacted
n3["push_credit_cards"]:::impacted
n4["redact_pii"]:::impacted
n5["collect_redactions"]:::impacted
n0 -->|uses| n1
n0 -->|calls| n3
n3 -->|uses| n1
n3 -->|calls| n2
n4 -->|calls| n5
n5 -->|calls| n0
n5 -->|uses| n1
classDef changed fill:#0d4429,stroke:#238636,color:#e6edf3
classDef impacted fill:#161b22,stroke:#6e7681,color:#c9d1d9
classDef flagged fill:#5a1e02,stroke:#d93f0b,color:#ffffff
classDef blocking fill:#67060c,stroke:#f85149,color:#ffffff

Loading

_{Green: changed behaviour. Grey: surrounding behaviour. Arrows name the call, use, implementation, or test relationship. Orange: has findings. Red: has a finding that blocks the merge.}