fix(build): update build and test tooling configuration, migrate project config to .smartconfig.json, and align TypeScript typings

readme.hints.md

@@ -3,9 +3,11 @@
 ## TC39 Decorator Migration (v6.0.0) - ✅ COMPLETED
 
 ### Final Status: All Tests Passing (157/157)
+
 Migration successfully completed on 2025-11-17.
 
 ### What Changed:
+
 - ✅ Removed `experimentalDecorators` from tsconfig.json
 - ✅ Refactored all 7 decorators to TC39 Stage 3 syntax
   - 5 property decorators: @globalSvDb, @svDb, @unI, @index, @searchable
@@ -14,13 +16,16 @@ Migration successfully completed on 2025-11-17.
 - ✅ All tests passing across Node.js and Deno runtimes
 
 ### Critical Discovery: TC39 Metadata Access Pattern
+
 **THE KEY INSIGHT**: In TC39 decorators, metadata is NOT accessed via `constructor[Symbol.metadata]`. Instead:
+
 - **Field decorators**: Write to `context.metadata`
 - **Class decorators**: Read from `context.metadata` (same shared object!)
 - The `context.metadata` object is shared between all decorators on the same class
 - Attempting to write to `constructor[Symbol.metadata]` throws: "Cannot assign to read only property"
 
 ### Implementation Pattern:
+
 ```typescript
 // Field decorator - stores metadata
 export function svDb() {
@@ -46,25 +51,30 @@ export function Collection(dbArg: SmartdataDb) {
 ```
 
 ### Runtime Compatibility:
+
 - ✅ **Node.js v23.8.0**: Full TC39 support
 - ✅ **Deno v2.5.4**: Full TC39 support
 - ❌ **Bun v1.3.0**: No TC39 support (uses legacy decorators only)
   - Removed "+bun" from test filenames to skip Bun tests
 
 ### Key Technical Notes:
+
 1. **Metadata Initialization Timing**: Class decorators run AFTER field decorators, allowing them to read accumulated metadata and initialize prototypes before any instances are created
 2. **Prototype vs Instance Properties**: Properties set on prototype are accessible via `this.propertyName` in instances
 3. **TypeScript Lib Support**: TypeScript 5.9.3 includes built-in decorator types (no custom lib configuration needed)
 4. **Interface Naming**: Used `ISmartdataDecoratorMetadata` extending `DecoratorMetadataObject` for type safety
 
 ### Files Modified:
+
 - ts/classes.doc.ts (property decorators + metadata interface)
 - ts/classes.collection.ts (class decorators + prototype initialization)
 - tsconfig.json (removed experimentalDecorators flag)
-- test/*.ts (renamed files to remove "+bun" suffix)
+- test/\*.ts (renamed files to remove "+bun" suffix)
 
 ### Test Results:
+
 All 157 tests passing across 10 test files:
+
 - test.cursor.ts: 7/7
 - test.deno.ts: 11/11 (queries working correctly!)
 - test.search.advanced.ts: 41/41
@@ -73,6 +83,7 @@ All 157 tests passing across 10 test files:
 - And 5 more test files
 
 ### Migration Learnings for Future Reference:
+
 1. `context.metadata` is the ONLY way to share state between decorators
 2. Class decorators must initialize prototypes from metadata immediately
 3. `Symbol.metadata` on constructors is read-only (managed by runtime)
@@ -82,10 +93,13 @@ All 157 tests passing across 10 test files:
 ## ES2022 Class Fields & Prototype Getters - Fixed in v7.0.15
 
 ### Issue
+
 ES2022 class fields (`useDefineForClassFields: true`) create own properties during construction that shadow prototype getters defined by decorators.
 
 ### Solution
+
 Use `declare` keyword for instance properties that are accessed via prototype getters:
+
 ```typescript
 // In SmartDataDbDoc (ts/classes.doc.ts):
 declare public collection: SmartdataCollection<any>;  // Type-only, no JS emitted
@@ -93,6 +107,7 @@ declare public manager: TManager;  // Type-only, no JS emitted
 ```
 
 ### Key Insight
+
 - `declare` tells TypeScript this is a type-only declaration
 - No JavaScript code is emitted for `declare` properties
 - Prototype getters defined by `@Collection` and `@managed` decorators are no longer shadowed