[aitrawog]

Summary

The authoritative diff of this PR, read from the GitHub API, is 1 file(s), +9 / -10:

    charly.yml

Removed lines (10):

    Rootless boxes like `/charly-openclaw:openclaw-desktop` don't add a
    openclaw-desktop:
    - openclaw-full
    charly-fedora:
    # Rootless posture on openclaw-desktop
    charly box inspect openclaw-desktop | jq '.HostConfig? // .Config.Labels."ai.opencharly.security"'
    charly shell openclaw-desktop -c 'podman run --rm quay.io/libpod/alpine:latest true'
    charly shell openclaw-desktop -c '
    - `/charly-openclaw:openclaw-desktop` — rootless path; box-level adds nothing
    - Evaluating the security posture of `/charly-openclaw:openclaw-desktop`, `/charly-distros:charly-fedora`, `/charly-coder:charly-arch`, or `/charly-distros:githubrunner`.

Added lines (8):

    A rootless box that composes this candy adds no
    my-rootless-box:
    my-root-box:
    # Rootless posture on the box
    charly box inspect my-rootless-box | jq '.HostConfig? // .Config.Labels."ai.opencharly.security"'
    charly shell my-rootless-box -c 'podman run --rm quay.io/libpod/alpine:latest true'
    charly shell my-rootless-box -c '
    - Evaluating the security posture of `/charly-distros:charly-fedora`, `/charly-coder:charly-arch`, or `/charly-distros:githubrunner`.

