openplanr 2.0.0 → 2.0.1
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/CHANGELOG.md +5 -0
- package/docs/CLI.md +14 -2
- package/lib/host-packages/claude/openplanr/.openplanr-content.json +2 -2
- package/lib/host-packages/claude/openplanr/skills/artifact/references/company-review.md +1 -1
- package/lib/host-packages/cursor/openplanr/.openplanr-content.json +2 -2
- package/lib/host-packages/cursor/openplanr/rules/planr-artifact/references/company-review.md +1 -1
- package/lib/host-packages/openai/openplanr/.openplanr-content.json +2 -2
- package/lib/host-packages/openai/openplanr/skills/artifact/references/company-review.md +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,10 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 2.0.1
|
|
4
|
+
### Patch Changes
|
|
5
|
+
|
|
6
|
+
- 17bcd1d: Present `planr company login` as the standard hosted sign-in command, with structured output and endpoint overrides documented only for automation and advanced environments.
|
|
7
|
+
|
|
3
8
|
## 2.0.0
|
|
4
9
|
### Major Changes
|
|
5
10
|
|
package/docs/CLI.md
CHANGED
|
@@ -59,9 +59,21 @@ These options apply to **all** commands:
|
|
|
59
59
|
The company route connects an explicitly configured workspace to selected local artifacts. Existing encrypted token shares remain separate. Sign in through the browser and choose the organization in the identity provider's consent screen:
|
|
60
60
|
|
|
61
61
|
```bash
|
|
62
|
-
planr company login
|
|
62
|
+
planr company login
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
The normal customer flow needs no service URL or output flag. For a remote or
|
|
66
|
+
headless session, print the authorization URL instead of launching it:
|
|
67
|
+
|
|
68
|
+
```bash
|
|
63
69
|
# Print the browser URL instead of launching it; open it on this same computer
|
|
64
|
-
planr company login --no-open --timeout 300
|
|
70
|
+
planr company login --no-open --timeout 300
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
Structured output is available for automation:
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
planr company login --json
|
|
65
77
|
planr company logout --json
|
|
66
78
|
```
|
|
67
79
|
|
|
@@ -156,7 +156,7 @@
|
|
|
156
156
|
},
|
|
157
157
|
{
|
|
158
158
|
"path": "skills/artifact/references/company-review.md",
|
|
159
|
-
"digest": "sha256:
|
|
159
|
+
"digest": "sha256:b31bb74501fd24ae388294a4ccf2b9161b128f0288b2fb03c99a762595e0eaba"
|
|
160
160
|
},
|
|
161
161
|
{
|
|
162
162
|
"path": "skills/artifact/references/design-sharing.md",
|
|
@@ -1175,5 +1175,5 @@
|
|
|
1175
1175
|
"digest": "sha256:53698324b62f43b672ce8fe1654c526c96fb202e313442f09c6fc1e72268677e"
|
|
1176
1176
|
}
|
|
1177
1177
|
],
|
|
1178
|
-
"contentDigest": "sha256:
|
|
1178
|
+
"contentDigest": "sha256:c1b06c3114328d0ba09d37c91479fff338aa0a9dc4e41aa78eacc4253e513998"
|
|
1179
1179
|
}
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
Use this route only for an explicitly configured company workspace. Existing `planr artifact share/publish/sync` token shares keep their separate encryption and authorization model. Never silently import a token share into company storage.
|
|
4
4
|
|
|
5
5
|
1. Read `planr company --help`. If this command is absent, report the actual installed CLI path/version and required local build; do not search the disk for runtime internals or silently install a public release.
|
|
6
|
-
2. Start browser sign-in with `planr company login
|
|
6
|
+
2. Start browser sign-in with `planr company login`; use `--no-open` to display its authorization URL and open it on the same computer. Add `--json` only when an automated caller needs the structured completion receipt. The hosted CLI uses `https://api.openplanr.dev` by default; `--api-url <origin>` is an advanced development, staging, or self-hosted override. The company service must advertise a configured public OAuth client. Choose the organization in the issuer's consent screen. The CLI stores renewable credentials in the OS keychain, or discloses its existing encrypted local-file fallback. Never print tokens, place them in arguments/URLs, or ask for them in chat. Tokens renew automatically; revoked access still fails closed. `company connect --token-stdin` and `PLANR_COMPANY_TOKEN` remain explicit developer fallbacks without automatic renewal.
|
|
7
7
|
3. List authorized projects with `planr company projects --json`. Actor and organization come from the verified token; identifiers in a request never establish permission.
|
|
8
8
|
4. For a user-requested publication, `planr company preview <repository-relative-file> --project <id> --kind diagram|design|plan|document --json` records the exact selected file, bytes, size and digest. Show the publication scope. `planr company publish <preview-id> --json` explicitly publishes that preview. Content becomes accessible to the managed company service; source code and unselected files stay local. No hidden recursive upload.
|
|
9
9
|
5. Inspect synchronization with `planr company status <binding-id> --json`. Update the same artifact using `planr company push <binding-id> --preview --json`, review the changed scope/content, then `planr company push <binding-id> --json`. Conflicts are comparisons to resolve, not permission to force overwrite.
|
|
@@ -16,7 +16,7 @@
|
|
|
16
16
|
},
|
|
17
17
|
{
|
|
18
18
|
"path": "rules/planr-artifact/references/company-review.md",
|
|
19
|
-
"digest": "sha256:
|
|
19
|
+
"digest": "sha256:b31bb74501fd24ae388294a4ccf2b9161b128f0288b2fb03c99a762595e0eaba"
|
|
20
20
|
},
|
|
21
21
|
{
|
|
22
22
|
"path": "rules/planr-artifact/references/design-sharing.md",
|
|
@@ -935,5 +935,5 @@
|
|
|
935
935
|
"digest": "sha256:6378ad3477e4be8b7e916c4249404c50cafecac1c70ffbf5a1a2fce195dfea16"
|
|
936
936
|
}
|
|
937
937
|
],
|
|
938
|
-
"contentDigest": "sha256:
|
|
938
|
+
"contentDigest": "sha256:15a50665d6a4de0b618f3e46c86323a336e193596a8a9de7b6c634614ed1aced"
|
|
939
939
|
}
|
package/lib/host-packages/cursor/openplanr/rules/planr-artifact/references/company-review.md
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
Use this route only for an explicitly configured company workspace. Existing `planr artifact share/publish/sync` token shares keep their separate encryption and authorization model. Never silently import a token share into company storage.
|
|
4
4
|
|
|
5
5
|
1. Read `planr company --help`. If this command is absent, report the actual installed CLI path/version and required local build; do not search the disk for runtime internals or silently install a public release.
|
|
6
|
-
2. Start browser sign-in with `planr company login
|
|
6
|
+
2. Start browser sign-in with `planr company login`; use `--no-open` to display its authorization URL and open it on the same computer. Add `--json` only when an automated caller needs the structured completion receipt. The hosted CLI uses `https://api.openplanr.dev` by default; `--api-url <origin>` is an advanced development, staging, or self-hosted override. The company service must advertise a configured public OAuth client. Choose the organization in the issuer's consent screen. The CLI stores renewable credentials in the OS keychain, or discloses its existing encrypted local-file fallback. Never print tokens, place them in arguments/URLs, or ask for them in chat. Tokens renew automatically; revoked access still fails closed. `company connect --token-stdin` and `PLANR_COMPANY_TOKEN` remain explicit developer fallbacks without automatic renewal.
|
|
7
7
|
3. List authorized projects with `planr company projects --json`. Actor and organization come from the verified token; identifiers in a request never establish permission.
|
|
8
8
|
4. For a user-requested publication, `planr company preview <repository-relative-file> --project <id> --kind diagram|design|plan|document --json` records the exact selected file, bytes, size and digest. Show the publication scope. `planr company publish <preview-id> --json` explicitly publishes that preview. Content becomes accessible to the managed company service; source code and unselected files stay local. No hidden recursive upload.
|
|
9
9
|
5. Inspect synchronization with `planr company status <binding-id> --json`. Update the same artifact using `planr company push <binding-id> --preview --json`, review the changed scope/content, then `planr company push <binding-id> --json`. Conflicts are comparisons to resolve, not permission to force overwrite.
|
|
@@ -20,7 +20,7 @@
|
|
|
20
20
|
},
|
|
21
21
|
{
|
|
22
22
|
"path": "skills/artifact/references/company-review.md",
|
|
23
|
-
"digest": "sha256:
|
|
23
|
+
"digest": "sha256:b31bb74501fd24ae388294a4ccf2b9161b128f0288b2fb03c99a762595e0eaba"
|
|
24
24
|
},
|
|
25
25
|
{
|
|
26
26
|
"path": "skills/artifact/references/design-sharing.md",
|
|
@@ -1135,5 +1135,5 @@
|
|
|
1135
1135
|
"digest": "sha256:53698324b62f43b672ce8fe1654c526c96fb202e313442f09c6fc1e72268677e"
|
|
1136
1136
|
}
|
|
1137
1137
|
],
|
|
1138
|
-
"contentDigest": "sha256:
|
|
1138
|
+
"contentDigest": "sha256:9b8e5e10a08322fccc23c4e70de4487ab5b22295720925505a0d0ddc551d3d02"
|
|
1139
1139
|
}
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
Use this route only for an explicitly configured company workspace. Existing `planr artifact share/publish/sync` token shares keep their separate encryption and authorization model. Never silently import a token share into company storage.
|
|
4
4
|
|
|
5
5
|
1. Read `planr company --help`. If this command is absent, report the actual installed CLI path/version and required local build; do not search the disk for runtime internals or silently install a public release.
|
|
6
|
-
2. Start browser sign-in with `planr company login
|
|
6
|
+
2. Start browser sign-in with `planr company login`; use `--no-open` to display its authorization URL and open it on the same computer. Add `--json` only when an automated caller needs the structured completion receipt. The hosted CLI uses `https://api.openplanr.dev` by default; `--api-url <origin>` is an advanced development, staging, or self-hosted override. The company service must advertise a configured public OAuth client. Choose the organization in the issuer's consent screen. The CLI stores renewable credentials in the OS keychain, or discloses its existing encrypted local-file fallback. Never print tokens, place them in arguments/URLs, or ask for them in chat. Tokens renew automatically; revoked access still fails closed. `company connect --token-stdin` and `PLANR_COMPANY_TOKEN` remain explicit developer fallbacks without automatic renewal.
|
|
7
7
|
3. List authorized projects with `planr company projects --json`. Actor and organization come from the verified token; identifiers in a request never establish permission.
|
|
8
8
|
4. For a user-requested publication, `planr company preview <repository-relative-file> --project <id> --kind diagram|design|plan|document --json` records the exact selected file, bytes, size and digest. Show the publication scope. `planr company publish <preview-id> --json` explicitly publishes that preview. Content becomes accessible to the managed company service; source code and unselected files stay local. No hidden recursive upload.
|
|
9
9
|
5. Inspect synchronization with `planr company status <binding-id> --json`. Update the same artifact using `planr company push <binding-id> --preview --json`, review the changed scope/content, then `planr company push <binding-id> --json`. Conflicts are comparisons to resolve, not permission to force overwrite.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "openplanr",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.1",
|
|
4
4
|
"description": "Deterministic OpenPlanr utilities for planning storage, validation, rendering, setup, diagnostics, and GitHub/Linear synchronization",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/cli/index.js",
|