You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Nov 9 this repo had 0 open PRs and 4 open issues. Try each PR and check each issue against main.
Done when
Every open PR and issue has a triage comment from this pass
Summary comment here
How to triage each item:
Read it, and for a PR check out the branch and try the change: build it, run the tests it touches, and exercise the behaviour it claims (for an issue, try to reproduce it on current main).
Check CI, conflicts, unanswered review feedback, and whether it is a genuine, in-scope contribution.
Leave a comment with the outcome and a next step: ready to merge (and why), needs changes (specific), duplicate or already fixed (link it), or close (with the reason).
Link it to the epic or issue it belongs to, and label it.
Tracking issue for a one-off triage pass over all open PRs and issues (milestone Nov 9-13, parent #45). It is process/coordination work, not a bug or feature, and is low urgency since it is a scheduled housekeeping sweep rather than a broken path.
Status update, 2026-11-11 14:50 IST: issues closed #1. The tables below are the triage as it was done; rows for those items are now settled.
tinysecurity: triage (tinysecurity#58, team#45)
Official main 24921ba = v0.20.0. openhuman pins 17c1284 = v0.19.0, 4 first-parent commits behind. None of the behaviour below differs between the two.
PRs
None open.
Issues
Issue
Verdict
Reason
Next step
#57 persist undecided approvals across restart + ListPending
still real (p2)
import_history stores every legacy row as inert Denied (engine.rs:1069-1077), ListPending is reserved (future.rs:141), and there's no pending filter. On CF, openhuman main's 2 storage_default_import_e2e legacy-approval tests FAIL at :176 ("list_pending returned 0 row(s)"). They've been stale since openhuman a26e3847a9 (10-25) moved list_pending to in-memory routes.
tinysecurity implements and releases. openhuman #[ignore]s or narrows those 2 tests now (pointing here), then does the host follow-up.
JudgeConfig.credential is init-only (policy.rs:394-396), the client is built once (judge.rs:96-97), and there's no callback. Since openhuman #8559 the judge is OFF for all desktops (modules/security/judge.rs:33-39).
Accept the lazy host-callback contract change and release; openhuman then turns the judge back on.
Fresh consent before every op (adapter_crypto.rs:543-544), and no scope or TTL in KeyringConsent2. The issue's "48 prompts a minute" is outdated: openhuman's READ_CACHE (#8553) stops the repeats within a run. The remaining per-launch prompts are tracked separately on the openhuman side (related, not a duplicate). #8597 didn't touch this.
A maintainer decides the read-grant shape. openhuman fixes its per-launch prompts separately (load only the session profile at startup).
Activity
tinysweeper commentedon Nov 9, 2026
Tracking issue for a one-off triage pass over all open PRs and issues (milestone Nov 9-13, parent #45). It is process/coordination work, not a bug or feature, and is low urgency since it is a scheduled housekeeping sweep rather than a broken path.
Labelled
priority: p3.M3gA-Mind commentedon Nov 11, 2026
tinysecurity: triage (tinysecurity#58, team#45)
Official main 24921ba = v0.20.0. openhuman pins 17c1284 = v0.19.0, 4 first-parent commits behind. None of the behaviour below differs between the two.
PRs
None open.
Issues
import_historystores every legacy row as inert Denied (engine.rs:1069-1077),ListPendingis reserved (future.rs:141), and there's no pending filter. On CF, openhuman main's 2storage_default_import_e2elegacy-approval tests FAIL at :176 ("list_pending returned 0 row(s)"). They've been stale since openhuman a26e3847a9 (10-25) moved list_pending to in-memory routes.#[ignore]s or narrows those 2 tests now (pointing here), then does the host follow-up.JudgeConfig.credentialis init-only (policy.rs:394-396), the client is built once (judge.rs:96-97), and there's no callback. Since openhuman #8559 the judge is OFF for all desktops (modules/security/judge.rs:33-39).adapter_crypto.rs:543-544), and no scope or TTL inKeyringConsent2. The issue's "48 prompts a minute" is outdated: openhuman's READ_CACHE (#8553) stops the repeats within a run. The remaining per-launch prompts are tracked separately on the openhuman side (related, not a duplicate). #8597 didn't touch this.docs/plans/security-module.md:3.M3gA-Mind commentedon Nov 12, 2026
Triage summary: this repo is at zero open PRs and zero open issues.
Issues fixed and merged:
Also merged:
Nothing left open from this pass.