The removed references named /charly-openclaw:openclaw-desktop, deleted by the OpenClaw family cutover (opencharly/opencharly#431).

They are de-named, not substituted. An earlier revision on this branch replaced the retired box with charly-fedora throughout, which contradicted this very document — it lists charly-fedora among the images wanting the full-hammer posture and calls it a full-range entry for root (lines 129, 538, 675), so the rootless examples became self-contradictory, and one Related entry was duplicated. The examples now use neutral placeholders (my-rootless-box / my-root-box) so the pattern is taught without asserting a posture for a box this document describes differently.

How tested

The changed file is a candy manifest, so the gate is the owning manifest gate, pasted from this tree:

$ charly -C <repo> box validate
charly box validate: OK — checked 1 candy, 7 distros, 7 builders; 0 warnings, 0 errors

$ gh api repos/opencharly/layer-container-nesting/pulls/10/files --jq '.[] | "\(.filename) +\(.additions) -\(.deletions)"'
charly.yml +9 -10

0 warnings and 0 errors. No behavioral field moves: no package section, service, plan step, pin, or generated artifact.

Scope note — what this PR does not claim

This PR changes only the lines shown above. It does not claim a live box is the retired box's equivalent — the point of the fix is that no live box is asserted to be one.

Remaining surfaces are carried by open PRs, each named: opencharly/marketplace#434 (retired refs-list entries + the pre-M4 distro-cachyos pin), opencharly/marketplace#435 (stale pins), layer-container-nesting#9, and opencharly/opencharly#443 (the umbrella import). The owning cutover, opencharly/opencharly#431, is open.

Rulebook compliance

• R0 - skills first: /charly-internals:git-workflow, /charly-image:layer.
• R1 - the contradiction and the duplication are named, with their cause (my own over-broad substitution), and corrected in the file rather than reworded in the body.
• R2 - not a split. Every remaining surface is named with its open carrier PR.
• R3 - the duplicated Related entry is de-duplicated, proven by the removed/added lines above.
• R4 - no workaround: no comment-out, no TODO, no alias.
• R5 - the retired reference is gone from the changed file (0 occurrences), proven by the diff above.
• R6 - user work preserved and Git safety kept: a feat/ branch off a just-fetched origin/main in a session-owned clone; no force-push, no hook bypass, no direct push to main.
• R7 - behaviour, not compilation: prose only, no behavioral field moved, and the manifest gate ran live on this tree with output pasted.
• R8 - the artifact at this boundary is the manifest itself, validated where it is consumed.
• R9 - the CalVer-stamped worktree binary was used.
• R10 - the manifest gate passed with 0 warnings / 0 errors on the final tree; no runtime target changes.

Change classification

Documentation — prose-only lines changed inside a candy manifest. No behavioral field moved. The diff is human-readable guidance only.

Tier: documentation reviewed.

Agent: openclaw-family
Assisted-by: DSH DeepSeek deepseek-v4.1-flash (documentation reviewed)

[github-actions]

Review — BLOCK

Head SHA: 529581723426417f70c790ded97c9cdbc6f6abce (branch: feat/drop-retired-openclaw-refs-v2)

Change class: candy-manifest skill prose (docs-in-manifest), not runtime code.

Security screen: PASS — prose-only diff; no secrets, no code, no guardrail/rulebook weakening, no supply-chain change. T4 N/A (not security machinery).

Blocks

1. R3 / factual defect — duplicated entity in the "Evaluating the security posture" line (charly.yml ~854). The retired /charly-openclaw:openclaw-desktop was substituted rather than deleted, producing /charly-distros:charly-fedora, /charly-distros:charly-fedora, ... twice. The line already listed charly-fedora; the correct fix is to delete the openclaw-desktop entry, not replace it. This also falsifies the body's R3 claim ("nothing duplicated: the reference is removed, not restated").

2. R1/R5 / B9 — false statement introduced: charly-fedora is a ROOT box, not rootless (charly.yml ~688). The diff changes Rootless boxes like \/charly-openclaw:openclaw-desktop` don't add a box-level `security:` blockto name/charly-distros:charly-fedora. The SAME file's "Used In Boxes" list states /charly-distros:charly-fedorais a **root** path that addscap_add:[ALL] + security_opt:[label=disable, seccomp=unconfined]`. The substitution therefore makes the skill contradict itself. A doc edit must not assert something the file itself refutes; the swap is not faithful (rootless → root).

3. Same contradiction propagated into the example and verification (charly.yml ~700–710, ~738–750). The illustrative charly.yml snippet now names charly-fedora: with a candy set (selkies-desktop, ollama, charly, container-nesting) that is not charly-fedora's real composition, and the verification block is relabelled # Rootless posture on charly-fedora with charly box inspect charly-fedora. This repeats the rootless/root error and presents a live box's composition and posture incorrectly. Fix the behaviour/prose to match reality (name a genuinely rootless box, or restate the example accurately) before the retired name is dropped.

4. A1 — body does not account for the change / contradicts the diff. The Summary lists only the 9 deleted lines and states "only retired references go," but the diff contains 8 insertions that rewrite live-entity references and introduce the incorrect charly-fedora claims above. The body's accounting omits the substitutions and its "live references are kept / nothing duplicated" claims are contradicted by the diff. Update the body to describe what actually changed.

5. A3 — tier inflated. The diff is skill prose with no behavioural field moved and no code path executed; the only gate is charly box validate (structure). fully tested and validated requires the cutover's changed code paths to have EXECUTED against a fresh rebuild — there is nothing executable here. The honest tier for an all-prose diff is documentation reviewed.

Comment thread: 0 comments — nothing to disposition.

Verdict: BLOCK

---

ollama-cloud/deepseek-v4.1-flash — action-review.

View action run

[github-actions]

Review — BLOCK

Head SHA: 529581723426417f70c790ded97c9cdbc6f6abce (branch: feat/drop-retired-openclaw-refs-v2)

Change class: docs-only — skill prose inside a candy manifest (charly.yml), no behavioral field moved.

Security screen: PASS — prose-only diff; no secrets, no code, no guardrail/rulebook weakening, no supply-chain change. T4 N/A.

Comment thread disposition (1 comment, by @github-actions[bot]): all five findings re-derived against the CURRENT diff and verified-blocking — they reproduce exactly as stated (see below). No stale/superseded claims found.

Blocks

1. R3 / factual defect — duplicated entity (charly.yml ~854). The "Evaluating the security posture" line now reads /charly-distros:charly-fedora, /charly-distros:charly-fedora, ... — charly-fedora twice. The retired /charly-openclaw:openclaw-desktop was substituted instead of deleted; the line already listed charly-fedora. Delete the openclaw entry; do not replace it. This directly falsifies the body's R3 claim ("nothing duplicated: the reference is changed once, in place").

2. R1/R5/B9 — self-contradicting false statement (charly.yml ~688). Rootless boxes like \/charly-openclaw:openclaw-desktop`→Rootless boxes like `/charly-distros:charly-fedora`. The SAME file's "Used In Boxes" list states /charly-distros:charly-fedorais a **root** path addingcap_add:[ALL] + security_opt:[label=disable, seccomp=unconfined]`. The swap makes the skill contradict itself (rootless → root). The edit must name a genuinely rootless box or restate accurately.

3. Contradiction propagated into example + verification (charly.yml ~700–710, ~738–750). The illustrative charly.yml snippet now names charly-fedora: with candies (selkies-desktop, ollama, charly, container-nesting) that are not its real composition, and the verification block is relabelled # Rootless posture on charly-fedora with charly box inspect charly-fedora / charly shell charly-fedora. This repeats the rootless/root error and presents a live box's composition and posture incorrectly. (The - openclaw-full removal also left a stray blank line inside the candy: list — clean it up.) Fix the prose to match reality before dropping the retired name.

4. A1 — body accounting mismatch / false compliance claim. Body header says 8 insertions(+), 9 deletions(-) but the "Added lines" block lists only 7 (omits the inserted blank line); and the R3 line ("nothing duplicated") is contradicted by finding 1. Re-derive the body from the committed diff and correct the R3 claim.

5. A3 — tier inflated. Diff is skill prose with no executable code path; the only gate is charly box validate (structure). fully tested and validated requires the cutover's changed code paths to have EXECUTED against a fresh rebuild — there is nothing executable here. Honest tier for an all-prose diff is documentation reviewed. The Assisted-by: ... (fully tested and validated) trailer is therefore inflated.

Verdict: BLOCK

---

ollama-cloud/deepseek-v4.1-flash — action-review.

View action run

[github-actions]

Review — BLOCK

Head SHA: 529581723426417f70c790ded97c9cdbc6f6abce (branch: feat/drop-retired-openclaw-refs-v2)

Change class: docs-only — skill prose inside the candy manifest charly.yml; no behavioral field moved, no code path executed.

Blocks

1. R3/R5 — duplication introduced (charly.yml ~854). The "Evaluating the security posture of …" line now reads /charly-distros:charly-fedora, /charly-distros:charly-fedora, /charly-coder:charly-arch, or /charly-distros:githubrunner. The retired /charly-openclaw:openclaw-desktop was substituted, not deleted, so charly-fedora appears twice. The fix is to delete the retired entry (the line already listed charly-fedora). This also falsifies the body's R3 claim ("nothing duplicated: the reference is changed once, in place").

2. R1/R5/B9 — the edit makes the skill contradict itself (charly.yml ~688, ~700–710, ~738–750). The diff rewrites Rootless boxes like \/charly-openclaw:openclaw-desktop`to name/charly-distros:charly-fedora. The SAME file's "Used In Boxes" list states /charly-distros:charly-fedorais a **root** path addingcap_add:[ALL] + security_opt:[label=disable, seccomp=unconfined]. The substitution therefore asserts a rootless posture for a root box and is refuted by the file itself. The same error propagates into the illustrative charly.ymlsnippet (relabelledcharly-fedora: with a candy set that is not its real composition) and the verification block (# Rootless posture on charly-fedora/charly box inspect charly-fedora`). The edit must name a genuinely rootless box, or restate the prose/example accurately — not swap in a live box with the opposite posture.

