fontlab-remopy 2.0.9__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (50) hide show
  1. fontlab_remopy-2.0.9/.gitignore +30 -0
  2. fontlab_remopy-2.0.9/CHANGELOG.md +567 -0
  3. fontlab_remopy-2.0.9/DEPENDENCIES.md +59 -0
  4. fontlab_remopy-2.0.9/LICENSE +201 -0
  5. fontlab_remopy-2.0.9/MIGRATION.json +36 -0
  6. fontlab_remopy-2.0.9/NOTICE +5 -0
  7. fontlab_remopy-2.0.9/PKG-INFO +349 -0
  8. fontlab_remopy-2.0.9/README.md +323 -0
  9. fontlab_remopy-2.0.9/examples/control.py +30 -0
  10. fontlab_remopy-2.0.9/examples/native_smoke.py +16 -0
  11. fontlab_remopy-2.0.9/glyphs/fontlab_remote.py +241 -0
  12. fontlab_remopy-2.0.9/install.vfpy +233 -0
  13. fontlab_remopy-2.0.9/pyproject.toml +47 -0
  14. fontlab_remopy-2.0.9/src/fontlab_remopy/__init__.py +21 -0
  15. fontlab_remopy-2.0.9/src/fontlab_remopy/__main__.py +5 -0
  16. fontlab_remopy-2.0.9/src/fontlab_remopy/actions.py +101 -0
  17. fontlab_remopy-2.0.9/src/fontlab_remopy/cli.py +100 -0
  18. fontlab_remopy-2.0.9/src/fontlab_remopy/client.py +225 -0
  19. fontlab_remopy-2.0.9/src/fontlab_remopy/discovery.py +26 -0
  20. fontlab_remopy-2.0.9/src/fontlab_remopy/host.py +15 -0
  21. fontlab_remopy-2.0.9/src/fontlab_remopy/mcp/__init__.py +125 -0
  22. fontlab_remopy-2.0.9/src/fontlab_remopy/mcp/compat.py +62 -0
  23. fontlab_remopy-2.0.9/src/fontlab_remopy/mcp/relay.py +79 -0
  24. fontlab_remopy-2.0.9/src/fontlab_remopy/mcp_bridge.py +24 -0
  25. fontlab_remopy-2.0.9/src/fontlab_remopy/platforms/__init__.py +27 -0
  26. fontlab_remopy-2.0.9/src/fontlab_remopy/platforms/crossover.py +54 -0
  27. fontlab_remopy-2.0.9/src/fontlab_remopy/platforms/macos/__init__.py +34 -0
  28. fontlab_remopy-2.0.9/src/fontlab_remopy/platforms/wine.py +76 -0
  29. fontlab_remopy-2.0.9/src/fontlab_remopy/py.typed +0 -0
  30. fontlab_remopy-2.0.9/src/fontlab_remopy/remote.py +79 -0
  31. fontlab_remopy-2.0.9/src/fontlab_remopy/results.py +109 -0
  32. fontlab_remopy-2.0.9/src/fontlab_remopy/setup.py +74 -0
  33. fontlab_remopy-2.0.9/test.sh +5 -0
  34. fontlab_remopy-2.0.9/tests/fixtures/mcp_server.py +30 -0
  35. fontlab_remopy-2.0.9/tests/test_api_surface.py +191 -0
  36. fontlab_remopy-2.0.9/tests/test_argument_guard.py +122 -0
  37. fontlab_remopy-2.0.9/tests/test_compatibility_boundaries.py +126 -0
  38. fontlab_remopy-2.0.9/tests/test_consumer_imports.py +80 -0
  39. fontlab_remopy-2.0.9/tests/test_control.py +271 -0
  40. fontlab_remopy-2.0.9/tests/test_crossover.py +259 -0
  41. fontlab_remopy-2.0.9/tests/test_deprecated_modules.py +64 -0
  42. fontlab_remopy-2.0.9/tests/test_discovery.py +39 -0
  43. fontlab_remopy-2.0.9/tests/test_glyphs_script.py +173 -0
  44. fontlab_remopy-2.0.9/tests/test_installer_archive.py +67 -0
  45. fontlab_remopy-2.0.9/tests/test_layout.py +158 -0
  46. fontlab_remopy-2.0.9/tests/test_mcp_bridge.py +57 -0
  47. fontlab_remopy-2.0.9/tests/test_mcp_bridge_deprecation.py +52 -0
  48. fontlab_remopy-2.0.9/tests/test_remote.py +81 -0
  49. fontlab_remopy-2.0.9/tests/test_sdk.py +80 -0
  50. fontlab_remopy-2.0.9/tests/test_setup_relay_boundaries.py +148 -0
