voidmachine 7.0.1 → 7.0.2

package/core-assets/skills/void-autopilot/SKILL.md

@@ -339,7 +339,10 @@ its proofs and returns its commit for coordinator publication; `semantic` -- two
 sends the ticket to a human. A worker never picks a side of a semantic conflict to keep the loop
 moving.
 
-**Serial fallback.** Without a merge queue, merges run one at a time: the oldest ready pull request
+**Serial fallback.** This path requires no queue service or paid plan.
+For CI optimization, use [void-verify CI feedback](../void-verify/references/ci-feedback.md);
+add neither a second scheduler nor a mandatory duration gate.
+Without a merge queue, merges run one at a time: the oldest ready pull request
 (or the one already merging) holds the turn. The kernel reads whether the base moved past its head
 itself, since GitHub reports it only under a protection that requires it: a head behind gets
 `update-branch`, its new head is reviewed again, then merged, then the next. `merge` reads it once

package/core-assets/skills/void-merge/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: void-merge
-description: Vider la file des PR ouvertes sans casser le dépôt. Ordre par déblocage plutôt que par date, CI verte ET à jour, artefacts générés régénérés, conflits de contenu rendus à leur auteur. Use when merging pull requests.
+description: Vider la file des PR ouvertes sans casser le dépôt. Fusions séquentielles, ordre stable et dépendances explicites, CI verte ET à jour, artefacts générés régénérés, conflits de contenu rendus à leur auteur. Use when merging pull requests.
 ---
 
 # merge — voidcorp craftsman edition
 
 `void-implement` s'arrête à la PR ouverte. `void-autopilot` laisse à une personne les PR qu'il ne peut
-pas armer. Personne ne dit comment vider la file. Ce geste a l'air trivial jusqu'au moment où il ne l'est pas.
+pas fusionner dans son mandat. Personne ne dit comment vider la file. Ce geste a l'air trivial jusqu'au moment où il ne l'est pas.
 
 **Attribution**: see `.source`.
 
@@ -36,19 +36,26 @@ Sortent de la file, sans discussion :
 
 Une file vide est un résultat, pas un échec : le dire et s'arrêter.
 
-## Étape 2 — Ordonner par déblocage, jamais par date
-
-L'ordre correct n'a aucun rapport avec le numéro ni l'ancienneté.
-
-1. **Une PR dont le contenu supprime la cause du conflit d'une autre passe avant elle.** Le cas
-   qui a motivé cette skill : la PR réparant le workflow de back-merge était en conflit
-   précisément parce que ce back-merge n'avait jamais tourné. Sans le back-merge d'abord, elle
-   restait bloquée pour toujours.
-2. À défaut de relation, **le moindre conflit d'abord** : ce qui se merge sans rien toucher, puis
-   ce qui demande une régénération.
-
-Chercher la relation explicitement : une PR en conflit avec la base, dont une autre PR ouverte (ou
-un geste manquant) explique le conflit, attend cette autre.
+## Étape 2 — Garder un ordre stable, identifier les dépendances
+
+Une seule fusion à la fois suffit, sans service de file ni abonnement particulier.
+Une file native déjà configurée reste compatible ; ses protections restent applicables.
+
+1. **Conserver le tour engagé.** Dans `void-autopilot`, le noyau choisit : une PR dont la
+   fusion est déjà armée garde son tour ; sinon, la plus ancienne PR ouverte non brouillon
+   parmi les tickets suivis passe d'abord. Utiliser ses actions, pas un script de fusion parallèle.
+2. **Hors autopilot, garder l'ordre des PR admissibles.** À défaut d'ordre explicite, partir
+   de la plus ancienne. Une PR dont la revue est acquise et dont seule la CI attendue tourne
+   conserve son tour ; une PR plus récente ne la dépasse pas simplement parce qu'elle est verte.
+3. **Un déblocage réel se traite explicitement.** Nommer la dépendance, le conflit ou le
+   blocage durable et son propriétaire. Hors autopilot, une PR préalable peut passer d'abord
+   avec cette raison. Sous autopilot, rendre ce blocage au coordinateur : ne pas contourner
+   le tour choisi par le noyau. Une PR rouge ou en conflit ne justifie pas une attente indéfinie.
+
+Remettre à jour seulement la PR dont le tour arrive, puis attendre ses preuves avant de
+fusionner. Ne pas remettre toutes les branches à jour après chaque fusion : la suivante
+ferait immédiatement vieillir ce travail. Le temps déjà dépensé ne rend jamais valide
+une preuve liée à un ancien commit ou à une ancienne base.
 
 ## Étape 3 — Trois conditions pour merger, toutes nécessaires
 

