Skip to content

fix: consolidate 16 passive pulse repairs and 5 security hardenings - #416

Closed
Knapp-Kevin wants to merge 131 commits into
mainfrom
fix/415-passive-pulse-collection
Closed

Knapp-Kevin wants to merge 131 commits into
mainfrom
fix/415-passive-pulse-collection

Conversation

@Knapp-Kevin

@Knapp-Kevin Knapp-Kevin commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner

2026-10-28 current-main integration checkpoint (current head 777e92c9adf71cddec2fb54cf2919faa025fcb55)

The previous GitHub merge conflict is resolved, not bypassed: compared current main 2130aa99b23ae8732ccbf7b77f9b9e5adb0fc75d against the PR's old base, found exactly five overlapping public accounting surfaces, retained their byte-identical current-main blobs (44 first-party, 826 third-party reviews, Microsoft candidate 102/102 NO-GO), and retained all 72 non-overlapping PR paths. The new two-parent merge commit is 777e92c9adf71cddec2fb54cf2919faa025fcb55; reconciliation evidence. GitHub now reports mergeable=true, PR remains DRAFT / HOLD.

Readback: five public accounting blobs match main exactly, the 44-entry consolidated first-party registry still matches all 21/21 changed SKILL.md identities, and all 21 behavioral statuses remain not-run. The 16 provenance source revisions and nine eligibility corrections remain intact. No package-security pass was invented. Remaining blockers: complete pinned final-package SkillSpector reports and independent adversarial/integration acceptance. Recheck against latest main before eventual merge.

2026-10-28 provenance truth repair (current head 66839a76ff1a7e4044ec3bed29b3ca6f3ce912ab)

Independent exact-source-revision readback found 16/16 pulse provenance source_snapshot_revision pointers stale, despite matching current manifest/verification fingerprints. Corrected all 16 to the existing candidate commit 1ae6f0698ca1b970dfea51683fedd34977d9548f, which resolves to their exact manifest blobs; refreshed check dates and narrowed nine stale unchanged-import labels to conditional-on-security-and-user-fit. The five non-pulse provenance source revisions were independently confirmed correct. Evidence and full identity matrix. 17 files changed, zero skill manifests or counts changed. All 16 corrected provenance records were read back at the new head. No scanner, behavioral test, or security approval was claimed.

Earlier merge state: DRAFT / HOLD; conflicts were subsequently reconciled in the 2026-10-28 integration checkpoint above. Qualifying final-package SkillSpector reports, independent adversarial acceptance, and current-main reconciliation remain required. Do not merge on the strength of this provenance repair.

2026-10-26 source-query/privacy remediation checkpoint (current head 5b1b83c459358f0be90a03ed66b19cd06006e9f3)

A further seven-skill exact-version static tranche corrected a functional regression from removing the old pulse runner: five sources.json GitHub search configurations still contain {SINCE} placeholders, but the replacement host procedure did not define how to bind them. The five affected skills (github-pulse, governance-pulse, inference-pulse, mcp-pulse, memory-pulse) now require explicit UTC date substitution, honest default-window labeling, and source-gap reporting. hf-pulse now defaults to public-only metadata rather than reading connected private Hub data; llama-pulse no longer requires an unavailable search capability. All 16 bundled pulse source JSONs were parsed; 11 have no {SINCE} placeholder.

All seven new manifest blobs match their individual verification companions and the 44-entry consolidated first-party registry. Provenance companions were refreshed. The individual 10-dimension static rubric remains VERIFIED at 16–17/20; all seven behavioral and final-version security states remain not-run. Exact evidence and eight unexecuted adversarial scenario interpretations: seven-skill review. This does not clear the 21-package final pinned security gate or independent acceptance. The first-party count remains 44, third-party reviews 721, sources 22, and admitted denominators unchanged.

Purpose and issue closure

Closes #415 after qualified merge. Consolidates the unique first-party security corrections from #410 under #402. This PR remains DRAFT and must not merge on mergeability or historical green checks alone.

Macro scope: 21 existing first-party skills, zero admissions

Current-main reconciliation

PR branch history includes an explicit merge of current main at 17c7d9abd58ecf670036949cda22cfe8da406726, retaining concurrent accessibility-review work. The earlier mergeability observation is superseded by the current 2026-10-28 checkpoint above. The five public accounting surfaces were reconciled together: 44 first-party skills, 44/44 provenance, 721 third-party exact-version reviews, 22 registered sources, unchanged admitted-source denominators. All 21 are revisions, not admissions.

Remaining acceptance blockers

  1. External exact-final package-security assessment: prior SkillSpector results were revision-bound and cannot clear the consolidated 21 changed packages; current inference-pulse and the five distinct hardenings have no qualifying final-blob security pass. Collect complete pinned scanner evidence for each applicable final package, fail closed on findings or incomplete coverage, and persist exact-version receipts under registry/security/.
  2. Independent adversarial/integration review of action authorization, private context, credential-bearing URLs, source/tool-output instructions, optional scheduling, source-list integrity, and cross-skill semantic regression. The static semantic review is not behavioral validation or independent human approval.
  3. Final readback and branch drift check before any merge. Use expected-head protection. Keep Repair first-party pulse skills referencing removed repository script runner #415 open until the repaired instructions are on main; P0: review remaining governed skill content and track exact-version security freshness #402 remains open for wider security backfill.

Architecture

