Skip to content

Test(contracts): verify shared task and self-hosted HTTP behavior - #2

Merged
adibhanna merged 3 commits into
mainfrom
refactor/ecosystem-boundaries-pr
Sep 16, 2026
Merged

adibhanna merged 3 commits into
mainfrom
refactor/ecosystem-boundaries-pr

Conversation

@adibhanna

@adibhanna adibhanna commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Summary

Add versioned behavior fixtures so the TUI can evolve independently while retaining compatible Markdown task parsing and self-hosted HTTP behavior.

  • Verify exact task round trips, including date/time-zone edge cases.
  • Exercise authentication, note read/write, invalid paths, and legacy/current API routes at root and prefixed mounts against a real Go server.
  • Record fixture provenance and how to run the optional server contract suite.

The TUI's runtime implementation and release configuration are unchanged.

Validation

  • Full Go test suite, go vet ./..., and binary build.
  • Real-server contracts pass with ZENNOTES_SERVER_CONTRACT_BINARY pointing to the extracted Go candidate containing the v2.50.4 fixes.

Companion work in ZenNotes owns the shared fixtures and prepares the znserver extraction. This PR can be reviewed independently of the later server publication/cutover.

Related boundary PRs

Add versioned behavior fixtures so the TUI can evolve independently while retaining compatible Markdown task parsing and self-hosted HTTP behavior.

- Verify exact task round trips, including date/time-zone edge cases.
- Exercise authentication, note read/write, invalid paths, and legacy/current API routes at root and prefixed mounts against a real Go server.
- Record fixture provenance and how to run the optional server contract suite.

The TUI's runtime implementation and release configuration are unchanged.
The shared task and HTTP fixtures are checksummed against provenance
recorded from the main repository. Git for Windows converts them to CRLF on
checkout, so both contract tests reported a checksum mismatch on the Windows
runner while Linux and macOS passed. Pin the fixture directories to LF so
every platform hashes the same bytes.
docs/desktop-integration.md shipped with v0.2.0 and explains the creation
metadata format, client compatibility and rollback behavior, but the README
never linked it. A short subsection now says what desktop-managed commands
and zn tui each follow and where the details live.
@adibhanna
adibhanna force-pushed the refactor/ecosystem-boundaries-pr branch from ee7aa64 to 37dc3f3 Compare September 16, 2026 22:45
@adibhanna
adibhanna marked this pull request as ready for review September 16, 2026 22:45
@adibhanna
adibhanna merged commit 37dc3f3 into main Sep 16, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant