Add missing README.md files for crates + vale lint fixes

[Copilot]

• Create README.md for thulp-core crate
• Create README.md for thulp-adapter crate
• Create README.md for thulp-browser crate
• Create README.md for thulp-cli crate
• Create README.md for thulp-guidance crate
• Create README.md for thulp-registry crate
• Review and ensure existing READMEs are up to date (thulp-mcp, thulp-query, thulp-skills, thulp-workspace)
  • Updated thulp-mcp README to use version 0.2 instead of 0.1
• Run vale prose linter on the entire project
  • Vale linter ran successfully on all 21 markdown files
  • No prose/grammar issues found (only technical term spelling which are valid)
• Verify all READMEs are tracked in git
• Fix CLI README: use positional arguments instead of --args flag for tools validate and mcp call commands

Summary

All 10 crates in the "crates" folder now have README.md files:

• thulp-adapter: OpenAPI to Thulp tool conversion
• thulp-browser: Web fetching and CDP automation
• thulp-cli: Command-line interface
• thulp-core: Core types and traits
• thulp-guidance: Prompt templates and LLM guidance
• thulp-mcp: MCP transport integration
• thulp-query: Query DSL for tool search
• thulp-registry: Thread-safe tool registry
• thulp-skills: Multi-step tool workflows
• thulp-workspace: Workspace management

Each README includes installation instructions, usage examples, and license information following the existing documentation pattern.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>missing READMEs for crates + vale lint fixes</issue_title>
<issue_description>- ensure existence of up to date README.md for each crate in the "crates" folder

• ensure the README is committed to git and pushed to github and crates.io for each crate we have
• lint entire project using the vale prose linter once</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes missing READMEs for crates + vale lint fixes #1

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[bkataru]

lgtm

[Copilot]

Pull request overview

This pull request adds comprehensive README documentation for six workspace crates (thulp-core, thulp-adapter, thulp-browser, thulp-cli, thulp-guidance, thulp-registry) and updates version references in the thulp-mcp README from 0.1 to 0.2. All READMEs follow a consistent structure with installation instructions, usage examples, and licensing information.

Changes:

• Created README.md files for 6 previously undocumented crates
• Updated thulp-mcp README to reference version 0.2 instead of 0.1
• Added comprehensive code examples, feature descriptions, and API documentation

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
crates/thulp-registry/README.md	New README documenting async thread-safe tool registry API
crates/thulp-mcp/README.md	Updated version references from 0.1 to 0.2
crates/thulp-guidance/README.md	New README documenting prompt template system
crates/thulp-core/README.md	New README documenting core types and traits
crates/thulp-cli/README.md	New README documenting CLI commands and usage
crates/thulp-browser/README.md	New README documenting web scraping and browser automation
crates/thulp-adapter/README.md	New README documenting OpenAPI to Thulp conversion

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The CLI uses positional arguments, not flags, for tool validation. The correct usage should be thulp tools validate read_file '{"path": "/etc/hosts"}' without the --args flag. The arguments parameter is defined as a positional argument in the CLI code (line 86-87 in main.rs), not as a flag.

Suggested change

	thulp tools validate read_file --args '{"path": "/etc/hosts"}'
	# JSON output for scripting
	thulp tools validate read_file --args '{}' --output json
	thulp tools validate read_file '{"path": "/etc/hosts"}'
	# JSON output for scripting
	thulp tools validate read_file '{}' --output json

[Copilot]

The CLI uses positional arguments, not flags, for tool validation. The correct usage should be thulp tools validate read_file '{}' without the --args flag. The arguments parameter is defined as a positional argument in the CLI code (line 86-87 in main.rs), not as a flag.

Suggested change

	# Validate with JSON arguments
	thulp tools validate read_file --args '{"path": "/etc/hosts"}'
	# JSON output for scripting
	thulp tools validate read_file --args '{}' --output json
	# Validate with JSON arguments (positional arguments parameter)
	thulp tools validate read_file '{"path": "/etc/hosts"}'
	# JSON output for scripting
	thulp tools validate read_file '{}' --output json

[Copilot]

The CLI uses positional arguments, not flags, for MCP tool calls. The correct usage should be thulp mcp call search '{"query": "test"}' without the --args flag. The arguments parameter is defined as a positional argument in the CLI code (line 116-117 in main.rs), not as a flag.

Suggested change

	thulp mcp call search --args '{"query": "test"}'
	thulp mcp call search '{"query": "test"}'

[bkataru]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Fixed in da61234. Changed tools validate and mcp call examples to use positional arguments instead of the incorrect --args flag.