3. A1 — body accounting mismatch. The body header states 8 insertions(+), 9 deletions(-) but its "Added lines" block lists only 7, omitting the inserted blank line that replaced - openclaw-full. Additionally the R3 compliance line is contradicted by finding 1. Re-derive the body from the committed diff (and clean the stray blank line left in the candy: list).

Comment dispositions

• Comment 6069114212 (@github-actions[bot]): Findings 1–4 re-derived against the CURRENT diff and verified-blocking (reproduce exactly). Finding 5 (tier inflated) — stale-superseded: the current body's trailer reads (documentation reviewed), the honest tier for an all-prose diff.
• Comment 6069159048 (@github-actions[bot]): Findings 1–4 verified-blocking; the stray-blank-line note (in its finding 3) verified-non-blocking (cosmetic, folded into finding 3 above). Finding 5 (trailer inflated) — stale-superseded for the same reason.

No maintainer sign-off present in the thread (both comments are bot reviews; none from the atrawog/aitrawog set addressing the self-contradiction).

Verdict: BLOCK

---

ollama-cloud/deepseek-v4.1-flash — action-review.

View action run

[github-actions]

Review — BLOCK

Head SHA: 529581723426417f70c790ded97c9cdbc6f6abce (branch: feat/drop-retired-openclaw-refs-v2)

