[patrickschiller]

Summary

Prepare Chrome, the local Codex plugin, and the hosted ChatGPT MCP service as version 1.1.0 alongside the released iOS app. Add the portal-ready ChatGPT plugin ZIP and reproducible release validation, and accept iOS capture_date/captured_at metadata when the older date field is absent.

Update English/German README and publication instructions, add the publishing checklists, and document the next iPhone/iPad onboarding implementation plan. The onboarding document is a plan, not an implemented authentication change. Built dist artifacts remain outside Git.

Related issue

Maintainer-requested release preparation; no separate issue.

Validation

• Capture suite: 23 tests passed.
• Python core and packaging suites: 66 tests passed.
• ChatGPT MCP suite: 34 tests passed, including OAuth/PKCE/refresh/revocation integration coverage.
• Cloudflare Worker dry-run build passed.
• iOS release validator passed for 1.1.0/build 11; product iOS sources are unchanged.
• Reproducible 1.1.0 release build passed with clean committed source inputs; 26 bundle files verified and all 25 checksum entries passed.
• Explicit file allowlist, public-content scan, and git diff whitespace checks passed.

Privacy, security, and compatibility

Browser permissions, GitHub scopes, credential handling, deletion behavior, and archive writes are unchanged. Remote archive reads now recognize existing iOS capture-date fields without a format migration. The new portable ChatGPT manifest uses OAuth/DCR with archive:read and the intended existing https://mcp.sourcebraid.com/mcp endpoint; it contains no credentials. Local configuration, private archives, website sources, and dist files are excluded.

Hosted MCP deployment and live endpoint/TLS validation remain required before submission. No store publication or service deployment is performed by this PR. The iOS onboarding plan proposes future authentication changes with their own implementation and acceptance work.

Checklist

• The change is focused and does not include private archive content, secrets, personal data, or unrelated files.
• I used synthetic or redistributable fixtures and screenshots.
• I added or updated tests for behavioral changes.
• Relevant tests pass, or I documented why a check could not run.
• User-facing English and German documentation stay consistent.
• Every commit includes a DCO Signed-off-by trailer (git commit -s).
• My contribution is licensed under the project's MIT License.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-15T21:49:51.625653Z	2bb4a13	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2bb4a1324b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add the required DCO sign-off trailer

This release checklist calls for DCO sign-off, but commit c92e22859df97b1e98cf180c462f10a98beb605e has no Signed-off-by: trailer. When submitted in a pull request, .github/workflows/dco.yml checks every commit and will reject this one, so the commit must be recreated or rebased with the required sign-off before it can merge.

AGENTS.md reference: AGENTS.md:L100-L101

Useful? React with 👍 / 👎.