Reconcile logging.console defaults across configuration references #769

The current references disagree about the default for logging.console:

• Configuration options says true.
• Logging configuration says false.

Public Harper source at 9993e3e supports disabled console capture when this option is absent: the live configuration handler uses logOptions.console ?? false, and defaultConfig.yaml omits the key. The schema description also says true, so it should not be used alone as evidence of the runtime default. This is a source trace, not a test of every released binary.

Confirm the intended supported-version default, then align the current documentation. Coordinate any schema-description correction with its source owner; this tracker does not request a runtime behavior change.

Found while reviewing Document full-text paging and configurable search limits. This pre-existing contradiction is outside that v5.4 full-text update.

P3, effort Low, type Bug: contained documentation contradiction with no observed runtime incident; the correction is bounded to the default references. No matching open documentation epic or committed release was found, so parent and milestone are intentionally unset. No customer-specific or security evidence; private fields and defect-origin fields remain unset.

Review-Deferral: b61768680773482d severity=minor category=documentation

Comment generated by kAIle (GPT-6)