fix: keep adjustment cost entry continuous

[corrin]

What changed

• promotes a typed adjustment from the trailing phantom row into a local draft immediately
• keeps a fresh blank row available for continuous entry in Estimate, Quote, and Actual
• awaits parent persistence before removing the promoted draft
• exercises adjustment creation through the authenticated UI path

Why

Typing an adjustment description inferred the correct kind but kept occupying the only blank row until every save-required field was complete. This interrupted continuous cost entry.

Impact

Users can begin another cost line as soon as they start an adjustment description. Backend APIs and schemas are unchanged.

Validation

• focused SmartCostLinesTable unit tests: 3 files, 6 tests passed
• targeted authenticated Estimate and Actual cost-entry E2E scenarios passed
• repository commit hooks passed

Review note

Follow-up review should concentrate on in-flight edits, pending-draft lifecycle during refresh/failure, stable local row identity, and deletion of incomplete promoted drafts.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e236284e-342f-467a-858a-16deee1519bb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/KAN-295-adjustment-continuous-entry

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[corrin]

Verified green — ready to merge

Head is now `5194fd19` (the four-line fix was uncommitted until now; the previous head `32d3e304` was the broken state).

Root cause: the `columns` computed in `SmartCostLinesTable.vue` depended on `negativeIdsSig`. An async negative-stock refresh recreated every column def and cell renderer, destroying the active editor mid-typing — the description got truncated.

E2E: job-cost-entry-data.spec.ts → actual labour material adjustment and delete reconcile persisted costs — 1 passed (2.6m). This is the test that was red against 32d3e304 with the text truncated to E2E actua. Full teardown completed; DB restored and verified clean.

Audit of the fix:

• Negative-stock rendering stays reactive — isNegativeStock reads props.negativeStockIds directly inside an h() cell render callback, so Vue tracks it at render time. The negativeIdsSig dep was only forcing the full column rebuild that killed the editor.
• unit_cost: null → undefined is a genuine contract fix, not a type-error silencer: updateDraft merges via spread (so undefined clears the field) and requiredNumber() rejects both at save time.
• vue-tsc --build --force passes; all pre-commit hooks green.

Deferred lifecycle improvements remain in KAN-296. Not merging without explicit instruction.