[tristantarrant]

Fixes the bug where ReadlineConsole always ran commands under a runtime whose context was a fresh internal default, silently shadowing whatever was configured via SettingsBuilder.aehsContext(...).

Changes

• ReadlineConsole — when an explicit context is configured on settings, use exactly that instance; otherwise keep today's managed fallback (new DefaultAeshContext(exportManager)) unchanged.
• Settings — additive default boolean hasExplicitAeshContext() { return true; }. External implementors are unaffected (their getter value was already used unconditionally by AeshCommandRuntimeBuilder.settings()); the console now honours it consistently too.
• SettingsImpl — precise explicitness tracking: setter marks on non-null, lazy default never does; copy constructor only carries explicitly configured contexts so copied settings keep their own fresh defaults.

Why this shape

aeshContext() is always non-null (lazy init, relied upon widely), so "user set one" vs "lazy default" needed a distinguisher — hence the additive interface method rather than changing getter semantics or nullability.

New regression test asserts console.context() returns identically the instance passed via settings when explicitly configured, and that unset settings still fall back to a managed default. Full module suite green (1577 tests).

Closes #687

[stalep]

Thanks!