@wirecat/cli-memo 0.0.0 → 0.5.1

package/LICENSE

@@ -0,0 +1,204 @@
+Copyright (c) 2026 Viacheslav Ptsarev
+
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,315 @@
+# cli-memo
+
+`memo` answers "what do I need to know about this person": who they are in each messenger, the
+newest messages each way, the notes about them, and the newest mail threads — each item with a link
+to its source.
+
+It reads the local message store that [tg-cli](https://github.com/WireCatLabs/tg-cli) and
+[max-cli](https://github.com/WireCatLabs/max-cli) share, Markdown notes such as an Obsidian vault, and mail
+through [Himalaya](https://github.com/pimalaya/himalaya). Source files and mailboxes are read-only.
+Notes you write here, links, labels, relationships and task reminders live in the local store.
+Retrieval is local; an explicitly selected model receives evidence only with the configured consent.
+
+**Status:** early. Context, notes and their links, document import, Gmail and IMAP imports, tasks,
+manual relationships, evidence bundles and local reminders work.
+
+## Your notes on messages, people and projects
+
+```sh
+memo notes add 'Prefers mornings' --about telegram:'Rin Example'
+memo notes add --file review.md --about 'msg:telegram/1/77/42' --about entity:ENTITY_ID --export
+memo notes list --about telegram:'Rin Example' --json
+memo notes edit NOTE_ID --revision 1 --text 'Prefers early mornings'
+memo notes remove NOTE_ID
+memo notes export --to /path/to/vault/memo --format obsidian
+```
+
+A note written here is the store's, not a file's, and is about whatever `--about` names: a person by
+`<messenger>:<name or id>`, or any stored record by its reference — `msg:`, `chat:`, `contact:`,
+`person:`, `entity:`, `task:`, `note:`. Several `--about` give it several subjects. An edit names the
+revision it changes, so an edit made meanwhile is never lost. tg and max `contacts notes` are the same
+notes.
+
+`export` writes them as files, in a folder's format, with `memo-id` and `memo-hash` in the front
+matter: import skips such a file, so an export inside a vault never comes back as a second note. A
+file edited since memo wrote it is left alone and reported; nothing is deleted. `--export [dir]` on `add`
+and `edit` writes one; with no folder given, `notes.export: { "dir": "…", "format": "…" }` in the
+config says where.
+
+## Open work
+
+```sh
+memo tasks add 'msg:telegram/1/77/42' --type request
+memo tasks add 'note:NOTE_ID' --provider telegram --account 1 --type request
+memo tasks list --provider telegram --account 1 --json
+memo tasks assign TASK_ID PERSON_UID --provider telegram --account 1
+memo tasks close TASK_ID --provider telegram --account 1 --as done
+```
+
+Native note tasks belong to the explicitly selected stored account. Their previews read current note
+text; deleting a note keeps its task with an unavailable source. Repeated creation of the same kind
+returns the existing task, including one already closed.
+
+`context` includes directly related open tasks and explicit task assignments. A task in a shared group
+belongs in a person's context only when they authored its source or you assigned it explicitly. Closed
+tasks stay closed on repeated creation. If several accounts of the requested provider exist, use
+`memo context telegram:101 --account 1`.
+
+## Search and gather evidence
+
+```sh
+memo search notes '"budget review" AND NOT cancelled' --limit 20
+memo search notes 'project progress' --filter 'date:2026-10-08' --tag project --folder /path/to/vault
+memo notes show note:NOTE_ID --json
+memo search all 'budget AND after:2026-09-01' --json
+memo ask 'What work is pending?' --query budget --all --json
+```
+
+Notes are searched by their words and word stems, in the query language messages use: phrases,
+`AND`/`OR`/`NOT`, `tag:`, `date:`; `--exact` matches every word as written. A message-only field such as
+`from:` is refused. They are also searched by meaning when the model is downloaded, and the two are
+ranked together: `by` says which ran, each hit's `foundBy` which found it, and `meaningSkipped` why
+meaning did not run. Each hit carries its reference, the first matching line and the links the note
+holds; `linked` counts what the notes found link to, with each person's name. Follow `nextOffset` with
+`--offset`.
+
+`notes show` takes `note:<id>` or a file in a configured folder, and answers with the note's tags, its
+links, its backlinks and, for a PDF or sheet, where its text came from.
+
+`search all` searches messages, imported mail and native notes together. Use `search messages`,
+`search mail`, or `search notes` for one resource; `search notes --type internal|file` narrows note kinds.
+`search all` includes a separate `tasks` list for open work linked to matching sources. Results identify source
+kind/account and skipped-resource coverage; a query using a field only messages have (`from:`, `after:`)
+searches the messages and says the notes were not searched. Missing hits do not prove that an event
+never happened.
+
+`ask` returns an evidence bundle for your chosen agent by default. To call a model, configure
+`MEMO_MODELS_ANALYSIS_PROVIDER`, `MEMO_MODELS_ANALYSIS_MODEL`, optionally
+`MEMO_MODELS_ANALYSIS_BASE_URL` and `MEMO_MODEL_API_KEY`, then pass `--model`. Remote calls also require
+`--allow-remote`. Model claims are generated and unverified, cite supplied evidence, and distinguish
+assertions, conclusions and inferences. Suggestions create no task until you explicitly run
+`memo tasks add <source> --type <kind>`. Answers are not saved as independent facts.
+
+## Organizations, families and projects
+
+```sh
+memo entities add 'Synthetic Studio' --kind organization
+memo relationships add person:PERSON_UID entity:ENTITY_ID --role author
+memo entities context ENTITY_ID --json
+memo tags add project --entity ENTITY_ID
+memo tags add follow-up --task TASK_ID
+```
+
+Organisations, families, projects and groups are yours, not one account's. Relationships use
+`member-of` or `related-to`; `list`, `remove` and `confirm` manage them. They are manual statements and
+never merge identities because names or domains match. `entities context` lists the entity's
+relationships, the notes about or linking it, and its tags. Tags on a task need no account; its
+reminders name the account it waits on.
+
+`memo relationships suggest --provider email --account owner@example.test` stores bounded weak
+shared-domain proposals for direct email contacts. Proposals retain rule provenance and remain
+unconfirmed; they do not enter confirmed person context. `relationships confirm <id>` records your
+explicit acceptance. Common free-mail domains are excluded from this heuristic.
+
+## Local task reminders
+
+```sh
+memo reminders schedule TASK_ID --at 2026-10-09T09:00:00+02:00 --timezone Europe/Madrid --provider telegram --account 1
+memo reminders poll --provider telegram --account 1 --json
+memo reminders ack REMINDER_ID RECEIPT --provider telegram --account 1
+memo reminders snooze REMINDER_ID --revision 1 --at 2026-10-10T09:00:00+02:00 --provider telegram --account 1
+memo reminders cancel REMINDER_ID --provider telegram --account 1
+```
+
+Reminders are local deliveries for an explicitly scheduled open task. Poll leases due deliveries;
+acknowledgement confirms consumption. Expired leases retry with a new receipt; integrations deduplicate
+by `deliveryId` (reminder ID and revision). State survives restart. Snooze checks the current revision;
+task closure cancels pending reminders. The import timer continues to import sources and does not
+deliver reminders to messengers or email. A caller can schedule `poll` using its chosen local scheduler.
+
+## Context about a person
+
+```sh
+memo context telegram:"Rin Example"     # or max:<name or id>, email:<address>
+```
+
+One answer from the shared store: every identity linked to the person (`tg|max contacts link`), the
+last message each way, recent messages in direct chats and groups, chats in common — mail included once
+an address is linked — then the notes linked to them: the note about them (`memo note`), notes that link
+them, notes that link the note about them, and the notes you wrote here about them. A name in a note's
+plain text is not a link and is not listed. What gave nothing is listed with the reason. `--json` for
+agents, `--limit` for more.
+
+## Notes
+
+```sh
+memo folders add /path/to/vault            # once: gives the folder an id
+memo notes import                          # load the notes into the shared store; run again after edits
+memo search notes "lighthouse budget"      # notes by their words and meaning, and what they link
+memo notes about telegram:"Rin Example"    # notes about a person, and the notes linking them
+```
+
+`import` stores each file as a note of its folder, named by its path inside the folder. An edited note
+keeps its old text as a revision; a note deleted from the folder loses its text on the next import, and a
+run that finds most notes missing at once deletes nothing and says so. A file moved inside the folder —
+gone from one path, the same content at another — keeps its id, its links and its tags.
+
+Import also stores what each note links, through the folder's format. A link to a note the folder has
+once becomes a link to that note. A name no note has, such as `[[Kai Sample]]`, is kept as written and
+becomes a link to the person the moment someone by that name, local alias or username is in the store —
+or stays unresolved while two people share it. A file's `tags:` and `#tags` become the note's tags, and
+a tag removed from the file is removed from the note — unless you added the same tag yourself.
+
+Import then embeds the notes for search by meaning with the local e5-small model (shared with tg and
+max: `tg models text download e5-small`), only what changed, at most 600 chunks a run — the next run
+continues. `--no-embed`, or `notes.embed: false` in the config, skips it.
+
+`about` takes `<messenger>:<name or id>` or a reference (`person:`, `entity:`, `note:`) and lists the
+notes about it, the notes that link it, the notes that link a note about it, and links written with the
+person's name that two people share. Hidden folders such as `.obsidian` are skipped, and nothing is ever
+written to a notes folder.
+
+Imports accept Markdown/TXT, CSV/TSV, text-layer PDF, DOCX, XLSX, ODT/ODS, PPTX and EPUB.
+PDF/DOCX use optional `unpdf` and `mammoth` packages installed alongside the CLI; modern office
+formats use the bounded built-in shared readers. Results report missing engines, unreadable files, unsupported legacy DOC/XLS, scanned
+PDFs needing an agent, oversized inputs and truncation. PDF page spans, CSV row/column ranges and
+XLSX sheet/cell addresses preserve source provenance. Files are capped at 50 MiB and stored text at
+200,000 characters. Content hashes detect equal-size edits.
+
+Folders and what to skip go in `~/.config/cli-memo/config.json`; `--folder` narrows a run to some of the
+configured folders and `--ignore` adds rules for one run. An ignore rule is a path inside the folder — a file, or a folder and everything under it —
+or a glob (`**/Private*`, `*.txt`):
+
+```json
+{ "notes": { "folders": [{ "id": "fld_…", "path": "/path/to/vault" }], "ignore": ["Journal/Private.md", "Archive"] } }
+```
+
+### Folders and their format
+
+```sh
+memo folders add /path/to/vault                     # gives the folder an id and prints it
+memo folders add /path/to/notes --format markdown   # a plain Markdown folder
+memo folders attach fld_… /other/path/to/vault      # the same folder on another computer
+memo folders list
+```
+
+A folder's id is the store's and is what notes and links use; its path is only where it is on this
+computer, so the config differs between computers and the id does not. `folders list` also shows the
+folders the store has from another computer, to attach. A path can belong to one id only. A bare path in
+`notes.folders`, or a folder with no id, is refused by import with both commands named — memo never
+invents an id, which would give every note a new identity. A folder imported before store version 25
+moves its path into this computer's config on the first run, with the id it already has.
+
+`format` says how the folder's notes are written. `obsidian` (the default) reads `[[Note|label]]` links
+with `#heading` and `#^block` anchors, `aliases`, `tags:` and inline `#tags`. `markdown` reads
+`[label](path.md)` links and `tags:`; a `#word` in its text is not a tag. Both read links to stored
+records — `[Rin](person:…)`, or a bare `msg:…` in the text.
+
+A Markdown file whose front matter carries `memo-id` was written by memo and is skipped by import.
+
+## Keeping it current
+
+```sh
+memo import                  # notes and mail, only what changed since the last run
+memo auto on --every 5m      # run memo import on a systemd user timer (default 5m, a minute or more)
+memo auto status             # on/off, interval, next and last run
+memo auto off                # stop and remove the timer
+```
+
+The config is the one source: `memo auto on/off` write `auto: { enabled, every }` to
+`~/.config/cli-memo/config.json`, and a hand edit there takes effect at the next timer run, which
+rewrites or removes its own timer to match. The timer runs `memo import` from the place it was set up
+from, with the `PATH` of that shell, so Himalaya and the keyring helper are found.
+
+`memo import` is incremental. A note whose size and change time are as this computer last saw them is
+not read; one whose content hash the store already has is not saved, so a second computer importing the
+same folder saves nothing new. What this computer last saw is kept per folder in memo's state folder. Mail reads bodies only of messages not stored yet. A lock
+keeps two imports from running at once, and one failing source does not stop the others.
+
+## Mail
+
+Gmail remains the default. For another IMAP provider, configure an account with `mode: "imap"`
+and `folders: ["INBOX", "Archive"]` in `mail.accounts`. Message-ID and reference headers preserve
+message/thread identities across folder moves and UID resets. Mail without Message-ID uses an explicit
+UIDVALIDITY/folder/UID fallback, which can change after a move/reset. Configured folders are listed
+completely before deletion checks; a changed folder scope skips deletion for that run.
+
+Imports index changed threads with the shared bounded pipeline and report the proven date/folder
+window, resumable indexing and missing models. No thread is called globally complete on the basis
+of one window. CC/BCC headers are retained when available. Readable attachments become separate source
+entries linked to their parent/part; extraction failures are reported. After installing an optional
+engine, use `memo mail import --retry-attachments` to reread a bounded batch of stored messages.
+
+```sh
+memo mail import --since 2026-09-01
+```
+
+Reads a Gmail account's All Mail through [Himalaya](https://github.com/pimalaya/himalaya) into the
+shared message store as provider `email`: one chat per Gmail thread, the mailbox address as the
+account, senders and recipients as people. Messenger search and person context then see mail too.
+
+- Read only: the mailbox is opened read-only, nothing is sent, and no mail is marked read.
+- Run it again any time: what is stored is skipped; `--max` (default 200) bounds the new mails read
+  per run, and the next run continues.
+- A mail deleted at the source loses its text in the store. The first two days of the window are left
+  alone, and a run that finds an unusually large share missing deletes nothing and says so. Mail moved
+  to Spam leaves All Mail and counts as deleted.
+
+Set the account up in Himalaya first (an IMAP account with a Gmail
+[app password](https://myaccount.google.com/apppasswords); `bin/mail-password <name>` stores it in the
+keyring), then name it in `~/.config/cli-memo/config.json`:
+
+```json
+{ "mail": { "accounts": [{ "name": "gmail", "address": "you@example.com" }] } }
+```
+
+## People
+
+Who is who is decided in messaging: `tg contacts link <person> email:<address>` (or `max contacts link`)
+records that a messenger identity and a mail address are one person, in the shared store. A same name
+is never enough. `memo` only names the note that is about the person:
+
+```sh
+memo note telegram:"Rin Example" ~/Notes/people/Rin.md
+memo note telegram:"Rin Example" --clear
+```
+
+An identity is `<messenger>:<name or id>`; a name two people share is refused, with their ids to
+choose from. The note must be imported first; the link is an `about` link in the store. Entries of an
+older `~/.config/cli-memo/people-notes.json` move into the store once their notes are imported; the file
+itself is left as it is.
+
+## Tags on sources
+
+```sh
+memo tags add work follow-up --note note:NOTE_ID
+memo tags add project --folder FOLDER_ID --path Projects
+memo search notes "budget" --tag work
+memo tags add follow-up --message 'msg:email/you%40example.com/12345/67890'
+memo tags add follow-up --chat 12345 --provider email --account you@example.com
+memo tags list --tag follow-up --json
+tg search mail 'tag:follow-up'
+```
+
+A note is labelled by its reference, an email or messenger message by its full `msg:` locator, a mail
+thread or chat by its exact id and account. A person, entity or task is labelled by `--person`,
+`--entity` or `--task`, with no account; a contact names its account. `--folder` with an id from
+`memo folders list`, and `--path` for one subfolder, labels every note under it at any depth. Tags use 1–32 letters a–z, digits or hyphens; case is ignored.
+Adding an existing tag or removing an absent one leaves it unchanged.
+
+Labels live in the shared local store. Tagging leaves note files, front matter, Gmail labels and mailbox
+flags untouched. Labels survive edits and moves of the note; a deleted note disappears from search.
+`tags list` shows up to 100 labels by default (`--limit` for more, `hasMore` in JSON); a note's tags
+say whether its file or you stated them. Contact identity
+tags remain available through `tg|max tags`.
+
+## Development
+
+```sh
+pnpm install
+pnpm lint && pnpm typecheck && pnpm test
+```
+
+## License
+
+[Apache License 2.0](LICENSE).

package/dist/answers/command.d.ts

@@ -0,0 +1,35 @@
+import { type Streams } from "@wirecat/cli-core";
+import { type ModelAdapter, type ModelTarget } from "@wirecat/cli-messaging/models";
+import type { Command } from "commander";
+import { type EvidenceItem } from "../search/command.js";
+interface Claim {
+    text: string;
+    sources: string[];
+    kind: "assertion" | "conclusion" | "inference";
+}
+interface SuggestedTask {
+    source: string;
+    kind: "question" | "request" | "mention" | "promise";
+    reason: string;
+}
+export declare const answerEvidence: (question: string, evidence: EvidenceItem[], options: {
+    target: ModelTarget;
+    consent: boolean;
+    key?: string;
+    adapters?: Record<string, ModelAdapter>;
+}) => Promise<{
+    claims: Claim[];
+    suggestions: SuggestedTask[];
+    model: {
+        provider: string;
+        name: string;
+    };
+    evidence: EvidenceItem[];
+    generated: boolean;
+    verified: boolean;
+    saved: boolean;
+    taskAcceptance: string;
+}>;
+export declare const askCommand: (program: Command, streams: Streams, env: NodeJS.ProcessEnv) => void;
+export {};
+//# sourceMappingURL=command.d.ts.map

package/dist/answers/command.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"command.d.ts","sourceRoot":"","sources":["../../src/answers/command.ts"],"names":[],"mappings":"AAAA,OAAO,EAA4B,KAAK,OAAO,EAAE,MAAM,mBAAmB,CAAA;AAC1E,OAAO,EAAE,KAAK,YAAY,EAAE,KAAK,WAAW,EAAgB,MAAM,+BAA+B,CAAA;AAEjG,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAA;AAExC,OAAO,EAAE,KAAK,YAAY,EAAiC,MAAM,sBAAsB,CAAA;AAGvF,UAAU,KAAK;IACb,IAAI,EAAE,MAAM,CAAA;IACZ,OAAO,EAAE,MAAM,EAAE,CAAA;IACjB,IAAI,EAAE,WAAW,GAAG,YAAY,GAAG,WAAW,CAAA;CAC/C;AACD,UAAU,aAAa;IACrB,MAAM,EAAE,MAAM,CAAA;IACd,IAAI,EAAE,UAAU,GAAG,SAAS,GAAG,SAAS,GAAG,SAAS,CAAA;IACpD,MAAM,EAAE,MAAM,CAAA;CACf;AAED,eAAO,MAAM,cAAc,aACf,MAAM,YACN,YAAY,EAAE,WACf;IAAE,MAAM,EAAE,WAAW,CAAC;IAAC,OAAO,EAAE,OAAO,CAAC;IAAC,GAAG,CAAC,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,YAAY,CAAC,CAAA;CAAE;;;;QAuD9F,QAAQ;QAAmB,IAAI;;;;;;;EAO3C,CAAA;AAED,eAAO,MAAM,UAAU,YAAa,OAAO,WAAW,OAAO,OAAO,MAAM,CAAC,UAAU,SA0EpF,CAAA"}