feat(recruiter): support multiple locations in opportunity edit screen

[rebelchris]

Summary

• Update the opportunity edit form to support adding, editing, and removing multiple locations instead of just one
• Replace singular location fields with a locations array in the form schema
• Implement multi-location UI with add/remove buttons using useFieldArray
• Update data transformation functions to handle locations array with externalLocationId for backend

Test plan

• Open opportunity edit screen and verify existing locations are loaded correctly
• Add a new location and verify it appears in the form
• Remove a location and verify it is removed
• Save the opportunity and verify all locations are persisted

Closes ENG-597

Created by Huginn 🐦‍⬛

Preview domain

https://eng-597-opportunity-edit-screen.preview.app.daily.dev

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
daily-webapp	Ready	Preview	Feb 9, 2026 10:00am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
storybook	Ignored		Feb 9, 2026 10:00am

[capJavert]

@claude do not do the types like this, always use z.infer from schema, also add to AGENTS.md so it never happens again

[claude]

Claude finished @capJavert's task in 13s —— View job

---

I'll analyze this and get back to you.

[rebelchris]

@claude did you adjust this?

[claude]

Claude finished @rebelchris's task in 1m 45s —— View job

---

Completed ✅

• Read current state of opportunity.ts schema file
• Check if AGENTS.md was updated with guidance
• Add Zod type inference guidance to AGENTS.md
• Review remaining manual types in opportunity.ts
• Commit and push changes

Summary

Yes, line 30 in opportunity.ts was already using z.infer correctly:

export type LocationEntry = z.infer<typeof locationEntrySchema>;

However, the AGENTS.md file had not been updated with this guidance as @capJavert requested. I've now added a dedicated section on Zod type inference with clear examples:

// ❌ WRONG: Manual type definition that duplicates schema
const userSchema = z.object({
  name: z.string(),
  age: z.number(),
});

interface User {
  name: string;
  age: number;
}

// ✅ RIGHT: Infer type from schema
export type User = z.infer<typeof userSchema>;

Note: The manual interfaces in lines 170-200 (LocationInput, SalaryInput, etc.) are GraphQL input types used by the GraphQL API layer, while the Zod schemas are for form validation. These serve different purposes, so they're appropriate to keep as-is.

Changes Made

• Updated AGENTS.md with Zod type inference best practices
• Committed and pushed to branch

View commit |