@tinchu0/knitt 0.1.0-beta.1 → 0.1.0-beta.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,25 +1,25 @@
1
1
  # npm installation and runtime lifecycle
2
2
 
3
- ## Try the unpublished release candidate
3
+ ## Install the npm preview
4
4
 
5
- Build and pack from the repository:
5
+ Run the published CLI:
6
6
 
7
7
  ```bash
8
- npm ci
9
- npm run check
10
- npm run build
11
- npm pack
8
+ npx @tinchu0/knitt@latest setup \
9
+ --workspace /path/to/project --client codex --client claude-code
12
10
  ```
13
11
 
14
- Then use the tarball (absolute paths work from any directory):
12
+ Add `--capture-new-sessions` to opt into independent local conversation histories and checkpoint-first handoffs. Version `0.1.0-beta.2` remains a preview. Both `latest` and `next` track the current preview release.
13
+
14
+ To test a source checkout before publication, run `npm ci`, `npm run check`, `npm run build` and `npm pack`, then install its exact artifact:
15
15
 
16
16
  ```bash
17
- npx --yes --package ./tinchu0-knitt-0.1.0-beta.1.tgz knitt setup \
17
+ npx --yes --package ./tinchu0-knitt-0.1.0-beta.2.tgz knitt setup \
18
18
  --workspace /path/to/project --client codex --client claude-code \
19
- --package /absolute/path/to/tinchu0-knitt-0.1.0-beta.1.tgz
19
+ --package /absolute/path/to/tinchu0-knitt-0.1.0-beta.2.tgz
20
20
  ```
21
21
 
22
- The outer `--package` tells npx which CLI to run. The `--package` after `setup` tells setup which exact artifact to install persistently. Before registry publication this second argument is required for applying setup; preview can run without it. The release candidate is configured for registry publication; until it is published, pass the explicit tarball to setup/update. After publication, omitting the internal package argument installs the CLI's exact published version. `update` follows the `next` registry tag for prerelease CLIs and `latest` for stable CLIs.
22
+ The outer `--package` selects the CLI; the `--package` after `setup` selects the artifact to install persistently. Without that inner option, setup installs the CLI's exact published version. `update` follows `next` for prerelease CLIs and `latest` for stable CLIs.
23
23
 
24
24
  Use `--preview` to inspect changes without creating installation/configuration files. Interactive setup asks before applying; automation must pass `--yes`. Repeat `--client` for several agents. Setup requires Git repository metadata to derive a stable repository identity.
25
25
 
@@ -38,7 +38,7 @@ The project-local `.memory/npm-connection.json` records original and generated s
38
38
 
39
39
  ## Commands
40
40
 
41
- Run commands through the tarball CLI above (or the eventual published package):
41
+ Run commands through `npx @tinchu0/knitt@latest` or the tarball CLI above:
42
42
 
43
43
  ```text
44
44
  knitt setup --workspace PATH --client codex --preview
@@ -57,6 +57,11 @@ Uninstall restores unchanged managed values and preserves independent additions
57
57
 
58
58
  ## Release gates
59
59
 
60
- The selected package is `@tinchu0/knitt`, owned by the intended npm account `tinchu0`. A registry lookup returned no public package on 2026-11-13; Terminal login as `tinchu0` is verified. Version `0.1.0-beta.1` is prepared with public access and the `next` tag; actual publication is still pending. Knitt is licensed under Apache-2.0; the LICENSE file ships in the npm package. Native Windows setup deliberately fails rather than writing POSIX hook commands. Linux tarball checks are the current local verification target; macOS/Windows live client behavior remains unverified.
60
+ The package is `@tinchu0/knitt`, published under npm account `tinchu0`, with Apache-2.0 licensing. The LICENSE file ships in the npm archive. Release `0.1.0-beta.2` includes opt-in local conversation memory. Native Windows setup deliberately fails rather than writing POSIX hook commands. Linux tarball checks are the local verification target; macOS/Windows live client behavior remains unverified.
61
61
 
62
62
  ChatGPT, Claude web and teammate machines require a separately reachable authenticated service. Packaging a CLI does not supply hosting, authentication accounts or background synchronization.
63
+
64
+
65
+ ### Optional local conversation mode
66
+
67
+ Add `--capture-new-sessions` to setup to opt a connected project into independent session capture and explicit continuation links. The preference survives subsequent setup/update operations. Existing connections keep their previous semantics until opted in. This mode upgrades the database using consistent SQLite backups; the updated installer blocks incompatible runtime downgrade rather than restoring data automatically. Use `doctor` for content-free capture status. See [setup and recovery](local-agent-memory.md).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tinchu0/knitt",
3
- "version": "0.1.0-beta.1",
3
+ "version": "0.1.0-beta.2",
4
4
  "type": "module",
5
5
  "engines": {
6
6
  "node": ">=24"
@@ -36,7 +36,8 @@
36
36
  "README.md",
37
37
  "docs/clients/connector-setup.md",
38
38
  "docs/clients/npm-installation.md",
39
- "LICENSE"
39
+ "LICENSE",
40
+ "docs/clients/local-agent-memory.md"
40
41
  ],
41
42
  "repository": {
42
43
  "type": "git",
@@ -45,7 +46,7 @@
45
46
  "description": "Shared conversation memory for coding agents",
46
47
  "publishConfig": {
47
48
  "access": "public",
48
- "tag": "next"
49
+ "tag": "latest"
49
50
  },
50
51
  "license": "Apache-2.0"
51
52
  }