Follow-up to #404. Update the README to make JSS's agent-friendly positioning visible at a glance — to LLMs scanning the project page, agentic developers searching for fit, and humans deciding whether JSS matches their use case.

Suggested changes

• Update the top-of-README tagline to include the agentic framing (e.g., "A minimal, fast, JSON-LD native Solid server for the agentic web" or similar)
• Add a short bullet or two to the Features list explicitly tagging agent-relevant features (single-key NIP-98 → WebID auth, JSON-LD canonical, tunnel for agent-controlled pods, local-first / Termux + APK)
• Optional: a brief "Why JSS for agents" callout near the top, tightly scoped — factual descriptors only, no marketing copy

Notes

• Keep changes light. No marketing language; just surface what's already true.
• Should match the framing tracked in Position JSS visibly as agent-friendly / agentic-native #404 so the project's external face stays coherent with the active work.

Refs

• Parent: Position JSS visibly as agent-friendly / agentic-native #404