## Summary
- Add visibility dropdown (Public/Private/Unlisted) to party edit
sidebar
- Add "Share with Crew" switch for crew members
- Implement /crew/teams page showing parties shared with crew
- Add API layer for party shares and crew shared parties
## Test plan
- [ ] Open party settings, verify visibility dropdown appears
- [ ] For users in a crew, verify "Share with Crew" switch appears
- [ ] Toggle crew share on/off, verify it persists
- [ ] Navigate to /crew/teams, verify shared parties load
- [ ] Test infinite scroll pagination on crew teams page
## Summary
- show element and proficiency labels below item name in search results
- remove element text from right side of row
- update hover to use background color instead of border
- clean up unused filter CSS
## Type changes
- update proficiency type to `number | number[]` to handle both weapons
(single) and characters (array)
## Summary
- Add Element, Rarity, and Proficiency picker components
- Refactor SearchContent filter layout with inline clear links
- Add theme-aware CSS variables for picker hover/selected states
- Add series filter support to search queries
## New Components
- **ElementPicker** - segmented/dropdown with element-specific colors
- **RarityPicker** - segmented/dropdown for R/SR/SSR
- **ProficiencyPicker** - segmented/dropdown for weapon types
## Picker Features
- Single and multi-select modes
- Auto-responsive: segmented on desktop, dropdown on mobile
- Manual mode override via `mode` prop
- Optional "Any" element for ElementPicker
- Contained/default style variants
- Tooltips on hover in segmented mode
## SearchContent Changes
- Rarity and Element filters on same row with space-between
- Clear links in filter headers (not buttons)
- Flexbox layout with consistent gaps
- Series dropdown filter
## Summary
Add job accessories feature and migrate jobs list to
DatabaseGridWithProvider pattern:
- Jobs list now uses DatabaseGridWithProvider (consistent with
weapons/characters/summons)
- Segmented control to switch between jobs and accessories views
- Full CRUD pages for job accessories (detail, edit, new)
- Job creation page for editors
- Navigation dropdown for jobs section
## Changes
### DatabaseGridWithProvider extension
- Extended to support `jobs` resource
- Added `searchJobs` method to search adapter
- Job-specific filters (row, proficiency, master_level, etc.)
- Collection filters hidden for jobs (no element/rarity/series)
### Job grid cells
- `JobIconCell` - portrait thumbnail
- `JobTierCell` - row tier badge
- `JobProficienciesCell` - weapon proficiency icons
- `JobFeaturesCell` - master/ultimate/accessory badges
### Job accessories
- Detail page with job info
- Edit/new pages for editors
- Type utilities (Shield/Manatura)
### Navigation
- Dropdown with "New job" and "New job accessory" options
## Dependencies
Requires hensei-api#206 for backend endpoints.
## Test plan
- [ ] Jobs list loads with DatabaseGridWithProvider
- [ ] Segmented control switches between jobs/accessories
- [ ] Job accessory detail/edit/new pages work
- [ ] Job creation page works for editors
- [ ] Navigation dropdown appears on job pages
## Summary
- add `maxExorcismLevel` to Weapon type
- add field to WeaponStatsSection in database pages (with min=1
validation)
- include in new/edit/import page payloads
- make BefoulmentSelect exorcism options dynamic (0 to maxExorcismLevel)
- pass maxExorcismLevel to BefoulmentSelect from edit panes
## Test plan
- [ ] verify maxExorcismLevel field appears in weapon stats section
- [ ] verify min=1 validation works
- [ ] verify exorcism dropdown shows correct options based on weapon's
maxExorcismLevel
## Summary
Removes the suggestion badge/accept/dismiss UI from batch import pages.
Form fields are still pre-populated with parsed wiki data, but users no
longer see sparkle icons or have to accept/dismiss individual
suggestions.
Changes:
- Rename type aliases: `*Suggestions` → `ParsedData*`
- Delete `SuggestionBadge.svelte` and `SuggestionDetailItem.svelte`
- Remove suggestion props from all section components
- Simplify import pages by removing dismissed state tracking and
handlers
**Requires:** jedmund/hensei-api#204
## Test plan
- [ ] Test batch import for characters, weapons, and summons
- [ ] Verify form fields still pre-populate from wiki data
- [ ] Verify edit pages still work (they share section components)
## Summary
- add suggestion support to metadata sections for name fields
- remove duplicate basic info sections from import pages
- auto-generate wikiJa and kamigame URLs from name (jp) field
## Test plan
- [ ] test batch import flow still works
- [ ] verify wikiJa/kamigame auto-populate when typing japanese name
- [ ] check metadata sections show suggestion badges
## Summary
- add detail and edit pages for weapon series at
`/database/series/weapons/[slug]`
- fix series table navigation to use slug instead of uuid
- add `?view=series` URL param for bookmarkable series view
- remove redundant `/database/series` page
- rename augment type `none` → `no_augment` for consistency
## Test plan
- [ ] navigate to /database/weapons, toggle to series view
- [ ] verify URL updates to ?view=series
- [ ] click a series row, should go to detail page
- [ ] back button returns to series view
- [ ] edit page saves correctly
## Summary
- Add weapon stat modifier types and API layer
- Rewrite AX skill components to fetch modifiers from API instead of
local data
- Add befoulment select component for weapon editing
- Update weapon edit views to use new modifier system
- Remove old hardcoded ax skill definitions
This is the frontend counterpart to the API weapon stat modifiers
feature. AX skills and befoulments are now fetched from the API instead
of being hardcoded in the frontend.
## Test plan
- [ ] Edit a weapon with AX skills, verify dropdown shows correct
options
- [ ] Add/remove AX skills on a weapon, verify saves correctly
- [ ] Add befoulment to a weapon, verify UI and save work
- [ ] Verify existing weapons with AX skills display correctly
shows when collection items got nuked
- red badge + dimmed look on orphaned weapons/summons/characters
- amber banner at party level if anything's orphaned
- types updated for `orphaned` field