Entirely passive. No repository-owned scripts, runtime, CI, runner, scheduler, scanner, watcher, installer or background service. Pinned upstream tooling remains upstream reference evidence. Behavioral validation is not-run unless independently evidenced.

Knapp-Kevin added a commit that referenced this pull request Oct 29, 2026
docs: reconcile source registry status and pre-acceptance evidence for #416

Copy link
Copy Markdown
Owner Author

Independent static pre-acceptance review of exact head 777e92c9adf71cddec2fb54cf2919faa025fcb55 is now persisted on main: 21-manifest / 16-source-list review (merged via #476). This was a read-only inspection of all 21 revised manifests and all 16 parsed bundled pulse source lists, not an external behavioral test or a SkillSpector scan.

Actionable draft wording drift:

  1. skills/mcp-pulse/SKILL.md says this repository's own contract depends on MCP and that external services go through MCP. Tier-1 governance says skillz is host-agnostic passive reference material; frame MCP as relevant only to an operator's separately bound platform.
  2. skills/gemini-pulse/SKILL.md presumes a Qor-logic .gemini/commands/ distribution; skills/perplexity-pulse/SKILL.md calls Sonar a backend for this repository's research series. Make these conditional on an authorized external host/project, or remove them.
  3. Several vendor pulses could explicitly state that fetched pages/README text is untrusted evidence, not instructions. The higher-risk governance/inference/memory pulses already make this boundary clearer.

The {SINCE} replacement instructions in five packages, public-only HF default, and separate approval for private context, scheduling and external publication are present at this head. The review includes eight adversarial cases with all observed outcomes NOT RUN.

HOLD remains: complete final-package pinned SkillSpector reports (21/21 where applicable), independent executed adversarial/integration acceptance, and fresh identity/readback after any manifest correction. Changing a SKILL.md requires updating its exact-version provenance/verification/consolidated identity and invalidating old scan applicability. I did not edit this concurrently owned branch or alter semantic/security states.

Copy link
Copy Markdown
Owner Author

2026-10-28 bounded implementation update (current branch HEAD 13de44fad71c3a906e0b8fba441e11488a5c5569): resolved the three stale host/runtime assumptions identified by independent static pre-acceptance review. mcp-pulse no longer claims skillz requires MCP or hard-codes a host scheduler; gemini-pulse no longer assumes a Qor .gemini/commands/ distribution; perplexity-pulse no longer implies a repository-owned Sonar research backend. The three exact SKILL.md blobs are d1a2d62b9f4ffa90a1c13480ca00034ddffd52ee, 1b6a1d2d4bca784a6bcaf75bd056b189c65f2ced, and f831906d8de3835e92eabae208566bb55dcc22be respectively. Updated all three provenance and verification companions and the consolidated 44/44 local verification registry. Each provenance source revision points to 17edbdf0559c74eb1fd03013578258a96c96c3ea, the commit containing the exact corrected manifests. Bounded review.

Acceptance remains HOLD. This was a static exact-version wording/authority review, not a SkillSpector scan, independent adversarial acceptance, or behavioral pass. The three changed fingerprints must be included in the final 21-package external exact-version security qualification. No first-party admission, corpus count, source pin, runtime, CI, or repository-owned scanner was changed. Current PR is draft and mergeable but not accepted.

Copy link
Copy Markdown
Owner Author

2026-10-28 ten-vendor-pulse trust-boundary tranche, pushed at head e8be35dad33df46079ffb70c0d235761fbde8454 (two [skip ci] commits).

Implemented: all ten vendor pulse manifests now explicitly treat fetched pages, repositories, search results, release notes, and community/tool output as untrusted evidence, not instructions; refuse source-supplied commands, settings changes, credential/private-context disclosure, messaging and scheduling; require separate authorization for private/gated data and user/workspace transmission; corroborate consequential claims with dated primary sources. Ten bundled sources.json files were read and JSON-parsed; none changed. Source-owned tooling remains untouched.

Exact evidence: 10/10 individual provenance source revisions resolve to the manifest commit 014b61b9da005d4665b391c45258f911faf39c51; 10/10 individual verification SHA values match the 44-entry consolidated registry. All ten retain individual 16/20 VERIFIED semantic-only decisions and validation_status: not-run. Per-package review and SHA matrix.

Flow: +32 changed files, 10 existing manifests, 20 companions, one consolidated registry, one review; zero admissions, zero denominator/count changes, public five-surface accounting unchanged. GitHub reports draft and mergeable, NOT accepted. External pinned SkillSpector complete final-package reports for all 21 changed first-party packages and independent adversarial/integration acceptance remain mandatory; the ten changed fingerprints cannot inherit prior scans. No scanner, behavioral test, CI or repository runtime was run or added.

Copy link
Copy Markdown
Owner Author

Superseded by draft #489, integration head 7c05bb6826d4382326a03aa4691107d10cd1f79c. All 21 distinct changed first-party package identities and associated static review/provenance/verification evidence were integrated. The older mcp-vetting and permissions-review implementations were intentionally superseded by the current-taxonomy corrections from #485 and #482.

Independent integration readback confirmed 44/44 consolidated first-party manifest fingerprints and 29/29 individual verification fingerprints, with all 29 provenance companions present. This closure is lifecycle consolidation only, not a merge or acceptance of the fixes. The integrated 29 distinct final packages still require complete externally executed pinned SkillSpector evidence and independent behavioral/adversarial acceptance; issues #402/#415/#478/#481/#483 remain open. The original branch and historical review evidence are preserved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Repair first-party pulse skills referencing removed repository script runner

1 participant