feat(condense): unify UI/API histories; condense metadata; API history excludes condensed children

[roomote]

fixed #8295
Implements condenseId/condenseParent across UI and API histories. On condense, summary parent gets condenseId and condensed children are marked with condenseParent; first original message is preserved. API request assembly now filters out children (records with condenseParent). Adds tagging of condense_context UI rows.

Key changes:

• packages/types: add condenseId/condenseParent to ClineMessage schema clineMessageSchema
• api message typing extended ApiMessage
• condense flow emits condenseId and attaches to summary summarizeConversation()
• central application of metadata and UI tagging Task.applyCondenseMetadataToHistories()
• API history filtered before requests Task.attemptApiRequest()

Local targeted tests passed: core/condense, core/sliding-window, core/task suites.

---

Important

Introduces condense feature to unify UI/API histories by adding condenseId and condenseParent, filtering condensed children from API requests.

• Behavior:
  • Implements condenseId and condenseParent in ClineMessage schema in message.ts.
  • Filters out messages with condenseParent in Task.attemptApiRequest() in Task.ts.
  • Adds condenseId to SummarizeResponse in index.ts.
• Functions:
  • summarizeConversation() in index.ts now generates condenseId and attaches it to the summary.
  • Task.applyCondenseMetadataToHistories() in Task.ts applies condense metadata to histories.
• Misc:
  • Extends ApiMessage type in apiMessages.ts to include condenseId and condenseParent.

^{This description was created by for 534afc5. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

In the condenseContext() method, the code extracts a local condenseId from the result and then calls applyCondenseMetadataToHistories(result), which may generate its own condenseId. To ensure consistency, consider using the returned condenseId from applyCondenseMetadataToHistories instead of destructuring it from result separately.

[ellipsis-dev]

In the applyCondenseMetadataToHistories() method, several casts are used (e.g. '(m as any).condenseParent') to check/update properties that are defined in the ClineMessage schema. Consider using proper type assertions to avoid 'as any'. Also, similar UI tagging logic (e.g. for condense_context messages at multiple locations) is duplicated; refactoring this into a shared helper would improve maintainability.

^{This comment was generated because it violated a code review rule: irule_tTqpIuNs8DV0QFGj.}

[roomote]

Reviewing my own code again—truly the ouroboros of automation nibbling its tail a line at a time.

[roomote]

[P3] condenseId source of truth for UI tagging.

applyCondenseMetadataToHistories may synthesize a condenseId when result.condenseId is missing. To avoid a mismatch between persisted histories and the UI tag on condense_context, capture the returned condenseId and use it here.

Suggested change

	;(this.clineMessages[idx] as any).condenseId = condenseId
	// Merge condense metadata into API and UI histories (mark children and replace summary)
	const { condenseId } = await this.applyCondenseMetadataToHistories(result)