memstack-skill-loader 4.15.0__tar.gz → 4.16.0__tar.gz

{memstack_skill_loader-4.15.0/src/memstack_skill_loader.egg-info → memstack_skill_loader-4.16.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memstack-skill-loader
-Version: 4.15.0
+Version: 4.16.0
 Summary: MCP server that vector-indexes MemStack Pro skills for on-demand loading
 Project-URL: Homepage, https://memstack.pro
 Project-URL: Documentation, https://memstack.pro/docs
@@ -72,7 +72,7 @@ activate_license(key="your-key", email="you@example.com")
 ```
 Use `key="free"` for the free tier, or your Pro key from [memstack.pro](https://memstack.pro) to unlock all 44 Pro skills (86 free + 44 Pro = 130 total). Then type `list skills` to verify.
 
-> **The first start is slow, and that is normal.** On the very first run after installing or upgrading, the server builds the skill index before it answers anything. Expect roughly a minute, nearly all of it loading the embedding model rather than reading your skills. **The server will look unresponsive for that time.** Let it finish. Every later start reuses the index and is not affected.
+> **The first start is slow, and that is normal.** On the very first run after installing or upgrading, the server builds the skill index before it answers anything. Nearly all of that time is a one-time download of the ~90 MB embedding model, so it tracks your network speed rather than the size of your skill library: indexing 86 skills itself takes about a second. On a fast connection the whole first start is around half a minute; on a slow one it is longer. **The server will look unresponsive for that time.** Let it finish. Every later start reuses the cached model and index and is not affected.
 
 > To override the skills path, set `MEMSTACK_SKILLS_DIR=/path/to/your/memstack/skills`.
 
@@ -80,7 +80,7 @@ Use `key="free"` for the free tier, or your Pro key from [memstack.pro](https://
 
 ## Troubleshooting
 
-**Nothing responds after a fresh install, and it does not seem to be failing either (during Step 4):** the first start builds the skill index before the server answers anything, which takes roughly a minute. Most of that is loading the embedding model, not reading your skills. There is no progress output, so a working first start and a hung one look identical. Wait it out before changing anything. If it is still silent well past a couple of minutes, then treat it as the interpreter mismatch below. Later starts reuse the index and respond immediately.
+**Nothing responds after a fresh install, and it does not seem to be failing either (during Step 4):** the first start builds the skill index before the server answers anything. Most of that is a one-time ~90 MB embedding-model download, not reading your skills, so the wait depends on your connection: around half a minute on a fast one, longer on a slow one. There is no progress output, so a working first start and a hung one look identical. Wait it out before changing anything. If it is still silent well past a few minutes, then treat it as the interpreter mismatch below. Later starts reuse the cached model and index and respond immediately.
 
 **`error: externally-managed-environment` (during Step 2)** — pip refuses to install on a system-managed Python. Add `--break-system-packages` · (in terminal):
 ```bash
@@ -111,7 +111,7 @@ MCP server that vector-indexes all 130 MemStack™ skills so Claude Code can cal
 
 - **No Anthropic API key required:** skill search and indexing run locally and never leave your machine. Three small calls happen on their own at session start — license validation, a Pro-bundle version probe, and a PyPI update check — and every other outbound call is one you trigger ([Data and privacy](#data-and-privacy))
 - **Pro skills auto-detected:** once activated, the Pro skills directory is added to your sources automatically, with no `config.json` edit
-- **Auto-reindex on start:** skills stay current without manual rebuilds. Only startup ever rebuilds, never a search. The first start pays a one-time build of roughly a minute; after that a rebuild happens in the background while the existing index keeps serving, so later starts are not delayed
+- **Auto-reindex on start:** skills stay current without manual rebuilds. Only startup ever rebuilds, never a search. The first start pays a one-time build dominated by the embedding-model download (see [Quick Start](#quick-start-5-minutes)); after that a rebuild happens in the background while the existing index keeps serving, so later starts are not delayed
 - **Memory Engine:** an append-only, versioned fact store with query-time recall scoring — facts decay with age and decay more slowly the more they are recalled. Facts flow in from the diary's `## FACTS` block and are exposed to Claude through five `mem_*` tools (see [Available Tools](#available-tools))
 - **Living memory at session start:** the SessionStart hook injects a compact, token-budgeted digest of the project's top recall-scored facts into context. It fails open — a missing, empty, or unreachable store never blocks startup
 - **8-page localhost dashboard:** Overview, Skills Manager, Burn Report, Memory Browser (project-aware diary reader), Memory Inspector (read-only Memory Engine fact views), Agent Monitor, Referrals, and Settings
@@ -248,9 +248,15 @@ The `pattern` field controls how skills are discovered:
 
 ## Release Notes
 
+### 4.15.1 (August 2026)
+
+- **Fixed: activating a Pro license on a PyPI install downloaded the Pro skills and never indexed them.** The skills landed in `~/.memstack/pro-skills`, activation reported success, and the catalog still showed only the 86 free skills. Setting `MEMSTACK_PRO_LICENSE_KEY` was the only workaround. Both of the paths that decide whether to attach the Pro source now share one predicate.
+- **Activation now takes effect immediately.** The reindex that follows an activation rebuilds with the Pro skills included, and the confirmation reports the post-activation count, so a restart is no longer needed.
+- First-start timing in these docs was reworded: it is dominated by a one-time embedding-model download and therefore varies with network speed, rather than being the fixed "roughly a minute" previously quoted.
+
 ### 4.15.0 (August 2026)
 
-- The skill index moved to the canonical state root, so a relative `vector_db_path` no longer depends on which directory the server happened to start in. **The first start after installing or upgrading rebuilds the index once, which takes roughly a minute**, nearly all of it loading the embedding model. Later starts are unaffected.
+- The skill index moved to the canonical state root, so a relative `vector_db_path` no longer depends on which directory the server happened to start in. **The first start after installing or upgrading rebuilds the index once**, nearly all of that time being a one-time embedding-model download. Later starts are unaffected.
 - New index guard classifies the index as current, drift, stale, absent, or rebuilding, and reports that verdict at startup and in the dashboard. Only startup may rebuild on its own, so no search request ever blocks on one.
 - Agent Runner git policy rewritten as an argv-level classifier, replacing a substring match that could not tell `git status` from `git push`.
 

{memstack_skill_loader-4.15.0 → memstack_skill_loader-4.16.0}/README.md

@@ -55,7 +55,7 @@ activate_license(key="your-key", email="you@example.com")
 ```
 Use `key="free"` for the free tier, or your Pro key from [memstack.pro](https://memstack.pro) to unlock all 44 Pro skills (86 free + 44 Pro = 130 total). Then type `list skills` to verify.
 
-> **The first start is slow, and that is normal.** On the very first run after installing or upgrading, the server builds the skill index before it answers anything. Expect roughly a minute, nearly all of it loading the embedding model rather than reading your skills. **The server will look unresponsive for that time.** Let it finish. Every later start reuses the index and is not affected.
+> **The first start is slow, and that is normal.** On the very first run after installing or upgrading, the server builds the skill index before it answers anything. Nearly all of that time is a one-time download of the ~90 MB embedding model, so it tracks your network speed rather than the size of your skill library: indexing 86 skills itself takes about a second. On a fast connection the whole first start is around half a minute; on a slow one it is longer. **The server will look unresponsive for that time.** Let it finish. Every later start reuses the cached model and index and is not affected.
 
 > To override the skills path, set `MEMSTACK_SKILLS_DIR=/path/to/your/memstack/skills`.
 
@@ -63,7 +63,7 @@ Use `key="free"` for the free tier, or your Pro key from [memstack.pro](https://
 
 ## Troubleshooting
 
-**Nothing responds after a fresh install, and it does not seem to be failing either (during Step 4):** the first start builds the skill index before the server answers anything, which takes roughly a minute. Most of that is loading the embedding model, not reading your skills. There is no progress output, so a working first start and a hung one look identical. Wait it out before changing anything. If it is still silent well past a couple of minutes, then treat it as the interpreter mismatch below. Later starts reuse the index and respond immediately.
+**Nothing responds after a fresh install, and it does not seem to be failing either (during Step 4):** the first start builds the skill index before the server answers anything. Most of that is a one-time ~90 MB embedding-model download, not reading your skills, so the wait depends on your connection: around half a minute on a fast one, longer on a slow one. There is no progress output, so a working first start and a hung one look identical. Wait it out before changing anything. If it is still silent well past a few minutes, then treat it as the interpreter mismatch below. Later starts reuse the cached model and index and respond immediately.
 
 **`error: externally-managed-environment` (during Step 2)** — pip refuses to install on a system-managed Python. Add `--break-system-packages` · (in terminal):
 ```bash
@@ -94,7 +94,7 @@ MCP server that vector-indexes all 130 MemStack™ skills so Claude Code can cal
 
 - **No Anthropic API key required:** skill search and indexing run locally and never leave your machine. Three small calls happen on their own at session start — license validation, a Pro-bundle version probe, and a PyPI update check — and every other outbound call is one you trigger ([Data and privacy](#data-and-privacy))
 - **Pro skills auto-detected:** once activated, the Pro skills directory is added to your sources automatically, with no `config.json` edit
-- **Auto-reindex on start:** skills stay current without manual rebuilds. Only startup ever rebuilds, never a search. The first start pays a one-time build of roughly a minute; after that a rebuild happens in the background while the existing index keeps serving, so later starts are not delayed
+- **Auto-reindex on start:** skills stay current without manual rebuilds. Only startup ever rebuilds, never a search. The first start pays a one-time build dominated by the embedding-model download (see [Quick Start](#quick-start-5-minutes)); after that a rebuild happens in the background while the existing index keeps serving, so later starts are not delayed
 - **Memory Engine:** an append-only, versioned fact store with query-time recall scoring — facts decay with age and decay more slowly the more they are recalled. Facts flow in from the diary's `## FACTS` block and are exposed to Claude through five `mem_*` tools (see [Available Tools](#available-tools))
 - **Living memory at session start:** the SessionStart hook injects a compact, token-budgeted digest of the project's top recall-scored facts into context. It fails open — a missing, empty, or unreachable store never blocks startup
 - **8-page localhost dashboard:** Overview, Skills Manager, Burn Report, Memory Browser (project-aware diary reader), Memory Inspector (read-only Memory Engine fact views), Agent Monitor, Referrals, and Settings
@@ -231,9 +231,15 @@ The `pattern` field controls how skills are discovered:
 
 ## Release Notes
 
+### 4.15.1 (August 2026)
+
+- **Fixed: activating a Pro license on a PyPI install downloaded the Pro skills and never indexed them.** The skills landed in `~/.memstack/pro-skills`, activation reported success, and the catalog still showed only the 86 free skills. Setting `MEMSTACK_PRO_LICENSE_KEY` was the only workaround. Both of the paths that decide whether to attach the Pro source now share one predicate.
+- **Activation now takes effect immediately.** The reindex that follows an activation rebuilds with the Pro skills included, and the confirmation reports the post-activation count, so a restart is no longer needed.
+- First-start timing in these docs was reworded: it is dominated by a one-time embedding-model download and therefore varies with network speed, rather than being the fixed "roughly a minute" previously quoted.
+
 ### 4.15.0 (August 2026)
 
-- The skill index moved to the canonical state root, so a relative `vector_db_path` no longer depends on which directory the server happened to start in. **The first start after installing or upgrading rebuilds the index once, which takes roughly a minute**, nearly all of it loading the embedding model. Later starts are unaffected.
+- The skill index moved to the canonical state root, so a relative `vector_db_path` no longer depends on which directory the server happened to start in. **The first start after installing or upgrading rebuilds the index once**, nearly all of that time being a one-time embedding-model download. Later starts are unaffected.
 - New index guard classifies the index as current, drift, stale, absent, or rebuilding, and reports that verdict at startup and in the dashboard. Only startup may rebuild on its own, so no search request ever blocks on one.
 - Agent Runner git policy rewritten as an argv-level classifier, replacing a substring match that could not tell `git status` from `git push`.
 

{memstack_skill_loader-4.15.0 → memstack_skill_loader-4.16.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "memstack-skill-loader"
-version = "4.15.0"
+version = "4.16.0"
 description = "MCP server that vector-indexes MemStack Pro skills for on-demand loading"
 readme = "README.md"
 requires-python = ">=3.10"

{memstack_skill_loader-4.15.0 → memstack_skill_loader-4.16.0}/src/memstack_skill_loader/__init__.py

@@ -1,3 +1,3 @@
 """MemStack Skill Loader — MCP server for semantic skill search."""
 
-__version__ = "4.15.0"
+__version__ = "4.16.0"

{memstack_skill_loader-4.15.0 → memstack_skill_loader-4.16.0}/src/memstack_skill_loader/config.py

@@ -126,6 +126,32 @@ def _auto_discover_skills() -> SkillSource | None:
     return None
 
 
+def _pro_license_present() -> bool:
+    """Return True if this installation has a Pro license on either supported path.
+
+    Both call sites in load_config must ask this question the same way. They did
+    not: the env-var-only form was written once, copied into the auto-discovery
+    branch, and then fixed in only one of the two copies (07676eb, 2026-05-20).
+    For the two and a half months after that, every PyPI install (which always
+    takes the auto-discovery branch, because a wheel has no config.json beside
+    the package) downloaded Pro skills on activation and never indexed them.
+    Keep this predicate the single source of truth so a third copy cannot drift.
+
+    The env var and license.json are both first-class: license.json is the
+    documented primary path (activate_license writes it), and the env var is the
+    documented alternative. This mirrors get_license_key() in license.py, which
+    has always resolved both.
+
+    Note this answers "is a license present", not "is it valid". Entitlement is
+    enforced at serve time against a live validate_license() call, so a stale
+    license.json here only affects what gets indexed, never what a caller is
+    allowed to read.
+    """
+    if os.environ.get("MEMSTACK_PRO_LICENSE_KEY"):
+        return True
+    return (Path.home() / ".memstack" / "license.json").exists()
+
+
 def load_config(config_path: Path | None = None) -> Config:
     """Load config from JSON file. Falls back to auto-discovery if not found."""
     if config_path is None:
@@ -138,7 +164,7 @@ def load_config(config_path: Path | None = None) -> Config:
             auto_reindex_on_start=True,
             config_source="auto-discovery",
         )
-        if os.environ.get("MEMSTACK_PRO_LICENSE_KEY"):
+        if _pro_license_present():
             config = config.with_pro_skills()
         return config
 
@@ -184,7 +210,7 @@ def load_config(config_path: Path | None = None) -> Config:
     )
 
     # Auto-detect pro-skills if license key is set (env var or license.json)
-    if os.environ.get("MEMSTACK_PRO_LICENSE_KEY") or (Path.home() / ".memstack" / "license.json").exists():
+    if _pro_license_present():
         config = config.with_pro_skills()
 
     return config

{memstack_skill_loader-4.15.0 → memstack_skill_loader-4.16.0}/src/memstack_skill_loader/dashboard.html

@@ -2141,7 +2141,7 @@
         <button class="mcp-tools-save-btn" style="background:#30363d;" onclick="verifyLicenseKey()">Verify</button>
         <span id="licenseKeyStatus" style="font-size:0.75rem;color:#484f58;"></span>
       </div>
-      <p style="color:#484f58;font-size:0.72rem;margin:0.35rem 0 0;">Unlocks Pro-tier compression and 42 exclusive skills. Stored at ~/.memstack/license.json.</p>
+      <p style="color:#484f58;font-size:0.72rem;margin:0.35rem 0 0;">Unlocks Pro-tier compression and <span id="settings-pro-skill-count">all</span> exclusive skills. Stored at ~/.memstack/license.json.</p>
     </div>
   </div>
 
@@ -5370,6 +5370,7 @@ async function loadSettings() {
     loadGitWorkflowGlobal();
     loadAgentModes();
     loadLicenseStatus();
+    loadProSkillCount();
     settingsLoaded = true;
   } catch (e) {
     console.error('Settings load failed:', e);
@@ -5396,6 +5397,25 @@ async function loadLicenseStatus() {
   }
 }
 
+// Pro skill count in the licence blurb, derived from /api/skills rather than
+// written into the markup -- a literal here read "42" while the enforced count
+// was 44. The static text says "all", so a failed or index-less fetch degrades
+// to a sentence that is still true rather than to a stale number.
+async function loadProSkillCount() {
+  const el = document.getElementById('settings-pro-skill-count');
+  if (!el) return;
+  try {
+    const res = await fetch('/api/skills', {headers: AUTH_GET});
+    const d = await res.json();
+    // Absent/unreadable index responses omit display_pro_count entirely and
+    // report pro_count 0; neither should overwrite the fallback.
+    const n = d.display_pro_count;
+    if (Number.isFinite(n) && n > 0) el.textContent = n;
+  } catch (e) {
+    /* keep the "all" fallback; a count is not worth a broken panel */
+  }
+}
+
 async function saveLicenseKey() {
   const input = document.getElementById('licenseKeyInput');
   const statusEl = document.getElementById('licenseKeyStatus');