docs: correct feature claims across website pages

Fix unrealistic wording verified against source: shell commands, build
targets and properties, MMTk plans, JIT compiler tiers, filesystem
read/write status, driver lists, JDWP port, and boot parameters.
Restore 'Developed with AI Agents' section on front page.
Remove JDWP integration test coverage from docs.

Author: LSantha

website/architecture/overview.md

@@ -12,15 +12,15 @@
 │                         Kernel                                │
 │  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐  │
 │  │  Scheduler  │  │  Memory Mgmt│  │  Interrupt Handling │  │
-│  │  (Isolate)  │  │  (MMTk/GC)  │  │  (IDT, PIC, APIC)   │  │
+│  │  (Isolate)  │  │  (def/GC)   │  │  (IDT, PIC, APIC)   │  │
 │  └─────────────┘  └─────────────┘  └─────────────────────┘  │
 └──────────────────────────┬──────────────────────────────────┘
                            │
 ┌──────────────────────────▼──────────────────────────────────┐
 │                      VmImpl (JVM)                           │
 │  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐  │
 │  │  Classloader│  │  JIT Compiler│  │  VM Magic / Unsafe  │  │
-│  │  (Plugin)   │  │  (L1 / L2)  │  │  (VMMagic annos)    │  │
+│  │  (Plugin)   │  │  (L1a/L1b/L2)│  │  (VMMagic annos)    │  │
 │  └─────────────┘  └─────────────┘  └─────────────────────┘  │
 └──────────────────────────┬──────────────────────────────────┘
                            │
@@ -35,7 +35,7 @@
 │  Core Services│  │   Drivers     │  │ Filesystems   │
 │  (Naming,     │  │  (PCI, USB,   │  │  (Ext2, FAT,  │
 │   Security,   │  │   IDE, Net,   │  │   ISO9660,    │
-│   Logging)    │  │   Audio)      │  │   NFS, NTFS)  │
+│   Logging)    │  │   Video)      │  │   NFS, NTFS)  │
 └───────────────┘  └───────────────┘  └───────────────┘
         │                  │                  │
         ▼                  ▼                  ▼
