Add jnak/notion-light-theme

[jnak]

Claude on behalf of Julien.

Adds Notion Light, a light theme built from the color tokens of Notion's light theme (read from the Notion desktop app).

• Source: https://github.com/jnak/paseo-notion-light-theme
• Pin: v0.1.1 at 36ddc33, plugin at the repository root
• Category: themes
• The release ships OVERVIEW.md, an icon and a screenshot, declared in paseo-plugin.json (requirements.paseo >=0.11.0)
• Theme data only: index.client.ts calls addTheme once. No server entry, settings, network or file access.

Record generated with scripts/add.ts; npm run validate passes. I filed #323 through the API first, so it missed the submission label and intake skipped it. This PR replaces it.

🤖 Generated with Claude Code

[paseo-bot]

Notion Light’s artifact review is approved, @jnak. The pinned theme, overview and interface image are ready. Publication is still waiting for GitHub to allow the validation workflow to run; the PR remains unmerged. No registry edits or author action are needed.

Review data

• Reviewed PR head: 2757767e3bfe1428b049e73f40525926f03d6fa1. Current main REVIEW.md blob: 43e9fd13148488473d606daf097c8b27e78ff25a. Read all PR discussion and linked submission #323; repository owner and submitter agree.
• Artifact: Git https://github.com/jnak/paseo-notion-light-theme.git, root plugin at 07baf75334547566fcfb4eda80c3e9129afd7226; v0.1.0 still identifies that exact commit. Fetched the exact tree without hooks or submodules. All 13 archive entries were checked before confined extraction: regular files/directories only, no path escapes or links. Downloaded archive SHA-256: 1d04f2ed1281a0af0e6443f5e74efece8d631e2a02745ee469118044740582db.
• Inspected the complete client entrypoint, manifest, package metadata, lockfile, README, author OVERVIEW.md, icon and screenshot. Required entrypoint and declared assets are present; package/manifest identity matches the intended theme. Manifest requires Paseo >=0.11.0.
• index.client.ts:4–24 registers one light theme with fixed color strings and returns its removal callback. Its SDK import is type-only. No server component, credentials, environment reads, filesystem access, network requests, subprocesses, dynamic code or runtime installation appears in the complete production source.
• No runtime dependencies, manifest installation/build commands, or package lifecycle scripts. The only package script is development typechecking; all 19 lockfile package entries are development dependencies with public npm sources and integrity. None needs installation for this theme. Development dependency internals were not audited or executed.
• Listing: the artifact's overview supplies the page and accurately explains appearance selection, minimum version and unofficial attribution. Viewed the interface image; sample workspace content is suitable. Resolved pinned icon/screenshot URLs return image/png and bytes identical to the reviewed artifact. No redundant registry overview or metadata override is needed.
• Trusted validator matches current main and passes: 234 well-formed records, one changed record matches its pinned artifact. The local registry test suite passes (127 tests). GitHub’s Validate run is paused with action_required, awaiting first-contributor workflow approval; no PR check has run. Attempting to approve the workflow returned HTTP 403. Branch-protection status could not be read by the integration. Merge was not attempted while validation is pending. No plugin/dependency code installed, built, imported or run; static review does not certify live rendering on every supported client.

[paseo-bot]

Notion Light 0.1.1 remains approved, @jnak. I rechecked the pinned theme, overview and interface image, and retried the required validation workflow. Publication still awaits GitHub allowing that validation to run, so the PR remains unmerged. No registry edits or author changes are needed.

Review data

• Reviewed PR head: d0bf8ffa04183c9c6271ad870b61799fbe4700cf. Main REVIEW.md blob: 43e9fd13148488473d606daf097c8b27e78ff25a. Read PR body, all comments/reviews and submission #323. Submitter and repository ownership agree. The prior approval covered 0.1.0; this review covers the new pin.

• Git artifact: https://github.com/jnak/paseo-notion-light-theme.git, root plugin at 36ddc33a3280d573d387855b596dddfb3211491d. Commit exists and tag v0.1.1 still identifies it. Downloaded exact tree without hooks or submodules; archive SHA-256 93a51950bdec1defbf6311f58b3d8f18c313199686a4ca8b920046240a56dd15. Checked all 13 entries before confined extraction, only regular files/directories and no path escapes or links.

• Inspected complete production source (index.client.ts), manifest, package, development lockfile, author overview, README and listing assets. Manifest/package identity, required entrypoint and assets match the intended theme; minimum Paseo version is 0.11.0.

• index.client.ts:4–24 registers fixed light-theme colors with addTheme and returns the removal callback. SDK import is type-only. Complete production source contains no server component, credential/environment reads, filesystem access, network requests, subprocesses, dynamic code or runtime software installation.

• No runtime dependencies, preparation/build commands or lifecycle scripts. Package script is development typechecking only. All 17 dependency entries in lock v3 are development-only, with public npm resolutions and SHA-512 integrity; none is installed to use this theme. Development dependency internals were not audited. No plugin or dependency code installed, built, imported or executed.

