caoer115/ucc
1
0
Fork 0
Code Issues Pull requests 45 Projects Releases Packages Wiki Activity

rounds: K3-pi-kind belongs to stage --pi-plugin — a stage with no pi plugin leaves the row not counted, named #39

Open
caoer115 wants to merge 0 commits from agent/e71449d2-k3-pi-stage into main
pull from: agent/e71449d2-k3-pi-stage
merge into: caoer115:main
Conversation 0 Commits - Files changed -
caoer115 commented 2026-10-17 02:29:33 +00:00
Owner
Copy link

Ruling (p), leader 3635f01e: K3-pi-kind failed on any stage without pi-plugin/ (67-native.sh at main adf501e), so every --public lane round on v3's stage tb237 (585c915d) blocked.

The #34 --legacy-prev pattern:

  • build-tarball.sh: PINS pi_plugin_sha256 is absent when the stage's ccc-statusd has no pi-plugin-ccc-statusd/ (already so; a comment line now says what reads it).
  • run.sh: stages= carries --pi-plugin only when PINS pins a sha (not absent, not unset).
  • manifest: K3-pi-kind pi stage: --pi-plugin; the header names the token.
  • 67-native.sh: a stage with no plugin (absent or unset) scores n with the reason; a stage that pins the plugin and lacks its file fails, and a pi run failure there fails as before.
  • score.py: docstring names the token; no logic change (a fail blocks whatever the marker).

Checks (scratch harness, worktree at 2713e2e): bash -n on the three scripts; the stages= line over PINS sha / absent / unset / missing file (--pi-plugin only for the sha; a missing PINS does not end run.sh under set -e); the 67-native.sh branch over the four stage shapes (sha → k3_pi runs, sha without dist/index.mjs → fail, absent and unset → n); score.py: no plugin + n → GATE pass, the row named under Not counted; no plugin + fail → block; plugin + fail or n → block; plugin + pass → pass.

Ruling (p), leader 3635f01e: K3-pi-kind failed on any stage without pi-plugin/ (67-native.sh at main adf501e), so every --public lane round on v3's stage tb237 (585c915d) blocked. The #34 --legacy-prev pattern: - build-tarball.sh: PINS pi_plugin_sha256 is `absent` when the stage's ccc-statusd has no pi-plugin-ccc-statusd/ (already so; a comment line now says what reads it). - run.sh: stages= carries `--pi-plugin` only when PINS pins a sha (not absent, not unset). - manifest: `K3-pi-kind pi stage: --pi-plugin`; the header names the token. - 67-native.sh: a stage with no plugin (absent or unset) scores n with the reason; a stage that pins the plugin and lacks its file fails, and a pi run failure there fails as before. - score.py: docstring names the token; no logic change (a fail blocks whatever the marker). Checks (scratch harness, worktree at 2713e2e): bash -n on the three scripts; the stages= line over PINS sha / absent / unset / missing file (`--pi-plugin` only for the sha; a missing PINS does not end run.sh under set -e); the 67-native.sh branch over the four stage shapes (sha → k3_pi runs, sha without dist/index.mjs → fail, absent and unset → n); score.py: no plugin + n → GATE pass, the row named under Not counted; no plugin + fail → block; plugin + fail or n → block; plugin + pass → pass.
v3's stage (585c915d) has no pi-plugin-ccc-statusd/, so 67-native.sh scored K3-pi-kind fail and every
--public lane round on it blocked. The #34 pattern: build-tarball.sh's PINS pi_plugin_sha256 (absent when
the stage's ccc-statusd has no plugin) decides; run.sh writes --pi-plugin into stages= only for a stage
that pins a sha; the manifest row carries stage: --pi-plugin; 67-native.sh scores n with the reason on a
stage with none (absent or unset). A stage that pins the plugin and lacks its file, or whose pi run fails,
still fails, and score.py blocks a fail whatever the marker.

Leader 3635f01e, ruling (p).
585c915d's ccc-statusd has the plugin; tb237 lacks it because build-tarball.sh learned to build it in
f53d0e4, after that stage was built. Leader c005a18f's text fix on PR #39.
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin agent/e71449d2-k3-pi-stage:agent/e71449d2-k3-pi-stage
git switch agent/e71449d2-k3-pi-stage

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff agent/e71449d2-k3-pi-stage
git switch agent/e71449d2-k3-pi-stage
git rebase main
git switch main
git merge --ff-only agent/e71449d2-k3-pi-stage
git switch agent/e71449d2-k3-pi-stage
git rebase main
git switch main
git merge --no-ff agent/e71449d2-k3-pi-stage
git switch main
git merge --squash agent/e71449d2-k3-pi-stage
git switch main
git merge --ff-only agent/e71449d2-k3-pi-stage
git switch main
git merge agent/e71449d2-k3-pi-stage
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
caoer115/ucc!39
No description provided.