Repository navigation
OP-PRIVACY: record the owner's clarification that name and Gmail are not restricted (umbrella of #184/#185/#186) - #172
d6g8k5htny-coder wants to merge 11 commits into
Conversation
…by hash tools/dropbox_reconcile.py (standard library only) finds Dropbox files that are not already preserved in the account's Git repositories or in Google Drive, without a model reading file contents: - index-git: every blob reachable from any ref, with sha256 and the Dropbox content_hash (sha256 over 4 MiB block digests). - index-drive: Drive identities from the Drive source-map export; for files up to one block, content_hash = sha256(sha256), so Drive SHA-256 values give exact Dropbox matches with no download. - xlsx-csv: stdlib export of the source-map workbook tabs. - classify: GIT_EXACT / DRIVE_EXACT / name+size / in-Dropbox duplicate / skip (app bundles, caches, run debris, installers) / MISSING. - fetch, extract, stage: download single-use URLs, extract text per type (text, json, url, rtf, docx/pptx/xlsx, ipynb, pdf via pdftotext, zip members), flag credential- and PII-shaped strings, and stage text copies within the intake-lane limits plus a Drive upload list. tests/test_dropbox_reconcile.py checks the content_hash against a value reported by the Dropbox API, a one-byte negative control, the tier order and the extractors. Scientific effect NONE; no inventory data is committed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
Adds harvest-links (collects download_link results, keeping only links newer than --since as fetchable and every content_hash for classify) and batches (25-id groups, the download_link maximum). This removes any need to re-type single-use URLs. Test added. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
stage now marks loose files whose bytes travel inside an uploaded zip (covered_by_zip) and never stages personal-looking file names (resume, tax forms, bank statements, ...) for GitHub. pack deflates the Drive upload list into size-capped zips that keep Dropbox paths and lists every held file with its reason. report writes a private Markdown summary of a classification. Tests cover each guard; removing any of them fails a test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
…-list The PR body states that an allow-list is required, but stage treated a missing --allow as 'allow everything not PII-flagged'. Fail closed: with no allow-list, no text copy is written to the GitHub packet directory; the Drive upload list is still produced. Two tests cover both branches; the first fails against the previous behaviour. Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
Review at
|
Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
harvest-fetch collects the connector's extracted text for each file from session transcripts. A text is restored as the exact original only when its bytes reproduce the file's Dropbox content_hash; the candidates cover the connector's extra trailing newline, CRLF endings and legacy single-byte encodings. Anything else (PDF or docx text, lossy decodes) stays text-only: stage may copy it to GitHub but never lists it as an original for Drive. Tests include the known 185-byte value and a one-word edit that must not recover. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
stage now requires an explicit --allow for GitHub copies (Cursor Agent's fix) also on the text-only path added for connector harvesting; the harvest test names its allow-list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
A zip member with a bad CRC, a truncated archive or a malformed docx or ipynb now yields extractor 'error:<Exception>' for that file or member, and extract continues with the rest (cursor[bot] review of #172). The new test fails against the previous code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
OP-PRIVACY-20260927 quotes the owner's instruction of 2026-09-27 and gives its operational meaning for every model. Personal information and material unrelated to the project never go where others can see them, and are purged when found; project material is published by repository role. AGENTS.md now points to it next to the autonomy instruction. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
audits/dropbox_import/2026-09-27 holds the project-related files found in Dropbox with no copy in any account repository or in the Drive source map. 93 are byte-identical originals (each reproduces its Dropbox content_hash); 14 are extracted text of PDF or Word files. MANIFEST.csv gives hashes, a one-line summary and a suggested home for each; NOT_IMPORTED.csv lists 26 project archives, figures and large logs that could not be imported. Under OP-PRIVACY-20260927, personal material and the owner's unrelated research are not published or named; only counts appear. Scientific effect NONE. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq
|
@cursor BOUNDED REPAIR / engineering AMEND at
Please add regression tests for top-level list, artifacts-object, rows-object, malformed JSON shape and failing Git subprocesses; require nonzero on retrieval/index failure and do not publish a valid-looking empty/partial success. Preserve the explicit --allow public-staging safeguard. Report exact amended head and both Python-mode results, then request fresh review. Do not self-merge or claim the entire Dropbox/Drive inventory is captured from a zero-row failed scan. No full mathematical or privacy-policy acceptance is implied by this bounded review. |
|
Both modes passed: |
A catalog list raised AttributeError, a rows object was discarded and written as [], and a failed git read exited 0 with an empty index. index-drive and index-git now require a complete read before writing --out. GitHub staging still requires an explicit --allow list. Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
|
Engineering amend at The three probes now behave as follows:
Regression tests cover the top-level list, an artifacts object, a rows object, the public Ran at
Requesting a fresh engineering review. This amend does not claim mathematical acceptance or privacy-policy acceptance. |
|
Integration scope check at668711f78c3b46271ffd85f8d2197724e0000613: the indexing repair response is received, but the current PR diff is now114 files, including107-source Dropbox intake material and a new governance/AGENTS directive. That is much broader than the earlier four-file tooling review and the requested bounded index repair. I have NOT cleared this expanded packet for merge. Please keep this PR as draft and separate the tested tool/index repairs into a small successor PR based on current main, with an explicit link back here. Do not duplicate source publication, drop/purge history, overwrite source files, or move private content. The archive/intake additions need their own existing/publication review and source-custody route, and the governance directive needs its own appropriate scope review. Preserve all commits and discussions. Post the exact narrow successor head plus hosted tests; do not treat review of the index functions as approval of114 files. This is scope isolation, not rejection of the recovered research material or a new scientific verdict. |
Scope split executed; this PR stays draftPer the 22:39 request, the tested tool/index repairs now have a narrow successor: #184 ( Nothing here is dropped, rewritten or purged; all eleven commits and the discussion remain on this branch. The intake material ( Privacy and relevance screen of the intake at 668711f (recorded for the intake successor)Method:
|
…tive-ac93 Record OP-PRIVACY-20260927, the owner's standing privacy and relevance rule (successor to #172)
…e-tool-ac93 Dropbox reconciliation tool and tests (narrow successor to #172)
…0260927-ac93 Dropbox import 2026-09-27: 107 project files that existed only in Dropbox (successor to #172)
Superseded: all content of head
|
| Successor | Content | Merge commit |
|---|---|---|
| #185 | governance/OP-PRIVACY-20260927.md (byte-identical), AGENTS.md standing-rule pointer, one docs/WORKSPACE.md link |
cdf8722bd011f8c4c9beeb6616656a1a4882f90f |
| #184 | tools/dropbox_reconcile.py, tests/test_dropbox_reconcile.py (byte-identical) |
648b02439137a077029e9faa6504bb70896fbac6 |
| #186 | audits/dropbox_import/2026-09-27/** (110 files, byte-identical), one docs/RESEARCH_INDEX.md paragraph |
aa422b187e33b34285bfc7464a5e208a085e0c46 |
Each landed serially on an up-to-date main with hosted verify, public-intake, public-shop (and navigation where triggered) green on the exact merged head. Custody and privacy screens are recorded in the #186 body: 107/107 archive SHA-256 and 93/93 Dropbox content_hash matches; no personal information found.
This PR is closed as superseded, not rejected. The branch claude/review-grok-github-uploads-gsthj3, its eleven commits and this discussion are preserved unchanged; nothing was purged, rewritten or force-pushed. No scientific status moved. Same-account review throughout: zero organizational-independence credit.


What this changes
This branch started as the Dropbox reconciliation work. That work is now split into successors:
audits/dropbox_import/2026-09-27/. Open.Current
mainis merged into this branch, so the diff againstmainholds two things:966106f). New since the split.governance/OP-PRIVACY-20260927.md.AGENTS.mdadds one sentence saying the same.docs/RESEARCH_INDEX.md. It drops out of this diff once Dropbox import 2026-09-27: 107 project files that existed only in Dropbox (successor to #172) #186 merges andmainis merged here again.Why this matters: the rule as merged in #185 still told models to purge the owner's fuller name and Gmail. A redaction pass over the hardening branch and a patch for
Math-had been prepared. Both were stopped and discarded before any push when the owner clarified.Type of change
Verification
python3 -B -m unittest discover -s tests -p 'test_*.py': OK.python3 -B -O -S -m unittest discover -s tests -p 'test_*.py': OK.workspace_landing_check.pyandnavigation_check.py:"problems": [].What this does NOT establish
Status discipline
NON-CERTIFYINGIndependence
Governance record of an owner instruction; same account; zero organizational-independence credit; scientific effect NONE.
🤖 Generated with Claude Code
https://claude.ai/code/session_01B6fUVkWEba9KPrZjfHujFq