docs(license): asset-license boundary — MIT for code/docs/tokens, marks carved out prospectively (P-3) - #14
Conversation
|
Warning Review limit reached
Next review available in: 59 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 40ce7b1cc5
ℹ️ 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".
…ty strings, report-chip fix (#18) * docs: add public project docs — security policy, contributing, code of conduct, support, changelog, owners, trademark notice, templates SECURITY.md routes vulnerabilities to GitHub private vulnerability reporting (the repo toggle for it is requested separately). TRADEMARKS.md is prospective-only with the honesty clause (rights reserved only to the extent actually controlled; provenance findings tracked separately) and does not restate the ASSET-LICENSE boundary proposed in PR #14. CHANGELOG entries are summarized from the git history. * feat(brand): canonical product identity strings — tagline and store description Tagline "A focused browser cleanup for Zoom error 1132." replaces "One-click fix for Zoom Error 1132" in the brand conventions, README, popup header descriptor, and the ds-bundle component copies. Store description "Clear Zoom site data in Chrome with one guided action." replaces the old summary in manifest.json (54/132 chars), _config.yml, index.md, STORE_LISTING.md, and STORE_PREP.md. As touched in the store docs: the store-name row now matches the listing copy ("1132 Fixer for Chrome"), the privacy-policy URL row is re-verified against the post-transfer GitHub Pages address (the pre-transfer URL is dead — Pages does not redirect across owners), and stale version references now match the repository's v1.2.5. At 360px the new popup descriptor renders as two centered lines (measured 279px + 82px); flagged for design review in the PR. * fix(report): fallback version chip v1.2.4 -> v1.2.5 report.html ships a hardcoded fallback label that bump-version.js does not rewrite (it only updates popup.html), so it drifted one release behind. Runtime still overwrites the chip from the manifest; only the pre-script fallback was stale. The systematic fix (a multi-surface version-consistency gate) is designed in the release-automation batch. * docs(templates): absolute doc links in issue forms (relative paths resolve wrong from issue pages) * docs(trademarks): working-draft marker pending legal confirmation; provenance-review status updated (review concluded 2026-08-09, per-asset dispositions pending) * docs(oss): cure EQ returns — exact working-draft marker; certification-honest store source block TRADEMARKS.md (R1): the variant draft banner is replaced by the exact working-draft marker "> Working draft — pending operator legal confirmation." as the top line of the file; the boundaries-in-effect sentence is retained so draft status cannot be read as the boundaries being suspended. STORE_LISTING.md (R2, Control-ruled): the detailed-description header "OPEN SOURCE" becomes "SOURCE CODE" and the body states the facts without an open-source label claim ("Source code is public under the MIT license.") — the label is gated on OSS certification. As touched in the same block, the two old-owner PrimeUpYourLife repository links now point at the current 1132-Fixer paths. Evidence at this tree: validate-extension 140/0 · store-listing verifier 8/8 within limits · popup e2e 91/0 · report e2e 32/0.
…ks carved out prospectively (P-3) ASSET-LICENSE.md: exact protected-file list, prospective-only carve-out with an explicit no-retraction sentence, rights reserved only to the extent controlled, per-file provenance table (all refresh marks + legacy rasters: provenance under review, CR-10); README License section links the boundary; the packager ships the notice in the store zip so the boundary travels with the icons. MIT text unmodified. Future public design-system packages carry the same boundary. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…package inventory Addresses the two unresolved review threads on #14, rebased onto main e09d566 so the #23 README/NOTICE work is preserved intact. P1 — public license declarations now carry the carve-out: - _layouts/default.html: hosted-site footer no longer says a bare "MIT License"; it scopes MIT to code/docs and links TRADEMARKS.md. - index.md: License line scopes MIT and links TRADEMARKS/ASSET-LICENSE/NOTICE. - STORE_LISTING.md: the SOURCE CODE block of the store copy states the boundary and links both notices. - STORE_PREP.md: long-description quick reference matches; Windows link corrected to the canonical 1132-Fixer/windows. - NOTICE.md / TRADEMARKS.md: cross-link ASSET-LICENSE.md as the per-file annex. - ASSET-LICENSE.md: declares itself the annex to TRADEMARKS.md (which governs mark wording) and lists report.* under the MIT-covered source. P2 — documented package inventory matches the packager: - scripts/package-extension.js ENTRIES ships NOTICE.md and TRADEMARKS.md alongside ASSET-LICENSE.md, so the carve-out travels with the package and the shipped README's links resolve. - STORE_PREP.md inventory rewritten: 19 entries in ENTRIES order, the report.* runtime added, and per-target byte counts and SHA-256 recorded from npm run package:all. Firefox is called out as a separate Gecko package, not one universal build. Version stays 1.2.7: version-bump.yml fires only on pushes to master that touch manifest.json, popup.*, or icons/ — none apply here. npm test green locally: validator 227/0, popup e2e 126/0, package smoke 55/0, report e2e 32/0, listing:verify 8/8. No store upload, no release, no tag.
40ce7b1 to
f3f5902
Compare
2 participants
Program BN-1132-FAMILY-FINALIZE (Botify-Network/Botify-Network#24209), operator-approved P-3 with the three legal guardrails: (a) prospective-only with an explicit no-retraction sentence; (b) zero historical-exposure analysis in license text (that analysis is a separate register finding); (c) rights reserved only to the extent actually controlled — every unproven asset says 'provenance under review — status will be corrected when established', consistent with the byte-level MARK-ASSET-CLASSIFICATION (all raster marks UNKNOWN). MIT text unmodified; boundary visible from README; notice ships in the store zip. Rollback: revert.