10 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
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] v0.1.2	2026-09-26 06:14:27 +00:00
NotExpectedYet	0e9f75cfab	Merge branch 'master' of https://git.notexpectedyet.com/Not-Expected-Yet/dsh-facet	2026-09-26 07:14:12 +01:00
NotExpectedYet	28f20a8aac	fix: show the settings card, and make an edit actually take effect ... `mode` and `extraRoots` carried no `volatile()` marker, so the framework's form projection dropped the whole entry from `settings.describe` and the plugin had no card under Plugins at all. The marker is what creates the card. It is also what turns each field into a reference rather than a value: the resolved config hands `apply` a `{get(), [write]}` per volatile field, which is how a settings write lands in a running plugin without re-applying it. So the policy and the guard now read both fields at the point of use instead of snapshotting them at mount, and `sectionOrder`/`contextOrder` stay unmarked because a prompt section cannot be re-ordered without a remount. A section is also registered once as a plain string, so the rule could not follow a live `mode` without freezing at load. The mode-specific sentence moved into the binding, which is a callback.	2026-09-26 07:13:33 +01:00
gitea-actions	e7401445d7	Release v0.1.1 [skip release] [skip actions] v0.1.1	2026-09-26 05:54:48 +00:00
NotExpectedYet	c41c555400	Merge branch 'master' of https://git.notexpectedyet.com/Not-Expected-Yet/dsh-facet	2026-09-26 06:54:31 +01:00
NotExpectedYet	651093a00c	docs: document installing the bundle from the repository ... The Install section only showed a local path, which is the one form that cannot be updated: pnpm records a commit for a bare git URL, so `dsh plugin update` has no version to move between. Show the `#semver:^0.1.0` form, and say why the fragment is the difference.	2026-09-26 06:53:13 +01:00
gitea-actions	e5867e6a9c	Release v0.1.0 [skip release] [skip actions] v0.1.0	2026-09-26 05:47:54 +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