fix(runtime): align Server assembly and Rustls provider ownership

[limityan]

Summary

• converge the loopback Server on the canonical Core Agent Runtime initializer, retain the product event-queue owner, publish shared services from the canonical owner, and fail startup when an explicit workspace cannot be opened
• run the complete bitfun-core library suite with product-full on Linux while preserving the existing minimal Core command on macOS and Windows
• keep Reqwest and RMCP provider-neutral, make services-core/tls-provider the sole Ring owner, and remove AWS-LC from the resolved dependency graph
• restore the stable product tool registration order exposed by the new Linux Core coverage and by the Desktop/CLI Peer tool catalog

Architecture and behavior

The Server drift came from a manual runtime bootstrap introduced before the canonical Core runtime-ownership initializer was established. Later lifecycle, token-usage, event-owner, and service-publication changes accumulated on the canonical path while the Server copy had no focused CI coverage. The current 1.0.0-explore base contains that history; this was not caused by a failed branch synchronization.

This change keeps the current loopback Server contract: one embedded ProductFull Runtime, single-user compatibility semantics, and existing multi-workspace behavior. --workspace remains an initial startup workspace rather than a connection-scoped policy. No new runtime profile, transport, or host abstraction is introduced.

Area	Before	After
Server Agent Runtime	manual second composition path	canonical Core initializer and event owner
Linux Core CI	feature-free library suite	product-full library suite
macOS/Windows Core CI	feature-free library suite	unchanged
Rustls provider closure	Ring and AWS-LC reachable	Ring only
Cargo lock	aws-lc-rs / aws-lc-sys present	absent

Validation

• cargo test --locked -p bitfun-core --features product-full --lib (2167 passed, 1 ignored)
• cargo test --locked -p bitfun-server (12 passed)
• cargo test --locked -p bitfun-services-core --no-default-features --features tls-provider --lib tls_provider::tests
• cargo check --locked -p bitfun-services-integrations --no-default-features --features product-full
• pnpm run check:core-boundaries:test (138 passed)
• pnpm run check:core-boundaries
• pnpm run check:github-config (21 passed)
• pnpm run check:repo-hygiene
• pnpm run fmt:rs
• git diff --check

Linux runner execution remains covered by the PR checks; the matching Cargo command was validated locally on Windows.