Repository navigation
Prepare opt-in Anti-Dark-Code preview metadata and validation evidence - #84
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current listing subtitle exceeds the directory limit, and the next preview needs a distinct version without weakening historical release verification. Prepare 2026.10.14-unified.19, shorten the new listing subtitle, preserve metadata for releases through unified.18, and refresh the existing version labels, field brief and provenance.
Skill instructions, approval requirements, status semantics and verification capabilities are unchanged. Existing plugin metadata and the canonical calendar version stay synchronized. Local evidence records both native host upgrade/rollback checks, actual generated-document workflows and consumer calibration/approval preservation, including upgrade from the published unified.18 archive.
Validation before push:
CI: Tests run 38646697945 passed on commit
00bef3a2229a2e8902fb91ed10d7112d5edbc9ff. All 14 jobs succeeded, including the required aggregate and PR-only shadow evidence check.The dated source evidence preserves the earlier native host results and their limits; CI does not establish human comprehension or native GUI installation on Windows/Linux.
Plugin publication remains on hold. No release tags, GitHub releases, directory submissions or stable catalog updates are authorized here. The owner has now authorized merging this source PR while continuing to hold plugin publication. The opt-in catalog bundle remains in the local handoff pending release approval; no released tag or directory listing is promoted by this merge. Existing dated local-preparation records describe their pre-push state.
Review: no blocking findings in the changed source, metadata, tests, brief/provenance or workflow triggers. No unresolved review threads. Main is development source: an unpinned catalog checkout follows that source, so released/stable installations should remain pinned to a reviewed revision. No automatic plugin-release workflow is configured; the existing GitHub Pages documentation build may run after merge.
Post-merge verification: merged as
e2091631f1ab82161cfa3ea170cc4afdd478591d; its file tree exactly matches reviewed head00bef3a2229a2e8902fb91ed10d7112d5edbc9ff. Tests 38649172745 passed all 13 executed jobs, including platform suites, all four mutation shards and the required aggregate. The PR-only shadow job was intentionally skipped on the push event. Pages 38649172231 passed all three jobs.Post-merge suite results: Linux 3.12/3.13, macOS 3.12 and international-path environment each report 758 passed, eight skipped and 703 passing subtests. Windows reports 761 passed, five skipped and 707 passing subtests. C-locale environment reports 757 passed, nine skipped and 703 passing subtests, matching its earlier PR-run counts; individual test skip reasons were not printed. No source fixes were required. No release tags, plugin releases, release assets or directory submissions were created.