When a node is created in a namespace, the namespace now owns it rather than the creator. This allows namespaces to manage content ownership. Namespace nodes themselves remain owned by their creator. Users retain transitive ownership through their default namespace: user→has_ownership→namespace→has_ownership→node.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Create a special _global namespace that every new user automatically
gets can_create_rel access to (inclusive of can_read). This provides
a shared space where all users can see and interact with published nodes.
- ensureGlobalNamespace creates _global on first use with self-ownership
- ensureUser grants can_create_rel to each new user on the global namespace
- User visibility still relies on existing post-BFS global readability
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- --due: show only nodes with a due date set
- --due-within N: show only nodes due within N days (includes overdue)
Implemented in service layer with post-fetch filtering, threaded through
API client and server, and exposed via CLI flags.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
The condition was backwards — it exited with "database already exists"
when the file was found, and tried to open it when it did not exist.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
eliaskohout