9 Commits

Include renames

Author	SHA1	Message	Date
gitea-actions	ef8829cb56	Release v0.2.0 [skip release] [skip actions]	2026-09-27 05:18:46 +00:00
NotExpectedYet	266e90aa2d	feat: set a conversation's scope from the composer, where the agent cannot reach ... The per-session scope the host half now reads had no writer. This is it: a crosshair on the composer tool row, present only in sessions running the facet preset, opening a panel that sets the focus and the paths allowed outside it. The gate is the session's own `agentPreset` projection rather than anything inferred from the URL or from the plugin being installed, so a control for a plugin that is not running never appears. It writes through the settings document — the same one the plugin card edits — because `settings.mutate` accepts a path under a volatile node and refuses anything else. That is what makes the split real rather than aspirational: the agent has no write path to `scopes`, and the panel's write is the only one that can widen a session. The panel also carries the mode details and the usage notes, which the preset picker's guide dialog cannot show for a preset no core package ships — its guide table holds four shipped ids and is looked up only for built-ins. Also adds `@deepseek-ai/dsh-client-ui-conversation` to the client half's inject list: registering into `conversation.input.left` is a dependency on the package that declares it, and `slots.inject` waits for a slot rather than creating one, so naming another package's slot without loading it first registers nothing — silently, because nothing errors.	2026-09-27 06:15:53 +01:00
gitea-actions	f36d46efa1	Release v0.1.4 [skip release] [skip actions]	2026-09-26 08:03:19 +00:00
gitea-actions	6e696f10a2	Release v0.1.3 [skip release] [skip actions]	2026-09-26 06:50:42 +00:00
NotExpectedYet	1be3a67b97	fix: put the settings card on the Plugins page with a browser half ... The `volatile()` markers made the Host serve the namespace, and that was as far as it went: the Plugins page does not build a card from a `Config` schema. It draws only what browser halves register into the slots it declares, which is why dsh-slopo, dsh-recall and dsh-context all ship a `client/` — and why this plugin, with two served fields, still showed nothing. The card registers into `plugins.bundle.config` while `configForms.whileServed` reports the namespace served. The two keys are deliberately different strings and that is the trap in the file: the settings document is filed under the profile entry id (`facet-policy`) while the card is keyed by the package name (`dsh-facet`). Every sibling plugin happens to name them identically. Binding the form to the wrong one yields a card that renders, saves, and writes nowhere, so `test/client.test.js` pins both, holds the card's field list to the schema's volatile fields, and refuses to register at all when the namespace is not served.	2026-09-26 07:39:57 +01:00
gitea-actions	e860ac2989	Release v0.1.2 [skip release] [skip actions]	2026-09-26 06:14:27 +00:00
gitea-actions	e7401445d7	Release v0.1.1 [skip release] [skip actions]	2026-09-26 05:54:48 +00:00
NotExpectedYet	cd43e87684	feat: tag and publish a Gitea release on every push to master ... A plugin installed as a bare git+https URL is pinned to a commit, so with no tags there is nothing for `dsh plugin update` to move to. The workflow reads the commit subjects since the last tag, bumps package.json, prepends CHANGELOG.md, tags vX.Y.Z, and publishes the Gitea release with those subjects as the body. The decision logic lives in .gitea/scripts/release.sh so it runs and is tested without a runner (`npm run test:release`).	2026-09-26 06:45:52 +01:00
NotExpectedYet	0858862cda	init	2026-09-26 06:45:50 +01:00