Recordsnpmexternal-editorfailure issue
Failure signature
UNKNOWN exit 13 Evidence gap ×1
Warning: Detected unsettled top-level await at <url>]:<n> · const ans = await promptPromise; · ^ · fil<path>:<n>
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-09-16 · Last seen: 2026-09-16
sha256:4a939d00eec4…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 3.1.0 FAIL
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-09-16 → 2026-09-16
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- external-editor 3.1.0: edit, editAsync, ExternalEditor This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWexternal-editorexternal-editor.editexternal-editor.editAsyncexternal-editor.ExternalEditornode 22.23.2 MIT-0 · 2026-09-16