@@ -0,0 +1,30 @@
1
+ .venv/
2
+ .local/
3
+ __pycache__/
4
+ .pytest_cache/
5
+ dist/
6
+ uv.lock
7
+ # Private and scratch state: macOS metadata, agent scratch dirs, local envs (never source)
8
+ .DS_Store
9
+ .omc/
10
+ **/.omc/
11
+ .superpowers/
12
+ .worktrees/
13
+ *.vfpyc
14
+
15
+ # Python and macOS (pypitrust)
16
+ *.py[cod]
17
+ *.egg-info/
18
+ .eggs/
19
+ build/
20
+ .ruff_cache/
21
+ .mypy_cache/
22
+ .coverage
23
+ .coverage.*
24
+ htmlcov/
25
+ .tox/
26
+ .nox/
27
+
28
+ # Python and macOS (pypitrust)
29
+ __version__.py
30
+ _version.py
@@ -0,0 +1,567 @@
1
+ ---
2
+ this_file: CHANGELOG.md
3
+ ---
4
+
5
+ ## 2026-11-17 — Relay refuses FontLab as its Python; installer stub 1.0.15 (Issue 259 follow-ups)
6
+
7
+ - `fontlab_remopy.mcp` refuses to start its relay when `sys.executable` is FontLab
8
+ itself, with a message saying to run it from a separate Python. Starting FontLab's
9
+ executable as a Python hangs the host (fl#8659).
10
+ - `install.vfpy` is now the stub from fontlab-python-instamix 1.0.15. It replaces an
11
+ installed instamix older than 1.0.13 and puts the old copy back if the upgrade
12
+ fails; linked checkouts and local builds are kept. A download that fails for
13
+ lack of root certificates (FontLab 9 for macOS) is retried with the system curl.
14
+
15
+ ## 2026-11-17 — Issue 258 task cleanup
16
+
17
+ - Q5 proprietary metadata/licence migration is no longer listed as open in WORK.md: Apache-2.0 source, legal metadata, release and downloads are qualified by the 2026-11-14 "Remopy 2.0.2 Apache release qualified" and "Apache-2.0 source qualification" entries in this file (v2.0.2, source `00d200b8924e5663e513f6f545882ec9bb4ef27a`).
18
+ - Merged the 2026-11-15 shared-installer TODO rows into the guarded common installer rows (same candidate; Instamix stub landed in the 2026-11-17 "Guarded common installer source qualification" entry) and the three overlapping native requalification rows into one row that names fl#8657 as the blocker.
19
+ - Documentation only; no source or native change.
20
+
21
+ ## 2026-11-17 — Guarded common installer source qualification
22
+
23
+ The installer validates the requested FontLab data context before reusing an
24
+ installed provider. Reuse requires the migration, message and failed-upgrade
25
+ rollback entry points; a provider missing these capabilities must be refreshed.
26
+ The copied bootstrap is the exact canonical Instamix 1.0.11 template. Legacy
27
+ rollback requires 1.0.9 or newer; context guarding originated in 1.0.10, and
28
+ shared-layout venv reuse requires 1.0.11. Package metadata, dependency floors,
29
+ runtime code, scripts, bundles and licences are unchanged.
30
+
31
+ In a fresh full checkout, the complete source suite passed on project-resolved
32
+ MCP 2.3.0, MCP 1.30.0 and MCP 1.26.0: 235 tests each, no skips, one retained
33
+ deprecation warning each, in 28.28, 25.07 and 24.80 seconds. These runs use local
34
+ SDK fixture servers and mocked host submissions. App's sibling UI example is
35
+ AST-read only; the common installer template is read as plaintext. No installer,
36
+ App, Fly or Instamix provider was executed. A separate unchanged normal-hook run
37
+ on the same runtime, installer and test bytes passed 235 tests in 28.69 seconds,
38
+ with no skips and the same warning. It found zero changed production modules;
39
+ that result makes no changed-module coverage claim.
40
+
41
+ Independent final review, current graph qualification, actual main integration,
42
+ exact-commit CI and release inputs remain separate gates. Documentation checks,
43
+ installed provider/consumer coherence, owner recovery and native/Windows receipt
44
+ acceptance are separate from these source tests. Existing consumer-execution,
45
+ Aidus/Fly, unknown Windows replay, private Pages and paused-work holds remain.
46
+
47
+
48
+ ## 2026-11-17 — Issue 256 Windows submission source checks
49
+
50
+ - Add explicit CrossOver/Wine launch and script submission providers and CLI
51
+ backend selection; keep macOS defaults, root exports and authenticated MCP
52
+ execution intact. Return ScriptSubmission with execution_verified false.
53
+ - Bind CrossOver to the validated absolute private bottle selector supported by
54
+ its installed launcher; derive single-separator C: executable paths from its
55
+ drive_c. Ordinary Wine uses an explicit WINEPREFIX and drive_c-only scripts.
56
+ - Reject invalid files, launchers, bottle/backend combinations, nonfinite or
57
+ nonpositive timeouts and native filenames that change Windows path semantics.
58
+ Report subprocess timeouts as unknown outcomes without automatic replay.
59
+ - Offline Python 3.11 arm64 checks: 235 tests pass on each locked, MCP 1.30.0
60
+ and MCP 1.26.0 SDK context; one existing deprecation warning each. Complete
61
+ changed modules have 94% CLI and 100% CrossOver/Wine combined coverage.
62
+ Scoped Ruff and genuine hatch-vcs wheel/sdist build pass.
63
+ - Source candidate awaits independent review and ordinary delivery. No native
64
+ process, installation, commit, push or release ran. Windows receipts,
65
+ standalone Python/uv bootstrap, wheel installation and MCP remain unverified.
66
+
67
+ ## 2.0.4 (2026-11-16)
68
+
69
+ - `install.vfpy` is now the short fontlab-instamix stub. It installs
70
+ fontlab-instamix from PyPI when it is missing, then installs this checkout from
71
+ its `[tool.fontlab-install]` table. The large legacy installer is gone.
72
+ - `tests/test_installer_archive.py` tests the stub, the install table and the sdist.
73
+ - README describes the stub install.
74
+
75
+ ## 2026-11-15 — Shared installer source alignment
76
+
77
+ Copied the reviewed shared installer exactly: dependency constraints and managed origins remain protected; inactive conditional dependencies are filtered before sibling execution in the resolver target Python. FontLab imports remain standard-library-only. Package identity, runtime APIs, dependency declarations, scripts, bundles and legal files are unchanged. The real source-archive check now includes the exact root installer; the prior omission was reproduced before the single allowlist addition.
78
+
79
+ Fresh isolated successor: the eight reviewed source postimages were hash-verified before transfer; the approved AGENTS priority amendment is separate. Independent source review passed. Focused archive/layout checks pass on Python 3.11 arm64 (9 passed). Controller full-suite checks passed on locked SDK, MCP 1.30.0 and MCP 1.26.0: each 179 passed with one existing missing-App-sibling skip, in 21.66/26.07/26.61 seconds pytest time (22.05/26.78/27.03 seconds command elapsed). The lock remains byte-exact. The older attempt remains held; historical graph scope and control-state uncertainty remain open. Normal hooks, fresh-main merge and independent merge review, main delivery/CI, tag/release/downloads, installed provider closure and admitted FontLab/native/full-cohort workflows remain pending. No owner-folder installation or native operation ran.
80
+
81
+
82
+
83
+ ## 2026-11-14 — Remopy 2.0.2 Apache release qualified
84
+
85
+ [Remopy v2.0.2](https://github.com/fontlabcom/fontlab-remopy/releases/tag/v2.0.2) binds source/main `00d200b8924e5663e513f6f545882ec9bb4ef27a`; annotated tag object `5ce9244f53300a0ccddac6a64c4de28faa1a66fd` peels to that source. The unchanged ordinary main hook passed 179 tests without skips in 31.06s, with all 16 production modules at least 80% combined coverage; the ordinary tag hook passed 179 tests in 30.55s. Exact-source CI43646468359 passed both 37-test documentation jobs with SOURCE==OUTPUT==that commit.
86
+
87
+ The two published assets were actually downloaded. Wheel SHA-256 `b320677b15eea41f53eec38393a1a9631a2ae728f18056c0c572d7fb7dcc16e8`; sdist SHA-256 `26205280fd20cb3513d565e3eb75c41b30626621eec535d582cdf43b37057030`. Current first-party source/docs and legal metadata use owner-authorized Apache-2.0; 47 inserted headers preserve runtime ASTs, third-party bytes/notices and frozen MIGRATION.json. All 17 runtime files and installed RECORD validate in a fresh prefix from the downloaded wheel; 78 transport/SDK/API tests passed in 11.05s with one warning and no native providers. Earlier three-SDK runs retain 178 passes and the missing-App-sibling skip; a real-App focused check passed six tests, and the final hook passed without that skip.
88
+
89
+ Independent postpublication REMOPY-RELEASE-REVIEW.md approves these bounded source/release/download/prefix results. The original archive contract and T17 remain open; the historical 149-file raw-mode FAIL is retained. Root install.sh, FontLab installation/native behavior, history/save-reopen, private Pages and cleanup were not performed.
90
+
91
+ ## 2026-11-14 — Apache-2.0 source qualification
92
+
93
+ - Apply owner-authorized Apache-2.0 to current first-party source and documentation;
94
+ retain the 2025 Fontlab Ltd. copyright in NOTICE, include both legal files in
95
+ wheel/sdist, and add SPDX headers to 47 authored Python/shell/vfpy files.
96
+ - Correct stale in-repository recovery claims without changing MIGRATION.json;
97
+ preserve all third-party frontend assets, source maps and notices byte-for-byte.
98
+ - Verify actual wheel/sdist legal bytes and metadata, all three SDK contexts
99
+ (178 passed, one existing App-sibling skip and one warning each), strict docs
100
+ and 37 documentation tests. Runtime code bodies and tracked modes are unchanged.
101
+ - Source candidate only: independent review, integration, released artifacts,
102
+ installation and native acceptance remain separate; private Pages stays held.
103
+
104
+ ## 2026-11-14 — Guarded documentation repair delivered to main
105
+
106
+ - Independent review approved the exact five-file source change
107
+ [aab6906](https://github.com/fontlabcom/fontlab-remopy/commit/aab6906aba43404eccbb584b39b0d1a4d27506ad)
108
+ (tree `32a4b2f29156728cf61480e86af949286c15f78c`). All 149 tracked
109
+ payloads and raw modes were verified; 144 unrelated files were unchanged.
110
+ - The unchanged installed pre-push hook passed 178 tests with one existing
111
+ warning in 28.18 seconds through the ordinary push (33.89 seconds). It
112
+ identified zero changed production modules; this is not a coverage result.
113
+ An earlier detached-checkout push failed before tests. A new owned tracking
114
+ branch at the same commit/tree supplied the real upstream baseline; no
115
+ owner branch changed and no hook was bypassed.
116
+ - [Documentation run 43581035677](https://github.com/fontlabcom/fontlab-remopy/actions/runs/43581035677)
117
+ passed both jobs on attempt 1. Its generated-only child
118
+ [58f30ba](https://github.com/fontlabcom/fontlab-remopy/commit/58f30ba1fde71e11389c37044f36a336ea0f1760)
119
+ has sole parent aab6906 and changes only the two sitemap files. Qualification
120
+ verified all 48 generated payloads and source epoch 1794648574. Four
121
+ controller phases verified the captured owner files, admin, indexes, refs
122
+ and attachments. Archive modes and checkout raw modes remain separate.
123
+ - Closed only this repair's review/main/hook/CI follow-up. Six inherited
124
+ expanded Ruff 0.14.10 findings, limited graph coverage and historical index
125
+ uncertainty remain. Release, artifacts, providers, licence migration, root
126
+ installer completion, all native/GUI/theme/typing/history checks, private
127
+ Pages and cleanup holds remain open. This entry records the delivered
128
+ repair; delivery of this progress update is not yet claimed.
129
+
130
+ ## 2026-11-14 — Guarded documentation comparison, isolated source verification
131
+
132
+ - Replaced the docs test's filename-only observation with a shared content/mode
133
+ patch at the same WORKTREE-to-INDEX boundary. External diff and text conversion
134
+ are disabled; every original output hash/count, source epoch and lineage
135
+ assertion remains. The added real Git five-state regression preserves index
136
+ bytes/mode and rejects content, deletion and executable-mode changes.
137
+ - Reproduced the original failure and both regression false positives before
138
+ repair. All 37 docs cases then pass; the strict hash-locked build reproduces
139
+ all 48 output payloads and raw modes. Each advertised SDK context passes the
140
+ same 178 runtime cases. A genuine App v1.2.16 source peer changes the existing
141
+ AST/signature skip to a pass. No native App or FontLab behavior is inferred.
142
+ - Complete-package combined coverage is 95.49%; all 16 modules exceed 80%
143
+ (minimum 84.06%). Selected Ruff 0.14.10 passes production and the changed
144
+ test, while its expanded scope still reports six existing test_remote.py
145
+ findings. Explicit Ruff 0.16.7 passes the expanded scope.
146
+ - Archived the complete previous WORK.md privately before updating progress.
147
+ Independent review, combined delivery checks, main/hook/exact-commit CI,
148
+ release, owner installation, native acceptance and licence migration remain
149
+ open. This entry records isolated verification only.
150
+
151
+ ## 2026-11-14 — Functional work order documented
152
+
153
+ - Added the owner's functional-progress-first guidance and repository-specific priorities, including cross-package compatibility and a later detailed testing pass. Existing mandatory hooks, holds and unfinished work remain in force.
154
+ - This change updates guidance and planning only; it establishes no new runtime, installed, native or release result.
155
+
156
+ ## 2026-11-12 — D46 documentation pass (Issue 250)
157
+
158
+ - Landed on `main` this session: `1f29bfa` (Ruff lint debt cleared, 44 findings to zero), `ff3b992` (test environment qualification), `297253d` (legacy `mcp_bridge` entry point warns on stderr only), `4c7782b` (2.0.0: eight deprecated pre-1.2 modules removed), `81b67ca` and `44dada7` (R7a Aidus relay migration closed; Issue 207 distribution comparison closed, shim-removal decision row opened). No source changed in this pass.
159
+ - New open TODO row: the Q5 licence audit (D46 licence rows).
160
+ - `WORK.md` now holds a short current status. Its previous 2,210-byte content (SHA-256 `8e2b1df16b76dd006c2cbf44a4e009b1cf0e0ce6b8e6561938f8c16dd67a5b68`, the Issue 250 lint-only round: Ruff 0.16.7, 151 passed on three MCP SDK lines, docs suite 36 tests with 2 failures and 11 errors both before and after) is archived on the workspace data volume.
161
+
162
+ ## 2026-11-12 — Breaking (2.0.0): eight deprecated modules removed (Issue 250)
163
+
164
+ - The owner chose removal (Q6=A). The eight pre-1.2 warning shims are gone; importing them raises `ModuleNotFoundError`. Change imports as follows:
165
+
166
+ | Removed import | Use instead |
167
+ | --- | --- |
168
+ | `fontlab_remopy.control` | `fontlab_remopy.client` (`FontLab`, `AsyncFontLab`) |
169
+ | `fontlab_remopy.controls` | `fontlab_remopy.actions` (`Controls`) |
170
+ | `fontlab_remopy.functions` | `fontlab_remopy.remote` (`remote_function`) |
171
+ | `fontlab_remopy.execution` | `fontlab_remopy.results` (`ExecutionResult`, `ResultTransportError`, `encode_execution`, `decode_execution`, `MAX_CODE_BYTES`, `MAX_OUTPUT_BYTES`) |
172
+ | `fontlab_remopy.native` | `fontlab_remopy.host` (`enable_mcp`) |
173
+ | `fontlab_remopy.mcp_api` | `fontlab_remopy.mcp` (`NativeExecutionError`, `bridge_parameters`, `probe_tools`, `call_tool`, `run_python`, `execute_script`) |
174
+ | `fontlab_remopy.mcp_compat` | `fontlab_remopy.mcp.compat` (`field`, `is_error`, `next_cursor`, `wire`, `unwrap`) |
175
+ | `fontlab_remopy.launch_api` | `fontlab_remopy.platforms` (`ScriptSubmission`, `find_bridge`, `launch`, `submit_script`, `DEFAULT_APP`) |
176
+
177
+ - `fontlab_remopy.mcp_bridge` still ships with its stderr `DeprecationWarning` and goes one major later.
178
+ - `tests/test_deprecated_modules.py` now checks that each removed path raises `ModuleNotFoundError`, is absent from the package, and that its replacement module provides every moved name; it also checks that `mcp_bridge` still ships.
179
+ - A caller re-audit of current remote mains (Aidus, App, Scriptmix, Plugmix, Examples, python-docs, Glyport, Fontport) found no code importer. The only hits are `tools/migrate_app_paths.py` rewrite tables, which keep the old names as inputs, and python-docs generated pages, which python-docs regenerates after the 2.0.0 release.
180
+
181
+ ## 2026-11-12 — `mcp_bridge` deprecation warning (Issue 250)
182
+
183
+ - `fontlab_remopy.mcp_bridge` now emits `DeprecationWarning` naming `fontlab_remopy.mcp.relay`, like the other eight shims. Under `python -m` the warning is attributed to `__main__`, so the default filters print it on stderr.
184
+ - Stdout stays byte-clean: it carries the MCP stdio protocol. New tests in `tests/test_mcp_bridge_deprecation.py` pin the import warning, the stderr warning under default filters and empty stdout; the real SDK round trip through `mcp_bridge` in `tests/test_sdk.py` still passes.
185
+ - The module comment and README no longer say Aidus imports it; Aidus writes `-m fontlab_remopy.mcp.relay`.
186
+ - Nothing is removed. Removing the shims needs a major release and an owner decision (caller audit: no maintained repository imports them).
187
+
188
+ ## 2026-11-12 — Issue 207 distribution comparison closed (Issue 250)
189
+
190
+ - The comparison half of the TODO row "Issue 207 distribution changes" is closed: it cannot be done, and no action was owed.
191
+ - The isolated Issue 207 Remopy candidate (`issue-207` successor, base 9957af31) no longer exists; it was an uncommitted tree and has been cleaned up.
192
+ - No Remopy distribution manifest was recorded for it. The only surviving record is the preflight status list in `verification/issue-207/canonical-delivery-preflight.json` (workspace root): it shows the candidate deleted nine modules and edited docs and four tests.
193
+ - The nine modules (`control`, `controls`, `execution`, `functions`, `launch_api`, `mcp_api`, `mcp_bridge`, `mcp_compat`, `native`) remain on main as deliberate deprecation shims, so the supported import paths stay.
194
+ - Whether to remove them is now its own open TODO row, pending a caller audit.
195
+
196
+ ## 2026-11-12 — Aidus relay migration (R7a) closed (Issue 250)
197
+
198
+ - The R7a half of the TODO row "Migrate the Aidus generator and guides from `fontlab_remopy.mcp_bridge` to `fontlab_remopy.mcp.relay`" is closed. It was already done in Aidus `main` 3ed19d7 (v1.1.10), the evidence for which follows:
199
+ - The generator launches `-m fontlab_remopy.mcp.relay` (`src/fontlab_aidus_agentus/core/fontlab_mcp.py:138`).
200
+ - The guides name only the relay (`src_docs/md/guides/external-agents-mcp.md:101,110,115`, `src_docs/md/guides/fontlab-mcp.md:67`).
201
+ - `git grep mcp_bridge` outside CHANGELOG finds only a pytest fixture named `mcp_bridge` in `tests/core/test_mcp_roundtrip.py`, not an import.
202
+ - Aidus tests already pin the generator: `test_server_config_when_generated_then_launches_the_mcp_relay_module` and `test_server_config_when_relay_module_named_then_it_is_importable` (`tests/core/test_mcp_roundtrip.py:191-202`).
203
+ - The eight deprecated shims and `mcp_bridge` stay for saved user configs, as `tests/test_deprecated_modules.py` pins. The Issue 207 distribution check stays open as its own row. No code change.
204
+
205
+ ## 2026-11-11 — consumer imports and App native_ui source re-check pinned (Issue 250)
206
+
207
+ - New `tests/test_consumer_imports.py`. `FontLab`, `enable_mcp`, `find_bridge`, `probe_tools` and `bridge_parameters` (the top-level names other maintained repositories import) must stay in `_EXPORTS` and `__all__` and resolve lazily to their canonical objects. App's `examples/native_ui.py` (App 7f96170) is parsed from the sibling checkout: it imports only `FontLab` from `fontlab_remopy`, calls it with no arguments as a context manager, and decorates helpers with `fl.python`; the test checks those names and the `python(self, function)` signature.
208
+ - The eight deprecated shims were already pinned by `tests/test_deprecated_modules.py` (identical module and named objects, `DeprecationWarning` naming the replacement) and the `mcp_bridge` relay entry point by `tests/test_sdk.py:31`; no duplicate test was added.
209
+ - Mutants: dropping `find_bridge` from `_EXPORTS` fails 1 consumer test; making `python`'s `function` keyword-only (`def python(self, *, function)`) or adding a required keyword argument each fail the native_ui test; silencing the `native` shim's warning fails 1 deprecation test; replacing the `control` alias with a subclass copy fails 1 deprecation test.
210
+ - TODO: row 7 now names the Aidus relay migration (R7a) and keeps the Issue 207 check (nothing pending visible on origin/main; compare the isolated candidate's manifest); the native_ui row keeps only the native run.
211
+
212
+ ## 2026-11-10 — three MCP SDK lines re-run from the isolated successor (Issue 250)
213
+
214
+ On origin/main 262dbac, `uv run --extra test python -m pytest -q` passed 152
215
+ tests on each of the locked SDK 2.x line, `mcp==1.30.0` and `mcp==1.26.0`
216
+ (arm64 Python from uv, no failures or skips). Offline SDK fixtures only; native
217
+ proof stays separate.
218
+
219
+ ## 2026-11-11 — Issue 250 documentation environment
220
+
221
+ - Document the separate locked Python 3.13 docs recipe. With the clean hash-locked install (`mkdocs-materialx==10.1.8`), all 36 docs tests pass; MaterialX 10.2 reproduces the earlier errors. SDK suite via the workspace recipe: 152 passed (the push gate also ran the added `__main__` entry test). No source or test change.
222
+
223
+
224
+ ## 2026-11-10 — live font editing rule (Issue 250, D44)
225
+
226
+ - AGENTS.md: agents test and edit the font open in FontLab 9, starting from the Desktop VFJs, and may save them.
227
+
228
+ ## 2026-11-10 — Issue 250 Ruff lint cleanup
229
+
230
+ - Add `test_package_entry_when_run_as_module_then_exits_with_cli_status` so the touched `__main__.py` meets the 80% changed-module coverage gate.
231
+ - Merge the nested `async with` in `src/fontlab_remopy/mcp/__init__.py` (SIM117) into one parenthesized statement so Ruff 0.17.4 also reports 0 (checked with `uvx ruff@0.17.4 check .`; 0.16.7 also 0).
232
+ - Clear all 44 Ruff 0.16.7 findings (44 → 0), using safe autofixes and
233
+ reviewed f-string conversions, preserving public names, export order and
234
+ exception behavior. Fourteen formatting expressions match their original
235
+ output in 112 comparisons, including Decimal and Fraction timeout values.
236
+ - Keep explained line-level exceptions for session-owned temporary-file
237
+ lifetime (SIM115), CLI error reporting (BLE001), the public malformed-response
238
+ RuntimeError (TRY004), compatibility export order (RUF022), and the ProperDocs
239
+ import's initialization side effects (F401). Retain the existing B017 fixture
240
+ exception; remove its unused PT011 suppression.
241
+ - Runtime suite: 151 passed before and after (152 at the push gate, which includes the added `__main__` entry test) on each of MCP 2.3.0, 1.30.0 and
242
+ 1.26.0. Run existing Python 3.13 with source/cached SDK paths and explicit
243
+ pytest-asyncio, without installation; see WORK.md for the command.
244
+ - Additional documentation suite: 36 tests before and after, with the same
245
+ 2 failures and 11 errors from the existing documentation environment and
246
+ asset mismatch. No new failures. Ruff ran from the installed uv tool because
247
+ uvx could not acquire its sandbox-protected cache lock.
248
+ - No Ruff configuration or whole-file formatting changes; legacy/frozen
249
+ evidence, native FontLab, installation and publication remain untouched.
250
+
251
+ ## 2026-11-10 — isolated graph guidance proposal
252
+
253
+ Prepare append-only AGENTS guidance for separate task-owned graph HOME and storage, ordinary-analysis scope and independently reviewed bounded recovery. Preserve existing integration rules and acceptance holds. This documentation proposal records no new runtime, test, native, integration or publication result.
254
+
255
+ ## 2026-11-10 — verified integration-round guidance
256
+
257
+ - Record current-main reconciliation in a new isolated successor, preservation
258
+ of concurrent work and exact reviewed staging, combined repository/graph
259
+ checks, independent merge review, required hooks and actual remote proof.
260
+ - Keep solved tasks in cumulative history and unfinished acceptance in the
261
+ future queue. Native, installation, adoption, Issue 123 and private Pages
262
+ boundaries remain unchanged. This entry records documentation only.
263
+
264
+ ## 2026-11-10 — install.vfpy always reinstalls scripts and dependencies
265
+
266
+ - Every install copies all files from `Scripts/` afresh and replaces any file
267
+ already at the same path. A symlinked script folder is replaced by a real
268
+ folder; the link target is never written. A directory where a script file
269
+ belongs is still refused.
270
+ - Required packages are installed on every run. Packages that no package
271
+ index carries (the fontlab-* packages, pythonqtside) are installed from
272
+ checkouts beside this one through their own `install.vfpy`, once per run
273
+ and safe against cycles. uv receives every other requirement, so version
274
+ ranges, markers and extras are enforced. Without uv, sibling checkouts are
275
+ still installed and only the remaining missing requirements are reported.
276
+ - The installer is byte-identical across all eleven installer repositories.
277
+
278
+ ## 2026-11-05 — independently approved documentation applied
279
+
280
+ [Task 2 final review](../verification/issue-230/task-2-fix2-review.md) records
281
+ SPEC PASS / QUALITY APPROVED. The [78-file application receipt](../verification/issue-230/task-2-apply.json)
282
+ includes this repository's six guides and preserves all 21 repository heads,
283
+ branches, indexes and non-selected diffs. This is applied documentation evidence,
284
+ not a new product test, installed artifact, native result or publication.
285
+
286
+ The complete earlier handoff/history below retains its proposal-stage statements
287
+ and dated source pins. Later review, application and delivery status belong in the
288
+ [live workspace ledger](../verification/issue-230/progress.md). Original future,
289
+ native, artifact and preservation contracts remain binding.
290
+
291
+ ## 2026-11-05 — documentation reconciliation proposal
292
+
293
+ Prepared repository-specific organization, test and MVP/delivery guidance from current source/test configuration and retained Issue 207–211 evidence. Distinguished current canonical layout from qualified candidates, future plugin ownership and unfinished native/artifact gates. Preserved all prior work and changelog evidence; no runtime completion, installation or publication is claimed. Historical checked tasks now require receipt/current-scope reconciliation rather than being silently counted complete.
294
+
295
+ ## 2026-11-05 — planning chronology reconciliation
296
+
297
+ Issue122worktree-only execution and old source-head handoff are superseded. Keep all three SDK lines, installed native/nonce/launch and relocated App UI consumer requirements on the current isolated tuple. Historical passing results retain their dated source and acceptance scope in the entries above and original history below. This documentation change creates no new runtime acceptance.
298
+
299
+ ---
300
+ this_file: CHANGELOG.md
301
+ ---
302
+
303
+ ## 2.0.4 (2026-11-16)
304
+
305
+ - Move the native UI example to fontlab-fontlabapp; retain a guide link and
306
+ current native requalification task instead of a duplicate implementation.
307
+ - Merge the Issue 201/204 branch into the issue 205 layout: the unknown-argument
308
+ guard (`tool_schema`, `unknown_arguments`, `refuse_unknown`) lives in
309
+ `mcp.compat`; `client.AsyncFontLab.tool` and `mcp.call_tool` use it; method
310
+ docstrings live in `client` and `actions`. The deprecated `control`,
311
+ `controls`, `mcp_api` and `mcp_compat` forwarders expose the same objects.
312
+
313
+ ## 1.2.0 — 2026-11-03 — issue 205 package layout
314
+
315
+ - Rename `control` to `client`, `controls` to `actions`, `functions` to
316
+ `remote`, `execution` to `results`, and `native` to `host`.
317
+ - Rename `mcp_api` to `mcp`, `mcp_compat` to `mcp.compat`, and `launch_api`
318
+ to the platform dispatcher `platforms` (macOS implementation in `platforms.macos`).
319
+ - Retain all eight old module paths as deprecated forwarders: imports emit
320
+ `DeprecationWarning` and alias the canonical modules, preserving object identity.
321
+ - Keep portable bridge discovery and submission data in `discovery`; importing
322
+ `platforms` on other systems no longer imports `platforms.macos`. Unsupported
323
+ launch/submission still raise `NotImplementedError` naming the platform.
324
+
325
+ - Move clients, named actions, remote functions, result transport and host setup
326
+ into `client.py`, `actions.py`, `remote.py`, `results.py` and `host.py`.
327
+ - Group MCP APIs, relay and SDK compatibility under `mcp/`; move macOS launch
328
+ and script submission to `platforms/macos/`, selected through `platforms`.
329
+ - Preserve all lazy public exports and the deprecated `mcp_bridge` entry point
330
+ and `normalize_result`/`relay` imports for external configurations and Aidus.
331
+ - Update tests, examples and current module references. Dependencies, native
332
+ execution limits, nonce handling and call serialization remain unchanged.
333
+
334
+ ## 2026-11-03 — installer options, licence and cleanup
335
+
336
+ - `install.vfpy` reads optional `[tool.fontlab-install]` keys: `name` (the distribution
337
+ record), `packages` (`[]` installs scripts only) and `dependencies` (what FontLab needs,
338
+ instead of `project.dependencies`). Symlinks inside `Scripts/` are not copied.
339
+
340
+ ## 2026-11-03 — install.vfpy fixes from runs inside FontLab 9
341
+
342
+ Verified by installing all nine packages inside FontLab 9 (Python 3.11.6, arm64).
343
+ - Dependencies with console scripts (glyphsLib, fontTools) failed: uv writes them to
344
+ `site-packages/../../../bin`, which resolves through the venv link to the FontLab
345
+ folder. `bin`, `share` and `include` there now link back into `.venv`.
346
+ - A failed install appends a `"failed"` record with the traceback and uv's output to
347
+ `install.log`; List/Uninstall ignore failed records.
348
+ - Package records include `WHEEL`, so `uv pip check` accepts them.
349
+ - Scripts are copied file by file into FontLab's `Scripts` folder, from a package's
350
+ `Scripts/` folder (exact case) and from folders listed in `[tool.fontlab-install] scripts`.
351
+ Folders shared by several packages merge, e.g. two packages' `Scripts/Kerning`. The
352
+ installer refuses to overwrite a file another package or the user put there; uninstall
353
+ removes only its own files, their `.pyc`, and folders left empty. An older install's
354
+ folder link (`Scripts/Aidus Code`) is replaced by copied files.
355
+ - `*.vfpyc` (FontLab's compiled `install.vfpy`) is ignored by Git.
356
+
357
+ ## 2026-11-03 — install.vfpy creates FontLab's venv
358
+
359
+ FontLab's `python/3.11/site-packages` is now always a real folder; packages are
360
+ symlinked into it, so no `.pth` processing is needed. `install.vfpy` creates `.venv` with
361
+ uv from FontLab's exact Python version and processor type, and links the venv's
362
+ site-packages to FontLab's folder, so `uv pip install --python .venv/bin/python` installs
363
+ into FontLab. An older layout (FontLab's folder linked into `.venv`) is migrated.
364
+
365
+ ## 2026-11-03 — reverse-domain extension id and install.log
366
+
367
+ `[tool.fontlab-install] id = "com.fontlab.remopy"` names this extension. `install.vfpy` keeps
368
+ `Extensions/com.fontlab.remopy/install.log` (JSON Lines; the last line lists every installed file),
369
+ puts copied code in `Extensions/com.fontlab.remopy/lib/`, and adds Scripts > Extensions >
370
+ List Extensions and Uninstall com.fontlab.remopy.
371
+
372
+ ## 2026-11-03 — install.vfpy without uv
373
+
374
+ `install.vfpy` now needs only FontLab's Python. It asks FontLab for its data folder
375
+ (`flPreferences().dataPathDefault`), links a Git checkout or copies a plain folder into
376
+ `Extensions/`, and writes a `.pth` plus `.dist-info` into `python/3.11/site-packages`.
377
+ uv is used only to add missing dependencies. It never replaces folders it does not own.
378
+
379
+ ## 2026-11-03 — release scripts
380
+
381
+ Added `build.sh` (uv build into dist/), `publish.sh` (`uv publish`; refuses a dirty
382
+ tree or an untagged HEAD) and `install.vfpy` (editable install into FontLab's venv
383
+ from inside FontLab). Version stays hatch-vcs from `vX.Y.Z` tags.
384
+
385
+ <!-- workspace-handoff:2026-11-03 -->
386
+ ## 2026-11-03 — documentation handoff for November 2–3
387
+
388
+ No new November 2–3 runtime delivery is attributed here; the current native-access hold is external to source tests.
389
+
390
+ No native retry, process restart or fence clearance was performed by this documentation task.
391
+
392
+ Observed canonical checkout: `main` at `d0afe25a6182`. No source integration is performed by this update.
393
+
394
+ Updated the requested AGENTS/TODO/PLAN/CHANGELOG/README documentation and
395
+ recorded the paused state. Existing project text, examples and history remain;
396
+ no runtime source, installation, native session, branch/ref, release or site was
397
+ changed by this documentation maintenance. Source/archive/ordinary/native and
398
+ promotion acceptance remain separate claims. Detailed workspace evidence is
399
+ recorded in the root CHANGELOG and retained verification reports.
400
+ <!-- /workspace-handoff -->
401
+
402
+ # Changelog
403
+
404
+
405
+ ## 2026-11-10 — Issue 250 documentation round
406
+
407
+ - AGENTS.md describes the delegation, integration and release workflow.
408
+ - WORK.md reset to the current round; the earlier bytes are archived on the owner's workspace data volume, not public.
409
+
410
+ ## 2026-11-03 — Issue 201: unknown tool arguments refused
411
+
412
+ - `tool()` (sync and async) now checks argument names against the live catalogue's input
413
+ schema (fetched once per connection) and raises `ValueError` naming the unknown and the
414
+ allowed names. FontLab drops unknown names silently, so `list_kerning_pairs(master="Bold")`
415
+ used the current master; the parameter is `master_name`. Names only, no type checks; tools
416
+ absent from the catalogue or with open schemas are not checked. `tests/test_argument_guard.py`.
417
+
418
+ ## 2026-11-03 — Issue 201: completeness audit
419
+
420
+ - Docstrings for every public client method; README API reference (names, error types,
421
+ the client `timeout` versus FontLab's fixed five-second `run_python` deadline, code and
422
+ output size limits); PyPI classifiers, keywords and `py.typed`.
423
+ - 33 offline tests (`tests/test_api_surface.py`): every named control, tool paging, error
424
+ paths, timeout fencing, sync-through-portal calls and `run`/`eval`/`execute_script` against a
425
+ fake session that executes the transmitted code. 83 tests pass on mcp 2.3, 1.30.0 and 1.26.0;
426
+ `control.py` 97% and `controls.py` 100% branch coverage. No FontLab contacted.
427
+
428
+ ## 2026-10-15 — issue 104 lane L6 completed (moved from PLAN.md/TODO.md)
429
+
430
+ - Stdlib-only Glyphs script `glyphs/fontlab_remote.py`: MCP over FontLab's bundled
431
+ `fontlab-mcp` bridge with deadlines on every read; unit tests against the SDK
432
+ fixture server; terminal run against live FontLab; real runs inside Glyphs 3.5.1
433
+ and 4.2 with FontLab responding (fonts, eval); README/CHANGELOG/WORK.
434
+ - MCP Python SDK v2 migration (R046 follow-up): `mcp>=1.26,<3`, new `mcp_compat.py`
435
+ (snake_case fields, wire dumps by alias, v1 RootModel unwrap); test fixtures use
436
+ `MCPServer` on v2 and `FastMCP` on v1. Suite: 49 passed on mcp 2.3.0, 1.30.0 and
437
+ 1.26.0. Native read-only session (47 tools, run_python, fonts, eval) passes on
438
+ 2.3.0 and 1.30.0 (workspace evidence `remopy-mcp2/`).
439
+
440
+ ## v0.2.1 (2026-10-16)
441
+
442
+ MCP SDK v2 support (mcp>=1.26,<3 via mcp_compat.py), Glyphs-side remote control script, CLI wire-format output, docs and dependency reconciliation (issues 101/104/106). Release review: verification/issue-106/reviews/X5-fontlab-remopy.md.
443
+
444
+
445
+ - 2026-10-15 (review R-mcp2): the `tools` and `call` CLI output uses the MCP wire
446
+ format (camelCase) on both SDK lines; DEPENDENCIES.md states the v1/v2 dependency
447
+ difference correctly.
448
+
449
+ - 2026-10-15 (R046): DEPENDENCIES.md re-evaluated; superseded the same day by
450
+ the MCP v2 support above (`mcp>=1.26,<3`, `mcp_compat.py`).
451
+
452
+ - Issue 104: `glyphs/fontlab_remote.py`, a stdlib-only script for Glyphs 3/4 that
453
+ controls FontLab through the bundled `fontlab-mcp` bridge (`tools`, `call`,
454
+ `run_python`, `eval`; deadlines on every read; `isError: null` accepted). Tested
455
+ against the SDK fixture server, from macOS's Python 3.9 and inside Glyphs 3.5.1
456
+ and 4.2 (their Python 3.13) against live FontLab 9.0.9783.
457
+
458
+ ## 2026-10-15 — completed checklist (moved from TODO.md)
459
+
460
+ - Record source provenance and baseline.
461
+ - Implement complete package migration and scoped modernization.
462
+ - Verify wheel, sdist, isolated installs and privacy.
463
+ - Verify relevant native behavior in FontLab.
464
+ - Add reusable ordinary sync/async control and decorated Python functions.
465
+ - Verify JSON/results/streams/errors, timeout fencing and process cleanup.
466
+ - Pass review and scoped fixes.
467
+ - Complete all three project iterations.
468
+ - Push, tag, release and verify assets.
469
+
470
+ ## 2.0.4 (2026-11-16)
471
+
472
+ - Document native UI composition from external Python, including actual TypeRig
473
+ widgets through the existing build callback.
474
+
475
+ - Preserve Unicode line separators in JSON values, captured streams and native
476
+ exceptions by splitting transport envelopes only on LF; never replay failures.
477
+ - Add reusable synchronous FontLab and AsyncFontLab contexts with JSON-native
478
+ eval/run/script results and separate stdout/stderr/native tracebacks.
479
+ - Add ordinary @fl.python functions with real signature/default binding,
480
+ metadata preservation, explicit capture/source boundaries and isolated scope.
481
+ - Add short fonts()/glyph(name), named native control helpers and live schemas.
482
+ - Keep idle sessions alive; fence queued/new calls after timeout/cancellation,
483
+ preserve unknown-outcome notes, and reap SDK bridge processes on cleanup.
484
+ - Preserve public NativeExecutionError when it escapes a connection context.
485
+
486
+ - Extract reusable fontlab_remopy launch, file submission, authenticated native
487
+ MCP discovery/call, verified Python/script execution and MCP setup APIs.
488
+ - Preserve actual tool/native errors and unknown timeout outcomes without retry.
489
+ - Retain narrow null isError normalization with official SDK message handling.
490
+ - Close relay stream channels before teardown and verify child cleanup by PID.
491
+ - Preserve current source hashes/licenses in an excluded recovery archive.
492
+ - Verify thirteen regressions and live MCP setup/46 tools/.flpy completion.
493
+ - Show unknown execution outcomes and retained setup status notes on CLI timeout.
494
+
495
+ ## v0.2.0 publication verified
496
+
497
+ Actual publication and independent downloaded-asset verification complete.
498
+ Three full-project iterations pass; installed tagged wheel/sdist each457tests.
499
+ Downloaded native smoke covers all eight packages and both formats, including
500
+ production ACP/native UI and TypeRig composition. Exact release URLs, immutable
501
+ code commit and asset digests are in RELEASE.md. This follow-up changes only
502
+ completion evidence; release code and tag are unchanged.
503
+
504
+ ## 2026-10-15 — workspace plan and checklist reconciliation
505
+
506
+ Completed repository scope archived after reading WORK.md and checking the
507
+ workspace evidence. Workspace release/integration gates remain in the parent
508
+ PLAN.md. Historical verification limits below remain part of the record.
509
+
510
+ ### Archived PLAN.md
511
+
512
+ # Plan
513
+
514
+ No open work. Issue 101 shipped as v0.2.0; the issue 104 Glyphs remote script and the MCP SDK v2 migration are complete and recorded in CHANGELOG.md.
515
+
516
+ ### Archived TODO.md
517
+
518
+ # Tasks
519
+
520
+ No open tasks.
521
+
522
+
523
+ ## 2026-11-06 — Issue 233 source/build-only site candidate
524
+
525
+ Added complete authored site pages, the separate 31-package hash-locked
526
+ ProperDocs/MaterialX environment, light fltheme26 controls, generated output and
527
+ a main-only two-job build workflow. The read-only job verifies exact source or
528
+ direct docs-only child lineage, non-doc identity, the shared source epoch and
529
+ full tracked/untracked parity. No Pages permission, request or deployment exists.
530
+
531
+ Strict builds, all 20 docs tests, actionlint and shellcheck passed. Independent
532
+ docs environments rebuilt every output file byte-identically. Real local Git
533
+ tests cover changed/unchanged output, foreign staged source, wrong checkout,
534
+ missing/unreachable main, stale/concurrent source, hook refusal, immutable lineage
535
+ and unexpected ignored output. Cross-date builds retain the original source epoch.
536
+ Local Chromium desktop/mobile searches and ordinary result clicks passed;
537
+ Escape returns focus to the opener and navigation closes. Dark OS preference
538
+ and stored slate remain light. Bulk fill/type event failures and the shared
539
+ outside-close focus gap remain disclosed; no WCAG or universal-repeatability
540
+ claim follows.
541
+
542
+ Product source/data, original licences, scripts, runtime locks, recovery pins
543
+ and Git refs/configuration remain unchanged. The later freeze found an isolated
544
+ index byte-guard exception; staged entries still match HEAD, with no cached
545
+ source changes. The cause is not proved. Preserve the current index and use
546
+ fresh delivery guards; no old index is restored. Source/generated
547
+ patches are local review candidates based on the current source epoch. Independent
548
+ review, actual main Actions, fresh-epoch generated delivery, installed/native
549
+ acceptance and private P/L remain separate. No product/native suite, owner
550
+ installation, commit, push or Pages operation was performed.
551
+
552
+
553
+ ## 2026-11-07 — Exact frontend notices and English search assets
554
+
555
+ Added exact upstream frontend notices and source-map provenance for the existing MaterialX 10.1.8 payload. Explicit English configuration and a small build hook reject language, corpus, reference, asset-set or hash drift before omitting the 35 unused language helpers. All nine retained core assets, original product legal files, guides, catalogue rows, media, runtime and dependency/build locks are preserved.
556
+
557
+ The strict site build and all 35 documentation tests pass. The complete new hook has 100% statement/branch coverage; real Git staging, checkout and archives preserve exact legal bytes. An independently installed matching lock reproduces all 48 output bytes and modes. Existing immutable source/output, epoch, concurrency and full-parity workflow checks remain active. Browser and independent review evidence are separate from these local checks.
558
+
559
+ Private Pages configuration, grants, requests and publication remain owner-held; this source follow-up adds none.
560
+ No product release or installation is claimed. Prior ordinary artifacts remain bound to their recorded revisions; a later Git revision changes genuine hatch-vcs metadata. Full current source archives include these documentation additions; no unchanged-sdist or whole-wheel identity is asserted. Native acceptance and owner installation remain separate.
561
+
562
+
563
+ ## 2026-11-07 — installed icon path-tuple inventory refinement
564
+
565
+ The current HTML/CSS contains 45 distinct ordered SVG path tuples. A complete scan of the four installed MaterialX icon families finds 43 exact installed matches and two unmatched Lucide tuples, refining the earlier known-candidate inventory. The additional installed match is the Font Awesome version caret-down. Its existing CSS header and full notice retain Font Awesome Free 7.1.0, Fonticons and CC-BY-4.0 icon attribution. The official NPM caret SVG has different raw path bytes; no unmodified-primary SVG, whole-geometry or optimizer-recipe equivalence is claimed. The two unmatched Lucide tuples retain their pinned SCSS source attribution.
566
+
567
+ A new actual-output regression derives these counts and checks installed matches, unmatched CSS references and the caret header. It fails against the prior 42 count and passes with the corrected metadata. All 36 current documentation tests pass; full strict and independent exact-lock builds match every output byte and mode. Only the legal paragraph, corresponding inventory and legal search row change in the site. Runtime, packaging, generators, vendor assets, full notices, existing guidance and the Fly search fix remain exact. Fresh browser verification and independent review are recorded separately. No private Pages operation, delivery, installed-product upgrade or native acceptance is claimed.