[servicememeai]

Scope

• Add generic ApplicationProfile V1 contract, shape-only Rust validator and validate-profile CLI. No trusted enrollment or actual capability activation.
• Document BridgeTask V1, capability/Pi/MCP boundary, and nonbreaking CloudFile Agent → Bridge migration.
• Replace app-specific sample/test data with generic enterprise examples; no company-specific logic in Local Bridge.
• Keep existing ChannelManifest, validate-channel, read-only MCP tools (bridge.status, cloudfile.status) and CloudFile Agent2 execution unchanged.

Key architecture guarantees

1. Business applications provide Profile and own business/AI/auth; Local Bridge must not know any specific app.
2. CloudFile and Bridge may mutually integrate; CloudFile remains the only owner of file Journal, Guard, upload/commit.
3. Do not change existing browser Host, SSO, CloudFile endpoints, persisted tasks/work copies, or production installer.
4. Dev/Prod are isolated; no host takeover. Profile parsing is not trust registration.

Validation

• Existing Rust CI (fmt/clippy/test/build) expected on PR; no remote Etech/CloudFile deployment or E2E claimed.
• Sample: cargo run -p local-bridge -- validate-profile examples/application-profile.json (shape only).
• Existing: status, mcp, validate-channel remain unchanged.

Follow-up (separate gated work)

• Application-owned Profile declaration and legacy binding in application repo, no runtime switches.
• Read-only Agent2 task adapter, then typed IPC, then separate real Windows/macOS E2E acceptance.
• Pi RPC and MCP expansion only when authorized implementation exists.