discovery-media-player 0.1.134 → 0.1.135

package/README.md

@@ -127,8 +127,8 @@ forking it. A fix lands once and reaches every instance on its next deploy.
 It reads `req.query` when the platform provides it (serverless, Express) and falls back to parsing
 `req.url` when it does not — so a bare `http.createServer` works too, without a shim.
 
-See [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) for the boundary, and
-[`docs/API.md`](docs/API.md) for the surface an integrator implements.
+See [`docs/ARCHITECTURE.md`](https://github.com/Juli1artha/discovery-media-player/blob/main/docs/ARCHITECTURE.md) for the boundary, and
+[`docs/API.md`](https://github.com/Juli1artha/discovery-media-player/blob/main/docs/API.md) for the surface an integrator implements.
 
 ---
 
@@ -152,8 +152,8 @@ Minimum configuration:
 | `PLAYER_BRAND_NAME`, `PLAYER_LOADER_NAME` | your name in the tab title and the loader |
 | `PLAYER_SOURCE_URL` | where readers can obtain the source (AGPL, see below) |
 
-Full list: [`docs/CONFIGURATION.md`](docs/CONFIGURATION.md).
-Examples you can copy: [`examples/`](examples/).
+Full list: [`docs/CONFIGURATION.md`](https://github.com/Juli1artha/discovery-media-player/blob/main/docs/CONFIGURATION.md).
+Examples you can copy: [`examples/`](https://github.com/Juli1artha/discovery-media-player/tree/main/examples).
 
 ---
 
@@ -166,10 +166,10 @@ your private network.
 
 The project has been through repeated external audits. The reports are published in the
 repository, unedited, with their follow-up ledgers — findings, fixes, and what was rejected
-with its reason: see [`docs/`](docs/README.md). Fixes are traced version by version in the
-[CHANGELOG](CHANGELOG.md).
+with its reason: see [`docs/`](https://github.com/Juli1artha/discovery-media-player/blob/main/docs/README.md). Fixes are traced version by version in the
+[CHANGELOG](https://github.com/Juli1artha/discovery-media-player/blob/main/CHANGELOG.md).
 
-Found a hole? [`SECURITY.md`](SECURITY.md) — please do not open a public issue.
+Found a hole? [`SECURITY.md`](https://github.com/Juli1artha/discovery-media-player/blob/main/SECURITY.md) — please do not open a public issue.
 
 ---
 
@@ -185,7 +185,7 @@ Player* are trademarks of 3D Discovery: fork the code freely, but call your fork
 This is the usual arrangement in open source, and it protects you as much as us — nobody should
 be able to publish something under this name that we did not write.
 
-One exception, on purpose: **[`src/bridge.ts`](src/bridge.ts) is MIT**
+One exception, on purpose: **[`src/bridge.ts`](https://github.com/Juli1artha/discovery-media-player/blob/main/src/bridge.ts) is MIT**
 ([`LICENSE-MIT`](LICENSE-MIT)). It is the message contract a host application imports to talk to
 the player. Putting it under the core licence would make integration itself a toll. We protect
 the player, not the people plugging into it.
@@ -194,10 +194,10 @@ the player, not the people plugging into it.
 
 ## Contributing
 
-[`CONTRIBUTING.md`](CONTRIBUTING.md) — how to run the tests, what the review looks for, and the
+[`CONTRIBUTING.md`](https://github.com/Juli1artha/discovery-media-player/blob/main/CONTRIBUTING.md) — how to run the tests, what the review looks for, and the
 one rule that matters: a behaviour worth keeping is worth a test that fails without it.
 
-Your first pull request asks you to sign the [CLA](CLA.md) — one reply, once, for good. You keep
+Your first pull request asks you to sign the [CLA](https://github.com/Juli1artha/discovery-media-player/blob/main/CLA.md) — one reply, once, for good. You keep
 the copyright in your work; you grant a licence that may be sublicensed, so that the core can stay
 AGPL while a commercial licence remains possible for organisations that cannot live with the
 network clause. Better said before you write the patch than after.

package/docs/HOST-CONTRACT.md

@@ -6,7 +6,7 @@
 > `node_modules` paths by hand is a guess about our tree, and it broke twice in one day.
 
 What a host application may call, what it must implement, and what will not change without a
-version bump. If you are integrating the player, this page and [`API.md`](API.md) are the two you
+version bump. If you are integrating the player, this page and [`API.md`](https://github.com/Juli1artha/discovery-media-player/blob/main/docs/API.md) are the two you
 need.
 
 ## Five rules
@@ -362,7 +362,7 @@ Four requirements, in order of what they cost when missed:
 
 ## The postMessage bridge
 
-Described once in [`src/bridge.ts`](../src/bridge.ts) and published as `discovery-media-player/bridge`
+Described once in [`src/bridge.ts`](https://github.com/Juli1artha/discovery-media-player/blob/main/src/bridge.ts) and published as `discovery-media-player/bridge`
 — **compiled JavaScript with type declarations, under MIT** rather than the core's AGPL, so that
 importing it is not a toll. Import it rather than copying constants: a message name retyped by hand
 is a contract in two copies, and the day it changes only one of them knows.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "discovery-media-player",
-  "version": "0.1.134",
+  "version": "0.1.135",
   "description": "Self-hosted document viewer: per-recipient tracked links, reading analytics, live presentation. The core knows nothing about the application hosting it — everything it borrows arrives through an injected context.",
   "keywords": [
     "pdf-viewer",
@@ -33,7 +33,6 @@
     "server",
     "supabase",
     "types",
-    "README.md",
     "LICENSE",
     "LICENSE-MIT",
     "docs/HOST-CONTRACT.md",

package/docs/README.md

@@ -1,56 +0,0 @@
-# Documentation
-
-Three readers, one section each. Start with the one that matches what you are trying to do —
-no document assumes you have read the others.
-
-## You are integrating the player into an application
-
-| Document | What it gives you |
-|---|---|
-| [`ARCHITECTURE.md`](ARCHITECTURE.md) | The one idea that holds the design: the core knows nothing about its host. Read this first. |
-| [`API.md`](API.md) | What a host can call, and what it must implement. |
-| [`HOST-CONTRACT.md`](HOST-CONTRACT.md) | The binding contract, with the dated journal of every boundary change. It ships **inside the package**: `require.resolve("discovery-media-player/contrat")`. |
-
-## You are running an instance
-
-| Document | What it gives you |
-|---|---|
-| [`CONFIGURATION.md`](CONFIGURATION.md) | Every environment variable. An instance is described entirely by its environment — there is no configuration file, on purpose. |
-| [`MIGRATIONS.md`](MIGRATIONS.md) | What happens to a database **already in service** when the player expects a newer schema. (French.) |
-| [`VERIFYING-RELEASES.md`](VERIFYING-RELEASES.md) | how to check, yourself, that the package or image you pulled is the one this repository built — the commands, the expected output, and which signing identity to expect. |
-| [`RETENTION.md`](RETENTION.md) | The declared perimeter of data retention: every personal-data column has a written policy, and CI enforces that the list is complete. Also an export of the package: `require.resolve("discovery-media-player/retention")`. |
-
-## You are contributing, or publishing a version
-
-| Document | What it gives you |
-|---|---|
-| [`../CONTRIBUTING.md`](../CONTRIBUTING.md) | how to run the benches, what review looks for, and the one rule: a behaviour worth keeping is worth a test that fails without it. |
-| [`../AGENTS.md`](../AGENTS.md) | the conventions that are not obvious from the file tree — which ones a guard enforces, and which ones only review does. |
-| [`RELEASING.md`](RELEASING.md) | the release train, freezing the candidate SHA, the read-only preflight to run **before** the tag, and what to do when a tag lands on the wrong commit. |
-| [`DEPENDENCIES.md`](DEPENDENCIES.md) | what the project depends on and why so little of it: the bar a new dependency has to clear, how updates arrive, the two upgrades deliberately held back, and the vulnerability thresholds a change has to clear to merge. |
-| [`SECURITY-PRACTICES.md`](SECURITY-PRACTICES.md) | the two standing policies: how secrets are handled (there are no long-lived ones, on purpose) and what happens when a security tool reports something. |
-| [`../MAINTAINERS.md`](../MAINTAINERS.md) | who can merge, who can publish, who reads a vulnerability report — and what one maintainer means for the answer. |
-
-## You are evaluating the project
-
-The external audit trail is public, unedited, and kept in the state it was received —
-an audit rewritten after the fact is no longer a trace. Findings and their fixes are
-tracked version by version in the [CHANGELOG](../CHANGELOG.md).
-
-| Document | What it is |
-|---|---|
-| [`THREAT-MODEL.md`](THREAT-MODEL.md) | what an attacker would go after, what stands in the way, and — the part most threat models omit — what is deliberately left standing. |
-| [`AUDIT-2026-08-14-RAPPORT.md`](AUDIT-2026-08-14-RAPPORT.md) | First external audit, on `0.1.17`. Historical. (French.) |
-| [`AUDIT-2026-08-14-SUIVI.md`](AUDIT-2026-08-14-SUIVI.md) | The follow-up ledger: done, decided-but-not-done, and rejected-with-reason. Historical. (French.) |
-| [`AUDIT-2026-08-15-SECONDE-PASSE.md`](AUDIT-2026-08-15-SECONDE-PASSE.md) | Second pass, on `0.1.26` — including what the first follow-up had marked too optimistically. Historical. (French.) |
-
-## Work in progress
-
-| Document | What it is |
-|---|---|
-| [`SPEC-MEMBRE-INJECTE.md`](SPEC-MEMBRE-INJECTE.md) | A specification sent to a host for agreement **before** the contract moves. Nothing in it is implemented. (French.) |
-
-Public entry points are in English. Documents that remain in French — audit traces, and the
-operational documents marked *(French)* above — are labelled explicitly, so nobody discovers
-the language after clicking. The reasoning behind the split is at the end of the
-[README](../README.md#contributing).