docs: agentic positioning — README tagline, Programmatic Auth bullet, npm keywords — closes #406#547
Merged
Merged
Conversation
) Per #406's 'keep changes light, no marketing language' constraint, this is deliberately a ~3-line README diff rather than a new section: - Tagline gains 'for the agentic web' (the issue's own suggested wording). Retrieval/embedding weight concentrates at the top of a README, so one tagline term outweighs a section further down. - One net-new Features bullet: Programmatic Auth via POST /idp/credentials — the most headless-agent-relevant capability JSS has, and previously undiscoverable from the README. Every other agent-relevant fact (MCP, NIP-98, JSON-LD, 402) was already in the Features list; restating them in a dedicated 'Why JSS for agents' section would be repetition, which doesn't help LLM readers and costs tokens. - package.json keywords gain json-ld, webid, mcp, agent, agentic — npm-search discoverability at zero README cost. Closes #406.
melvincarvalho
added a commit
that referenced
this pull request
Jun 11, 2026
Eight PRs merged since 0.0.206 — IdP hardening, protocol conformance, and the de-Googled-phone (#46) arc: IdP / auth - #558 passkey login degrades cleanly on stale WebViews / insecure contexts instead of crashing — drops a redundant browser crypto.randomUUID and guards both ceremonies on secure-context + WebAuthn (closes #556) - #554 IdP login-form error now survives the POST→redirect→GET cycle (rode in a non-persisted field that Interaction.save() dropped); failed sign-ins show the error instead of a silent re-render (closes #514) - #551 RFC 9207 'iss' authorization-response param normalized to match the discovery issuer, so strict OIDC clients (solid-oidc) complete sign-in (closes #524) Tunnel - #555 opt-in, per-tunnel credential passthrough (Cookie / Authorization / Set-Cookie) so authenticated access works through a tunnel; the relay's own IdP session cookies are isolated from the tunnel client (closes #530) Content negotiation / git - #553 HEAD now mirrors GET's negotiated Content-Type / Content-Length / Cache-Control for files (RFC 9110 §9.3.2 parity) (closes #552) - #550 git WAC preHandler 401/402/403 responses carry the git CORS headers, so browser git clients see the status, not a CORS error (closes #548) - #549 first HTTP-contract coverage for the git handler + fixes a DATA_ROOT test-pollution bug (closes #375) Docs / metadata - #547 README tagline + npm keywords surface the agentic positioning (closes #406)
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
1 participant
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.
Closes #406.
Per the issue's "keep changes light, no marketing language" constraint, this is deliberately a ~3-line README diff rather than a new section.
Rationale: why no "Why JSS for agents" section
Auditing the README against agent-relevant facts: everything except one was already in the Features list (MCP, NIP-98 auth, JSON-LD native, HTTP 402, tunnel). LLM readers consume the whole README in context — restating facts in a dedicated section doesn't increase their weight, it just costs tokens. The two genuine gaps were:
POST /idp/credentials(token issuance from email/password, no browser flow) — the single most headless-agent-relevant capability JSS has — was completely absent from the README.Changes
…Solid server.→…Solid server for the agentic web.(the issue's own suggested wording)POST /idp/credentialsissues tokens from email/password; agents and headless clients authenticate with no browser flowpackage.jsonkeywordsjson-ld,webid,mcp,agent,agentic— npm-search discoverability at zero README costThe endpoint claim is verifiable at
src/idp/credentials.js:1-3("Programmatic credentials endpoint… Allows obtaining tokens via email/password without browser interaction").Suite: 926/926 passing (docs + metadata only; no code paths touched).