feat: use host Action for task manager CPU chip - #4
Draft
carlosflorencio wants to merge 4 commits into
Draft
carlosflorencio wants to merge 4 commits into
carlosflorencio wants to merge 4 commits into
Conversation
carlosflorencio
force-pushed
the
feature/standardize-task-man-vzc
branch
from
September 27, 2026 18:30
9813415 to
8a87561
Compare
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.
Change
The Task Manager CPU top-bar trigger uses host-owned
ui.Actionwhen available. It shows a decorative CPU icon and live CPU percentage with a localized accessible label and interpolated tooltip. Older supported API v1 hosts retain the existing chip and detailed meter. The mobile legacy path readsprops.slotProps.presentation. Plugin id, registration, keybinding, modal, polling, sampling, process attribution, provider behavior, permissions, and platform support remain unchanged.Conflict resolution against latest main
The PR still targets
main, now at356dd945767979a553660e897676e81f5ad4200c(release0.1.3). This branch merges that base in commit0ccbd61563ca5611e39bb7e2349a9da6bdd22fd6; the published PR history was not rewritten.The resolution preserves main's marketplace archive checksum fix, SDK
plugin-packGo tool declaration and updated dependency checksums, current-platform packaging CI check, and0.1.3manifest/Makefile/CHANGELOG metadata. The release checksum step extracts the internal package checksums from the exact version-verified archive and appends that archive's SHA-256.Compatibility
570600439036e81f8e9e1c63f15c4abce8a6c846in.kandev-sdk-ref. This is a reproducible source pin, not a runtime minimum.min_kandev_versionremains unset. The Action is feature-detected and the legacy path remains for older API v1 hosts.570600439036e81f8e9e1c63f15c4abce8a6c846and pre-Action host7eb9c228b86907a161969f34e19761de0dd3863f, using isolated fixtures and synthetic CPU data. The conflict resolution did not change the UI or harness files.Checks on the conflict-resolved tree
go mod tidyis reproducible;go.modandgo.sumremain unchanged after tidy.npm ci --prefix .harnesscompleted with no reported vulnerabilities.make check-format,make vet, andmake testpassed. UI tests: 3/3; package-verifier and release-version negative tests passed.make test-harnesspassed with no console errors.make verify-packagepassed for all five manifest platforms;make verify-package-hostpassed on linux-amd64.sh scripts/verify-release-version.sh v0.1.3 kandev-plugin-task-manager-0.1.3.tar.gzpassed.git diff --checkpassed.Coordination with PR #3
PR #3 remains open at
f214c7bacd773ec9925f8e46462dad1c7902e73b. This PR does not include it. Both PRs modifyui/bundle.js,Makefile,README.md,.gitignore,.github/workflows/ci.yml,.harness/build-globals.mjs,.harness/harness.js,.harness/package.json,.harness/real-app.mjs,.harness/shoot.mjs, andgo.sum. PR #3 introduces configurable multi-metric top-bar content and sampler/product behavior. This PR preserves the current single-metric CPU behavior and sampling. Reconcile the Action shell and mobile presentation with #3's multi-metric rendering and integrate the browser harness changes before either merge order. Preserve #3's product/sampling changes if it lands first; do not restore the prior single-metric UI or replace its fixtures. Dependabot PR #1 overlaps the Go dependency update; resolve against the final module state.No stable release containing PR #3943 has been validated. Keep this PR Draft until a stable host release includes that change and this package is re-pinned and checked against it.