From bf1e16e1f3c433f2bbfcd5eb5124620201bd6a0c Mon Sep 17 00:00:00 2001 From: Sylvain Duchesne Date: Mon, 17 Aug 2026 10:53:05 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20un=20tag=20de=20d=C3=A9p=C3=B4t=20ne=20?= =?UTF-8?q?dit=20pas=20quel=20paquet=20il=20a=20fig=C3=A9?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .project/concepts/app-contract/_debt.md | 7 +++++++ .../polyfill-surface/contract_polyfill-surface.md | 2 ++ .../e2e-harness/ng-e2e-helpers/contract_ng-e2e-helpers.md | 2 ++ .project/concepts/sign-in/_debt.md | 8 ++++++++ 4 files changed, 19 insertions(+) create mode 100644 .project/concepts/app-contract/_debt.md create mode 100644 .project/concepts/sign-in/_debt.md diff --git a/.project/concepts/app-contract/_debt.md b/.project/concepts/app-contract/_debt.md new file mode 100644 index 0000000..b70383b --- /dev/null +++ b/.project/concepts/app-contract/_debt.md @@ -0,0 +1,7 @@ +# Doc-debt — app-contract + +> Presence of a block = doc to update. Processed → delete the block; no blocks left → delete this file. +> One block = one "big change": `why` + `files` + `verify` (leaves to review). + +## Raw markers (consolidate into blocks, then delete) +- TOUCHED packages/polyfill/src/surface/subscribe.ts @2026-08-17 (session f93872b5-293a-4916-a353-181409a96d42) diff --git a/.project/concepts/app-contract/polyfill-surface/contract_polyfill-surface.md b/.project/concepts/app-contract/polyfill-surface/contract_polyfill-surface.md index 389a02e..b20173c 100644 --- a/.project/concepts/app-contract/polyfill-surface/contract_polyfill-surface.md +++ b/.project/concepts/app-contract/polyfill-surface/contract_polyfill-surface.md @@ -173,6 +173,8 @@ What each level means here, in this package's own terms: **A tag says where it comes from.** A release cut on `main` carries a **full version** (`1.0.0`), and the three rules above govern what changes between two full versions. Work still on a branch carries a **pre-release** of the version it is heading for (`1.0.0-dev.3`), which sorts *below* that version by construction — so you can pin what exists today while the tag itself tells you the surface has not been released and may still move before it is. Between two pre-releases of the same version nothing is promised: re-pull and read this leaf again. When the branch lands, the full version appears alongside; the pre-release keeps resolving, so no reference you pinned is ever withdrawn from under you. +**Tags carry the package name**, because this repository publishes more than one engagement and their versions move independently: `polyfill/v1.0.0-dev.1` is this package, `ng-e2e-helpers/v…` is the other one. A bare `v…` tag would say nothing about which surface it froze the day the two diverge — which is the day one of them takes a major and the other does not. + `1.0.0` is a baseline, not a claim of maturity: it is the number that makes your pin mean something. Nothing was released before it, so none of the changes named above is a bump from anything — but the next release very likely is a major. What exists today is `1.0.0-dev.1`, on a branch: pin that string exactly, and anchor your `usage_` leaf's `against:` on it — `against: @ng-eventually/polyfill@1.0.0-dev.1`, the string you pinned, never the version it is heading for. There is no changelog file and no deprecation window: **the sections above are the release note.** A removal or a narrowing lands in `## Surface` and `## Guarantees` in the same version that ships it, and a symbol is never left published-but-dead as a courtesy. Diff this leaf between two pulls — `## Guarantees` and `## Non-guarantees` before `## Surface`, because that is where a narrowing shows up first. diff --git a/.project/concepts/e2e-harness/ng-e2e-helpers/contract_ng-e2e-helpers.md b/.project/concepts/e2e-harness/ng-e2e-helpers/contract_ng-e2e-helpers.md index 712a358..66a79b8 100644 --- a/.project/concepts/e2e-harness/ng-e2e-helpers/contract_ng-e2e-helpers.md +++ b/.project/concepts/e2e-harness/ng-e2e-helpers/contract_ng-e2e-helpers.md @@ -156,6 +156,8 @@ What each level means here, in this package's own terms: **A tag says where it comes from.** A release cut on `main` carries a **full version** (`1.0.0`), and the three rules above govern what changes between two full versions. Work still on a branch carries a **pre-release** of the version it is heading for (`1.0.0-dev.3`), which sorts *below* that version by construction — so you can pin what exists today while the tag itself tells you the surface has not been released and may still move before it is. Between two pre-releases of the same version nothing is promised: re-pull and read this leaf again. When the branch lands, the full version appears alongside; the pre-release keeps resolving, so no reference you pinned is ever withdrawn from under you. +**Tags carry the package name**, because this repository publishes more than one engagement and their versions move independently: `ng-e2e-helpers/v1.0.0-dev.1` is this package, `polyfill/v…` is the other one. A bare `v…` tag would say nothing about which surface it froze the day the two diverge — which is the day one of them takes a major and the other does not. + `1.0.0` is a baseline, not a claim of maturity: it is the number that makes your pin mean something. Nothing was released before it. What exists today is `1.0.0-dev.1`, on a branch: pin that string exactly, and anchor your `usage_` leaf's `against:` on it — `against: ng-e2e-helpers@1.0.0-dev.1`, the string you pinned, never the version it is heading for. There is no changelog file and no deprecation window: **the sections above are the release note.** A removal or a narrowing lands in `## Surface` and `## Guarantees` in the same version that ships it. Diff this leaf between two pulls — `## Guarantees` and `## Non-guarantees` before `## Surface`, because that is where a narrowing shows up first. diff --git a/.project/concepts/sign-in/_debt.md b/.project/concepts/sign-in/_debt.md new file mode 100644 index 0000000..92e6405 --- /dev/null +++ b/.project/concepts/sign-in/_debt.md @@ -0,0 +1,8 @@ +# Doc-debt — sign-in + +> Presence of a block = doc to update. Processed → delete the block; no blocks left → delete this file. +> One block = one "big change": `why` + `files` + `verify` (leaves to review). + +## Raw markers (consolidate into blocks, then delete) +- TOUCHED packages/polyfill/src/emulated-verifier/connect.ts @2026-08-17 (session f93872b5-293a-4916-a353-181409a96d42) +- TOUCHED packages/polyfill/src/shared-wallet/bootstrap.ts @2026-08-17 (session f93872b5-293a-4916-a353-181409a96d42)