• Author OVERVIEW.md supplies the displayed listing page, explaining appearance selection, limitations and unofficial attribution. Viewed the static interface image with sample content; pinned screenshot and icon URLs return image/png and bytes identical to the artifact. Static review does not verify live rendering on every supported client.

• Registry edits: none needed, no submission file remains and no redundant registry overview added. Trusted current-main validator run from this checkout passes: 234 well-formed records, one changed artifact matched. Registry suite passes all 127 tests.

• Validate run for this exact PR head has action_required, with no checks run. Attempt to approve the workflow returned HTTP 403. Required remote validation is incomplete; no merge attempted.

• Rechecked 2026-10-11T20:04:49.594479+00:00: PR head and main REVIEW.md blob remain unchanged. Freshly downloaded the exact Git tree, confirmed v0.1.1 still identifies the pin, checked all archive paths/types before confined extraction, and reread the complete production source and listing content. Both pinned PNG URLs return image/png and byte-identical reviewed assets. Trusted current-main validation passes again (234 well-formed records, one changed artifact matched). Retrying approval of the required Validate workflow returned HTTP 403; it still has action_required and no check jobs. Prior approval is retained, no new approval or merge performed. No plugin/dependency code executed.

• Execution 7649b4ce-54a4-544a-8323-3c9d2566aabb recheck at 2026-10-11T20:33:29.679339+00:00: head and main policy remain unchanged. Fresh exact-tree retrieval and tag verification passed; all 13 archive entries were checked before confined extraction. Complete production source and displayed overview were reread; the interface image was viewed, and pinned icon/media return image/png with identical artifact bytes. Trusted current-main online validation passes (234 records, one changed pin). Retrying authorization of the linked Validate run returned HTTP 403; it still has action_required with no checks run. The existing approval is retained; no new approval or merge, no registry edits or author changes required. No plugin/dependency code executed.

[paseo-bot]

Notion Light remains approved, @jnak. I rechecked the pinned theme and listing, updated the branch from current main, and retried authorization of the required validation workflow. GitHub still refuses that authorization, so the plugin remains unpublished and the PR is unmerged. No author changes or registry edits are needed.

Review data

• Reviewed head: 8ede21771a8035eef6672df534c014f2bd73227a. Main REVIEW.md blob: 43e9fd13148488473d606daf097c8b27e78ff25a. Read all PR discussion and submission Notion Light #323; no new author requirement.
• Exact Git artifact: jnak/paseo-notion-light-theme at 36ddc33a3280d573d387855b596dddfb3211491d; tag v0.1.1 still identifies it. Fresh archive SHA-256: 93a51950bdec1defbf6311f58b3d8f18c313199686a4ca8b920046240a56dd15. All 13 archive paths/types checked before confined extraction.
• Reread complete production source, manifest, package metadata and displayed author overview. The sole entry registers fixed theme colors and returns cleanup. No runtime dependencies, preparation commands, lifecycle scripts, network, credential/file access, subprocesses or runtime installation. Development tools are not required to use the theme. Prior image inspection remains applicable to this identical artifact; trusted online validation verifies the selected assets and exact pin.
• Trusted current-main online validation passes: 234 records, one changed artifact matched. No plugin or dependency code executed. Live rendering was not exercised.
• Retrying authorization of the required Validate run returned HTTP 403. Remote checks have not run. Existing artifact approval retained; the branch update changed no plugin record or artifact. Trusted validation passed again at this head; no new approval or merge performed.

[paseo-bot]

Notion Light 0.1.1 is approved, @jnak. The pinned theme, your overview and interface image are ready; no registry edits or author changes are needed.

Review data

• Reviewed registry head: 8ede21771a8035eef6672df534c014f2bd73227a. Main REVIEW.md blob: 43e9fd13148488473d606daf097c8b27e78ff25a. Read all PR discussion, reviews and submission #323; attribution matches the repository owner.
• Exact Git artifact: https://github.com/jnak/paseo-notion-light-theme.git at 36ddc33a3280d573d387855b596dddfb3211491d; v0.1.1 still identifies that commit. Fresh archive SHA-256: 93a51950bdec1defbf6311f58b3d8f18c313199686a4ca8b920046240a56dd15. Checked all 13 archive paths and types before confined extraction, regular files/directories only.
• Read complete production source, manifest, package, development lockfile and displayed author overview. index.client.ts:4–24 registers fixed light-theme colors and returns cleanup. No runtime dependencies, preparation commands, lifecycle scripts, network requests, credential/environment/file access, subprocesses or runtime software installation. Development dependency internals were not audited or executed.
• Viewed the supplied interface image with sample workspace content. The pinned assets resolve with image/png; trusted online validation confirms the pin and listing. No fallback overview is needed.
• Trusted registry scripts match current main. Online changed-record validation passes. Current branch metadata reports no required remote status checks; main BOTS.md permits trusted local validation for bot PRs. The earlier workflow-authorization delay is not an artifact requirement. Live rendering was not exercised, and no plugin/dependency code was installed, built, imported or run.