wip

Author: simbo1905

AGENTS.md

@@ -15,20 +15,6 @@ This file provides guidance to agents (human or AI) when working with code in th
 
 ## Quick Start Commands
 
-### Building the Project
-```bash
-# Full build
-mvn clean compile
-mvn package
-
-# Build specific module
-mvn clean compile -pl json-java21
-mvn package -pl json-java21
-
-# Build with test skipping
-mvn clean compile -DskipTests
-```
-
 ### Running Tests
 
 You MUST NOT ever filter test output as you are looking for something you do not know what it is that is the nature of debugging.
@@ -260,7 +246,7 @@ PY
 ### Debugging Parser Issues
 1. Enable `FINER` logging: `-Djava.util.logging.ConsoleHandler.level=FINER`
 2. Use `./mvn-test-no-boilerplate.sh` for clean output
-3. Focus on specific test: `-Dtest=JsonParserTests#testMethod`
+3. Focus on specific test: `-Dtest=JsonParserTests#testMethod` using `FINEST` logging
 4. Check JSON Test Suite compatibility with compatibility suite
 
 ### API Compatibility Testing
@@ -292,11 +278,6 @@ PY
 - **Why:** Early detection of upstream API changes to keep the backport aligned.
 - **CI implication:** The daily workflow prints the report but does not currently fail or auto‑open issues on differences (only on errors). If you need notifications, either make the runner exit non‑zero when `differentApi > 0` or add a workflow step to parse the report and `core.setFailed()` when diffs are found.
 
-### json-java21-schema
-- **Validator** for JSON Schema 2020-12 features
-- **Tests** include unit, integration, and annotation-based checks (see module guide)
-- **OpenRPC IT**: See `json-java21-schema/src/test/java/io/github/simbo1905/json/schema/OpenRPCSchemaValidationIT.java` and resources under `json-java21-schema/src/test/resources/openrpc/` (thanks to OpenRPC meta-schema and examples, Apache-2.0).
-
 ## Security Notes
 - **Stack exhaustion attacks**: Deep nesting can cause StackOverflowError
 - **API contract violations**: Malicious inputs may trigger undeclared exceptions

json-java21-schema/AGENTS.md

@@ -267,16 +267,16 @@ flowchart LR
 - Dedup ensures each remote is compiled at most once.
 
 4.2 Object/runtime (MVF)
-- Exactly as today: Runtime follows only Local references inside the primary root.
-- Remote roots are compiled and parked in the registry but not traversed (until future work/tests enable it).
+- Exactly as today: Runtime follows Local references inside the current root which may be only one if no remote ref.
+- Remote roots are compiled and parked in the registry but and traversed
 - This preserves byte-for-byte API behavior and test outcomes.
 
 ⸻
 
 5) Your words (short summary, in your own terms)
 - "Don't add a new phase; make compile naturally handle multiple sources using a stack that starts with the initial schema."
 - "Collect local vs remote $ref while compiling; rewrite/tag them; push unseen remotes; deduplicate; compile each into its own root; when the stack is empty, we have an immutable list of roots."
-- "Runtime stays the same now (single root, local refs only), so all existing tests pass unmodified."
+- "Runtime stays the same when no remote ref so only a (single root, when local refs only), so all existing tests pass unmodified."
 - "Use sealed interfaces / data-oriented tags so future remote traversal becomes a simple exhaustive match without touching today's behavior."
 - "Cycle at compile-time should throw a named JDK exception (no new type)."
 - "No legacy; no recursion; single path; stack-based eval and compile."