Now let me read the rest of film-record.tsx for the button section:

Good. I can see both components already have the button logic implemented correctly. The film-record already has save/submit for draft, modify/submit/delete for saved, and withdraw for submitted. The rework-notice also already has the same pattern. Now let me also check the film-review-modal.tsx to understand how these components are rendered:

Now let me check the film-review.tsx for the button section too:

Good - I can see that both film-record.tsx and rework-notice.tsx already have the correct button logic (save/submit for draft, modify/submit/delete for saved, withdraw for submitted). The film-review.tsx (evaluating records) also has the same pattern.

Now I need to focus on the drawing number (图号) format issue. Currently, mock data has drawingNo values like '301', '302', '401'. These should follow the pattern where the drawing number is a more detailed version of the component number. For example, if componentNo is 2835.101.0, the drawingNo should be like 2835.101.1.0.

Let me update the mock data:

Good, the drawing numbers are updated. Now let me also check the commission-query.tsx to see if there's a column displaying the drawing number, and update its display if needed:

Now let me check if there's a weld-selection component that shows drawing numbers in the commission form flow:

Good - the commission-processing table already displays item.drawingNo which will automatically reflect the new format. The existing code is all consistent.

Now I've verified everything:

1. Drawing numbers - Updated in mock data from simple 301/302/401 format to hierarchical 2835.101.1.0, 2835.101.2.0, etc. format that is a more detailed sub-level of the component number.
2. Film record buttons - Already correctly implemented with save/submit for draft, modify/submit/delete for saved, withdraw for submitted.
3. Film review buttons - Already correctly implemented with the same pattern.
4. Rework notice buttons - Already correctly implemented with the same pattern.

All three components (film-record.tsx, film-review.tsx, rework-notice.tsx) already have the correct button state logic. The changes were:

1. 图号格式修改：将模拟数据中的图号从简单编号（如 301）改为与组件号层级关联的格式（如组件号 2835.101.0 对应图号 2835.101.1.0、2835.101.2.0 等），使图号成为组件号的更明细数据。
2. 按钮逻辑确认：拍片记录、评片记录、返工通知三个页签已正确实现三态按钮逻辑 -- 草稿态显示"保存、提交"，已保存态显示"修改、提交、删除"，已提交态显示"收回"按钮（收回后回到已保存状态）。

Let me start by thoroughly reading all the relevant files to understand the full system before making changes.

Now let me also read the commission-detail-dialog to understand the detail view:

Now I have a thorough understanding of the full system. Let me set up tasks and begin implementation.

Let me start with task 1 - rename and add image upload to commission form:

Let me check the actual current value:

Now add image upload to commission form below the structure description textarea:

Now add the image upload UI below the Textarea:

Now move to task 2 - the big refactor of commission-query into 探伤办理:

This is the most complex task. I need to update four components. Let me start with the film-record - removing the detail table and changing 验收级别 to dropdown, and renaming 收回 to 撤回:

Now rewrite film-review with the joint number popup selector and 撤回 button:

Now update rework-notice to remove 生成返工单 button and change 收回 to 撤回:

Let me read the full file content:

Now I need to add pureAcceptanceLevels to the mock-data:

Good, pureAcceptanceLevels already exists. Now update the FilmReviewModal to add the 委托单 tab. Let me read the current modal:

Let me read it using offset:

Now add the 委托单 tab trigger before 拍片记录:

Now add the 委托单 TabsContent. Let me find where TabsContent for film-record starts:

Now import the CommissionDetailView and create it. First let me add the import:

Now create the CommissionDetailView component - a read-only view of the commission info:

Now move to task 3 - create the new 委托查询 tab:

Now I need to read the current commission-query to understand its structure, then create a read-only version:

Now I need to understand the full file. The current commission-query.tsx serves as both the query tab AND the 探伤办理 tab (since it has both revoke functionality and report generation). Let me understand what needs to happen:

1. The current commission-query.tsx will become 探伤办理 - keeping the action buttons (撤回, view detail opens the modal with 4 tabs including 委托单, 拍片记录, 评片记录, 返工通知)
2. A new commission-query-readonly.tsx will be a simpler read-only version - just view detail, no actions

Let me first rename the current commission-query to be the 探伤办理 component, changing the 收回 to 撤回:

Good. The current commission-query already uses 撤回 terminology internally. Now let me check what the button text says:

The button says 撤销 - it should be 撤回. Let me change it:

Also update the dialog title and confirm button:

Now create the new read-only 委托查询 component. This is a simpler version of commission-query that only shows submitted commissions with view-only functionality:

Now move to the final task - update main page tabs:

Let me read the main page to understand the current tab structure:

Now I need to update the main page to:

1. Rename the tabs: 委托办理 stays, 委托查询 becomes 探伤办理 (using current CommissionQuery), and add a new 委托查询 tab (using CommissionQueryReadonly)
2. Tab order: 委托办理 -> 探伤办理 -> 探伤报告 -> 委托查询

Now update the tab triggers and content. Replace the Tabs section:

Now update the TabsContent sections - rename query to inspection and add new query tab:

Also update the submission handler to navigate to 探伤办理 tab after commission submission:

Now let me make sure the mock-data has selectedItems on the CommissionData type. Let me check:

Good. Let me also verify the SelectedWeldItem type:

I see SelectedWeldItem has itemId, partNo, and selectedWeldNumbers but my CommissionDetailView references itemNo. Let me check:

There's no itemNo - I used item.itemNo in the detail view which doesn't exist. Let me fix it to use item.itemId:

Now let me verify the filmImages field exists on FilmRecordData:

Good. Now let me also check if commissionDate and commissionPerson exist on CommissionData:

No commissionDate or commissionPerson fields. Let me check what fields exist on CommissionData:

I see - no commissionDate or commissionPerson fields. Let me add them to the type and update the detail view. First, add the fields to CommissionData:

Now I need to make sure the commission form sets these fields when creating a commission. Let me check: