7 Commits

Include renames

Author	SHA1	Message	Date
pyh	dbf6138df2	release: 1.0.1 ... Ships the rewritten README inside the package and pins the documented install specs to this version.	2026-09-30 11:54:43 +08:00
pyh	105e86edd5	docs: rewrite the README around the plugin itself ... Only the features, the behaviour boundaries, the three ways to install it, and a precise compatibility statement remain; the release pipeline, the file layout and the local-directory install method are gone. The install section now mirrors how a published DSH plugin is described: npm package plus custom registry, a pinned git URL, or a downloaded tgz.	2026-09-30 11:46:17 +08:00
pyh	ec8aadedb7	docs: record what the release workflow actually depends on ... The publish section now says why the workflow avoids external actions, that a repeated version is a skip rather than a failure, and that an npm registry line pointing elsewhere produces a misleading 'version already exists'.	2026-09-30 11:37:25 +08:00
pyh	f4e107782a	ci: make a repeated release a no-op and drop the misleading diagnostics ... Gitea does not implement the npm whoami endpoint and npm refuses to read an auth token back, so both lines only produced error-looking output. The run now checks the registry first and skips publishing a version that already exists, which also makes a manual re-run safe.	2026-09-30 11:28:57 +08:00
pyh	733f0ba456	ci: fall back to a PAT and self-diagnose the publish step ... The first tagged run failed inside the publish step within a second, which is the shape of an auth rejection rather than a build problem. The step now prefers a repository NPM_TOKEN secret when one exists, prints the effective registry and a masked token, and runs npm whoami so a re-run names the cause instead of just failing.	2026-09-30 11:05:33 +08:00
pyh	37468d6ac9	feat!: publish as @dsh-plugin/session-delete with an automated Gitea npm release ... The registry owner is the scope the package must publish under, so the name moves from @local/ to @dsh-plugin/ in all three places that must agree: package.json, cordis.patch.yml, and the client module id. `private` goes away because npm refuses to publish such a package, and publishConfig pins the registry to this organization's npm endpoint. The tag workflow publishes whatever version the pushed v* tag names, using the built-in Gitea job token, and refuses a tag that disagrees with package.json.	2026-09-30 11:00:39 +08:00
pyh	39a39adfec	feat: permanently delete a conversation, sweep orphaned spill files	2026-09-30 10:43:38 +08:00