@ttt-productions/ttt-core 0.4.1 → 0.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/dist/constants/chat.d.ts +7 -7
  2. package/dist/constants/chat.js +7 -7
  3. package/package.json +1 -1
package/dist/constants/chat.d.ts CHANGED
@@ -1,12 +1,12 @@
1
1
  /**
2
- * Chat-related constants shared between ttt-core (schemas) and chat-core (UI/runtime).
2
+ * Maximum chat message length (characters) used by ttt-core's chat callable
3
+ * and system-message-action schemas for backend validation.
3
4
  *
4
- * These live here so ttt-core's schemas/chat.ts and schemas/system-message-actions.ts
5
- * can use them without depending on chat-core (which would create a circular package
6
- * dependency — chat-core already depends on ttt-core).
7
- *
8
- * chat-core re-exports these constants from its public surface so existing chat-core
9
- * consumers see no change.
5
+ * Split ownership by design: chat-core owns its own UI/runtime default
6
+ * (`MAX_CHAT_MESSAGE_LENGTH` in `chat-core/src/constants.ts`); ttt-core owns
7
+ * the value used by callable wire validation. The values are intentionally
8
+ * aligned at 4000; consumers wanting a different limit should override at
9
+ * their own call site rather than expecting cross-package coordination.
10
10
  */
11
11
  export declare const MAX_CHAT_MESSAGE_LENGTH = 4000;
12
12
  //# sourceMappingURL=chat.d.ts.map
package/dist/constants/chat.js CHANGED
@@ -1,12 +1,12 @@
1
1
  /**
2
- * Chat-related constants shared between ttt-core (schemas) and chat-core (UI/runtime).
2
+ * Maximum chat message length (characters) used by ttt-core's chat callable
3
+ * and system-message-action schemas for backend validation.
3
4
  *
4
- * These live here so ttt-core's schemas/chat.ts and schemas/system-message-actions.ts
5
- * can use them without depending on chat-core (which would create a circular package
6
- * dependency — chat-core already depends on ttt-core).
7
- *
8
- * chat-core re-exports these constants from its public surface so existing chat-core
9
- * consumers see no change.
5
+ * Split ownership by design: chat-core owns its own UI/runtime default
6
+ * (`MAX_CHAT_MESSAGE_LENGTH` in `chat-core/src/constants.ts`); ttt-core owns
7
+ * the value used by callable wire validation. The values are intentionally
8
+ * aligned at 4000; consumers wanting a different limit should override at
9
+ * their own call site rather than expecting cross-package coordination.
10
10
  */
11
11
  export const MAX_CHAT_MESSAGE_LENGTH = 4000;
12
12
  //# sourceMappingURL=chat.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ttt-productions/ttt-core",
3
- "version": "0.4.1",
3
+ "version": "0.4.2",
4
4
  "description": "Core types, Firestore path constants, and shared constants for TTT Productions",
5
5
  "repository": {
6
6
  "type": "git",