jupyterlab-advanced-code-viewer-extension 0.1.2__tar.gz

jupyterlab_advanced_code_viewer_extension-0.1.2/.agents/JOURNAL.md

@@ -0,0 +1,20 @@
+# Claude Code Journal
+
+This journal tracks substantive work on documents, diagrams, and documentation content.
+
+---
+
+1. **Task - Project creation** (v0.1.0): Created `jupyterlab_advanced_code_viewer_extension` as new JupyterLab extension<br>
+   **Result**: Scaffolded by `new-jupyterlab-extension.sh --headless` from copier template `jupyterlab/extension-template` v4.6.5, `kind: frontend-and-server`, settings and tests enabled. Purpose per `docs/brief.md`: bring follow-the-file, change display, marks, comments and notes panel of siblings `jupyterlab_advanced_markdown_viewer_extension` and `jupyterlab_advanced_html_viewer_extension` to notebooks and source files, inside the editor while the user types, no viewer mode. Repository initialised with `git init -b main` and initial import commit. Added `.claude/CLAUDE.md` overlay importing user and workspace layers without copying them: Makefile-only lifecycle, lockfile trio rule, Makefile version check (1.45, identical to canonical), pm-tools-only trackers, CLI agent-skill rule, graphify scope control, Required Skills table. Added `.claude/settings.json` with `worktree.bgIsolation: none`, as HTML viewer sibling. README rewritten: seven template badges, features and limitations from the brief, sections below Uninstall dropped. Tests on three tiers: pytest (hello route, 403 without token), Jest `request.spec.ts` (`requestAPI` against mocked `ServerConnection`), Galata (activation, settings load, hello route) with port from `JUPYTER_TEST_PORT` and own settings folder.
+
+2. **Task - Dependency floors raised to installed toolchain** (v0.1.0): raised ranges in `package.json`, `pyproject.toml` and `ui-tests/package.json` to installed major.minor before first build<br>
+   **Result**: Copier template v4.6.5 declares ranges from JupyterLab 4.0; jupyterlab-extension skill rule: floor at installed and tested major.minor, ceiling next major, floors read from installed packages. `@jupyterlab/*` from lab 4.6.4 (application ^4.6.0, coreutils ^6.6.0, services ^7.6.0), dev tools from `node_modules` after `make check_dependencies` (eslint 9.39, prettier 3.9, jest 29.7; typescript stays ~5.5.4), Python from `pip list` (jupyter_server>=2.21,<3, pytest>=9.1,<10); `dev` extra pulls `test`. Galata ^5.6.0, Playwright ^1.64.0, browser build 1248 in image. CI: jupyterlab>=4.6,<5, Python 3.13, badge URLs skipped by link check. Test server sets `c.GalaxaHubMotd.open_on_start = False`: MOTD startup tab hangs Galata. `make build`, `make test` green: jest 6, pytest 2, auth gate. Galata 3 of 3 against built labextension through scratch `JUPYTER_CONFIG_PATH`, no `make install`; 3 of 3 red without the extension. `package.json` committed with `yarn.lock`; Makefile 1.45 writes no `package-lock.json`.
+
+3. **Task - Acceptance criteria proposed, INTENT.md folded in** (v0.1.0): filed 278 open criteria through pm-tools, updated README from `INTENT.md`, removed that file<br>
+   **Result**: Star Colonel ordered `INTENT.md` consumed into README and criteria, then removed, criteria fairly granular. Read both siblings' trackers through pm-tools (Markdown viewer 199 items, HTML viewer 78), started from the categories the brief maps. `docs/acc-crit-advanced-code-viewer.md`: 23 categories, each description naming its release; release 1 99, release 2 47, release 3 93, release 4 36, README 3; 80 CRITICAL; every criterion names its test file. INTENT decision origins kept as body clause: user 10, plan 13, proposed and unanswered 11, new in this proposal 35. ACC-APPLY-29 and ACC-CELLS-123 log why Markdown viewer's rejected ACC-APPLY-15 (undo) returns: editor in scope here. README gained INTENT lead, Sibling extensions and Releases tables (all Not built), three limits. Both siblings installed in this lab (1.0.31, 1.0.36), observable live. `pm-tools check docs --strict` clean; handle @kj as sibling rosters.
+
+4. **Task - GitHub repository created** (v0.1.0): created public repository `stellarshenson/jupyterlab_advanced_code_viewer_extension`, set as `origin`<br>
+   **Result**: Star Colonel ordered project created on git host through my-vault and my-git. Host and visibility taken from siblings: both viewers public on GitHub under `stellarshenson`, and `package.json` URLs plus README badges already name that address. Vault was locked; `jupyterlab-passkey vault exec --env GITHUB_TOKEN=github/api` unlocked by passkey and passed token in environment only, so it reached neither transcript, argv nor disk. No `gh` CLI, so REST `POST /user/repos` from a short Python script: description from `package.json`, `auto_init` false to keep local history, other settings GitHub defaults. `git ls-remote origin` exit 0 with stored credentials. Not registered as `~/workspace` submodule.
+
+5. **Task - Template upgrade and scoped npm name** (v0.1.1): refreshed at template v4.6.5 with Makefile 1.46, labextension renamed to `@stellarshenson/jupyterlab-advanced-code-viewer-extension`<br>
+   **Result**: Fleet campaign `tmp/workflows/scoped-npm-names` in the jupyterlab folder. Template stays v4.6.5, Makefile 1.45 → 1.46. Floors moved: `@jupyter/eslint-plugin` ^1.4.0, `typescript` ~5.8.0, `typescript-eslint` ^8.72.0, `coverage>=7.17,<8`, `pytest>=9.2,<10`. Rename because npm refuses unscoped dashed name whose underscored form is published, and JupyterLab URI parser refuses underscore in unscoped plugin id. Settings id and labextension path follow new name; Python module and PyPI distribution keep theirs, so `pip install` unchanged. Journal moved to `.agents/JOURNAL.md` by `journal-tools layout`, `.claude/JOURNAL.md` is link. Verified by `build_test.py`: Jest 6, pytest 2, Galata 3, browser check, labextension. One lint warning stays: unused `error` variable.

