Audited and corrected wiki docs against the codebase
Audited every wiki page against the actual code, smoke tests, and in-repo
docs, then fixed the verified inaccuracies. The cross-cutting corrections:
the MCP HTTP port (3747 to 3475), the real MCP tool names (list_media_files,
search_media_files, etc.), removal of commands and flags that do not exist
(secrets delete to remove, the bogus secrets import --public-key, psi geocode),
and the config file names (databases.json/desktop.json to .toml). Also
clarified that S3 credentials live in the secrets vault or AWS_* env vars and
are never stored in a toml file.
Reworked the larger pages: Command-Reference gained the missing commands
(mcp, news, hash-cache) and corrected flag names, while internal-only items
were kept out (the debug REST API option, the debug tools group, clear-cache,
and the orphan commands). Database-Code had a fabricated IPsi/Psi section
removed and its package paths corrected (packages/api to packages/node-api).
Claude-Integration and How-It-Works dropped hard tool counts so they will not
need updating on every tool change.
Restructured the getting-started guides for non-developers: removed the
build-from-source section and all CLI references from the desktop guide, added
a "Where to store your database" section recommending a local-primary,
cloud-replica, partial-on-constrained-devices strategy with a mermaid diagram,
and pointed cloud storage at the existing configuration doc (which already
carries the DigitalOcean Spaces recommendation). Added two new developer pages,
Building-From-Source-CLI and Building-From-Source-Desktop, with commands taken
from the real package.json scripts.
Finally, stripped every em dash from all wiki pages to match the project's
style rule (bold definition lists became colons, other em dashes became
commas). The legacy database-format checksum wording was left as-is because it
could not be verified against the now-removed v5 source, and the unfinished
Overview-Summary-Draft page was deleted.
Updated Managing-Secrets.md for new vault format and inferred secret names
- Removed claims about auto-generated 8-char IDs.
- Corrected the `psi secrets import` description: only a private-key
file is read, the secret name is derived from the filename, no
`.key.pub` is consulted.
- Refreshed example secret names from `abc12345` to `production-key`.
- Fixed an outdated fuzzy-match example flag (`--key` →
`--encryption-key`).
- Documented the new inline-create name inference for `psi dbs add`
(`<dbname>:s3` / `<dbname>:encryption` / `<dbname>:geocoding`).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Updated doc to match latest code.
Fix stale shared: prefix in secrets command examples
- Remove shared: prefix from all psi secrets view/edit/delete/send
examples in Command-Reference.md and Managing-Secrets.md — vault
secret names are now plain identifiers (e.g. abc12345)
- Update --s3-cred-id/--encryption-key-id/--geocoding-key-id option
descriptions from "secret ID" to "vault secret name" to match the
new terminology
Update docs for credential resolution redesign
Reflects changes made to the code:
- -k / --key and PSI_ENCRYPTION_KEY now accept a file path or vault
secret name (not just file paths); document both and their priority
order
- PSI_ENCRYPTION_KEY added to env var tables in Configuration-CLI and
Command-Reference
- Secret naming convention updated: the shared: prefix has been removed;
database-linked secrets are now stored as plain 8-char alphanumeric
names (e.g. abc12345, not shared:abc12345)
- Keychain and plaintext vault examples updated to match (psi-s3test01,
abc12345.json)
- databases.json field names updated: encryptionKeyId → encryptionKey,
s3CredentialId → s3Key, geocodingKeyId → geocodingKey
Updated doco to match latest code.
Updated doco to match latest code.
Updated doco to match latest code.
Updated documentation around credential sharing.
Documentation for secure credential sharing.
Changed the "vault" command to "secrets".
Updated doco for new features.