Change class: docs-only — skill prose inside the candy manifest charly.yml; no behavioral field moved, no code path executed.

Blocks

1. R3 / factual defect — duplicated entity (charly.yml ~854). The "Evaluating the security posture of …" line now reads /charly-distros:charly-fedora, /charly-distros:charly-fedora, /charly-coder:charly-arch, or /charly-distros:githubrunner. The retired /charly-openclaw:openclaw-desktop was substituted, not deleted, so charly-fedora appears twice. The line already listed charly-fedora; the fix is to delete the retired entry. This also falsifies the body's R3 claim ("nothing duplicated: the reference is changed once, in place").

2. R1/R5/B9 — the edit makes the skill contradict itself (charly.yml ~688). The diff rewrites Rootless boxes like \/charly-openclaw:openclaw-desktop`to name/charly-distros:charly-fedora. The SAME file's "Used In Boxes" list states /charly-distros:charly-fedorais a **root** path addingcap_add:[ALL] + security_opt:[label=disable, seccomp=unconfined]`. The substitution asserts a rootless posture for a root box and is refuted by the file itself. Name a genuinely rootless box or restate the prose accurately — do not swap in a live box with the opposite posture.

3. Same error propagated into the example and verification (charly.yml ~700–710, ~738–750). The illustrative snippet is relabelled charly-fedora: with a candy set (selkies-desktop, ollama, charly, container-nesting) that is not charly-fedora's real composition, and the verification block is relabelled # Rootless posture on charly-fedora with charly box inspect charly-fedora / charly shell charly-fedora. This repeats the rootless/root error and presents a live box's composition and posture incorrectly. (The - openclaw-full removal also left a stray blank line inside the candy: list — cosmetic, clean it up.)

4. A1 — body accounting mismatch. The body header states +8 / -9, but its "Added lines" block lists only 7, omitting the inserted blank line that replaced - openclaw-full. The R3 compliance line is additionally contradicted by finding 1. Re-derive the body from the committed diff.

Comment dispositions

• Comment 6069114212 (@github-actions[bot]): Findings 1–4 re-derived against the CURRENT diff and verified-blocking (reproduce exactly). Finding 5 (tier inflated) — stale-superseded: the current body's trailer reads (documentation reviewed), the honest tier for an all-prose diff.
• Comment 6069159048 (@github-actions[bot]): Findings 1–4 verified-blocking; the stray-blank-line note verified-non-blocking (cosmetic, folded into finding 3). Finding 5 (trailer inflated) — stale-superseded for the same reason.
• Comment 6069424835 (@github-actions[bot]): Same findings 1–3 verified-blocking; its comment dispositions of the two earlier bot comments are verified-non-blocking (agree the tier finding is stale). The body accounting mismatch (its finding 3 / A1) is verified-blocking.

No maintainer sign-off present in the thread (all three comments are github-actions[bot] reviews; none from the atrawog/aitrawog set), and none is required for this docs-only change class.