@@ -70,9 +70,9 @@ JNode uses **Isolates** (similar to processes but lighter-weight):
 - See [Plugin System](https://github.com/LSantha/jnode_ai/wiki/Plugin-System)
 
 ### 4. MMTk Integration
-- **Memory Management Toolkit** (Rust) for GC
-- JNode binds via JNI: `org.jnode.vm.memmgr.mmtk`
-- Supports: Immix, GenImmix, MarkSweep, SemiSpace
+- **Memory Management Toolkit** bindings for garbage collection
+- Available MMTk plans: `org.jnode.vm.memmgr.mmtk.ms` (MarkSweep), `...genrc` (generational), `...nogc` (no collection)
+- Default memory manager is `org.jnode.vm.memmgr.def`; MMTk plans are experimental
 - See [MMTk Bindings](https://github.com/LSantha/jnode_ai/wiki/MMTk-Bindings)
 
 ### 5. VMMagic Annotations
@@ -124,13 +124,12 @@ See [Paging Implementation](https://github.com/LSantha/jnode_ai/wiki/Paging-Impl
 
 | Compiler | Tier | Status |
 |----------|------|--------|
-| **L1** | Baseline | ✅ Stable |
-| **L2** | Optimizing | ⚠️ Experimental |
-| **None** | Interpreter | ✅ Always available |
+| **L1A / L1B** | Baseline | Default |
+| **Stub** | Stub generation | For non-Java natives |
+| **L2** | Optimizing | Test-only, not selected at boot |
 
-- L1: Fast compilation, basic optimization
-- L2: SSA-based, inlining, escape analysis
-- Selected via `jnode.compiler` property
+- L1A/L1B: baseline bytecode compilers; `jnode.compiler` accepts `L1A`, `L1B`, or `default` (→ L1A)
+- L2: optimizing compiler, used only in test harness (`testCompilers`)
 - See [JIT Compilers](https://github.com/LSantha/jnode_ai/wiki/JIT-Compilers)
 
 ## Further Reading

website/development/index.md

@@ -76,21 +76,6 @@ sh build.sh regression-tests
 
 Runs shell command tests against a booted JNode image.
 
-### JDWP Integration Tests
-
-Requires a **running JNode VM with JDWP listener** (VirtualBox recommended):
-
-```bash
-# Start JNode in VirtualBox with JDWP on port 8000
-# Then run:
-cd tests/jdwp
-python3 -m pytest -v
-```
-
-- 75 tests covering: classes, methods, fields, threads, invocation, constructors
-- See [tests/jdwp/AGENTS.md](https://github.com/LSantha/jnode_ai/blob/master/tests/jdwp/AGENTS.md) for setup
-- **Run these after any JDWP code change** — they are the regression suite
-
 ### Boot Testing
 
 ```bash
@@ -129,8 +114,8 @@ See [jnode-interact skill](https://github.com/LSantha/jnode_ai/blob/master/.open
 Best with VirtualBox:
 
 1. Enable Serial Port 1 → Host Pipe → `/tmp/jnode-com1`
-2. Port forward: `VBoxManage modifyvm "JNode" --natpf1 "jdwp,tcp,,8000,,8000"`
-3. Connect: `jdb -attach localhost:8000`
+2. Port forward: `VBoxManage modifyvm "JNode" --natpf1 "jdwp,tcp,,6789,,6789"`
+3. Connect: `jdb -attach localhost:6789`
 
 See [VirtualBox Guide](../getting-started/virtualbox.md) for JDWP setup.
 
@@ -181,20 +166,10 @@ The project uses a label system managed by [sync-labels.js](https://github.com/L
 
 | Family | Examples |
 |--------|----------|
-| `kind/*` | `kind/bug`, `kind/feature`, `kind/investigate`, `kind/wiki` |
+| `kind/*` | `kind/bug`, `kind/feature`, `kind/investigate`, `kind/chore` |
 | `agent/*` | `agent/in-progress`, `agent/done`, `agent/needs-info` |
 | `area/*` | `area/core`, `area/fs`, `area/net`, `area/vm`, `area/build` |
 
 ### Agent Automation
 
-Trigger OpenCode agent via issue comments:
-
-```bash
-/oc fix        # Fix the issue
-/oc investigate # Investigate and report
-/oc review     # Review a PR
-/oc wiki       # Update wiki
-/oc triage     # Triage new issue
-```
-
-See [opencode.yml](https://github.com/LSantha/jnode_ai/blob/master/.github/workflows/opencode.yml) and [jnode-issue-resolver skill](https://github.com/LSantha/jnode_ai/blob/master/.opencode/skills/jnode-issue-resolver/SKILL.md).
+An experimental agent-based workflow exists for triaging and resolving issues. It's still exploratory — see [opencode.yml](https://github.com/LSantha/jnode_ai/blob/master/.github/workflows/opencode.yml) and [jnode-issue-resolver skill](https://github.com/LSantha/jnode_ai/blob/master/.opencode/skills/jnode-issue-resolver/SKILL.md) for details.

website/development/testing.md

@@ -6,7 +6,6 @@
 |------|---------|-------------|
 | **JUnit** | `sh build.sh tests` | Unit tests for all subprojects |
 | **Regression** | `sh build.sh regression-tests` | Shell command integration tests |
-| **JDWP** | `pytest tests/jdwp/` | Remote debugging protocol tests |
 | **Boot** | QEMU/VirtualBox | Full OS boot verification |
 
 ## JUnit Tests
@@ -38,37 +37,6 @@ sh build.sh regression-tests
 
 Tests are defined in `tests/regression/` and executed via the shell.
 
-## JDWP Integration Tests
-
-**Requirements:**
-- JNode running in VirtualBox with JDWP listener on port 8000
-- Serial console configured (for agent interaction)
-- Python 3.8+ with pytest
-
-```bash
-# 1. Start JNode in VirtualBox (see VirtualBox guide)
-# 2. Verify JDWP: telnet localhost 8000 → "JDWP Handshake"
-# 3. Run tests
-cd tests/jdwp
-python3 -m pytest -v
-```
-
-### Test Coverage (75 tests)
-
-| Category | Tests |
-|----------|-------|
-| Classes, methods, fields | 18 |
-| Threads, thread groups | 12 |
-| Stack traces (`where`) | 8 |
-| Classpath, connectors | 6 |
-| Method invocation | 15 |
-| Constructors | 10 |
-| Version, capabilities | 6 |
-
-**Run after any JDWP code change** — this is the regression suite for the debug backend.
-
-See [tests/jdwp/AGENTS.md](https://github.com/LSantha/jnode_ai/blob/master/tests/jdwp/AGENTS.md) for full setup.
-
 ## Boot Testing
 
 ### QEMU (CI)
@@ -134,11 +102,12 @@ The [ant.yml](https://github.com/LSantha/jnode_ai/blob/master/.github/workflows/
 
 ## Test Utilities
 
-| Tool | Purpose |
-|------|---------|
-| `jnode-interact` skill | Interactive QEMU testing via serial |
-| `jnode-java-coding` skill | Compile/run Java on live JNode |
-| `filesystem-debug` skill | Analyze FS test failures |
-| `jnode-kdb-serial` skill | Kernel debugger via serial |
+| Tool | Purpose | Location |
+|------|---------|----------|
+| `jnode-interact` skill | Interactive QEMU testing via serial | repo `.opencode/skills/` |
+| `filesystem-debug` skill | Analyze FS test failures | repo `.opencode/skills/` |
+| `jnode-issue-resolver` skill | Issue/PR resolution protocol | repo `.opencode/skills/` |
+| `jnode-java-coding` skill | Compile/run Java on live JNode | user config |
+| `jnode-kdb-serial` skill | Kernel debugger via serial | user config |
 
-See [.opencode/skills/](https://github.com/LSantha/jnode_ai/tree/master/.opencode/skills) for available debugging skills.
+See [.opencode/skills/](https://github.com/LSantha/jnode_ai/tree/master/.opencode/skills) for the repo's skills.

website/getting-started/building.md

@@ -13,9 +13,9 @@ sh build.sh <target> [options]
 | Target | Description |
 |--------|-------------|
 | `assemble` | Compile Java, build native, create bootimage (no ISO) |
-| `cd-x86-lite` | **Minimal x86 ISO** — kernel, shell, basic drivers (~15 MB) |
-| `cd-x86_64-lite` | Minimal x86_64 ISO (experimental) |
-| `cd-x86` | Full x86 ISO with GUI, network, all plugins |
+| `cd-x86-lite` | Bootable x86 CD image (kernel, shell, core subsystems) |
+| `cd-x86_64-lite` | Bootable x86_64 CD image (experimental) |
+| `cd-x86` | Same as `cd-x86-lite`, plus source tarball included on the CD |
 | `tests` | Run all JUnit + regression tests |
 | `clean` | Remove all build artifacts |
 
@@ -57,10 +57,12 @@ Key properties in `jnode.properties` or via `-D`:
 | Property | Default | Description |
 |----------|---------|-------------|
 | `jnode.bits` | `32` | Target architecture: `32` or `64` |
-| `jnode.memmgr.plugin.id` | `org.jnode.vm.memmgr.mmtk.MMTkMemoryManager` | GC implementation |
-| `jnode.compiler` | `l1` | JIT: `l1`, `l2`, or `none` |
+| `jnode.memmgr.plugin.id` | `org.jnode.vm.memmgr.def` | Memory manager; alternatives: `org.jnode.vm.memmgr.mmtk.nogc` (beta), `org.jnode.vm.memmgr.mmtk.genrc` (alpha), `org.jnode.vm.memmgr.mmtk.ms` |
+| `jnode.compiler` | `default` | JIT compiler: `L1A`, `L1B`, or `default` |
 | `jnode.enable.jnasm` | `true` | Use JNasm assembler |
-| `jnode.plugin.list` | `default-plugin-list.xml` | Plugin set: `default` or `full` |
+| `target.plugin.list` | `default` | Plugin set for the jar packager: `default` or `full` |
+
+The bootimage itself always uses `all/conf/system-plugin-list.xml`.
 
 ## Build Output Structure
 

website/getting-started/quick-start.md

@@ -1,6 +1,6 @@
 # Quick Start
 
-Get JNode running in 5 minutes.
+Build a JNode ISO and boot it in QEMU.
 
 ## Prerequisites
 
@@ -44,9 +44,9 @@ jnode>
 ```bash
 jnode> help
 jnode> ls /
-jnode> ps
+jnode> memory
 jnode> vminfo
-jnode> mem
+jnode> uname
 ```
 
 Type `exit` to shut down cleanly.

website/getting-started/virtualbox.md

@@ -36,18 +36,18 @@ You'll see the boot banner and shell prompt.
 
 ## JDWP Remote Debugging
 
-JNode listens for JDWP on port **8000** by default (configured in `jnode.properties`).
+JNode's `debug` command starts a JDWP listener on port **6789** by default (override with the `port` argument).
 
 ### Port Forwarding (NAT)
 
 ```bash
-VBoxManage modifyvm "JNode" --natpf1 "jdwp,tcp,,8000,,8000"
+VBoxManage modifyvm "JNode" --natpf1 "jdwp,tcp,,6789,,6789"
 ```
 
 ### Connect with jdb
 
 ```bash
-jdb -attach localhost:8000
+jdb -attach localhost:6789
 ```
 
 ### Supported JDWP Features
@@ -63,7 +63,7 @@ jdb -attach localhost:8000
 | Watchpoints | ❌ |
 | Breakpoints | ⚠️ Limited |
 
-See [JDWP Setup Wiki](https://github.com/LSantha/jnode_ai/wiki/GDB-Debugging-Support) and [JDWP Tests](../development/testing.md#jdwp-integration-tests).
+See [JDWP Setup Wiki](https://github.com/LSantha/jnode_ai/wiki/GDB-Debugging-Support).
 
 ## Shared Folders (Optional)
 
@@ -81,7 +81,7 @@ For file transfer between host and JNode:
 |-------|-----|
 | Boot hangs at "Loading..." | Ensure **I/O APIC** enabled, try `-cpu pentium` in QEMU first |
 | No serial output | Verify pipe path, check `socat` / PuTTY connection |
-| JDWP connection refused | Check port forwarding, firewall, `jnode.properties` `jdwp.port=8000` |
+| JDWP connection refused | Check port forwarding, firewall, `debug` command arguments |
 | Network not working | Try Bridged Adapter instead of NAT; check `dhcp eth0` |
 
 ## VM Export for Distribution

website/index.md

@@ -4,15 +4,21 @@
 [![Java 8](https://img.shields.io/badge/Java-8-blue.svg)](https://openjdk.java.net/projects/jdk/8/)
 [![License](https://img.shields.io/badge/License-LGPL%202.1-green.svg)](https://www.gnu.org/licenses/lgpl-2.1.html)
 
-**JNode** is an experimental operating system written in Java. It builds its own JVM, kernel, drivers, filesystems, network stack, and GUI, and boots them on bare metal with only a few hundred lines of assembly at the very bottom. It's a platform for exploring OS design, JVM implementation, and system-level Java. This fork is developed at scale with modern AI-based, agentic methodologies — OpenCode agents resolve issues, review code, and boot-test every build.
+**JNode** is an experimental operating system written in Java. It builds its own JVM, kernel, drivers, filesystems, network stack, and GUI, and boots them on bare metal with only a few hundred lines of assembly at the very bottom. It's a platform for exploring OS design, JVM implementation, and system-level Java.
+
+---
+
+## Developed with AI Agents
+
+This is a fork of the classic JNode project, maintained as a living experiment in agent-driven development. GitHub Actions and OpenCode agents triage issues, implement fixes, review pull requests, update the wiki, and boot every build in QEMU before it lands. Batching is coordinated through an orchestrator workflow, with agentic skills for QEMU boot testing, JDWP debugging, and filesystem diagnosis.
 
 ---
 
 ## Quick Links
 
 | Topic | Description |
 |-------|-------------|
-| [:material-rocket-launch: Quick Start](getting-started/quick-start.md) | Build and boot your first JNode ISO in 5 minutes |
+| [:material-rocket-launch: Quick Start](getting-started/quick-start.md) | Build and boot your first JNode ISO |
 | [:material-hammer-wrench: Building](getting-started/building.md) | Detailed build instructions for x86 and x86_64 |
 | [:material-cpu-64-bit: Run in QEMU](getting-started/qemu.md) | Test JNode in QEMU with serial logging |
 | [:material-virtualbox: Run in VirtualBox](getting-started/virtualbox.md) | JDWP debugging support via VirtualBox |
@@ -48,7 +54,7 @@ See [Architecture Overview](architecture/overview.md) for details.
 | [Network Stack](subsystems.md#network-stack) | IPv4, TCP, UDP, DNS, NetAPI | [Network-Stack](https://github.com/LSantha/jnode_ai/wiki/Network-Stack) |
 | [Shell](subsystems.md#shell) | Commands, syntax, aliases, plugins | [Shell-Commands](https://github.com/LSantha/jnode_ai/wiki/Shell-Commands) |
 | [GUI/AWT](subsystems.md#gui-awt) | Video drivers, input, AWT peers, Thinlet | [GUI-AWT](https://github.com/LSantha/jnode_ai/wiki/GUI-AWT) |
-| [Drivers](subsystems.md#drivers) | PCI, USB, IDE, SCSI, Ethernet, Audio | [Driver-Framework](https://github.com/LSantha/jnode_ai/wiki/Driver-Framework) |
+| [Drivers](subsystems.md#drivers) | PCI, USB, IDE, SCSI, Ethernet, video, input | [Driver-Framework](https://github.com/LSantha/jnode_ai/wiki/Driver-Framework) |
 
 See [Subsystems](subsystems.md) for details.
 
@@ -57,7 +63,7 @@ See [Subsystems](subsystems.md) for details.
 ## Development
 
 - [Build & Test](development/index.md) — Ant-based build, JUnit, regression tests
-- [Testing](development/testing.md) — JUnit, regression tests, JDWP integration tests
+- [Testing](development/testing.md) — JUnit, regression, boot testing
 
 ---
 
@@ -78,12 +84,6 @@ See [Reference](reference.md) for details.
 
 ---
 
-## Developed with AI Agents
-
-This is a fork of the classic JNode project, maintained as a living experiment in agent-driven development. GitHub Actions and OpenCode agents triage issues, implement fixes, review pull requests, update the wiki, and boot every build in QEMU before it lands. Batching is coordinated through an orchestrator workflow, with agentic skills for QEMU boot testing, JDWP debugging, and filesystem diagnosis.
-
----
-
 ## Community
 
 - **Issues**: [GitHub Issues](https://github.com/LSantha/jnode_ai/issues)