@sjawhar/pi-legion-envoy 5.16.0 → 5.16.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/legion.js +1 -1
- package/dist/skills/dispatch/SKILL.md +6 -0
- package/package.json +1 -1
package/dist/legion.js
CHANGED
|
@@ -33415,7 +33415,7 @@ import { logger } from "@oh-my-pi/pi-utils";
|
|
|
33415
33415
|
// package.json
|
|
33416
33416
|
var package_default = {
|
|
33417
33417
|
name: "@sjawhar/pi-legion-envoy",
|
|
33418
|
-
version: "5.16.
|
|
33418
|
+
version: "5.16.1",
|
|
33419
33419
|
type: "module",
|
|
33420
33420
|
omp: {
|
|
33421
33421
|
extensions: [
|
|
@@ -312,6 +312,12 @@ and is not re-staffed. A todo with a finished spec reads as queued work that nob
|
|
|
312
312
|
(LEGION-173 sat in todo for two weeks with a complete spec; AGENTC-1010's v4 plan sat in backlog
|
|
313
313
|
with nobody building it).
|
|
314
314
|
|
|
315
|
+
A close that says the defect cannot happen cites the code that makes it impossible. An issue
|
|
316
|
+
closed because a rewrite forecloses it names the file and line in the rewrite that does so; a
|
|
317
|
+
close that cannot name one is not foreclosed, it is unread. The cheapest way for a rewrite to reach
|
|
318
|
+
parity is to port the code, defect included: LEGION-211's bare `git worktree prune`, filed against
|
|
319
|
+
the TypeScript daemon, had been ported into the Go coordinator and was live in production.
|
|
320
|
+
|
|
315
321
|
The audit finds four shapes:
|
|
316
322
|
|
|
317
323
|
- **Unstaffed work.** A plan or measurement exists, and no one is building it.
|