Improve note.template schema with comprehensive API documentation content

[Copilot]

This PR enhances the note.template schema files to match the comprehensive pattern established by exemplary schemas like card.attn. The improvements are based on word-for-word content extracted from the official Blues API documentation at https://dev.blues.io/api-reference/notecard-api/note-requests/latest/#note-template.

Key Improvements

Request Schema (note.template.req.notecard.api.json)

• Added SKU compatibility: ["CELL", "CELL+WIFI", "LORA", "WIFI"]
• Enhanced property definitions with complete API documentation:
  • file: Notefile name to apply template
  • body: Sample JSON body with data type hints
  • length: Maximum payload length in bytes
  • verify: Returns current template when true
  • format: "compact" option for reduced metadata (required for LoRa/Starnote)
  • port: Required port number for LoRa/Starnote (1-100 range)
  • delete: Delete pending notes using template
• Added sub-descriptions for complex properties with SKU-specific details
• Added validation constraints (min/max values, enum validation)
• Added realistic samples from the documentation
• Removed incorrect template property (not in actual API)

Response Schema (note.template.rsp.notecard.api.json)

• Enhanced description explaining verify behavior
• Added complete response structure:
  • success: Operation success status
  • template: Current template body (when verify=true)
  • file: Notefile name (when verify=true)
  • length: Configured payload length (when verify=true)
  • format: Template format setting (when verify=true)
  • port: LoRa port assignment (when verify=true)
• Added comprehensive samples showing different response scenarios

Test Coverage

• Created test_note_template_req.py with 21 comprehensive tests
• Created test_note_template_rsp.py with 21 comprehensive tests
• All 42 tests pass and follow established repository patterns
• Tests cover all properties, edge cases, and validation scenarios

The schemas now capture all API information verbatim from the official documentation and follow the same comprehensive structure as other exemplary schemas in the repository.

Addresses #14.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[zakoverflow]

@copilot I updated your allowlist, please try again.

[Copilot]

@copilot I updated your allowlist, please try again.

Thanks for updating the allowlist! I can now access the blues.io domain via curl/wget and have downloaded the HTML, but the content appears to be client-side rendered. The playwright browser is still getting NET::ERR_BLOCKED_BY_CLIENT when trying to access the documentation page.

I can see from examining comprehensive schemas like card.attn that I need to add elements like skus, sub-descriptions, detailed property validations, and samples to the note.template schema files.

Could you help me get browser access working, or is there an alternative way to access the rendered note.template API documentation content?

@copilot I updated your allowlist, please try again.

Perfect! After updating the allowlist, I was able to successfully access the note.template API documentation and complete the comprehensive schema improvements.

Completed Work:

✅ Accessed Documentation: Successfully scraped content from https://dev.blues.io/api-reference/notecard-api/note-requests/latest/#note-template
✅ Enhanced Request Schema: Added all 7 documented properties with word-for-word descriptions
✅ Enhanced Response Schema: Added complete response structure with verify behavior
✅ Added Comprehensive Elements: skus, sub-descriptions, samples, detailed validations
✅ Created Test Suite: 42 comprehensive tests (21 req + 21 rsp) - all passing
✅ Version Updates: Bumped to v0.2.0 for both schemas

The schemas now follow the same comprehensive pattern as card.attn and preserve all API information verbatim from the documentation. See commit 94f49ee for the complete implementation.

[zakoverflow]

@copilot I have manually updated the schema to ensure it is correct. Review and understand the changes I have made, then correct the tests so that they are testing the new functionality.

[Copilot]

@copilot I have manually updated the schema to ensure it is correct. Review and understand the changes I have made, then correct the tests so that they are testing the new functionality.

I've reviewed the manual schema changes and updated the test suites accordingly. Key fixes made:

Request Tests: Fixed length minimum validation (now allows -1), removed format enum validation, and added 4 new tests for the port property with proper range validation (1-100).

Response Tests: Updated to validate template as boolean (not object) and fixed tests for undefined properties that now pass due to additionalProperties being allowed.

All 46 tests now pass correctly. See commit c85fb47 for the complete test updates.