Skip to content

docs: remove live captures from quota verification notes - #3953

Closed
luvs01 wants to merge 2 commits into
lidge-jun:devfrom
luvs01:agent/quota-verification-privacy-20260908
Closed

docs: remove live captures from quota verification notes#3953
luvs01 wants to merge 2 commits into
lidge-jun:devfrom
luvs01:agent/quota-verification-privacy-20260908

Conversation

@luvs01

@luvs01 luvs01 commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Summary

The historical provider-quota verification notes retain live Accounts and Usage captures and operator-specific execution details. Remove all four captures from this verification unit and retire its outdated planned-filename list. Apply one retention rule to both surfaces: screenshots from a real operator profile are unnecessary once the behavioral evidence is recorded in text. The cleanup does not claim that the Usage captures were independently cleared of personal information.

Describe the isolated verification without the local home path, exact process/port values or account-pool details, and remove the working-service address and process identity from the opening plan. Preserve the verified outcomes: the existing proxy was left untouched, Accounts and Usage refresh performed real reads, and the scratch home was moved to Trash. This is a seven-file documentation cleanup; the removal applies to the current tree, not Git history.

Verification

  • Based on dev 514350e6f79ed4539378388bc39d3fc79ff2c70c; head ca21efd29730086ede902c4701124893ce58b404.
  • The branch changes exactly three Markdown files and removes four PNGs. git diff --cached --check passed before commit. All four assets are absent, and the repository index contains no literal Markdown references to their filenames or the two stale planned names.
  • Text readback confirms the original wire JSON, UI before/after results, real refresh observations and historical CI results are unchanged. The isolated-instance outcome and move-to-Trash record remain, while the edited plan and isolation record omit the working-service address, exact process values, local home path and account-pool details.
  • The base-identical privacy-scan.ts passed against the sparse checkout containing the changed Markdown and root guidance. This is scoped validation, not a claim of a new full-repository scan. The captures were not opened or displayed during the cleanup.
  • Independent read-only review of the final seven-file scope found no historical outcome changes or dangling asset references. The final wording also preserves the distinction between a planned command and an observed execution.
  • Addresses the review about capture names, Usage retention and the opening plan. Usage captures are removed under the same rule instead of asserting that they are safe to retain.
  • CodeRabbit's follow-up review explicitly reviewed ca21efd29730086ede902c4701124893ce58b404 and found no actionable findings.
  • No runtime, configuration, package, generated-site or test input changes. The current-head Cross-platform CI and React Doctor require maintainer approval (action_required); neither executed its scope check. Metadata hygiene passed. Keep the PR in draft until the required checks complete.

Checklist

  • Scope stays focused and avoids unrelated cleanup.
  • Docs or release notes were updated when needed.
  • Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Review readiness checklist

  • All CI tests are green on my local testing.
  • I pushed my PR to the latest dev commit.
  • I resolved all correct Codex and CodeRabbit findings.
  • My PR is ready for review.

@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: a252dd72-8196-454a-845f-5753c8b16f9d

📥 Commits

Reviewing files that changed from the base of the PR and between 514350e and 05fd828.

