Reconnexion/ng-eventually
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: T01.i est close, et la doc perimee d-open-repo passe a T01.j

Browse Source
This commit is contained in:
Sylvain Duchesne
2026-09-21 14:45:14 +02:00
parent 6c1d281755
commit 5cbcabecf2
2 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.tasks/todo/T01.j-a-failure-must-not-read-as-an-absence.md
+4
View File
@@ -43,6 +43,10 @@ Reads that silently answered empty will start failing. That is the POINT, and it
**Record the durable fact** in `.project/concepts/app-contract/` as a `knowledge_` leaf: what the target answers for an unreachable, an unsynced and an empty document, and which of those a caller can tell apart. That fact is worth keeping whatever the fix turns out to be. Do NOT open a `bug_` leaf for something this task repairs.
### One incidental repair, since you are in this territory anyway
`docs/internal-contract.md`'s `open-repo.ts` section is stale: wrong line numbers, it names a non-existent `ensurePhysicalRepoOpen` export, and since T01.i it also names the deleted `ensureReposOpen`. Correct what that section says about the functions you touch. Do NOT undertake a general sweep of that document - the drift is broad and pre-existing, and fixing all of it is not this task.
### Verification
**The e2e must run.** Unit tests cannot judge this: the whole subject is what happens when the network does not answer. Run the polyfill e2e suite and report its counts verbatim. If the broker is unreachable, report the suite as UNRUN - never substitute a typecheck for the measurement.