forkit-connect 0.1.5 → 0.1.6

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.
package/QUICKSTART.md CHANGED
@@ -22,6 +22,8 @@ export PATH="$HOME/.local/bin:$PATH"
22
22
  ```bash
23
23
  forkit-connect init
24
24
  forkit-connect login
25
+ forkit-connect workspace select
26
+ forkit-connect runtime register
25
27
  forkit-connect scan
26
28
  forkit-connect inbox
27
29
  forkit-connect changes
@@ -33,15 +35,22 @@ forkit-connect start
33
35
 
34
36
  - `init` creates local Connect identity and privacy posture metadata.
35
37
  - `login` completes the device-login flow against Forkit.dev.
38
+ - `workspace select` binds the governed workspace/project lane when the account supports it.
39
+ - `runtime register` creates or reuses a governed runtime for the current repo/worktree and stores its runtime key locally.
36
40
  - `scan` detects supported local runtimes and AI models.
37
41
  - `inbox` shows what is ready to connect, what needs confirmation, and what is already connected.
38
42
  - `changes` shows the local evidence trail, runtime signal history, and anything still waiting to sync.
39
43
  - `status` summarizes readiness, daemon state, discovery counts, and next recommended action.
40
- - `start` launches the daemon loop for continued local discovery and sync preparation.
44
+ - `start` launches the daemon loop for continued runtime observation, check-ins, and sync preparation.
41
45
 
42
46
  ## Useful Next Commands
43
47
 
48
+ - `forkit-connect scan` — detect supported local runtimes and AI models
49
+ - `forkit-connect inbox` — review what is ready to connect or already connected
50
+ - `forkit-connect changes` — inspect local evidence and runtime signal history
44
51
  - `forkit-connect connect <modelNameOrDiscoveryHash>` — prepare or sync a Passport draft for a detected model
52
+ - `forkit-connect runtime observe --gaid <gaid>` — emit one repo-scoped runtime journal immediately
53
+ - `forkit-connect runtime register --dry-run --json` — inspect the runtime payload before creating it
45
54
  - `forkit-connect daemon status` — inspect daemon state
46
55
  - `forkit-connect pulse status` — inspect best-effort local runtime telemetry
47
56
  - `forkit-connect agent review` — inspect detected local AI agents
package/README.md CHANGED
@@ -60,6 +60,8 @@ If `~/.local/bin` is already on your `PATH`, the command is immediately accessib
60
60
  - `forkit-connect login` — link this device to Forkit.dev with the device flow
61
61
  - `forkit-connect scan` — discover local runtimes and AI models
62
62
  - `forkit-connect inbox` — review the Smart Registration Inbox
63
+ - `forkit-connect runtime register` — register or reuse the current repo/worktree as a governed runtime
64
+ - `forkit-connect runtime observe --gaid <gaid>` — emit a repo-scoped runtime journal for the current runtime target
63
65
  - `forkit-connect status` — show public Connect readiness status
64
66
  - `forkit-connect changes` — view collected local evidence, runtime signal history, and pending sync items
65
67
  - `forkit-connect start` — start the local daemon loop
@@ -70,7 +72,16 @@ If `~/.local/bin` is already on your `PATH`, the command is immediately accessib
70
72
 
71
73
  ## Advanced Commands
72
74
 
73
- Advanced flows remain available under the same binary, including `connect`, `review`, `daemon`, `config`, `pulse`, `c2`, `train`, `agent`, and notification utilities.
75
+ Advanced flows remain available under the same binary, including `connect`, `review`, `daemon`, `config`, `pulse`, `c2`, `train`, `agent`, notification utilities, and runtime target management.
76
+
77
+ Runtime registration notes:
78
+
79
+ ```bash
80
+ forkit-connect runtime register --workspace <workspaceId> --project <projectId>
81
+ forkit-connect runtime register --dry-run --json
82
+ ```
83
+
84
+ The command infers the current repo/worktree, records safe runtime identity metadata, and reuses the same governed runtime on repeat runs instead of creating duplicates.
74
85
 
75
86
  Useful notification diagnostics:
76
87