index: add reasoning-switch 1.0.7

[apoapostolov]

Adds reasoning-switch at 8963b9cdff22a4064b5bdce6b3de21178720d681 (v1.0.0).

What it does

A statusbar word + gear chip controlling the focused session's reasoning effort.

• Click the word - rotates the session through the levels checked in the dialog, via the same session-scoped gateway call the app's own model menu makes (config.set, key reasoning). Never writes the global profile default.
• Gear - dialog (styled after provider-status) listing the standardized levels (none, minimal ... ultra, mirroring the backend's VALID_REASONING_EFFORTS):
  • per-level color from a theme-aware palette (native select, color-scheme pinned per app mode);
  • checkbox to include the level in the rotation;
  • per-level prompt limit: after N user prompts at that level, the plugin automatically demotes to the next lower checked level (e.g. high for 3 prompts, then back to medium).

Implementation notes

• JS-only: host.request('config.get'/'config.set') + host.state (focused session, awaiting-response edge = user prompt). No Python backend.
• Config persists in plugin-scoped storage; the rotation counter is per session id.

[opus-fivel]

Thanks for this — reasoning-switch itself looks good, but I can't merge this PR as it stands. Three things, and the first is the one that matters.

1. This changes pstack, which isn't yours, and breaks it

The diff repins pstack:

"repo": "iap/pstack-hermes",
-      "ref": "2bca26a13cca72cb1c57458915091cd29bb22cb2",
+      "ref": "d7c4c703121d36353ca10b282d8ee9ba8ba87d5f",

That new SHA does not exist in iap/pstack-hermes. Checked directly against the API rather than taking the gate's word for it:

GET repos/iap/pstack-hermes/commits/d7c4c703121d…
→ 422  No commit found for SHA: d7c4c703121d36353ca10b282d8ee9ba8ba87d5f

The pin currently on main (2bca26a1) resolves fine. So merging this would take a working entry and point it at nothing — pstack would install nothing for everyone, and it would look fine in the diff.

pstack is listed by iap, and house rules are that only the listing author edits their own entry. Even with a valid SHA this isn't yours to move. Please drop that hunk entirely. If pstack genuinely needs repinning, that's a PR from iap.

2. The pin doesn't match the description

The body says reasoning-switch is added at 8963b9cdff22a4064b5bdce6b3de21178720d681. The diff pins 9fd9799f47a432e96ed7b14a5f31bd00690b4112.

Both commits exist, so this isn't broken — but they're different commits, and the one that ships is the one in the JSON, not the one in the description. Please make them agree, and say which one you actually want.

This is the third PR where the body and the diff describe different things. I review the diff, so nothing bad has gone in — but it costs a round trip every time, and on this PR it's what hid the pstack change. Worth a look at whatever's generating these.

3. One plugin per PR

This changes two entries. Split it: reasoning-switch on its own.

Not blocking, worth fixing while you're in there

• reasoning-switch has "homepage": "". Either give it a real URL or drop the key — an empty string reads as a broken link rather than an absent one.
• No capabilities. Recommended, not required, but it's what people filter on.

Re-open or push to this branch with just reasoning-switch and I'll merge it. #45 and #46 are both in.

[apoapostolov]

You were right on all three counts, and the root cause was worse than a bad hunk: every "repin reasoning-switch" commit from ff1d6ac onward actually edited the pstack entry, not ours — the repin tooling matched the wrong entry, so pstack's ref got walked through reasoning-switch's SHAs, ending on d7c4c703 (a commit in my plugin repo, hence the 422 in iap's repo). That's what hid in the diff, and it's the same wrong-entry matching that caused the body/diff pin mismatches you called out.

Fixed by rebuilding the branch as one commit off current main:

• pstack hunk gone entirely; its entry is byte-identical to main (verified programmatically)
• reasoning-switch only, pinned to d7c4c703 (1.0.7, the actual repo tip — body and diff now agree)
• homepage key dropped (was empty string), capabilities added (statusbar, dialog)

Happy to send the repin-tooling fix upstream in my own plugins — and #45/#46 noted, thanks.

[opus-fivel]

Merged. Everything I asked for is here: single entry, pstack untouched, capabilities added, and homepage dropped rather than left as an empty string.

And I owe you a correction on the last round. I said d7c4c703121d… "does not exist." That was true of iap/pstack-hermes, which is where the old diff pointed it — but the SHA is perfectly real in your own repo:

d7c4c703121d  reasoning-switch 1.0.7: drop 'before auto-demoting' (stretched dialog)

So the original problem was a transposition, not a fabricated pin — your reasoning-switch SHA had landed in pstack's ref field. My wording implied you'd invented a commit, and it deserved a more precise description than the one I gave it.

Verified before merging, against the API rather than the gate:

• d7c4c703 resolves in apoapostolov/hermes-agent-awesome-plugins
• plugins/reasoning-switch resolves at that commit — __init__.py, desktop/, plugin.yaml
• one entry changed, and it is your own

#44 is still conflicting, and that one is on me: I merged #45 and #46 while it was open and both moved index.json. Same conflict will now have shifted again with this merge. I'll deal with it — no action needed from you.