Add AI conversation memory and cost tracking protocols

[Copilot]

Implements two core AI protocols: conversation state management with token budgeting, and comprehensive cost tracking with multi-level budget enforcement.

Conversation Protocol (conversation.zod.ts)

Multi-turn conversation state with token-aware context management:

• Message schema supporting multimodal content (text, image, file) and tool calls
• Token budget strategies: FIFO, importance-based, semantic similarity, sliding window, summarization
• Automatic context pruning with configurable reserves and buffers
• Session lifecycle with context preservation and analytics

constsession: ConversationSession={id: 'session-1',context: {sessionId: 'session-1',userId: 'user-1',agentId: 'support_agent'},tokenBudget: {maxTokens: 8192,strategy: 'sliding_window',slidingWindowSize: 20,enableSummarization: true,},messages: [...],tokens: {totalTokens: 230,budgetRemaining: 7962,budgetPercentage: 0.028},};

Cost Protocol (cost.zod.ts)

Granular cost tracking with hierarchical budget enforcement:

• Cost entry tracking by model, provider, operation, user, agent, object
• Budget types: global, user, agent, object, project, department
• Alert system with threshold warnings and anomaly detection
• Cost analytics with multi-dimensional breakdowns
• Optimization recommendations based on usage patterns

constbudget: BudgetLimit={type: 'user',scope: 'user-123',maxCost: 100,period: 'monthly',softLimit: 80,warnThresholds: [0.5,0.75,0.9],enforced: true,allowRollover: true,};

Both protocols export TypeScript types derived from Zod schemas for runtime validation and type safety.

Original prompt

8. AI 对话记忆

文件: packages/spec/src/ai/conversation.zod.ts
工作量: 3 天
功能: 多轮 AI 对话，令牌预算管理

9. AI 成本跟踪

文件: packages/spec/src/ai/cost.zod.ts
工作量: 3 天
功能: 监控和控制 AI API 成本

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
spec	Ready	Preview, Comment	Jan 23, 2026 0:00am

[github-actions]

This PR is very large. Consider breaking it into smaller PRs for easier review.

[Copilot]

Pull request overview

Adds new AI protocol schemas for (1) multi-turn conversation memory with token budgeting and (2) detailed cost tracking with budget/alert/reporting structures, and wires them into the AI module exports with accompanying Vitest coverage.

Changes:

• Introduces Conversation* Zod schemas/types for message/session state, token budgeting, pruning events, and analytics.
• Introduces Cost* Zod schemas/types for cost entries, budgets/status, alerts, analytics, and query filters.
• Adds Vitest test suites for both protocols and exports them from packages/spec/src/ai/index.ts (plus new npm lockfiles).

Reviewed changes

Copilot reviewed 5 out of 7 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
packages/spec/src/ai/index.ts	Exposes the new conversation and cost protocols from the AI namespace.
packages/spec/src/ai/conversation.zod.ts	Defines conversation message/session/token budget schemas and derived types.
packages/spec/src/ai/conversation.test.ts	Adds Vitest coverage validating conversation protocol parsing and defaults.
packages/spec/src/ai/cost.zod.ts	Defines cost tracking/budget/alert/report schemas and derived types.
packages/spec/src/ai/cost.test.ts	Adds Vitest coverage validating cost protocol parsing and defaults.
packages/spec/package-lock.json	Adds an npm lockfile for @objectstack/spec.
package-lock.json	Adds an npm lockfile at monorepo root.

Files not reviewed (1)

• packages/spec/package-lock.json: Language not supported

[Copilot]

Since the monorepo uses pnpm (root package.jsonpackageManager + pnpm-lock.yaml), committing an additional packages/spec/package-lock.json adds a second lockfile for the same package set and can lead to inconsistent installs. Consider removing this lockfile and relying on pnpm’s lockfile only.

[Copilot]

MessageContentSchema is too permissive: it allows invalid combinations like { type: "image" } without imageUrl, or imageUrl/fileUrl present while type defaults to text. Consider modeling content as a discriminated union on type (e.g., text requires text, image requires imageUrl, file requires fileUrl, etc.) so invalid message payloads are rejected at validation time.

Suggested change

	*/
	exportconstMessageContentSchema=z.object({
	type: MessageContentTypeSchema.default('text'),
	text: z.string().optional().describe('Text content'),
	imageUrl: z.string().url().optional().describe('Image URL for vision models'),
	fileUrl: z.string().url().optional().describe('File attachment URL'),
	mimeType: z.string().optional().describe('MIME type for files'),
	metadata: z.record(z.any()).optional().describe('Additional metadata'),
	});
	*
	*Discriminatedunionon`type`toensurevalidcombinations:
	*-`text`→requires`text`
	*-`image`→requires`imageUrl`
	*-`file`→requires`fileUrl`
	*-`code`→requires`text`(codecontent)
	*-`structured`→primarilyuses`metadata`/optional`text`
	*/
	constBaseMessageContentMetadataSchema=z.object({
	metadata: z
	.record(z.any())
	.optional()
	.describe('Additional metadata'),
	});
	exportconstMessageContentSchema=z.discriminatedUnion('type',[
	// Plain text content
	BaseMessageContentMetadataSchema.extend({
	type: z.literal('text'),
	text: z.string().describe('Text content'),
	}),
	// Image content (for vision models), with optional caption/alt text
	BaseMessageContentMetadataSchema.extend({
	type: z.literal('image'),
	imageUrl: z.string().url().describe('Image URL for vision models'),
	text: z.string().optional().describe('Alt text or caption for the image'),
	}),
	// File attachment content
	BaseMessageContentMetadataSchema.extend({
	type: z.literal('file'),
	fileUrl: z.string().url().describe('File attachment URL'),
	mimeType: z.string().optional().describe('MIME type for files'),
	text: z.string().optional().describe('Optional description of the file'),
	}),
	// Code content (source code snippet)
	BaseMessageContentMetadataSchema.extend({
	type: z.literal('code'),
	text: z.string().describe('Code content'),
	mimeType: z
	.string()
	.optional()
	.describe('MIME type or language identifier for the code'),
	}),
	// Structured content (JSON-like payloads, tables, etc.)
	BaseMessageContentMetadataSchema.extend({
	type: z.literal('structured'),
	text: z.string().optional().describe('Optional human-readable summary of the structured content'),
	}),
	]);

[Copilot]

TokenBudgetConfigSchema defaults strategy to sliding_window, but slidingWindowSize is optional, which makes the default configuration ambiguous (it’s not clear what window size applies). Consider either (a) providing a sensible default for slidingWindowSize, or (b) making the config a discriminated union so slidingWindowSize is required when strategy === "sliding_window" (and similarly require minImportanceScore/semanticThreshold for their strategies).

Suggested change

	slidingWindowSize: z.number().int().positive().optional().describe('Number of recent messages to keep'),
	slidingWindowSize: z.number().int().positive().default(50).describe('Number of recent messages to keep'),

[Copilot]

ConversationSessionSchema contains both context.sessionId and a top-level id, but there’s no guarantee they match. This can lead to inconsistent session identifiers across the protocol. Consider removing sessionId from ConversationContextSchema (derive it from ConversationSession.id), or add validation to enforce equality.

Suggested change

sessionId: z.string().describe('Conversation session ID'),

[Copilot]

BudgetLimitSchema allows period: "custom" without customPeriodDays, even though the schema describes customPeriodDays as the custom period definition. Consider enforcing that customPeriodDays is required when period === "custom" (and ideally disallow it for non-custom periods) so invalid budget configurations don’t validate.