diff-patch-worker.js · part 1
Full reference4 text occurrences from agent-cli/package/diff-patch-worker.js, part 1. Every entry preserves the shipped literal and its saved verdict or selection reason.
File contents and all parts · All files
Shipped text
use strict
Source: agent-cli/package/diff-patch-worker.js, bytes 6–18, SHA-256 4ee188e1744c1981.
Jev judged not model-facing (confidence 0.06; role code_data). This is a classifier judgment, not proof of delivery.
Readable text: use strict
use strict
newlineIsToken may not be used with patch-generation functions, only with diffin
Source: agent-cli/package/diff-patch-worker.js, bytes 4037–4130, SHA-256 8a2675c86852d456.
Jev judged not model-facing (confidence 0.09; role code_data). This is a classifier judgment, not proof of delivery.
Readable text: newlineIsToken may not be used with patch-generation functions, only with diffing functions
newlineIsToken may not be used with patch-generation functions, only with diffing functions
No newline at end of file
Source: agent-cli/package/diff-patch-worker.js, bytes 5067–5097, SHA-256 29d81d614c59537a.
Jev judged not model-facing (confidence 0.04; role code_data). This is a classifier judgment, not proof of delivery.
Readable text: \ No newline at end of file
\ No newline at end of file
Cannot omit file headers on a multi-file patch. (The result would be unparseable
Source: agent-cli/package/diff-patch-worker.js, bytes 5272–5437, SHA-256 5d59938800e076b7.
Jev judged not model-facing (confidence 0.08; role code_data). This is a classifier judgment, not proof of delivery.
Readable text: Cannot omit file headers on a multi-file patch. (The result would be unparseable; how would a tool trying to apply the patch know which changes are to which file?)
Cannot omit file headers on a multi-file patch. (The result would be unparseable; how would a tool trying to apply the patch know which changes are to which file?)