SkillPedia Skills Encyclopedia
中文 EN
Today's updates 2026-11-18 UTC

No new commits yet today

Open the update feed

Skills 2026-10-11 03:26 UTC

hol-guard

Committed by zerocodefast. Update Category: New Features & Capability Expansion. Commit details: feat(guard): decide bulk approve-once eligibility in the native resident (#4020). This update introduces new capabilities and expands supported use cases.

zerocodefast 52eb843 hashgraph-online/hol-guard

CommitRaw commit message

feat(guard): decide bulk approve-once eligibility in the native resident (#4020)

* feat(guard): decide bulk approve-once eligibility in the native resident

The resident now decides whether a pending approval request may be approved
once in a bulk action: block and sandbox-required policies, non-pending
requests, secret file reads, blocked decision categories and blocked command
hints. Python only narrows stored requests, batches them in one call and
decodes the verdicts; an unavailable resident raises instead of approving.
Secret path classification uses the shared native classifier, which is
slightly stricter than the previous Python one for bare key file names.
Parity vectors were recorded from the previous Python implementation.

Signed-off-by: ZCF <291624129+zerocodefast@users.noreply.github.com>

* fix(guard): chunk bulk eligibility by the resident byte cap

Pack bulk approval calls under the encoded byte limit as well as the item count. A prompt that cannot fit in one call is ineligible on its own, and the rest of the batch is still judged. The sed matcher uses the shared Python whitespace helper.

Signed-off-by: ZCF <291624129+zerocodefast@users.noreply.github.com>

* fix(guard): pack bulk eligibility chunks from one encoding per item

Encode each approval item once and add the JSON array separator, so a bulk approve does not re-encode the growing chunk for every item.

Signed-off-by: ZCF <291624129+zerocodefast@users.noreply.github.com>

* fix(guard): keep ephemeral reaping when one home has no verdict

Ask the pure daemon-state shape question on the context resident so a stale temp home does not get its own runtime. A lifecycle failure on one state file leaves that home untouched and still lets the process inventory retire other daemons that the resident marks inactive.

Signed-off-by: ZCF <291624129+zerocodefast@users.noreply.github.com>

---------

Signed-off-by: ZCF <291624129+zerocodefast@users.noreply.github.com>