mftsccs-node 0.2.23 → 0.2.25

package/README.md

@@ -2,7 +2,7 @@
 
 **mftsccs-node** - Full Pack of Concept and Connection System
 
-A powerful TypeScript library for building knowledge graphs and managing complex relationships between concepts. CCS-JS provides a complete solution for creating, querying, and managing concepts and connections with support for offline-first architecture, transactions, and flexible schema querying.
+A powerful TypeScript library for building knowledge graphs and managing complex relationships between concepts. CCS-JS provides a complete solution for creating, querying, and managing concepts and connections with support for transactions, runtime caching, and flexible schema querying.
 
 [![npm version](https://img.shields.io/npm/v/mftsccs-node.svg)](https://www.npmjs.com/package/mftsccs-node)
 [![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](https://opensource.org/licenses/ISC)
@@ -106,7 +106,7 @@ A **Composition** is a hierarchical structure of related concepts and connection
 
 ## ✨ Key Features
 
-- 🔄 **Offline-First Architecture**: Local IndexedDB storage with backend synchronization
+- 🔄 **Runtime Caching**: In-memory compatibility store and backend synchronization helpers
 - 🔐 **Security & Access Control**: Fine-grained permissions per concept/connection
 - 🌳 **Binary Tree Indexing**: O(log n) lookups by ID, character, and type
 - 📦 **Transactions**: ACID-like operations with rollback support
@@ -149,8 +149,8 @@ updateAccessToken('new-access-token');
 
 **Important**:
 - Call `init()` once at application startup
-- System loads data from IndexedDB asynchronously
-- Check `IdentifierFlags` to ensure data is loaded before queries
+- `init()` returns a Promise; await it before making API calls that depend on auth or hydrated caches
+- `IdentifierFlags` are also updated for callers that poll readiness
 
 ```typescript
 import { IdentifierFlags } from 'mftsccs-node';
@@ -912,31 +912,9 @@ const retrieved = await GetComposition(composition.id);
 console.log(retrieved); // Full nested structure
 ```
 
-### Local Storage (Offline Support)
+### Local Compatibility APIs
 
-Work with local concepts for offline functionality:
-
-```typescript
-import {
-  CreateTheConceptLocal,
-  GetCompositionLocal,
-  MakeTheInstanceConceptLocal
-} from 'mftsccs-node';
-
-// Create local concept (survives offline)
-const localConcept = await MakeTheInstanceConceptLocal(
-  "note",
-  "Offline note",
-  1,
-  4
-);
-
-// Retrieve from local storage
-const composition = await GetCompositionLocal(
-  localConcept.id,
-  localConcept.userId
-);
-```
+Frontend-origin local/offline helpers are not exported by the Node package. Server consumers should use the backend-backed concept, connection, and composition APIs instead of local concept creation helpers.
 
 ### Bulk Operations
 
@@ -1041,7 +1019,7 @@ ccs-js/
 │   ├── Api/              # Backend API integration (45 files)
 │   ├── Services/         # Business logic layer (73+ files)
 │   ├── DataStructures/   # Core data models (70+ files)
-│   ├── Database/         # IndexedDB persistence (4 files)
+│   ├── Database/         # Node in-memory compatibility storage (4 files)
 │   ├── Constants/        # Configuration (2 files)
 │   ├── Helpers/          # Utility functions (3 files)
 │   ├── Drawing/          # UI visualization (2 files)
@@ -1121,6 +1099,40 @@ const documents = await FreeschemaQueryApi(query, "token");
 
 ---
 
+## Local Package Testing
+
+You can call `SchemaQueryListener` from this repository without creating another project.
+
+1. Copy `scripts/.env.example` to `scripts/.env` and set `CCS_BASE_URL`, `CCS_ACCESS_TOKEN`, and optionally `CCS_SCHEMA_QUERY_FILE`.
+2. Edit `scripts/schema-query.example.json` or create another query JSON file.
+3. Run:
+
+```bash
+npm run schemaquery:test
+```
+
+To reuse an already-built `dist/bundle.js`, run:
+
+```bash
+npm run schemaquery:test:built -- --query scripts/schema-query.example.json
+```
+
+You can override values from the command line:
+
+```bash
+npm run schemaquery:test -- --query scripts/schema-query.example.json --base-url https://your-api-url.com --token your-token --type YourTypeName --format DATAID
+```
+
+The runner prints the full `SchemaQueryListener` result as JSON, including the top-level `count`.
+
+If the backend returns an error, inspect the raw API response:
+
+```bash
+npm run schemaquery:test:built -- --query scripts/schema-query.example.json --raw
+```
+
+---
+
 ## 🤝 Contributing
 
 Contributions are welcome! Please follow these steps: