chore(release): memory-core 0.2.0 - account vault + discover schema#15
Merged
Conversation
Prepare the config layer for the agentage account sync channel (V4).
- Export isAccountVault(entry): the reserved "agentage" origin is the
account channel sentinel (promoted from the internal isAgentage).
- Add discover[] to the config schema + types: optional discovery roots
{ path, autosync?, ignore? }. Shape only - the CLI daemon watches them.
- Add scanDiscoverRoots(config, deps?): pure, fs-injectable enumeration of
candidate account vaults in the flat account shape (path + agentage
origin + local mcp), filtering by vault-name rule, ignore, and
already-registered name/path; autosync:false -> interval 0.
- Publish the config JSON Schema: schema/vaults.schema.json (zod
toJSONSchema, committed + in the npm files whitelist) with a
generate-schema script and a drift test; export vaultsSchemaPath().
- README: account entry shape + discover[]. Version 0.1.3 -> 0.2.0.
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
1 participant
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.
What
Prepares the config layer for the agentage account sync channel (decision V4). Additive minor:
0.1.3 -> 0.2.0.Changes
isAccountVault(entry)- exported predicate; the reservedagentageorigin is the account-channel sentinel (promoted from the internalisAgentage). No new per-entry fields; an account vault is the existing flat shape{ path, origin: [{ remote: "agentage", interval? }] }.discover[]on the config schema +DiscoverRoottype - optional discovery roots{ path, autosync?=true, ignore?: string[] }. Validated and passed through; the watching/persistence lives in the CLI daemon.scanDiscoverRoots(config, deps?)- pure, fs-injectable helper that enumerates candidate account vaults in the account shape (path+agentageorigin +mcp:['local']), skipping names that fail the vault-name rule^[A-Za-z0-9_-]{1,64}$, areignored, or already match a registered vault by name or resolved path.autosync:false->interval:0. No writes.schema/vaults.schema.jsonderived from the live zod schema (buildVaultsJsonSchema,z.toJSONSchema), committed and added to the npmfileswhitelist.npm run generate-schemaregenerates it; a drift test deep-equals committed vs live so drift fails CI. Consumers resolve it viavaultsSchemaPath().vaultsDir/autodiscoverzero-config behavior untouched.discover[].New exports
isAccountVault,scanDiscoverRoots,DiscoverCandidate,ScanDeps,DiscoverRoot,isValidVaultName,VAULT_NAME_PATTERN,buildVaultsJsonSchema,vaultsSchemaPath,VAULTS_SCHEMA_FILENAME.Verification
npm run verifygreen locally: type-check + lint + format:check + build + 104 tests (89 pre-existing + 15 new).npm ciin sync.