Tracking Issue: deliver supported Source ingestion

[PsiACE]

Goal

Track delivery of supported Source ingestion after #1240 defines the Source identity and materialization contract.

Parent roadmap: #1352.

This issue coordinates the accepted Source contract, one supported document integration, historical prompt import, and any derived processing those deliveries require. It does not redefine the public Source model or API.

Current baseline

PowerContext currently accepts idempotent captured text through ContentSource and POST /v1/sources/content. #1240 decides whether this remains the common capture boundary for external integrations or one Source implementation alongside others.

#1300 separately tracks explicit, default-off import of historical user prompts from one Agent host. It does not import full sessions or restore an executable Agent session.

Tracking

• Complete research: define the Source integration shape #1240 and record the accepted Source identity and materialization decisions in an RFC.
• After research: define the Source integration shape #1240 is accepted, select one supported document Source integration. The bounded validation from research: define the Source integration shape #1240 may graduate only if it meets the support criteria below; otherwise, track the supported integration in a separate child issue.
• Deliver initial import and subsequent provider-supported change handling through the accepted Source semantics.
• Complete feat: add opt-in import of pre-install user prompts from one agent host #1300 for explicit historical user-prompt import from one supported Agent host.
• Decide whether either delivered integration requires asynchronous derived processing. If it does, create a bounded child issue for status, retries, idempotency, failure isolation, and resource limits. If it does not, record that no background processing is required.
• Add maintained setup and troubleshooting documentation, plus tests for each supported integration.

Completion criteria

• The RFC from research: define the Source integration shape #1240 is accepted, and the public API, code, tests, and maintained documentation describe the same Source contract.
• At least one document integration is supported as a product integration rather than retained as sample or validation code.
• Repeated observation is idempotent. Updates and other provider-supported changes preserve exact provenance according to the accepted contract.
• Users can see whether ingestion succeeded and which items failed.
• The external system remains authoritative. Read permissions, retention, deletion, and disconnect behavior are documented.
• Historical prompt import remains an explicit Source import. It does not claim session restore, Handoff, Task Outcome, or full transcript support.
• Product status and documentation distinguish Source acceptance from completion of any later derived processing.

Boundaries

• This issue does not select a document provider before research: define the Source integration shape #1240 settles the contract.
• research: define the Source integration shape #1240 owns the Source design and bounded validation. Do not start a parallel Source pilot without coordinating with its owner.
• Provider discovery, synchronization, credentials, checkpoints, retries, and provider-specific change handling remain connector responsibilities.
• This issue does not create a connector marketplace or a general workflow runtime.
• Background processing is conditional. It is required only when accepted work cannot safely finish within the request cycle.

[knqiufan]

@PsiACE I've noticed that #1384 could also be included in this tracking issue for coordinated work purposes. So I suggest that the following content can be added to this tracking issue:

• Include feat: Supports importing existing data #1384 as related Source-ingestion work, while keeping it separate from feat: add opt-in import of pre-install user prompts from one agent host #1300: feat: add opt-in import of pre-install user prompts from one agent host #1300 backfills historical user prompts, whereas feat: Supports importing existing data #1384 imports already-derived Codex memories and first needs a Source-vs-Memory-Artifact decision.
• Add feat: add opt-in import of pre-install user prompts from one agent host #1300 and feat: Supports importing existing data #1384 as sub-issues of this tracker.
• Mark research: define the Source integration shape #1240 as a dependency for the shared Source identity/materialization contract, while noting that bounded work which stays on the existing ContentSource contract may proceed independently.

This should make ownership, sequencing, and completion status easier to follow.

[knqiufan]

I will first proceed with the work of #1300.