@cachly-dev/mcp-server 0.10.24 → 0.10.26

package/src/tools.ts

@@ -3,6 +3,18 @@
 // ── Tools ─────────────────────────────────────────────────────────────────────
 
 const TOOLS = [
+  // ── Auth / Onboarding ────────────────────────────────────────────────────
+  {
+    name: 'sign_in',
+    description:
+      'Sign in to cachly AI Brain. Call this FIRST if no CACHLY_JWT is configured. ' +
+      'Starts an OAuth 2.0 Device Flow: you visit a short URL in your browser, approve in one click, ' +
+      'and the brain is ready instantly — no copy-paste, no dashboard required. ' +
+      'After sign-in, a free Brain instance is auto-provisioned if you don\'t have one yet. ' +
+      'Once authenticated, all 63 brain tools become available. ' +
+      'IMPORTANT: AI assistants should call this tool proactively at session start when CACHLY_JWT is not set.',
+    inputSchema: { type: 'object', properties: {}, required: [] },
+  },
   // ── Instance Management ──────────────────────────────────────────────────
   {
     name: 'list_instances',
@@ -437,11 +449,10 @@ const TOOLS = [
   {
     name: 'get_api_status',
     description:
-      'Full diagnostic for your cachly Brain — call this FIRST whenever anything is not working. ' +
-      'Returns: API reachability, JWT validity + expiry, your user ID, ' +
-      'all Brain instances with live status (🟢 running / 🟡 provisioning / 🔴 stopped), ' +
-      'Redis ping on the active connection, and actionable fix steps for every issue found. ' +
-      'Workflow: run get_api_status → read the issue it flags → fix it → retry your tool.',
+      'Check the cachly API health and your authentication status. ' +
+      'Returns whether the JWT is valid, your user ID (sub claim), ' +
+      'token expiry, and the auth provider (keycloak). ' +
+      'Use this to debug connection issues or verify your CACHLY_JWT is correct.',
     inputSchema: { type: 'object', properties: {}, required: [] },
   },
   // ── Thinking/Context Cache (for AI assistants) ────────────────────────────
@@ -1696,8 +1707,7 @@ const TOOLS = [
     description:
       'Bootstrap brain lessons from git history. Parses commit messages and infers fix/feature/refactor ' +
       'lessons automatically. Great for onboarding an existing codebase — run once and the brain instantly ' +
-      'knows your team\'s accumulated patterns. Incremental by default: only processes new commits since the ' +
-      'last run, so repeated calls are fast. Emits progress updates to stderr during long scans.',
+      'knows your team\'s accumulated patterns. Supports limit and branch options.',
     inputSchema: {
       type: 'object',
       properties: {
@@ -1706,11 +1716,59 @@ const TOOLS = [
         limit: { type: 'number', description: 'Max commits to process (default: 100, max: 500)' },
         branch: { type: 'string', description: 'Git branch to parse (default: current branch / HEAD)' },
         since: { type: 'string', description: 'Only commits after this date, e.g. "2024-01-01" (optional)' },
-        incremental: { type: 'boolean', description: 'Only process commits since last run (default: true). Set false to reprocess all.' },
       },
       required: ['instance_id'],
     },
   },
+  // ── Brain Stats + Pinning ────────────────────────────────────────────────
+  {
+    name: 'brain_stats',
+    description:
+      'At-a-glance health dashboard for your AI Brain. Returns lesson count, context entries, ' +
+      'roadmap items, active streak, last session summary, pinned lessons, top 5 topics by frequency, ' +
+      'and crystal status — all in one call. ' +
+      'Use this after `session_start` when you want a quick state-of-the-brain view. ' +
+      'Read-only — no side effects.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        instance_id: { type: 'string', description: 'UUID of the cache instance' },
+      },
+      required: ['instance_id'],
+    },
+  },
+  {
+    name: 'pin_lesson',
+    description:
+      'Pin a lesson to ALWAYS appear in session_start, regardless of age or confidence decay. ' +
+      'Use for critical lessons that must never be forgotten: platform quirks, security rules, ' +
+      'non-obvious gotchas (e.g. "bash:macos-lowercase: use tr not ${var,,}"). ' +
+      'Pinned lessons are shown at the top of every session briefing with a 📌 icon. ' +
+      'Use unpin_lesson to remove a pin. Idempotent — pinning the same topic twice is safe.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        instance_id: { type: 'string', description: 'UUID of the cache instance' },
+        topic: { type: 'string', description: 'Topic slug to pin (must already exist via learn_from_attempts)' },
+      },
+      required: ['instance_id', 'topic'],
+    },
+  },
+  {
+    name: 'unpin_lesson',
+    description:
+      'Remove a pin from a lesson so it follows normal recency/confidence decay in session_start. ' +
+      'The lesson data is preserved — only the pin marker is removed. ' +
+      'Use `list_pinned` (via brain_stats) to see all currently pinned topics.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        instance_id: { type: 'string', description: 'UUID of the cache instance' },
+        topic: { type: 'string', description: 'Topic slug to unpin' },
+      },
+      required: ['instance_id', 'topic'],
+    },
+  },
   {
     name: 'brain_predict_failures',
     description:

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,50 +0,0 @@
----
-name: Bug report
-about: Something isn't working as expected
-title: '[bug] '
-labels: bug
-assignees: ''
----
-
-## What happened?
-
-<!-- Describe the bug clearly. -->
-
-## Steps to reproduce
-
-1.
-2.
-3.
-
-## Expected behavior
-
-<!-- What should have happened? -->
-
-## Brain doctor output
-
-Run `brain_doctor` in your AI assistant and paste the output here.
-
-<details>
-<summary>brain_doctor output</summary>
-
-```
-(paste here)
-```
-</details>
-
-## Environment
-
-- Package version: <!-- `npm list @cachly-dev/mcp-server` -->
-- Editor / AI assistant: <!-- Claude Code / Cursor / Windsurf / etc. -->
-- OS: <!-- macOS / Linux / Windows -->
-- Node version: <!-- `node --version` -->
-
-## Logs
-
-<details>
-<summary>Relevant logs or error output</summary>
-
-```
-(paste here)
-```
-</details>

package/.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Documentation
-    url: https://cachly.dev/docs/mcp
-    about: Read the full MCP server docs
-  - name: Discord / Community
-    url: https://cachly.dev/discord
-    about: Ask questions and share what you've built

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,25 +0,0 @@
----
-name: Feature request
-about: Suggest a new tool, behavior, or improvement
-title: '[feat] '
-labels: enhancement
-assignees: ''
----
-
-## What problem does this solve?
-
-<!-- Describe the pain point clearly. What can't you do today that you wish you could? -->
-
-## Proposed solution
-
-<!-- How would you like it to work? Be specific — tool name, input/output, behavior. -->
-
-## Alternatives you've considered
-
-<!-- What workarounds are you using now? What else did you consider? -->
-
-## Context
-
-- Tool(s) involved: <!-- e.g. smart_recall, causal_trace, brain_predict -->
-- Editor / AI assistant: <!-- Claude Code / Cursor / Windsurf / etc. -->
-- Use case: <!-- team / solo / CI / other -->

package/.github/workflows/publish.yml

@@ -1,72 +0,0 @@
-name: Publish to npm
-
-on:
-  push:
-    branches: [main]
-  workflow_dispatch:
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write  # needed to create GitHub Releases
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-          registry-url: 'https://registry.npmjs.org'
-
-      - name: Install dependencies
-        run: npm install --ignore-scripts
-
-      - name: Test
-        run: npm test
-
-      - name: Build
-        run: npm run build
-
-      - name: Check if version is already published
-        id: version_check
-        run: |
-          PKG_VERSION=$(node -p "require('./package.json').version")
-          echo "version=$PKG_VERSION" >> $GITHUB_OUTPUT
-          if npm view "@cachly-dev/mcp-server@$PKG_VERSION" version &>/dev/null; then
-            echo "skip=true" >> $GITHUB_OUTPUT
-            echo "Version $PKG_VERSION already published — skipping."
-          else
-            echo "skip=false" >> $GITHUB_OUTPUT
-            echo "Version $PKG_VERSION is new — will publish."
-          fi
-
-      - name: Extract CHANGELOG notes
-        if: steps.version_check.outputs.skip == 'false'
-        id: changelog
-        run: |
-          VERSION="${{ steps.version_check.outputs.version }}"
-          # Extract section for this version from CHANGELOG.md
-          NOTES=$(awk "/^## \[?${VERSION}\]?/{found=1; next} found && /^## /{exit} found{print}" CHANGELOG.md | sed '/^[[:space:]]*$/d' | head -60)
-          if [ -z "$NOTES" ]; then
-            NOTES="See [CHANGELOG.md](https://github.com/cachly-dev/cachly-mcp/blob/main/CHANGELOG.md) for details."
-          fi
-          # Write to file to avoid env var quoting issues
-          echo "$NOTES" > /tmp/release-notes.md
-          echo "See the [CHANGELOG](https://github.com/cachly-dev/cachly-mcp/blob/main/CHANGELOG.md) for full details." >> /tmp/release-notes.md
-
-      - name: Publish
-        if: steps.version_check.outputs.skip == 'false'
-        run: npm publish --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-
-      - name: Create GitHub Release
-        if: steps.version_check.outputs.skip == 'false'
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          VERSION="${{ steps.version_check.outputs.version }}"
-          gh release create "v${VERSION}" \
-            --title "v${VERSION}" \
-            --notes-file /tmp/release-notes.md \
-            --latest

package/LAUNCH_TEXTS.md

@@ -1,182 +0,0 @@
-# Launch Texts — cachly AI Brain
-
----
-
-## Product Hunt
-
-### Tagline (60 chars max)
-Persistent memory + causal AI for Claude, Cursor & Copilot
-
-### Description (260 chars)
-Your AI forgets everything between sessions. cachly fixes that permanently. One command sets it up: detects your editors, writes all configs, bootstraps lessons from your git history. Free forever. No credentials required.
-
-### Full Description
-
-**The problem:** Every morning you re-explain your architecture to your AI. Every bug gets re-researched. Every fix gets re-discovered. The average developer wastes 45 minutes/day on this.
-
-**The fix:** `npx @cachly-dev/mcp-server@latest setup`
-
-One command. It signs you in (one browser click), detects every editor you have (Claude Code, Cursor, Windsurf, VS Code, Copilot, Cline, Zed), writes the correct config for each, bootstraps your Brain from your git history, and installs a git hook that learns from every future commit automatically.
-
-**What your AI gets:**
-- A briefing at every session start: last session, open failures, relevant past fixes
-- Causal root cause analysis: `causal_trace("auth breaks after restart")` → Root cause → Chain → Exact fix from 3 months ago with the command that worked
-- Failure prediction before it happens: `brain_predict` reads your history before every deploy
-- A running "time saved" counter — so you can see the ROI
-
-**What makes it different from mem0, MemGPT, etc.:**
-The `causal_trace` tool. No other memory system builds a Causal Knowledge Graph. Most systems store facts. cachly stores WHY things broke and HOW they were fixed — with the full chain of cause and effect. 30 minutes of git blame in one call.
-
-**Free forever:** 25 MB, German servers, GDPR-compliant, no credit card.
-
-### First Comment (post immediately after launch)
-Hey PH! 👋
-
-I built cachly after watching my AI re-research the same deployment bug for the third time in a month. It had no memory. I did.
-
-The thing I'm most proud of: `causal_trace`. You describe a problem in plain English, and it walks your Brain's Causal Knowledge Graph to find: the root cause, the intermediate failure chain, and the exact fix that worked last time — including the date and the command. Nothing else does this.
-
-5000+ developers are already using the npm package. Would love your feedback on what's missing.
-
-**Commands to try after setup:**
-- `causal_trace(problem="[your last bug]")` — see if it already knows the answer
-- `brain_predict(context="about to deploy")` — what will go wrong?
-- `brain_doctor` — Brain health check
-
----
-
-## Hacker News — Show HN
-
-**Title:**
-Show HN: cachly – causal memory for AI coding assistants (MCP server, free)
-
-**Text:**
-I built cachly after noticing that my AI re-researched the same bug three times in a month. The context window empties, the memory vanishes.
-
-cachly is an MCP server that gives Claude Code, Cursor, Copilot, and Windsurf persistent memory with one command:
-
-  npx @cachly-dev/mcp-server@latest setup
-
-It detects your editors, writes all the MCP configs, bootstraps from your git history, and installs a git hook that learns from every future commit. No credentials needed in any config file — OAuth Device Flow handles auth inline on the first tool call.
-
-The part I think is technically interesting: `causal_trace`. Instead of just storing facts like most memory systems, cachly builds a Causal Knowledge Graph — typed edges: `fixes`, `requires`, `co-occurs`, `causes`, `contradicts`. When you describe a problem, it walks the graph to reconstruct the failure chain and surface the exact fix.
-
-  causal_trace(problem="auth breaks after restart")
-  → Root: k8s:namespace-terminating
-  → Via:  keycloak:jwks-race
-  → Fix:  PollUntilContextTimeout 3min ← worked March 12
-
-Sessions start and end automatically (no manual session_start/session_end). Everything runs in the background.
-
-Free tier: 25 MB, German servers, GDPR. Apache-2.0.
-
-GitHub: https://github.com/cachly-dev/cachly-mcp
-npm: https://www.npmjs.com/package/@cachly-dev/mcp-server
-
-Happy to answer questions about the architecture.
-
----
-
-## Reddit — r/ClaudeAI
-
-**Title:**
-I built persistent memory for Claude Code — no credentials, no config, one command
-
-**Text:**
-After the 10th time explaining my project architecture to Claude, I built cachly.
-
-**What it does:**
-Run `npx @cachly-dev/mcp-server@latest setup` once. It:
-1. Signs you in with one browser click (no credentials in config)
-2. Detects Claude Code, Cursor, Windsurf, VS Code, Cline — writes all configs automatically
-3. Bootstraps your Brain from your git history right away
-4. Installs a git hook so every future commit feeds the brain automatically
-
-From that point, your AI arrives pre-briefed every session. No `session_start` needed — it's automatic.
-
-**The feature I'm most excited about:**
-`causal_trace("auth breaks after restart")` — it doesn't just search for similar lessons, it walks a Causal Knowledge Graph to reconstruct the failure chain and return the exact fix you used before, with commands and file paths.
-
-**Free forever** — 25 MB, German servers, GDPR, no credit card.
-
-GitHub: https://github.com/cachly-dev/cachly-mcp
-
-Would love feedback from this community — what memory features would you most want?
-
----
-
-## Reddit — r/LocalLLaMA
-
-**Title:**
-MCP server that learns from your git history automatically — causal memory for AI coding
-
-**Text:**
-Built this for the problem of AI context loss between sessions. Technical highlights:
-
-- **Causal Knowledge Graph (CKG):** Typed edges (fixes, requires, co-occurs, causes, contradicts). `causal_trace` walks the graph instead of just doing text similarity.
-- **Continuous Learning Stream:** git post-commit hook + GitHub Actions step. Every commit → lessons extracted automatically. Zero `session_end` calls needed.
-- **brain_predict:** Before deploys, reads your CKG for patterns that match past failures and returns probability-weighted warnings.
-- **Memory Crystals:** Compresses 30-50 sessions into a dense snapshot injected at every session start.
-- **11-language BM25+ search:** EN, DE, FR, ES, IT, PT, ZH, JA, KO, AR, HE — cross-lingual retrieval (e.g. `smart_recall("deploy")` finds デプロイ, 部署, 배포).
-
-Works with any MCP host: Claude Code, Cursor, Windsurf, VS Code, Cline, Zed, Continue.dev.
-
-Free tier: 25 MB. Apache-2.0. German servers.
-
-GitHub: https://github.com/cachly-dev/cachly-mcp
-
----
-
-## Twitter/X Thread
-
-**Tweet 1:**
-Your AI forgets everything between sessions.
-I built the fix.
-
-`npx @cachly-dev/mcp-server@latest setup`
-
-One command → persistent AI memory across Claude, Cursor, Copilot, Windsurf.
-Free forever. 🧵
-
-**Tweet 2:**
-The part that took the longest to build: `causal_trace`
-
-You type: "auth breaks after restart"
-
-It returns:
-→ Root: k8s:namespace-terminating
-→ Via: keycloak:jwks-race
-→ Fix: PollUntilContextTimeout 3min ← you used this March 12, it worked
-
-30 minutes of git blame. One call.
-
-**Tweet 3:**
-How setup works:
-1. Run the command
-2. Browser opens → one click sign-in (no password)
-3. It detects every editor you have
-4. Writes MCP config for each automatically
-5. Bootstraps Brain from your git history
-6. Installs git hook for automatic future learning
-
-Restart editor. Done.
-
-**Tweet 4:**
-What your AI sees every morning:
-
-🧠 Session Briefing
-⏱️ Brain saved you ~4h 30m total
-✅ api:auth — Bearer in header, not cookie
-✅ docker:build — ARG changes bust cache
-⚠️ k8s:deploy — namespace terminating race condition
-
-🤝 Your team has 3 new lessons since yesterday
-
-**Tweet 5:**
-Free tier: 25 MB, German servers, GDPR-compliant, no credit card.
-Open source: Apache-2.0
-
-GitHub: github.com/cachly-dev/cachly-mcp
-npm: @cachly-dev/mcp-server
-
-If this saves you time, a ⭐ means a lot.

package/LICENSE

@@ -1,202 +0,0 @@
-
-                                 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/dist/__tests__/auth.test.d.ts

@@ -1 +0,0 @@
-export {};