Address tuxmea review comments on OpenFact landing page

- Drop legacy facts note (mixed two separate deprecations)
- Clarify resolution selection: highest-weighted wins (verified in source)
- Separate facts vs. report storage: facts are not persisted without
  OpenVoxDB; only reports go to local disk by default
- Fix cross-collection link: remove ../ prefix on about_agent.html

Signed-off-by: Michael Harp <mike@mikeharp.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: miharp

docs/_openfact_5x/index.md

@@ -8,12 +8,6 @@ structured data about a node's operating system, hardware, networking, and more.
 in OpenVox manifests as top-scope variables (e.g. `$facts['os']['family']`) and are used by the
 catalog compiler to make node-specific decisions.
 
-> **Note:** Legacy flat facts (e.g. `$::osfamily`) are hidden from `facter`'s default CLI output
-> and are not collected or sent to OpenVox Server in OpenVox 8. From the CLI you can still view
-> them with `facter --show-legacy`. In the agent, they can be re-enabled by setting
-> `include_legacy_facts=true` in the agent's `puppet.conf`, but this is not recommended.
-> Use the structured `$facts` hash instead.
-
 OpenFact is the community-maintained continuation of Puppet's Facter, originally adopted under
 [Vox Pupuli](https://voxpupuli.org/) stewardship alongside OpenVox. It is downstream-compatible
 with Facter — existing custom facts and external facts work unchanged.
@@ -23,11 +17,14 @@ with Facter — existing custom facts and external facts work unchanged.
 OpenFact runs on each managed node and resolves facts by querying the system directly: reading
 `/proc` entries, running shell commands, calling OS APIs, and so on. Results are returned as a
 structured hash. When a fact can be resolved in multiple ways (for example, differently on Linux
-versus Windows), OpenFact picks the first applicable resolution and discards the rest.
+versus Windows), OpenFact runs the highest-weighted applicable resolution.
 
 **In an agent/server deployment**, OpenFact runs automatically at the start of each agent run.
-The collected facts are sent to OpenVox Server, where they are available to the catalog compiler
-and stored for reporting.
+The collected facts are sent to OpenVox Server and made available to the catalog compiler.
+Facts are not persisted without OpenVoxDB — they are used during catalog compilation and then
+discarded. The agent run produces a report, which OpenVox Server stores on local disk by default;
+without periodic cleanup, report storage will grow unbounded. OpenVoxDB is an optional component
+that provides durable storage for facts, catalogs, and reports.
 
 **Standalone**, the `facter` CLI lets you query facts directly on any node — useful for
 ad-hoc inspection, debugging, or scripting without triggering a full agent run.
@@ -36,7 +33,7 @@ ad-hoc inspection, debugging, or scripting without triggering a full agent run.
 
 OpenFact ships inside the `openvox-agent` package and does not need to be installed separately.
 The version bundled with a given agent release is listed in
-[Component versions in openvox-agent](../../openvox/latest/about_agent.html).
+[Component versions in openvox-agent](/openvox/latest/about_agent.html).
 
 ## Getting started