# Forge 4.0.10

Matched Anvil, Hammer and Connect release candidate. No database migration or knowledge reclassification is required by this correction.

Connect no longer treats the entire general working-fact collection as mandatory startup material. All rules, protected questionnaire knowledge, explicit protected facts, current restrictions, identity, workspace, assignment and operational state remain mandatory. General working facts are selected deterministically within an 8,000-character budget, preferring the current stored mission and newer facts. Whole records only; no content truncation.

The complete current collection remains accessible through `forge_connect_history` with `collection=working-knowledge`, optional all-words `query`, and bounded paging. Oversized evidence remains chunk-readable. Collection hashes participate in refresh invalidation. Continuations reject changed current collections instead of silently serving a stale current snapshot. Historical intelligence remains separately available.

The normal 128,000-character aggregate and 16,000-character message bounds remain unchanged. Truly oversized mandatory protected context still fails closed. This replaces the temporary aggregate-limit workaround in 4.0.9+hotfix.1.

No SSH, VPN, TLS, invitation, execution-approval, archive, or user-permission behavior is changed. Existing records and evidence are not rewritten or deleted. Install Connect under the affected Windows account and start a fresh Codex chat after installation; verify the running MCP reports 4.0.10. Merely seeing an updated skill does not establish the running version.

Controlled test results and exact installer hashes accompany the release. Customer-specific acceptance is separate; no claim is made that all customer connection failures are fixed. Public download replacement and customer deployment require separate direction.