OSS-Singularity/zcode-dispatch-observatory
OSS-Singularity/zcode-dispatch-observatory
Watch
1
0
Fork
You've already forked zcode-dispatch-observatory
 0
Code Issues Pull requests Projects Releases 137 Packages Wiki Activity Actions

Pinky KKK: housekeeping — EEE-V ZCODEHOME fold + FV-6 yamllint (v1.68.0) #98

Closed
ClaudiuSchuster wants to merge 1 commit from oss-oo/pinky-kkk-housekeep into main
pull from: oss-oo/pinky-kkk-housekeep
merge into: OSS-Singularity:main
Conversation 0 Commits 1 Files changed 7 +277 -12
ClaudiuSchuster commented 2026-10-13 06:25:34 +00:00
Owner

Two MasterBrain-cleared parked items.

K1 (EEE-V-ZCODEHOME): quota_zcode_provider_key read $ZCODE_HOME/v2/config.json while the applet reads $ZCODE_HOME/config.json — they coincided only because ZCODE_HOME is unset on the station. The chain now mirrors the applet's _zcode_providers/zcode_provider_key byte-equivalently: ZCODE_HOME-set contributes /config.json (no /v2) FIRST, the home default ~/.zcode/v2/config.json always follows, provider-dict fallthrough, non-dict entries read as no options. Tests pin BOTH conditions (fixture roots) plus a station leg EXECUTING the applet's own resolution for byte-comparison (skips on forge CI).

K2 (FV-6): the standing yamllint INFO on .forgejo/workflows/check.yml fixed at source — --- document-start added, over-long apt-get line split; the justified truthy disable-line stays (workflow schema mandates on:), spacing fixed so vanilla yamllint is also clean. Zero findings under the Super-Linter lane config AND vanilla defaults.

G3: full suite green on the worktree (983 OK, 1 expected env-gated skip); live-spot: station quota key resolves identically pre/post fold (read-only).

Two MasterBrain-cleared parked items. K1 (EEE-V-ZCODEHOME): quota_zcode_provider_key read $ZCODE_HOME/v2/config.json while the applet reads $ZCODE_HOME/config.json — they coincided only because ZCODE_HOME is unset on the station. The chain now mirrors the applet's _zcode_providers/zcode_provider_key byte-equivalently: ZCODE_HOME-set contributes <root>/config.json (no /v2) FIRST, the home default ~/.zcode/v2/config.json always follows, provider-dict fallthrough, non-dict entries read as no options. Tests pin BOTH conditions (fixture roots) plus a station leg EXECUTING the applet's own resolution for byte-comparison (skips on forge CI). K2 (FV-6): the standing yamllint INFO on .forgejo/workflows/check.yml fixed at source — --- document-start added, over-long apt-get line split; the justified truthy disable-line stays (workflow schema mandates on:), spacing fixed so vanilla yamllint is also clean. Zero findings under the Super-Linter lane config AND vanilla defaults. G3: full suite green on the worktree (983 OK, 1 expected env-gated skip); live-spot: station quota key resolves identically pre/post fold (read-only).
Pinky KKK: housekeeping — EEE-V ZCODEHOME fold + FV-6 yamllint (v1.68.0)
All checks were successful
Checks / Functional checks (pull_request) Successful in 34s
Details Explain this check
c2cefcc298 
K1 (EEE-V): quota_zcode_provider_key now mirrors the applet's
_zcode_providers/zcode_provider_key chain byte-equivalently — a set
ZCODE_HOME contributes <ZCODE_HOME>/config.json (NO /v2 segment, the
applet's spelling) FIRST, the home-based ~/.zcode/v2/config.json
always follows as fallback, a parseable candidate without a provider
dict falls through, and a non-dict provider entry reads as no options
(never a crash). Pinned by tests for BOTH conditions (ZCODE_HOME set
to a fixture root; unset → station default) plus a station leg that
EXECUTES the applet's own resolution for byte-comparison (skipped on
forge CI where the applet source is absent).

K2 (FV-6): the standing yamllint INFO on .forgejo/workflows/check.yml
fixed at source — document-start marker added, the over-long apt-get
line split; the pre-existing truthy disable-line keeps its justified
exception (the on: key is workflow-schema-mandated), spacing fixed so
vanilla default yamllint is clean too. Zero findings under both the
Super-Linter lane config and vanilla defaults.
ClaudiuSchuster closed this pull request 2026-10-13 06:36:16 +00:00
All checks were successful
Checks / Functional checks (pull_request) Successful in 34s
Details Explain this check

Pull request closed

This pull request cannot be reopened because the branch was deleted.
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
OSS-Singularity/zcode-dispatch-observatory!98
No description provided.