Extend Onboarding and Context

Onboarding Ownership

Original sources and semantic Context live in object storage. PostgreSQL coordinates onboarding status, chats, source manifests, revisions, and activation. The generated review is agent-authored untrusted input and must pass backend preflight before activation.

Add a File Type

1. Define extension and media-type acceptance.
2. Set explicit filename and size limits.
3. Parse or extract without executing embedded content.
4. Normalize text to UTF-8.
5. Preserve the original source and record a typed derived artifact when needed.
6. Reject absolute, traversing, symlinked, or unsafe object paths.
7. Add malformed, oversized, mislabeled, and unsupported-file tests.
8. Update the onboarding UI accept list and Upload Reference.

Do not accept a format merely because a browser can preview it. It must produce safe, deterministic evidence for the runtime.

Extend Structured Questions

Question types and answer payloads are bounded shared contracts. Preserve ordered question IDs, required/skippable semantics, attachment ownership, and the one-to-four question batch limit.

When adding a question capability:

• update shared types and Zod validation;
• update the trusted structured-questions MCP server;
• update frontend rendering and draft preservation;
• validate final ordered responses in the backend;
• add message, attachment, and navigation tests; and
• document operator behavior.

Extend Activation Review

Preflight activation against organization identity, selected departments, retained sources, operational minimum, and known gaps. Invalid agent-authored review content must become a recoverable issue, not take down the conversation page.

Extend Context Structure

Use a stable file path and explicit evidence metadata. Promote verified reusable facts, policies, decisions, and workflow knowledge—not temporary drafts or hidden reasoning.

contextctl verify may validate staged local structure but remains read-only and network-free. Promotion belongs to the authenticated backend control plane.

Add an Audit Rule

Define the scope, evidence requirement, severity, durable health payload, and remediation path. Make repeated audit execution idempotent and preserve historical health revisions.

Integration-Scoped Context Review

Keep full Context audits and integration reconciliation as typed, mutually exclusive task variants. The full branch may inspect all Context and retained onboarding evidence. The integration branch may inspect only the affected safe-registry records, previous health, and exact relevant facts and workflows. Backend hydration and promotion validators enforce that boundary; prompt prose is not a security boundary.

integration_usage.key remains the semantic workflow reference. Optional connector_key links the usage to an exact current registry key. Do not infer connection state from organization.constraints.allowedIntegrations, profile mcpServerKeys, provider display names, or onboarding prose.

Use typed durability for pending connector keys and at most one active review rather than adding a parallel health table. Queue the durability update in the same transaction as the material registry change, attempt immediate materialization, and let scheduler recovery close failures and restarts. Scoped promotion must fence the health revision, registry revision, authorization epoch, relevant Context hashes, and request generation before merging only the reviewed integration findings.