v1.1.0

[diggy]

What's Changed

• Add docs dir with project knowledge and prompt templates by @diggy in Add docs dir with project knowledge and prompt templates #3
• Update README.md with "Prompting" section by @diggy in Update README.md with "Prompting" section #4
• Create LICENSE by @diggy in Create LICENSE #6
• 2025-04-22_diggy_fix-semantic-linking-and-add-tests by @diggy in 2025-04-22_diggy_fix-semantic-linking-and-add-tests #10
• 2025-04-22_diggy_bump-version-to-1.1.0 by @diggy in 2025-04-22_diggy_bump-version-to-1.1.0 #11
• v1.1.0 by @diggy in v1.1.0 #12

Full Changelog: v1.0.0...v1.1.0

---

This discussion was created from the release v1.1.0.

---

• This release fixes a bug with semantic link types (get_linked_notes displays all link types as 'reference' regardless of actual semantic type #8, reported by @matt-edmondson), and extends the test suite wrt semantic linking

---

Verification of Zettelkasten MCP Server Link Type Issues

I'll systematically test the fixes by creating notes, establishing semantic links, and then verifying the correct display of link types through both functions.

...

Confirmation of Issue Resolution

Both issues have been successfully resolved:

1. Issue 1 (Incorrect Link Types): The zk_get_linked_notes tool now correctly displays the semantic link types. This confirms that the fix for the link parsing in _parse_note_from_markdown is working correctly, properly extracting and interpreting the link types from the markdown content.

2. Issue 2 (Duplicate Links Section): The zk_get_note tool now displays a single "## Links" section with the correct semantic links. This confirms that the duplicate links section issue has been fixed - the function is no longer adding a redundant links section to the note content.

The bidirectional semantic link types are also working correctly:

• When note A "extends" note B, note B shows "extended_by" for the link back to note A
• When note A "contradicts" note B, note B shows "contradicted_by" for the link back to note A
• When note A "supports" note B, note B shows "supported_by" for the link back to note A

This thorough testing confirms that both issues have been completely resolved.

---

I've created a comprehensive test suite for the semantic link types functionality in the Zettelkasten MCP implementation. This test file provides exhaustive coverage of the various aspects of semantic link handling across different layers of the application.

Key Areas Covered in the Test Suite

The test suite thoroughly examines:

1. Basic Link Type Operations

   • Creation of all semantic link types (reference, extends, refines, contradicts, etc.)
   • Verification that link types are stored and retrieved correctly
   • Testing for unique constraints on link types between the same note pairs

2. Bidirectional Link Semantics

   • Creation of bidirectional links with proper semantic inverses
   • Verification that each link pair follows the correct semantic relationship
   • Handling of symmetric relationships like "reference" and "related"

3. Link Persistence

   • Verification that link types persist correctly through save and load operations
   • Testing of link data integrity throughout the application lifecycle
   • Proper parsing of semantic links from markdown content

4. Link Modification and Removal

   • Updating existing links with new types or descriptions
   • Removing specific link types between notes
   • Bidirectional link removal

5. Advanced Usage Patterns

   • Multiple different link types between the same notes
   • Cycles of semantic links between notes
   • Link type reporting in search results and similarity functions

6. MCP Tool Integration

   • Testing the zk_get_linked_notes tool to verify correct semantic type display
   • Testing the zk_create_link tool for proper semantic link creation
   • Verification of correct bidirectional link creation through MCP tools

This test suite ensures that semantic link types function correctly throughout the entire system, from the database layer through to the MCP server interface. Running these tests will validate that links maintain their semantic meaning at every step of processing.

The tests also provide valuable regression protection, ensuring that future code changes don't inadvertently break the semantic link functionality that has been fixed.