threadnote 1.1.3 → 1.1.5

package/docs/share.md

@@ -194,12 +194,15 @@ threadnote share sync --team friends   # other team
 threadnote share sync --no-push        # pull only
 ```
 
-`share sync` will auto-commit any uncommitted edits in the worktree, fetch and
-rebase from the remote, reindex pulled markdown files into OpenViking (so
-`recall` finds them immediately), and push. Pass `--no-auto-commit` to refuse
-syncing when the worktree is dirty. Automatic recall/read sync never commits a
-dirty shared worktree; it warns and leaves that case for explicit
-`threadnote share sync`.
+`share sync` will auto-commit edits in Threadnote-managed share paths, fetch and
+rebase onto the configured upstream, reindex pulled markdown files into
+OpenViking (so `recall` finds them immediately), and push. Managed share paths
+are root guidance/metadata files (`README.md`, `AGENTS.md`, `CLAUDE.md`,
+`SKILL.md`, `.gitignore`) plus `durable/` and `agent-artifacts/`. If other dirty
+files remain after staging those paths, sync stops before rebase so you can
+commit, remove, or ignore them. Pass `--no-auto-commit` to refuse syncing when
+the worktree is dirty. Automatic recall/read sync never commits a dirty shared
+worktree; it warns and leaves that case for explicit `threadnote share sync`.
 
 ### Take a memory back
 
@@ -280,8 +283,8 @@ updates the git `origin` URL and verifies it with `git fetch`.
 
 ## Conflict resolution
 
-`share sync` uses `git pull --rebase` against the remote. When git can't merge
-cleanly:
+`share sync` fetches the remote, then rebases onto the branch's configured
+upstream. When git can't merge cleanly:
 
 1. The pull command reports the conflict and leaves the worktree in a
    rebase-in-progress state.

package/docs/troubleshooting.md

@@ -8,7 +8,9 @@ Run:
 threadnote install
 ```
 
-The installer prefers `uv`, then `pipx`, then `python3 -m pip install --user`.
+The installer prefers `uv`, then `pipx`, then `python3 -m pip install --user`. For `curl | sh` installs, the wrapper
+reattaches `threadnote install` to your terminal when possible so it can prompt to install `uv` and continue instead of
+falling straight through to the pip fallback.
 
 ## `uv` Fails With `UnknownIssuer`
 
@@ -83,8 +85,14 @@ For detached starts, logs are written to:
 ~/.openviking/logs/server.log
 ```
 
-If `start` reports that OpenViking did not become healthy, open that log. Certificate failures during the first embedding
-model download are covered above.
+If `start` reports that OpenViking did not become healthy, first check whether it finished shortly after the timeout:
+
+```bash
+threadnote doctor --dry-run
+```
+
+If it still is not healthy, open that log. Certificate failures during the first embedding model download are covered
+above.
 
 ## Port Already In Use
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "threadnote",
-  "version": "1.1.3",
+  "version": "1.1.5",
   "type": "commonjs",
   "main": "dist/threadnote.cjs",
   "description": "Shared local context and handoffs for development agents",

package/scripts/install.sh

@@ -116,7 +116,11 @@ install_package "$runtime"
 threadnote_bin="$(find_threadnote "$runtime")" || die "Installed $PACKAGE, but could not find the threadnote command."
 
 say "Running threadnote install"
-"$threadnote_bin" install "$@"
+if { true </dev/tty; } 2>/dev/null; then
+  "$threadnote_bin" install "$@" </dev/tty
+else
+  "$threadnote_bin" install "$@"
+fi
 
 if ! have threadnote; then
   say ""