⛔ Files ignored due to path filters (2)
  • devlog/_plan/260904_provider_quota_refresh/assets/030_accounts_refresh_button.png is excluded by !**/*.png
  • devlog/_plan/260904_provider_quota_refresh/assets/040_accounts_refresh_result.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • devlog/_plan/260904_provider_quota_refresh/030_wp3_live_verification_and_pr.md
  • devlog/_plan/260904_provider_quota_refresh/031_live_verification_record.md
💤 Files with no reviewable changes (1)
  • devlog/_plan/260904_provider_quota_refresh/030_wp3_live_verification_and_pr.md

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.


📝 Walkthrough

Walkthrough

The live-verification documentation removes account refresh screenshots, condenses isolation details, and generalizes the Accounts tab provider description.

Changes

Provider quota refresh verification

Layer / File(s) Summary
Live verification evidence updates
devlog/_plan/260904_provider_quota_refresh/030_wp3_live_verification_and_pr.md, devlog/_plan/260904_provider_quota_refresh/031_live_verification_record.md
Removed the 030_accounts_refresh_button.png asset entry. Condensed the Isolation section. Generalized the Accounts tab description to “pooled OAuth provider.”

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to 05fd8

This change removes live account screenshots and sensitive operational details from historical quota-refresh notes while retaining the documented verification outcomes. It does not alter product behavior or deployment configuration and is ready to merge after normal repository checks.

Suggested reviewers: lidge-jun

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: removing live capture assets from provider-quota verification documentation. It matches the changes in devlog/_plan/260904_provider_quota_refresh/030_wp3_l…
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Sep 7, 2026
@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Deterministic PR hygiene checks passed.

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

⏳ DRAFT

  • review readiness checklist open (2/4 boxes ticked).

What to do

  • Tick all four boxes in the PR description once you're done (currently 2/4).

Review readiness checklist

  • ⬜ All CI tests are green on my local testing.
  • ✅ I pushed my PR to the latest dev commit.
  • ✅ I resolved all correct Codex and CodeRabbit findings.
  • ⬜ My PR is ready for review.

2/4 boxes ticked.

This PR stays in draft until every box above is ticked.

@luvs01

luvs01 commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@lidge-jun

Copy link
Copy Markdown
Owner

리뷰 · 우선순위 52 / 80

지금 dev 끝은 514350e6f입니다. 방금 올라온 건 #3948 C 트랙 config/init 문서 마감이고, 런타임 팁은 그 아래 #3941(설정 임시파일 배타 쓰기 + init 게시 복구)입니다. 패키지는 2.48.0입니다. 이 PR(#3953)은 그 방향과 겹치지 않는, 이미 끝난 검증 기록의 개인정보/운영 흔적 청소입니다.

무엇을 하나요. devlog/_plan/260904_provider_quota_refresh/ 안에 남아 있던 실제 Accounts 화면 캡처 두 장(030_accounts_refresh_button.png, 040_accounts_refresh_result.png)과, 검증 기록에 적힌 로컬 홈 경로(/Users/jun/...), 포트·pid·계정 풀 세부 설명을 지우고, “격리 scratch에서 돌렸고 기존 프록시는 손대지 않았다 / Trash로 옮겼다”는 결과만 남깁니다. 런타임·설정·테스트 입력은 건드리지 않습니다. HEAD 514350e6f 기준이라 베이스도 맞습니다.

왜 중요한가. 저장소에 올라간 live UI 캡처와 운영자 홈 경로는 재현에 꼭 필요하지 않은데 개인·환경 정보가 남습니다. 문서-only라 위험은 낮고, 히스토리까지 지우지는 않는다고 본문에 분명히 적었습니다. 다만 같은 폴더의 000_plan.md에는 아직 port 10100 / pid 73184 같은 문장이 남아 있을 수 있습니다. 이번 diff 범위 밖이라면 의도인지 한 줄만 확인해 주세요.

경로/심볼 - 030_wp3_live_verification_and_pr.md 샷 표 - 030_accounts_refresh_button.png 행만 지우고 040_refresh_result.png 행은 남깁니다. 실제 지운 파일 이름은 040_accounts_refresh_result.png입니다. 표에 남은 040_refresh_result.png가 다른 예정 샷인지, 오타/옛 이름인지 구분이 안 됩니다.

경로/심볼 - 031_live_verification_record.md Assets 표 - Accounts 캡처 두 행을 지웠고, Usage 쪽 010/020은 남깁니다. Usage 캡처에도 계정·쿼터 숫자가 보일 수 있으니, “Accounts만 민감하고 Usage는 남겨도 된다”는 기준을 한 줄로 적어 두면 나중에 다시 안 싸웁니다.

경로/심볼 - Isolation 문단 - “영구 삭제”로 세게 쓰지 않고 “Trash로 옮김”을 유지한 점은 좋습니다. 사실 기록을 과장하지 않습니다.

경로/심볼 - CI - 본문대로 PR CI가 maintainer approval(action_required) 대기입니다. draft 체크리스트의 “ready for review”도 아직 비어 있습니다.

메인테이너의 판단이 필요한 지점

  • Usage 캡처(010/020)까지 같은 이유로 지울지, Accounts만으로 충분한지
  • 000_plan.md의 live proxy/port/pid 문장까지 같은 패스로 정리할지
  • 문서-only 프라이버시 청소를 draft CI 승인 전에 빨리 merge할지

너의 추천
의도는 맞고 범위도 작습니다. 040_refresh_result.png vs 040_accounts_refresh_result.png 이름만 정리하고, Usage 캡처를 남기는 이유를 한 줄 보강한 뒤 draft 체크리스트와 CI 승인만 채우면 merge해도 됩니다. 런타임 위험은 없습니다. 지금 당장 막아야 할 버그 큐(#3949 계열 affinity 등)보다는 아래입니다. types/config split과 무관하니 close-don't-rebase 대상은 아닙니다.

이 댓글은 grok-bot이 작성했습니다

@luvs01 luvs01 changed the title docs: remove live account captures from quota verification notes docs: remove live captures from quota verification notes Sep 7, 2026
@luvs01

luvs01 commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Addressed the capture-retention review in ca21efd29730086ede902c4701124893ce58b404.

Both Accounts and Usage captures are removed under one retention rule. The stale planned-filename table is retired, and the opening plan no longer identifies the working service by its exact address or process ID. The historical wire JSON, UI results, real refresh observations, CI record and move-to-Trash outcome are preserved. The final scope is three Markdown files and four deleted PNGs in the same verification unit.

The scoped privacy scan, diff checks, literal-reference check and independent read-only review passed. The new-head CI still requires maintainer approval; the PR remains a draft.

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '== Repository and HEAD =='
git remote -v | head -n 2
git status --short
git rev-parse HEAD
git show -s --format='%H%n%P%n%s' HEAD

echo '== Changed files against merge base =='
base="$(git merge-base HEAD origin/dev 2>/dev/null || git merge-base HEAD dev)"
printf 'base=%s\n' "$base"
git diff --name-status "$base"...HEAD
git diff --stat "$base"...HEAD

echo '== Diff =='
git diff --find-renames --find-copies --unified=80 "$base"...HEAD -- devlog/_plan/260904_provider_quota_refresh

echo '== Verification unit files =='
fd -t f . devlog/_plan/260904_provider_quota_refresh | sort

echo '== Remaining capture-name references =='
rg -n -i -C 2 '(030_accounts_refresh_button|040_accounts_refresh_result|040_refresh_result|010.*usage|020.*usage|accounts.*\.png|usage.*\.png)' devlog/_plan/260904_provider_quota_refresh || true

echo '== Remaining potentially sensitive operational literals =='
rg -n -i -C 2 '(/Users/|OPENCODEX_HOME|localhost|127\.0\.0\.1|0\.0\.0\.0|port|pid|launchd|proxy|accounts?.{0,40}(pool|oauth|anthropic)|[0-9]{4,5})' devlog/_plan/260904_provider_quota_refresh || true

echo '== Affected Markdown with line numbers =='
for f in \
  devlog/_plan/260904_provider_quota_refresh/000_plan.md \
  devlog/_plan/260904_provider_quota_refresh/030_wp3_live_verification_and_pr.md \
  devlog/_plan/260904_provider_quota_refresh/031_live_verification_record.md
do
  if [ -f "$f" ]; then
    echo "----- $f -----"
    cat -n "$f"
  fi
done

Length of output: 2206


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '== Available references =='
git branch -a
git show-ref --heads --remotes || true

echo '== Pull request metadata =='
gh pr view 3953 --repo lidge-jun/opencodex \
  --json number,state,isDraft,baseRefName,baseRefOid,headRefName,headRefOid,commits,files,statusCheckRollup \
  --jq '{number,state,isDraft,baseRefName,baseRefOid,headRefName,headRefOid,commits:[.commits[]|{oid,messageHeadline}],files:[.files[]|{path,additions,deletions}],checks:[.statusCheckRollup[]|{name,conclusion,status}]}'

base="$(gh pr view 3953 --repo lidge-jun/opencodex --json baseRefOid --jq .baseRefOid)"
echo "== Base object availability: $base =="
git cat-file -t "$base" || true

if git cat-file -e "$base^{commit}" 2>/dev/null; then
  range="$base...HEAD"
else
  range="HEAD^...HEAD"
  echo 'Base object is unavailable locally; inspecting the verified follow-up commit delta.'
fi

echo "== Changed files: $range =="
git diff --name-status "$range"
git diff --stat "$range"
echo "== Documentation diff: $range =="
git diff --find-renames --find-copies --unified=60 "$range" -- devlog/_plan/260904_provider_quota_refresh

echo '== Files in verification unit =='
fd -t f . devlog/_plan/260904_provider_quota_refresh | sort

echo '== Remaining deleted-capture references =='
rg -n -i -C 2 '(030_accounts_refresh_button|040_accounts_refresh_result|040_refresh_result|010.*usage|020.*usage|accounts.*\.png|usage.*\.png)' devlog/_plan/260904_provider_quota_refresh || true

echo '== Remaining operational-detail literals =='
rg -n -i -C 2 '(/Users/|OPENCODEX_HOME|localhost|127\.0\.0\.1|0\.0\.0\.0|[[:<:]]port[[:>:]]|[[:<:]]pid[[:>:]]|launchd|[[:<:]]proxy[[:>:]]|accounts?.{0,40}(pool|oauth|anthropic)|[0-9]{4,5})' devlog/_plan/260904_provider_quota_refresh || true

echo '== Affected Markdown with line numbers =='
for f in \
  devlog/_plan/260904_provider_quota_refresh/000_plan.md \
  devlog/_plan/260904_provider_quota_refresh/030_wp3_live_verification_and_pr.md \
  devlog/_plan/260904_provider_quota_refresh/031_live_verification_record.md
do
  [ -f "$f" ] || continue
  echo "----- $f -----"
  cat -n "$f"
done

Length of output: 45459


@luvs01 Reviewed commit ca21efd29730086ede902c4701124893ce58b404.

I found no actionable findings.

The diff consistently removes all four live-profile captures. It removes their stale filename inventory. It removes the exact local address, port, process ID, and home path. The retained records preserve the verification results without claiming that removed Usage captures were safe to retain.

The remaining gate is external to this documentation change. PR #3953 is still a draft, and the current check set includes approval-dependent or queued checks.

You are interacting with an AI system.

@lidge-jun

Copy link
Copy Markdown
Owner

Carried into dev via #3955 (9c54000) and #3959 (01c23ae), including your updated capture-retention scope. Original authorship is retained with Co-authored-by in both landed commits. We additionally aligned American-English wording and explicitly made the completed scratch-isolation record supersede the original working-service restart plan. Current-head hosted scope CI succeeded for both carries (3 jobs each; 10 product jobs skipped, not counted as passes), independent privacy reviews passed, and landed trees/parents/dev ancestry were verified. Historical blob removal was explicitly out of scope; Git history remains unchanged. Closing this source PR as carried, not directly merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants