Remove redundant field name declarations in object protocol

[Copilot]

Field names were declared twice in the object fields protocol - once as the map key and again as a name property within the field definition.

Before:

fields: {
  account: {
    name: 'account',  // redundant
    label: 'Account',
    type: 'lookup',
    reference: 'account',
  }
}

After:

fields: {
  account: {
    label: 'Account',
    type: 'lookup',
    reference: 'account',
  }
}

Changes

• Removed redundant name properties from field definitions in object.test.ts
• FieldSchema.name remains optional for standalone field validation use cases

Examples and documentation already followed the correct pattern; only test assertions needed alignment.

Original prompt

object fields 协议中，name感觉写了两遍

fields: {

account: {
  name: 'account',
  label: 'Account',
  type: 'lookup',
  reference: 'account',
  required: true
},

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
spec	Ready	Preview, Comment	Jan 25, 2026 2:42pm

[Copilot]

Pull request overview

This PR removes redundant field name declarations from the object protocol test file. Field names were being specified twice: once as the map key in the fields object, and again as a name property within each field definition. Since ObjectSchema.fields uses z.record(FieldSchema) where map keys serve as field identifiers, and FieldSchema.name is already optional, the duplication was unnecessary.

Changes:

• Removed redundant name properties from all field definitions in object.test.ts where fields are defined within an object's fields map
• Maintained proper usage where the name property is derived from the map key (e.g., first_name, account_name, subject)