package/core-assets/skills/void-verify/references/ci-feedback.md

@@ -40,15 +40,16 @@ concurrency keys: `cancel-in-progress: false` alone still replaces pending runs
 shared group. Keep integration checks before entry to the protected branch; checking
 only after merge permits broken integration.
 
-GitHub couples required PR and merge queue checks. Preserve both. Remove a redundant
-post-merge run only after checking that no release, promotion or artifact consumer
+Where a repository already uses a merge queue, preserve both its required PR and
+merge-group checks. A queue is optional; sequential merging needs no queue setup.
+Remove a redundant post-merge run only after checking that no release, promotion or artifact consumer
 needs it, and that the protected integration path proves the merged result. The
 example has no push trigger; add one where it provides distinct release evidence.
 
-For reusable enforcement, the caller must also declare `ready_for_review`,
-`converted_to_draft` and `merge_group: checks_requested`, keeping its existing
-check names. Put concurrency only in that caller; the called workflow inherits
-`github.workflow` and must not cancel the same group. Its admission guard runs
+For reusable enforcement, the caller must also declare `ready_for_review` and
+`converted_to_draft`, keeping its existing check names. Preserve
+`merge_group: checks_requested` where a queue is configured. Put concurrency only
+in that caller; the called workflow inherits `github.workflow` and must not cancel the same group. Its admission guard runs
 from the immutable harness checkout before Node setup and floor execution.
 GitHub-hosted runner usage belongs to the caller, even when the reusable workflow
 is public and the caller private. Compare latency and job-minutes before making
@@ -71,6 +72,41 @@ Rollback: restore the prior workflow triggers and admission step together. Resto
 full draft CI costs runner time but does not weaken the floor. Leave protection and
 review evidence unchanged. Existing missions and receipts are not migrated.
 
+## Measure feedback before changing CI
+
+On a CI optimization request, use existing run history to agree a project-specific
+feedback target, separately for ordinary changes and documentation changes. Around ten
+minutes for a complete PR and a few minutes for documentation can start the discussion;
+they are advisory targets, not timeouts, required checks or permission to omit tests.
+Report the sample size, median and p95 when the sample supports it. A missed target
+calls for diagnosis of the critical path, not a retry or another reporting service.
+
+Record separately: time waiting for execution, elapsed time until all required results
+are available, and summed job execution minutes across parallel jobs and all attempts.
+Include cancelled work and runs invalidated by branch updates. A later PR overtaking an
+older one only wastes CI when that change actually invalidates work; do not assume a
+saving from ordering alone. Use provider billing data for money: job-minutes are not
+billed minutes. Missing runner-wait timestamps mean unknown, not zero; dependency waits
+are not automatically runner waits. A run update timestamp is not its completion time.
+
+For GitHub, inspect a concrete run and repeat for earlier attempts when present:
+
+```sh
+gh run view RUN_ID --repo OWNER/REPO --attempt ATTEMPT --json attempt,event,headSha,createdAt,startedAt,jobs
+```
+
+Job start/completion times describe execution intervals; inspect the workflow dependencies
+and every required workflow before deriving the feedback delay. Another CI provider's
+native run/job view supplies the same evidence; this is no GitHub prerequisite.
+
+Investigate a full build/test cache miss on a documentation-only diff by tracing actual
+inputs and cache keys. Markdown may feed generated assets, executable skills or contract
+tests; the extension alone proves nothing. Optimize unaffected work only when dependencies
+are proven; otherwise keep the complete suite above. Preserve exact-candidate checks,
+release artifacts and integration evidence. Reuse local evidence with unchanged inputs
+instead of asking every agent to repeat the same full suite. Adopt workflow changes in
+the consumer's existing configuration; updating these references does not rewrite it.
+
 Sources read for GitHub Actions (hosted service):
 - https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request
 - https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency
@@ -78,3 +114,6 @@ Sources read for GitHub Actions (hosted service):
 - https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-jobs-with-conditions
 
 - https://docs.github.com/en/actions/reference/workflows-and-actions/reusing-workflow-configurations
+
+- https://cli.github.com/manual/gh_run_view
+- https://docs.github.com/en/rest/actions/workflow-jobs