Repository navigation
npm-installable, self-diagnosing, useful with zero setup (v0.11.0) - #21
Merged
Merged
Conversation
…ro setup (v0.11.0) The install path opened with "the first `add` will fail". Four paragraphs of pnpm workarounds stood between a reader and a working plugin, and a session was useful to its peers only after a model remembered to call peer_card. Both are fixed here. **Installable from npm.** Package metadata, a public publishConfig, a trimmed file list, and a tarball verified at 170 kB with nothing extra. `dsh plugin add dsh-agent-messaging` replaces the git-dependency two-step, which is kept in a collapsed section for people who want it. **Zero setup.** A session is now informative before it declares anything: where a card was never published, the workspace is read for the honest part of one — the directory the session works in, and what the humans wrote about that directory in AGENTS.md or README.md. Marked `inferred from the workspace, not declared`, because a reader has to be able to tell an inference from a statement, and peer_card becomes an upgrade rather than a prerequisite. Deliberately no derived alias. An alias is an address; two sessions in one directory would derive the same one and make every send to it ambiguous. A folded display name is unique by construction, so a guessed alias would be worse than none. **A doctor.** `npx dsh-agent-messaging doctor` checks node, the build, the state root, presence records, socket permissions, and the harness packages — one line per check, remedy included in the line that reports the problem, non-zero exit on anything blocking. Written to be run by an agent debugging its own install as much as by a person. **A skill, not just tools.** The tools say what is possible; the new `peer-coordination` skill says what is wise — claim before editing shared code, verify what you did not produce, record what was settled, and stop replying when an exchange is over. Every rule in it came out of a measured run, including the one that cut traffic 65%. Optional service, so a profile without the skill subsystem still gets the tools. **A machine-readable manifest.** dsh-plugin.json describes the tools, capabilities, config and commands for the catalogs that would otherwise hand-write it, and tests/manifest.test.ts fails when it drifts from the source. **Contributions open.** Closing this repository to pull requests was the wrong call: it suppressed exactly the outside evidence the project runs on. The auto-close workflow is gone and CONTRIBUTING says what is most useful — a run where coordination cost more than it caught. 380 tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Four things that stood between a reader and a working plugin.
Installable from npm
The install section opened with "the first
addwill fail" — four paragraphs of pnpm workarounds. Now:Package metadata, public
publishConfig, trimmed file list; tarball verified at 170 kB with nothing extra in it. The git-dependency path is kept in a collapsed section for anyone who wants it.Zero setup
A session used to be useful to its peers only after a model remembered to call
peer_card. Models don't do reliable setup. Where a card was never published, the workspace is now read for the honest part of one — the directory the session works in, and the headline of that directory'sAGENTS.mdorREADME.md— and shown asinferred from the workspace, not declared.No derived alias, deliberately. An alias is an address; two sessions in one directory would derive the same one and make every send to it ambiguous. A folded display name is unique by construction, so a guessed alias is worse than none.
A doctor
One line per check, the remedy inside the line that reports the problem, non-zero exit on anything blocking,
--jsonfor machines. Written to be run by an agent debugging its own install as much as by a person.A skill, not just tools
Tools say what is possible; the new
peer-coordinationskill says what is wise — claim before editing shared code, verify what you did not produce, record what was settled, and stop replying when an exchange is over. Every rule in it came out of a measured run rather than a style guide, including the one that cut traffic 65%. Registered against the optionalskillsservice, so a profile without that subsystem still gets the tools.A machine-readable manifest
dsh-plugin.jsondescribes the tools, capabilities, config and commands, so catalogs don't hand-write it.tests/manifest.test.tsfails when it drifts from the source.Contributions open
Closing this repo to pull requests was the wrong call — it suppressed exactly the outside evidence the project runs on. The auto-close workflow is gone, and CONTRIBUTING now says what is most useful: a run where coordination cost more than it caught.
380 tests. Publishing to npm is the one step left, and it is the maintainer's to run.