@junminghuang - Thanks for the MR, LGTM! I added one comment for discussion but it's definitely not blocking.

Summary

Adds comprehensive documentation for the conversation compaction feature, which automatically summarizes older conversation history to stay within LLM token limits.

Closes #2036

What does this MR do?

• Creates docs/context_management/compaction.md with:

  • Feature overview explaining what compaction is and why it's needed
  • Supported workflow types table showing integration status
  • Configuration guide for Legacy Chat Workflow and Flow Registry Experimental
  • Configuration parameters reference
  • How compaction works (token estimation, threshold check, summarization)
  • State management explanation for different workflow types
  • Best practices and feature flag information

• Updates docs/flow_registry/experimental.md with:

  • Adds compaction parameter to AgentComponent optional parameters
  • Adds compaction parameter to OneOffComponent optional parameters
  • Adds YAML examples for both components with compaction enabled

How to set up and validate locally

1. Review the documentation files for accuracy and completeness
2. Run make lint-doc to verify documentation linting passes

Related issues and MRs

• Closes #2036
• Parent issue: &42 #1863
• Original compaction implementation: !4629
• Chat workflow integration: !4867

Thought (non-blocking): Having more than max_recent_messages and not triggering compaction seems a bit unintuitive here, as it is a max. However I think this matches the code so I think it's OK.

David Hamp-Gonsalves (c2c7c86e) at 16 Mar 18:38

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-cng: ✅ test report for 9509838a

+-------------------------------------------------------------------------------------+
|                                   suites summary                                    |
+--------------------------------+--------+--------+---------+-------+-------+--------+
|                                | passed | failed | skipped | flaky | total | result |
+--------------------------------+--------+--------+---------+-------+-------+--------+
| Security Risk Management       | 18     | 0      | 20      | 0     | 38    | ✅     |
| Plan                           | 98     | 0      | 9       | 0     | 107   | ✅     |
| Software Supply Chain Security | 64     | 0      | 27      | 0     | 91    | ✅     |
| Create                         | 124    | 0      | 33      | 0     | 157   | ✅     |
| Verify                         | 50     | 0      | 27      | 0     | 77    | ✅     |
| Tenant Scale                   | 41     | 0      | 11      | 0     | 52    | ✅     |
| Package                        | 25     | 0      | 23      | 0     | 48    | ✅     |
| Manage                         | 1      | 0      | 4       | 0     | 5     | ✅     |
| Deploy                         | 6      | 0      | 4       | 0     | 10    | ✅     |
| Monitor                        | 15     | 0      | 10      | 0     | 25    | ✅     |
| Secure                         | 2      | 0      | 3       | 0     | 5     | ✅     |
| Analytics                      | 0      | 0      | 2       | 0     | 2     | ➖     |
| Fulfillment                    | 1      | 0      | 8       | 0     | 9     | ✅     |
| Ai-powered                     | 0      | 0      | 3       | 0     | 3     | ➖     |
| Growth                         | 0      | 0      | 1       | 0     | 1     | ➖     |
+--------------------------------+--------+--------+---------+-------+-------+--------+
| Total                          | 445    | 0      | 185     | 0     | 630   | ✅     |
+--------------------------------+--------+--------+---------+-------+-------+--------+

Bruno Cardoso (ff03767b) at 16 Mar 18:38

... and 3 more commits

Parameter coercion will not occur in this case. present? will interrupt and this is identical to not passing it at all.

No worries, thanks!

Daniele Bracciani (100002f1) at 16 Mar 18:37

... and 1 more commit

nit: wouldn't pipeline down below return nil if it's not found anyways?

So we can just do pipeline here?

Michael Usachenko (bbce5076) at 16 Mar 18:37

question: @kerrizor Are we ok here if partition_id is nil?

Michael Usachenko (769b22b8) at 16 Mar 18:37

... and 1 more commit

Summary

• Replaces edges_of_type("MEMBER_OF").into_inner() in traversal_with_order_by with a full assert_edge_set covering all 9 MEMBER_OF edges from the seed data.
• Removes MustInspect::into_inner entirely — it was a public escape hatch that let callers satisfy both the enforcement tracker and the MustInspect drop guard without actually verifying any data.
• Replaces all 12 into_inner() calls in enforcement unit tests with real assertions (assert_node_ids, assert_edge_set, assert_edge_count).

Without into_inner, the only way to consume a MustInspect value is through Deref — you have to actually read the data or it panics on drop. The enforcement tracker and MustInspect are now complementary with no bypass: the tracker enforces "call the right methods", MustInspect enforces "look at what came back."

Depends on !574.

Uma Chandran (4d143c32) at 16 Mar 18:37

Duration Analysis