clawnify 0.21.0 → 0.22.0
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/README.md
CHANGED
|
@@ -111,6 +111,7 @@ clawnify ai-files install # Install rules + skills + MCP into your agen
|
|
|
111
111
|
clawnify ai-files uninstall # Remove them
|
|
112
112
|
clawnify workspace # The org's workspace repo, what maps where, how to edit locally
|
|
113
113
|
clawnify workspace clone [dir] # Clone the org's Clawnify git repo (see below)
|
|
114
|
+
clawnify knowledge pull [dir] # Company Knowledge as markdown in knowledge/ (see below)
|
|
114
115
|
```
|
|
115
116
|
|
|
116
117
|
## Workspace repo
|
|
@@ -119,6 +120,24 @@ An org's apps and website live in one git repo: Clawnify git, or GitHub if the o
|
|
|
119
120
|
|
|
120
121
|
`clawnify workspace clone` clones Clawnify git and sets git, in that clone only, to sign in with your Clawnify login, so `git pull` and `git push` need no token. Any member can clone; owners and admins push, and a push rebuilds only the folders it changed. CI and other tools without a login use an access token (Settings, Access tokens) as the password: `read` to clone, `write` to push.
|
|
121
122
|
|
|
123
|
+
The clone also gets the org's Company Knowledge on disk, so a coding agent can read it beside the code: `knowledge/` is added to `.gitignore`, pulled, and refreshed after each `git pull` by a `post-merge` hook (a pull with `--rebase` does not run it).
|
|
124
|
+
|
|
125
|
+
## Company Knowledge on disk
|
|
126
|
+
|
|
127
|
+
```bash
|
|
128
|
+
clawnify knowledge pull # published documents → knowledge/ at the workspace root
|
|
129
|
+
clawnify knowledge pull --files # also the original Company files, in knowledge/files/
|
|
130
|
+
clawnify knowledge pull --project <id> # a Project's sources → knowledge/projects/<name>/
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
Every published document becomes a markdown file, in folders that follow its folder in Clawnify, with frontmatter carrying its `id`, `title`, `version`, `edit_revision` and `body_sha256`. The folder is a read-only copy: change documents in Clawnify, where they are reviewed and published.
|
|
134
|
+
|
|
135
|
+
- **Incremental.** Each pull lists only ids and revisions, so a document that has not changed since the last pull is neither downloaded nor written again. `.clawnify-knowledge.json` in the folder records what the pull wrote.
|
|
136
|
+
- **Your edits are kept.** A file changed since the last pull is left as it is and reported, never overwritten. `--strict` makes that exit non-zero.
|
|
137
|
+
- **Removals.** A document unpublished or deleted in Clawnify has its file removed, unless you changed that file. Files the pull did not write are never touched.
|
|
138
|
+
- **Never committed.** The pull refuses a folder inside a git repository that git does not ignore, or one holding committed files.
|
|
139
|
+
- **One org per folder.** The pull refuses a folder bound to another org: by the workspace's `clawnify.json`, a Clawnify git remote, or an earlier pull. `--org` cannot override that.
|
|
140
|
+
|
|
122
141
|
## Websites
|
|
123
142
|
|
|
124
143
|
`clawnify init --type website` scaffolds a minimal Astro project:
|
|
@@ -658,7 +658,7 @@ async function pollUntilReady(resourceId, options = {}) {
|
|
|
658
658
|
}
|
|
659
659
|
|
|
660
660
|
// src/version.ts
|
|
661
|
-
var VERSION = "0.
|
|
661
|
+
var VERSION = "0.22.0";
|
|
662
662
|
|
|
663
663
|
export {
|
|
664
664
|
OAUTH_CLIENT_ID,
|
|
@@ -673,6 +673,7 @@ export {
|
|
|
673
673
|
readManifest,
|
|
674
674
|
manifestKind,
|
|
675
675
|
readProject,
|
|
676
|
+
findProjectRoot,
|
|
676
677
|
saveProject,
|
|
677
678
|
readWorkspaceConfig,
|
|
678
679
|
findWorkspaceRoot,
|