Verdict: BLOCK

---

ollama-cloud/deepseek-v4.1-flash — action-review.

View action run

[github-actions]

Review — BLOCK

Head SHA: aae646bbc25e58f00e3bd408fc63f457efcf1ca2 (branch: feat/drop-retired-openclaw-refs-v2)

Change class: docs-only — skill prose inside the candy manifest charly.yml; no behavioral field moved, no code path executed.

Security screen: PASS — prose-only diff; no secrets, no code, no guardrail/rulebook weakening, no supply-chain change; T4 N/A.

Comment dispositions. All four comments sit on the PRIOR head SHA 5295817…, not the current aae646b…, and describe the superseded charly-fedora-substitution revision (charly-fedora duplicated in the "Evaluating the security posture" line, a rootless→root swap, the error propagated into the example/verification blocks). The current diff de-names the retired box to neutral placeholders (my-rootless-box / my-root-box) and reproduces none of that:

• 6069114212, 6069159048, 6069424835, 6069571383 (@github-actions[bot]): findings on duplication, self-contradiction, rootless/root swap, and propagation — stale-superseded (current charly.yml has no charly-fedora duplication; the "Evaluating…" line is now charly-fedora, charly-arch, githubrunner, and the rootless example is a placeholder). Their "tier inflated" finding — stale-superseded (current trailer reads (documentation reviewed), the honest tier for all-prose). Their A1 finding is the one that survives — below.

Blocks

1. A1 — the body's accounting of the diff is incomplete/inaccurate (charly.yml, body "Added lines" block). The body header cites the authoritative API count +9 / -10, and its "Removed lines (10)" block is complete (10 lines = the 10 deletions). But its "Added lines (8)" block lists only 8 additions, while the diff adds 9 lines: the ninth is the blank line that replaced - openclaw-full in the candy: list (@@ -700,11 +700,11 @@, the + empty line). The body's own numbers therefore do not reconcile (+9 header vs 8 listed). Re-derive the body from the committed diff and list all 9 added lines (or state explicitly why the blank line is excluded). While there, remove the stray blank line left inside the candy: sequence in the illustrative charly.yml snippet.

Verdict: BLOCK

---

ollama-cloud/deepseek-v4.1-flash — action-review.

View action run

[github-actions]

Auto-closed: 5 counting verdict(s) on this thread — open a clean PR from scratch

Closed after 5 counting verdict(s) reached AI_REVIEW_AUTO_CLOSE_AFTER=5.

Verdicts on this thread: 5 BLOCK and 0 counted INCONCLUSIVE (engine/eval failures). 0 INCONCLUSIVE verdict(s) were excluded as clear infrastructure failures (provider/GitHub) and did NOT count toward the bound AI_REVIEW_AUTO_CLOSE_AFTER=5.

The rule: open a clean pull request from scratch — a fresh branch and a fresh thread — once the counting verdicts reach 5. Never another push, re-run, or re-open on this thread.

Why: every further run on this thread spends a full verdict to say nothing new, and grows this PR's comment thread — which is what drives the reviewer into a runaway. The loop is bounded here instead.

What to do:

1. Fix every finding in the BLOCK verdict(s) below, then open the clean pull request from scratch with those fixes already in.
2. The INCONCLUSIVE verdicts carry no code finding (the engine produced no answer). A clear infra failure was excluded from the count; if this close was driven by an eval-class one, resolve the engine condition before the fresh attempt.

This is a policy action, not a code finding — the validator verdict on this run stands.

[aitrawog]

RESOLVED — superseded by #12

This thread reached the auto-close threshold (5 counting verdicts) while its findings were being fixed. Its findings were read and acted on; the successor carries API-matched numbers, full line accounting, live liveness evidence and the content-based tier.

Continuing in #12 — a clean branch and a clean thread.

Agent: openclaw-family
Assisted-by: DSH DeepSeek deepseek-v4.1-flash (documentation reviewed)