@knowledge-stack/ksapi 1.160.2 → 1.161.0

package/README.md

@@ -1,4 +1,4 @@
-# @knowledge-stack/ksapi@1.160.2
+# @knowledge-stack/ksapi@1.161.0
 
 A TypeScript SDK client for the localhost API.
 
@@ -710,7 +710,7 @@ and is automatically generated by the
 [OpenAPI Generator](https://openapi-generator.tech) project:
 
 - API version: `0.1.0`
-- Package version: `1.160.2`
+- Package version: `1.161.0`
 - Generator version: `7.21.0`
 - Build package: `org.openapitools.codegen.languages.TypeScriptFetchClientCodegen`
 

package/dist/apis/PathPartsApi.d.ts

@@ -43,6 +43,7 @@ export interface ListPathPartEventsRequest {
     since?: Date | null;
     until?: Date | null;
     recursive?: boolean;
+    includeChurn?: boolean;
     limit?: number;
     offset?: number;
 }
@@ -241,6 +242,7 @@ export interface PathPartsApiInterface {
      * @param {Date} [since] Only events at or after this timestamp
      * @param {Date} [until] Only events strictly before this timestamp
      * @param {boolean} [recursive] Include events from descendant path_parts as well as the subject itself
+     * @param {boolean} [includeChurn] Include intra-document churn hidden by default (raw chunk/section edits, version-metadata updates, and the v0 version-created row). Off by default so one upload / one logical edit shows as one event; ignored when an explicit kind is set.
      * @param {number} [limit] Number of items per page
      * @param {number} [offset] Number of items to skip
      * @throws {RequiredError}
@@ -248,13 +250,14 @@ export interface PathPartsApiInterface {
      */
     listPathPartEventsRequestOpts(requestParameters: ListPathPartEventsRequest): Promise<runtime.RequestOpts>;
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * @summary List Path Part Events Handler
      * @param {string} pathPartId
      * @param {string} [kind] Filter to a single event kind
      * @param {Date} [since] Only events at or after this timestamp
      * @param {Date} [until] Only events strictly before this timestamp
      * @param {boolean} [recursive] Include events from descendant path_parts as well as the subject itself
+     * @param {boolean} [includeChurn] Include intra-document churn hidden by default (raw chunk/section edits, version-metadata updates, and the v0 version-created row). Off by default so one upload / one logical edit shows as one event; ignored when an explicit kind is set.
      * @param {number} [limit] Number of items per page
      * @param {number} [offset] Number of items to skip
      * @param {*} [options] Override http request option.
@@ -263,7 +266,7 @@ export interface PathPartsApiInterface {
      */
     listPathPartEventsRaw(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PaginatedResponseEventResponse>>;
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEvents(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PaginatedResponseEventResponse>;
@@ -483,12 +486,12 @@ export declare class PathPartsApi extends runtime.BaseAPI implements PathPartsAp
      */
     listPathPartEventsRequestOpts(requestParameters: ListPathPartEventsRequest): Promise<runtime.RequestOpts>;
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEventsRaw(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PaginatedResponseEventResponse>>;
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEvents(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PaginatedResponseEventResponse>;

package/dist/apis/PathPartsApi.js

@@ -441,6 +441,9 @@ class PathPartsApi extends runtime.BaseAPI {
             if (requestParameters['recursive'] != null) {
                 queryParameters['recursive'] = requestParameters['recursive'];
             }
+            if (requestParameters['includeChurn'] != null) {
+                queryParameters['include_churn'] = requestParameters['includeChurn'];
+            }
             if (requestParameters['limit'] != null) {
                 queryParameters['limit'] = requestParameters['limit'];
             }
@@ -466,7 +469,7 @@ class PathPartsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEventsRaw(requestParameters, initOverrides) {
@@ -477,7 +480,7 @@ class PathPartsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEvents(requestParameters, initOverrides) {

package/dist/esm/apis/PathPartsApi.d.ts

@@ -43,6 +43,7 @@ export interface ListPathPartEventsRequest {
     since?: Date | null;
     until?: Date | null;
     recursive?: boolean;
+    includeChurn?: boolean;
     limit?: number;
     offset?: number;
 }
@@ -241,6 +242,7 @@ export interface PathPartsApiInterface {
      * @param {Date} [since] Only events at or after this timestamp
      * @param {Date} [until] Only events strictly before this timestamp
      * @param {boolean} [recursive] Include events from descendant path_parts as well as the subject itself
+     * @param {boolean} [includeChurn] Include intra-document churn hidden by default (raw chunk/section edits, version-metadata updates, and the v0 version-created row). Off by default so one upload / one logical edit shows as one event; ignored when an explicit kind is set.
      * @param {number} [limit] Number of items per page
      * @param {number} [offset] Number of items to skip
      * @throws {RequiredError}
@@ -248,13 +250,14 @@ export interface PathPartsApiInterface {
      */
     listPathPartEventsRequestOpts(requestParameters: ListPathPartEventsRequest): Promise<runtime.RequestOpts>;
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * @summary List Path Part Events Handler
      * @param {string} pathPartId
      * @param {string} [kind] Filter to a single event kind
      * @param {Date} [since] Only events at or after this timestamp
      * @param {Date} [until] Only events strictly before this timestamp
      * @param {boolean} [recursive] Include events from descendant path_parts as well as the subject itself
+     * @param {boolean} [includeChurn] Include intra-document churn hidden by default (raw chunk/section edits, version-metadata updates, and the v0 version-created row). Off by default so one upload / one logical edit shows as one event; ignored when an explicit kind is set.
      * @param {number} [limit] Number of items per page
      * @param {number} [offset] Number of items to skip
      * @param {*} [options] Override http request option.
@@ -263,7 +266,7 @@ export interface PathPartsApiInterface {
      */
     listPathPartEventsRaw(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PaginatedResponseEventResponse>>;
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEvents(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PaginatedResponseEventResponse>;
@@ -483,12 +486,12 @@ export declare class PathPartsApi extends runtime.BaseAPI implements PathPartsAp
      */
     listPathPartEventsRequestOpts(requestParameters: ListPathPartEventsRequest): Promise<runtime.RequestOpts>;
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEventsRaw(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PaginatedResponseEventResponse>>;
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEvents(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PaginatedResponseEventResponse>;

package/dist/esm/apis/PathPartsApi.js

@@ -405,6 +405,9 @@ export class PathPartsApi extends runtime.BaseAPI {
             if (requestParameters['recursive'] != null) {
                 queryParameters['recursive'] = requestParameters['recursive'];
             }
+            if (requestParameters['includeChurn'] != null) {
+                queryParameters['include_churn'] = requestParameters['includeChurn'];
+            }
             if (requestParameters['limit'] != null) {
                 queryParameters['limit'] = requestParameters['limit'];
             }
@@ -430,7 +433,7 @@ export class PathPartsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEventsRaw(requestParameters, initOverrides) {
@@ -441,7 +444,7 @@ export class PathPartsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEvents(requestParameters, initOverrides) {

package/docs/PathPartsApi.md

@@ -561,11 +561,11 @@ example().catch(console.error);
 
 ## listPathPartEvents
 
-> PaginatedResponseEventResponse listPathPartEvents(pathPartId, kind, since, until, recursive, limit, offset)
+> PaginatedResponseEventResponse listPathPartEvents(pathPartId, kind, since, until, recursive, includeChurn, limit, offset)
 
 List Path Part Events Handler
 
-List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
 
 ### Example
 
@@ -597,6 +597,8 @@ async function example() {
     until: 2013-10-20T19:20:30+01:00,
     // boolean | Include events from descendant path_parts as well as the subject itself (optional)
     recursive: true,
+    // boolean | Include intra-document churn hidden by default (raw chunk/section edits, version-metadata updates, and the v0 version-created row). Off by default so one upload / one logical edit shows as one event; ignored when an explicit kind is set. (optional)
+    includeChurn: true,
     // number | Number of items per page (optional)
     limit: 56,
     // number | Number of items to skip (optional)
@@ -625,6 +627,7 @@ example().catch(console.error);
 | **since** | `Date` | Only events at or after this timestamp | [Optional] [Defaults to `undefined`] |
 | **until** | `Date` | Only events strictly before this timestamp | [Optional] [Defaults to `undefined`] |
 | **recursive** | `boolean` | Include events from descendant path_parts as well as the subject itself | [Optional] [Defaults to `false`] |
+| **includeChurn** | `boolean` | Include intra-document churn hidden by default (raw chunk/section edits, version-metadata updates, and the v0 version-created row). Off by default so one upload / one logical edit shows as one event; ignored when an explicit kind is set. | [Optional] [Defaults to `false`] |
 | **limit** | `number` | Number of items per page | [Optional] [Defaults to `20`] |
 | **offset** | `number` | Number of items to skip | [Optional] [Defaults to `0`] |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knowledge-stack/ksapi",
-  "version": "1.160.2",
+  "version": "1.161.0",
   "description": "OpenAPI client for @knowledge-stack/ksapi",
   "author": "OpenAPI-Generator",
   "repository": {

package/src/apis/PathPartsApi.ts

@@ -112,6 +112,7 @@ export interface ListPathPartEventsRequest {
     since?: Date | null;
     until?: Date | null;
     recursive?: boolean;
+    includeChurn?: boolean;
     limit?: number;
     offset?: number;
 }
@@ -336,6 +337,7 @@ export interface PathPartsApiInterface {
      * @param {Date} [since] Only events at or after this timestamp
      * @param {Date} [until] Only events strictly before this timestamp
      * @param {boolean} [recursive] Include events from descendant path_parts as well as the subject itself
+     * @param {boolean} [includeChurn] Include intra-document churn hidden by default (raw chunk/section edits, version-metadata updates, and the v0 version-created row). Off by default so one upload / one logical edit shows as one event; ignored when an explicit kind is set.
      * @param {number} [limit] Number of items per page
      * @param {number} [offset] Number of items to skip
      * @throws {RequiredError}
@@ -344,13 +346,14 @@ export interface PathPartsApiInterface {
     listPathPartEventsRequestOpts(requestParameters: ListPathPartEventsRequest): Promise<runtime.RequestOpts>;
 
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * @summary List Path Part Events Handler
      * @param {string} pathPartId 
      * @param {string} [kind] Filter to a single event kind
      * @param {Date} [since] Only events at or after this timestamp
      * @param {Date} [until] Only events strictly before this timestamp
      * @param {boolean} [recursive] Include events from descendant path_parts as well as the subject itself
+     * @param {boolean} [includeChurn] Include intra-document churn hidden by default (raw chunk/section edits, version-metadata updates, and the v0 version-created row). Off by default so one upload / one logical edit shows as one event; ignored when an explicit kind is set.
      * @param {number} [limit] Number of items per page
      * @param {number} [offset] Number of items to skip
      * @param {*} [options] Override http request option.
@@ -360,7 +363,7 @@ export interface PathPartsApiInterface {
     listPathPartEventsRaw(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PaginatedResponseEventResponse>>;
 
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     listPathPartEvents(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PaginatedResponseEventResponse>;
@@ -945,6 +948,10 @@ export class PathPartsApi extends runtime.BaseAPI implements PathPartsApiInterfa
             queryParameters['recursive'] = requestParameters['recursive'];
         }
 
+        if (requestParameters['includeChurn'] != null) {
+            queryParameters['include_churn'] = requestParameters['includeChurn'];
+        }
+
         if (requestParameters['limit'] != null) {
             queryParameters['limit'] = requestParameters['limit'];
         }
@@ -976,7 +983,7 @@ export class PathPartsApi extends runtime.BaseAPI implements PathPartsApiInterfa
     }
 
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     async listPathPartEventsRaw(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<PaginatedResponseEventResponse>> {
@@ -987,7 +994,7 @@ export class PathPartsApi extends runtime.BaseAPI implements PathPartsApiInterfa
     }
 
     /**
-     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".
+     * List events anchored to a specific path_part subject.  Subject permission is enforced via the existing ``PathPermissionService`` — caller must have ``can_read`` on the subject\'s materialized_path (OWNER/ADMIN bypass). Events are ordered newest-first by ``ts`` and paginated.  When ``recursive=True``, events on any descendant of the subject are included — useful for \"all events under this folder\" or \"all events under this workflow definition\".  By default the feed collapses intra-document churn to match the tenant-wide admin view; pass ``include_churn=True`` for the complete forensic feed (the agent\'s ``list_events`` tool does this).
      * List Path Part Events Handler
      */
     async listPathPartEvents(requestParameters: ListPathPartEventsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<PaginatedResponseEventResponse> {