Build RedXaiHM v0.1 reference database engine

[RedXDevelopment]

Summary

Builds the first working RedXaiHM reference implementation for durable .RedXai databases while preserving the original language design.

Language and validation

• Exact RedXaiStore header with required database ID=1
• Optional IDs on values, with 0 invalid and supplied IDs unique across a document/project
• Case-insensitive Boolean and NELL values, including original NELL$
• Numbers, percentages, strings, symbols, references, collections, nested ;[ ... ]: arrays, and retained comments
• Original positional closing metadata plus canonical named metadata
• Access-point placement, API-key shape, allowed-language extensions, sharing, global access, and reference validation

Engine

• Lexer, parser, AST helpers, canonical serializer, and public Node.js SDK
• Database-scoped ID/name indexes
• Find, set, rename, add, move, copy, and delete operations
• Validated transactions with rollback
• Exact .RedXai extension enforcement
• Lock files, stale-lock recovery, owner-only temporary files, fsync, atomic rename, backups, and validated backup recovery

Tooling

• CLI for init, validate, format, get, set, delete, and edit
• Token-protected localhost editor that validates and atomically saves
• Official red-X SVG and Windows .RedXai file association installer
• Specification, security model, roadmap, identity-account example, and legacy syntax example
• Zero runtime dependencies
• CI on Node.js 20 and 22

Verification

Local npm run ci passes 32 tests with 0 failures, covering parsing, original syntax compatibility, exact header rules, validation, project-wide duplicate IDs, forward references, indexed SDK operations, rollback, storage/backup/recovery, editor token protection, and editor saves.

Security boundary

This does not claim custom encryption. RedX Crypt remains a later milestone and will use reviewed authenticated-encryption primitives. The current alpha should not be migrated into production identity storage until migration, dual-write, backup/restore, and load testing are complete.