jupyterlab_advanced_code_viewer_extension-0.1.2/.claude/CLAUDE.md

@@ -0,0 +1,194 @@
+<!-- @import /home/lab/.claude/CLAUDE.md -->
+<!-- @import /home/lab/workspace/.claude/CLAUDE.md -->
+
+# Project-Specific Configuration
+
+This file is an overlay. It imports two layers and copies neither:
+
+- **User layer** - `/home/lab/.claude/CLAUDE.md`, applies to every project on this machine
+- **Workspace layer** - `/home/lab/workspace/.claude/CLAUDE.md`, applies to everything under `~/workspace`
+
+Both layers apply in full. Rules below extend or strengthen them; where they overlap, the stricter
+wording wins. The workspace `/home/lab/workspace/.claude/` directory and the skills the two layers
+name carry every standard not restated here.
+
+## Mandatory Bans (Reinforced)
+
+The following workspace rules are STRICTLY ENFORCED for this project:
+
+- **No automatic git tags** - only create tags when user explicitly requests
+- **No automatic version changes** - only modify version in package.json/pyproject.toml/etc. when user explicitly requests
+- **No automatic publishing** - never run `make publish`, `npm publish`, `twine upload`, or similar without explicit user request
+- **No manual package installs if Makefile exists** - use `make install` or equivalent Makefile targets, not direct `pip install`/`uv install`/`npm install`
+- **No automatic git commits or pushes** - only when user explicitly requests
+
+## Project Context
+
+JupyterLab 4 extension, `kind: frontend-and-server`, scaffolded from the official copier template
+`jupyterlab/extension-template` v4.6.5. The brief is `docs/brief.md`; read it in full before any
+design or code work, its section "Sibling records to read" included.
+
+The extension brings the functions of the two read-only viewers, `jupyterlab_advanced_markdown_viewer_extension`
+and `jupyterlab_advanced_html_viewer_extension`, to notebooks and to every text file the file editor
+opens. The open document follows the file while an AI agent or another program writes it and shows
+each change; the user's unsaved edits are kept; the user and the agent mark passages and write
+comment threads that are stored in the file.
+
+**The rule that shapes this project**: it works while the user edits. It adds no viewer widget, no
+viewer mode and no review mode. Every function is active in a notebook's command mode and edit mode,
+in a rendered and an unrendered Markdown cell, and in the file editor while the user types. Functions
+are switched on and off by settings, under the Markdown viewer's setting names.
+
+**Read first**, as the brief orders: the two siblings beside this project,
+`../jupyterlab_advanced_markdown_viewer_extension` and `../jupyterlab_advanced_html_viewer_extension`
+- their README, `docs/`, `.claude/CLAUDE.md`, `.claude/JOURNAL.md`, `src/`, `ui-tests/tests/` and
+the agent skill under `.agents/skills/`. Their trackers are read through `pm-tools` only. A rejected
+criterion or defect there records a decision already refused; do not propose it again without a new
+reason. No sibling extension becomes an install dependency without the Star Colonel's word.
+
+**Architecture at creation** (the scaffold; the brief's releases replace it):
+
+- **Frontend** (TypeScript, `src/`) - `index.ts` the plugin with the settings load, `request.ts` the
+  call to the server namespace `jupyterlab-advanced-code-viewer-extension`
+- **Server** (Python, `jupyterlab_advanced_code_viewer_extension/`) - `routes.py` the `hello` route,
+  every handler under `@tornado.web.authenticated`; `.github/scripts/check_auth.py` is the gate
+- **Schema** (`schema/plugin.json`) - the settings; the names follow the Markdown viewer where the
+  function is the same
+- **Notes code** - copied from the two viewers into this project and kept in modules separate from
+  the editor and notebook code, so a shared package can be taken out later; the two viewers are not
+  changed from here
+- **Tests** - pytest in `jupyterlab_advanced_code_viewer_extension/tests/`, Jest in `src/__tests__/`,
+  Playwright/Galata in `ui-tests/`
+- **CI/CD** - GitHub Actions plus jupyter-releaser under `.github/workflows/`
+
+**Feature specification** - criteria in `docs/acc-crit*.md`, defects in `docs/defects*.md`, both
+written and read only through `pm-tools`.
+
+## Build Lifecycle - Makefile Only
+
+The Makefile owns the whole build lifecycle. Never run `pip`, `jlpm`, `yarn`, `npm`,
+`python -m build`, `twine`, or any build, publish or clean command directly - those bypass the
+project-local `.nodeenv/` toolchain the Makefile pins.
+
+| Target          | Effect                                                                                  |
+| --------------- | --------------------------------------------------------------------------------------- |
+| `make install`  | build and install the extension (raises the patch version, by design of Makefile 1.42+) |
+| `make publish`  | release to npm and PyPI - needs explicit approval every time                            |
+| `make clean`    | remove build artefacts                                                                  |
+| `make mrproper` | remove all build and virtual-environment artefacts                                      |
+| `make build`    | re-resolve `yarn.lock`, format, build the wheel and the sdist into `dist/`              |
+| `make test`     | Jest, pytest and the endpoint authentication gate                                       |
+
+**Makefile version check**: the local Makefile declares its version on line 1. Compare it against
+`/home/lab/workspace/private/jupyterlab/@utils/jupyterlab-extensions/Makefile` and copy the canonical
+file over the local one as soon as a newer version is found. Check at the start of any build work.
+Local version at project creation: 1.45, identical to canonical.
+
+**The Galata suite has no Makefile target**, so it is the one lifecycle step outside the Makefile:
+`jlpm install` and `jlpm playwright install chromium` in `ui-tests/`, then
+`JUPYTER_TEST_PORT=<free port> jlpm playwright test`. Port 8888 belongs to this workstation's own
+lab. Redirect output to a file instead of `| tee`, which reports tee's exit status. The suite runs
+against the extension that `make install` put into the lab.
+
+## Dependency Ranges
+
+The rule is the jupyterlab-extension skill's: floor at the installed and tested `major.minor`,
+ceiling at the next major, in `pyproject.toml`, `package.json` and `ui-tests/package.json` alike.
+Floors are read from the installed packages (`pip list`, `node_modules/<pkg>/package.json`), never
+from PyPI or the npm registry. `typescript` keeps its tilde; `lib0` and `webpack` stay exact under
+`resolutions`. A range edit is followed by `make build`, which re-resolves `yarn.lock`.
+
+## Git Rules (Project-Specific)
+
+- The repository was initialised with `git init -b main` and an initial import of every artefact
+- **Always commit `package.json`, `package-lock.json` and `yarn.lock` together** - a lockfile left
+  behind makes CI fail with YN0028 on an immutable install. Makefile 1.41+ produces no
+  `package-lock.json`, so in practice this is `package.json` with `yarn.lock`, and
+  `ui-tests/package.json` with `ui-tests/yarn.lock`
+
+## Journal Rules (Project-Specific)
+
+- **APPEND ONLY**: New journal entries MUST be appended at the end of the file, never inserted between existing entries
+- Entries maintain strict chronological order by position - the last entry in the file is always the most recent work
+- Never reorder, move, or insert entries out of sequence
+- The Stellars **journal plugin** is the canonical tool for this file: create via `/journal:create`, append via `/journal:update`, archive via `/journal:archive`. The `journal:journal` skill auto-triggers on any mention of "journal" and runs `journal-tools check` after every write
+- Direct edits to `JOURNAL.md` are a last resort - prefer the plugin so modus secundis format, continuous numbering and append-only order are enforced automatically
+
+## Acceptance Criteria and Defects
+
+- Criteria live in `docs/acc-crit*.md` and defects in `docs/defects*.md`, written **only** through
+  the project-management plugin (the `pm-tools` CLI), never by a hand edit of either file:
+  `/project-management:acc-crit` adds, closes, rejects or relates a criterion,
+  `/project-management:defect` files, triages, logs or closes a defect, `/project-management:report`
+  gives status and coverage
+- **Every feature gets its acceptance criteria before the code**, and every criterion names the test
+  that proves it
+- **Functional tests under `ui-tests/` are part of every feature**, not an afterthought, and run
+  green before a release
+- Each release of the brief is complete by itself: criteria, tests, README, agent skill where it
+  applies
+- Close a criterion only on evidence - the test that ran and what it showed
+
+## Tests
+
+All three tiers of the jupyterlab-extension skill's testing strategy, written to its
+`references/galata-testing.md`:
+
+- **pytest** under `jupyterlab_advanced_code_viewer_extension/tests/` for the server code
+- **Jest** under `src/__tests__/` for frontend logic
+- **Playwright/Galata** under `ui-tests/` for everything visible in the browser: the port through
+  the one variable `JUPYTER_TEST_PORT`, the test server on its own settings folder, no snapshot-only
+  assertions, and a suite that can fail - mutate what a test guards and watch it go red before
+  trusting its green
+- Galata tests act as the agent: they write the file on disk while the test types in the same
+  document, then assert the text, the cursor, the undo history and the absence of the File Changed
+  dialog
+
+## Command-Line Tools and Their Agent Skill
+
+A command-line tool the extension ships (an entry point under `[project.scripts]` in
+`pyproject.toml`) gets the `--help` and the agent skill that the jupyterlab-extension skill's section
+"Agent Skill for a Shipped CLI" prescribes.
+
+- **Name** - the extension's name in kebab-case, `jupyterlab-advanced-code-viewer-extension`, for
+  the directory and the `name:` field alike
+- **Location** - `.agents/skills/jupyterlab-advanced-code-viewer-extension/SKILL.md` in the
+  repository root, and in the wheel through one line in the `shared-data` table of `pyproject.toml`
+- **Same commit** - the skill and the `--help` text change in the commit that changes the CLI
+- **Never inside the Python package** - the CI link check imports the package for every link in a
+  Markdown file inside it, and fails without `jupyter_server`
+- **Reference implementation** -
+  `/home/lab/workspace/private/jupyterlab/jupyterlab_notifications_extension`
+
+## Scope Control - graphify
+
+- Run `/graphify` once the first source is in place to build `tmp/graphify-out/`
+- Run `graphify affected` before editing existing code to learn its callers and dependents; that
+  affected set is the change budget, and an edit outside it needs the Star Colonel's word
+- Run `graphify update` after every edit
+- `tmp/` is gitignored, so the graph never ships
+
+## Required Skills
+
+| Skill                                   | Use                                                                                   |
+| --------------------------------------- | ------------------------------------------------------------------------------------- |
+| `jupyterlab-extension`                  | extension development guidelines, testing strategy, CI/CD, caveats                    |
+| `my-browser`                            | browser automation for screenshots and UI verification against the running JupyterLab |
+| `project-management:project-management` | acceptance criteria and defects through the `pm-tools` CLI                            |
+| `graphify`                              | the codebase graph and the impact analysis that bounds every change                   |
+| `journal:journal`                       | the project journal through the `journal-tools` CLI                                   |
+
+## Strengthened Rules
+
+- **No mode** - no viewer mode, no review mode, no separate viewer widget; a function that needs a
+  mode to be entered is a design error, not a setting
+- **The user's document is sacred** - a change from disk never moves the cursor or the selection,
+  never takes the focus, never enters the user's undo history, and never shows the File Changed
+  dialog once applied; a save never overwrites a disk change the extension has not applied
+- **A marker never changes what the program does** - a marker inside a string, a here-document or a
+  template literal is refused or placed outside; a file kind without a comment syntax takes no mark
+- **No kernel execution** - the extension starts none
+- **Styling through JupyterLab CSS variables only** - no literal colours, so every theme renders the
+  change display and the marks; verify on stock light and stock dark with `my-browser`
+- **No screenshot claim without a render** - a statement about visible behaviour needs a real
+  browser session behind it

jupyterlab_advanced_code_viewer_extension-0.1.2/.claude/JOURNAL.md

@@ -0,0 +1 @@
+../.agents/JOURNAL.md

jupyterlab_advanced_code_viewer_extension-0.1.2/.claude/settings.json

@@ -0,0 +1,5 @@
+{
+  "worktree": {
+    "bgIsolation": "none"
+  }
+}

jupyterlab_advanced_code_viewer_extension-0.1.2/.copier-answers.yml

@@ -0,0 +1,18 @@
+# Changes here will be overwritten by Copier; NEVER EDIT MANUALLY
+_commit: v4.6.5
+_src_path: https://github.com/jupyterlab/extension-template
+advanced: false
+author_email: konrad.jelen@gmail.com
+author_name: Stellars Henson
+has_ai_rules: false
+has_binder: false
+has_settings: true
+kind: frontend-and-server
+labextension_name: '@stellarshenson/jupyterlab-advanced-code-viewer-extension'
+project_short_description: Follow a notebook or a source file while an AI agent writes
+    it, see each change in the editor as you work, and mark and comment on code with
+    notes stored in the file
+python_name: jupyterlab_advanced_code_viewer_extension
+repository: https://github.com/stellarshenson/jupyterlab_advanced_code_viewer_extension
+test: true
+

jupyterlab_advanced_code_viewer_extension-0.1.2/.gitignore

@@ -0,0 +1,137 @@
+*.bundle.*
+lib/
+node_modules/
+*.log
+.eslintcache
+.stylelintcache
+*.egg-info/
+.ipynb_checkpoints
+*.tsbuildinfo
+jupyterlab_advanced_code_viewer_extension/labextension
+# Version file is handled by hatchling
+jupyterlab_advanced_code_viewer_extension/_version.py
+
+# Integration tests
+ui-tests/test-results/
+ui-tests/playwright-report/
+
+# Created by https://www.gitignore.io/api/python
+# Edit at https://www.gitignore.io/?templates=python
+
+### Python ###
+# Virtual environments
+.venv
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage/
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# pyenv
+.python-version
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# Mr Developer
+.mr.developer.cfg
+.project
+.pydevproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# End of https://www.gitignore.io/api/python
+
+# OSX files
+.DS_Store
+
+# Yarn cache
+.yarn/
+
+.nodeenv/
+
+logs/
+
+tmp/
+
+# Jest JUnit report
+junit.xml

jupyterlab_advanced_code_viewer_extension-0.1.2/.prettierignore

@@ -0,0 +1,14 @@
+node_modules
+**/node_modules
+**/lib
+**/package.json
+!/package.json
+jupyterlab_advanced_code_viewer_extension
+eslint.config.mjs
+.venv
+.claude
+tmp
+docs/brief.md
+docs/acc-crit*.md
+docs/defects*.md
+.agents

jupyterlab_advanced_code_viewer_extension-0.1.2/.yarnrc.yml

@@ -0,0 +1,2 @@
+nodeLinker: node-modules
+enableScripts: false

jupyterlab_advanced_code_viewer_extension-0.1.2/CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+<!-- <START NEW CHANGELOG ENTRY> -->
+
+## [0.1.2] - 2026-10-30
+
+### Changed
+
+- Upgrade to extension template v4.6.5 and Makefile 1.46
+
+### Fixed
+
+- Take the scoped @stellarshenson/jupyterlab-advanced-code-viewer-extension npm name
+
+<!-- <END NEW CHANGELOG ENTRY> -->

jupyterlab_advanced_code_viewer_extension-0.1.2/CONTRIBUTING.md

@@ -0,0 +1,113 @@
+# Contributing
+
+## Development install
+
+Note: You will need Node.js to build the extension package.
+You may install it from [nodejs.org](https://nodejs.org/en/download). We
+recommend using the latest LTS version of Node.js.
+
+The `jlpm` command is JupyterLab's pinned version of
+[yarn](https://yarnpkg.com/) that is installed with JupyterLab. You may use
+`yarn` or `npm` in lieu of `jlpm` below.
+
+```bash
+# Clone the repo to your local environment
+# Change directory to the jupyterlab_advanced_code_viewer_extension directory
+
+# Set up a virtual environment and install package in development mode
+python -m venv .venv
+source .venv/bin/activate
+pip install --editable ".[dev,test]"
+
+# Link your development version of the extension with JupyterLab
+jupyter-builder develop . --overwrite
+# Server extension must be manually installed in develop mode
+jupyter server extension enable jupyterlab_advanced_code_viewer_extension
+
+# Rebuild extension Typescript source after making changes
+# IMPORTANT: Unlike the steps above which are performed only once, do this step
+# every time you make a change.
+jlpm build
+```
+
+You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.
+
+```bash
+# Watch the source directory in one terminal, automatically rebuilding when needed
+jlpm watch
+# Run JupyterLab in another terminal
+jupyter lab
+```
+
+With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).
+
+By default, the `jlpm build` command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:
+
+```bash
+jupyter lab build --minimize=False
+```
+
+## Development uninstall
+
+```bash
+# Server extension must be manually disabled in develop mode
+jupyter server extension disable jupyterlab_advanced_code_viewer_extension
+pip uninstall jupyterlab_advanced_code_viewer_extension
+```
+
+In development mode, you will also need to remove the symlink created by `jupyter-builder develop`
+command. To find its location, you can run `jupyter labextension list` to figure out where the `labextensions`
+folder is located. Then you can remove the symlink named `@stellarshenson/jupyterlab-advanced-code-viewer-extension` within that folder.
+
+## Endpoint authentication
+
+Every verb method of every handler must carry a `@tornado.web.authenticated`
+decorator, or, if the endpoint is meant to be public, an explicit
+`@allow_unauthenticated`/`@ws_authenticated` decorator from
+`jupyter_server.auth.decorator`. The `build` workflow enforces this by running:
+
+```sh
+python .github/scripts/check_auth.py
+```
+
+## Testing the extension
+
+### Server tests
+
+This extension is using [Pytest](https://docs.pytest.org/) for Python code testing.
+
+Install test dependencies (needed only once):
+
+```sh
+pip install -e ".[test]"
+# Each time you install the Python package, you need to restore the front-end extension link
+jupyter-builder develop . --overwrite
+```
+
+To execute them, run:
+
+```sh
+pytest -vv -r ap --cov jupyterlab_advanced_code_viewer_extension
+```
+
+#### Frontend tests
+
+This extension is using [Jest](https://jestjs.io/) for JavaScript code testing.
+
+To execute them, execute:
+
+```sh
+jlpm
+jlpm test
+```
+
+### Integration tests
+
+This extension uses [Playwright](https://playwright.dev/docs/intro) for the integration tests (aka user level tests).
+More precisely, the JupyterLab helper [Galata](https://github.com/jupyterlab/jupyterlab/tree/master/galata) is used to handle testing the extension in JupyterLab.
+
+More information is provided within the [ui-tests](./ui-tests/README.md) README.
+
+## Packaging the extension
+
+See [RELEASE](RELEASE.md)

jupyterlab_advanced_code_viewer_extension-0.1.2/LICENSE

@@ -0,0 +1,29 @@
+BSD 3-Clause License
+
+Copyright (c) 2026, Stellars Henson
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.