@rikaidev/yomi 0.2.6

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 RikaiDev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/NOTICE

@@ -0,0 +1,81 @@
+Yomi
+
+This product includes software developed by third parties. Yomi's LINE
+protocol implementation was written with reference to the projects below —
+their field layouts, E2EE chunk ordering, and request shapes informed this
+independent implementation. Their license terms and copyright notices are
+reproduced here as required.
+
+================================================================================
+LINEJS — https://github.com/evex-dev/linejs
+Referenced for: TalkService/AuthService request shapes and the Letter-Sealing
+E2EE payload layout (chunk ordering, integer encoding). Referenced in comments
+throughout src/line/.
+
+MIT License
+
+Copyright (c) 2024-2026 Evex Developers
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+================================================================================
+CHRLINE — https://github.com/DeachSword/CHRLINE
+Referenced for: verifying LINE protocol field layouts and the passwordless
+(secondary-device) login flow. Referenced in comments in src/line/auth/.
+
+BSD 3-Clause License
+
+Copyright (c) 2021, DeachSword
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its contributors
+   may be used to endorse or promote products derived from this software
+   without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+================================================================================
+LINE-Protocol — https://github.com/er1ce/LINE-Protocol
+Referenced for: LINE Thrift enum definitions used to set correct on-the-wire
+values — ContentType (e.g. FILE=14), MessageRelationType (REPLY=3), and
+ServiceCode (TALK=1). Referenced in comments in src/line/.
+
+Licensed under the Apache License, Version 2.0. You may obtain a copy of the
+License at https://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.

package/PRIVACY.md

@@ -0,0 +1,39 @@
+# Yomi — Data & Privacy
+
+Yomi reads your LINE messages on your behalf and exposes them to an AI agent.
+This is the canonical statement of what it captures and how you stay in control.
+It is the single source of truth: Yomi surfaces this same text to the agent on
+connect (via the MCP server `instructions`) and through the `get_scope_policy`
+tool.
+
+## What Yomi captures
+
+By default, Yomi indexes **all** of your LINE conversations into a **local,
+on-device** search index (`data/search-index.db`) so an agent can search across
+them. This is a capture-all default — nothing is excluded until you say so.
+
+## Where your data goes
+
+Everything stays **on your machine**. Yomi never uploads your messages anywhere.
+The only data that leaves your device is whatever the agent surfaces in its
+replies to you — and in a cloud assistant, that surfaced text is processed by
+that assistant's model. Yomi itself makes no outbound copy of your messages.
+
+## Excluding conversations
+
+You can exclude any conversation at any time, in plain language to the agent
+(e.g. "don't index my chats with X"):
+
+- **`exclude_chats`** — stop indexing a conversation **and delete its
+  already-indexed messages** from the local index. Exclusion purges past data,
+  not just future capture.
+- **`include_chats`** — re-allow a previously excluded conversation.
+- **`list_excluded_chats`** — see what is currently excluded.
+- **`get_scope_policy`** — see this policy plus the current exclusion list.
+
+## Consent
+
+Because the default is capture-all, Yomi surfaces this policy to the agent on
+connect so the agent can tell you the default — and that you can exclude
+conversations — **before** doing any bulk read. You should get to make an
+informed choice.