Rename the gbrain starter pack to **Entity vault…#26
Merged
Conversation
…ain-compatible) (#1593) * feat(open-knowledge): rename gbrain starter pack to Entity vault (GBrain-compatible) Reposition the former `gbrain` starter pack as a human cockpit for GBrain-style Markdown brains rather than a GBrain reimplementation. - Breaking pre-release rename: canonical pack id is now `entity-vault` with no `gbrain` alias (`ok seed --pack gbrain` no longer resolves). - Display name "Entity vault (GBrain-compatible)" across pack picker, seed dialog, toast, and CLI list; PackId type mirrors + icon map updated. - Tighten dossier templates for GBrain-compatible parsing: document-level `title:`, explicit `--- timeline ---` sentinel, parseable `- **YYYY-MM-DD** | source | @author — … Confidence: …` bullets, and path-qualified `[[folder/slug|Label]]` links. - Rewrite workflow doc and move route `/workflows/gbrain` → `/workflows/entity-vault` (no redirect); update cross-links. - Add interop contract + power-user demo path; honest Markdown+Git interop, no deep GBrain integration implied. - Spec, report, evidence, and changeset included. * chore(open-knowledge): address PR review on entity-vault rename - Pin `original`/`transcript` template types in starter.test.ts expectedTypes (the `type: idea`→`type: original` change was previously untested). - Rename file-local `GBRAIN_*` consts → `ENTITY_VAULT_*` to match the pack id and sibling packs' `<PACK>_FOLDERS` naming (no behavior change). - Fix the entity-vault pack SKILL.md guidance contract: it no longer claims the convention is never repeated in document bodies (templates carry short inline reminders at point-of-use); the skill stays the canonical reference. - Add the `--- timeline ---` sentinel to the docs Compatibility details list. Declined (respecting prior decisions): keep the docs "Naming note" (D6) and no `/workflows/gbrain` redirect (D2); OkPackId 3-file dedup is pre-existing/out of scope. --------- GitOrigin-RevId: 31559509c8574fe24c7c66d322be46c53f76e560
…1617) Every Release run on inkeep/open-knowledge main fails at 'Publish to npm via Trusted Publishing' with: npm error code E422 ... PUT .../@inkeep%2fopen-knowledge - Error verifying sigstore provenance bundle: Failed to validate repository information: package.json: "repository.url" is "", expected to match "https://github.com/inkeep/open-knowledge" @inkeep/open-knowledge (packages/cli) is the only public package; the other five are private and skipped. Its package.json had no repository field, so npm could not match the publish against the GitHub Actions provenance claim and rejected it. The field was present (pointing at open-knowledge-legacy) until the mirror re-point removed it without restoring the new URL. Re-add repository pointing at inkeep/open-knowledge so provenance verification passes. This unblocks both the beta cadence (every push) and stable promotion publishes. GitOrigin-RevId: 96cb532a672a86c6575345f7cd017e14021cea27
![inkeep-internal-ci[bot]](https://avatars.githubusercontent.com/u/123133689?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Automated approval from agents-private public-mirror-sync (run: https://github.com/inkeep/agents-private/actions/runs/26923478433). Source of truth is the monorepo; direct edits on inkeep/open-knowledge are overwritten on next sync.
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rename the
gbrainstarter pack to Entity vault (GBrain-compatible) and reposition it as a human cockpit for GBrain-style Markdown brains rather than a GBrain reimplementation. This is a breaking pre-release rename: the canonical pack ID is nowentity-vaultwith nogbrainalias, sook seed --pack gbrainno longer resolves — useok seed --pack entity-vault. The pack picker, seed dialog, toast, and CLI list now show "Entity vault (GBrain-compatible)". Generated dossier templates are tightened for GBrain-compatible parsing — document-leveltitle:frontmatter, an explicit--- timeline ---sentinel, and parseable- **YYYY-MM-DD** | source | @author — … Confidence: …timeline bullets with path-qualified[[folder/slug|Label]]links. The workflow doc moved from/workflows/gbrainto/workflows/entity-vault. OK edits and reviews the Markdown; Garry Tan'sgbrain, if installed, can still import/sync the same vault — interop is Markdown + Git, with no deep integration implied.Restore the
repositoryfield on the published CLI package, pointing atinkeep/open-knowledge. It was dropped when the mirror was re-pointed offopen-knowledge-legacy, which left npm Trusted Publishing unable to verify provenance and failed every release publish withE422 ... "repository.url" is "".