# Fresh pack install can apply autonumber metadata before object specs

## Summary

On a fresh local install of the downstream PingCAP stack, `salesforce-crm-standard`
pack install can fail during autonumber verification because some declared
autonumber metadata is verified before the corresponding object fields are fully
available in `_System_Field`.

## Observed failure

```text
pack salesforce-crm-standard: autonumber_counter autonumber_counters: autonumber verify: invariant violated: 1 violation(s): V8: 6 of 6 reachable declared autonumber seeds are NOT written in _System_Field
```

Affected fields observed in the failure:

- `Case.CaseNumber`
- `Contract.ContractNumber`
- `Order.OrderNumber`
- `OrderItem.OrderItemNumber`
- `Quote.QuoteNumber`
- `QuoteLineItem.LineNumber`

## Why this looks upstream

Both `object_spec` and `autonumber_format` are installed in the
`object_metadata` phase. Without an explicit dependency edge that guarantees
field metadata exists first, `autonumber_format` can be processed before the
target fields are fully present in `_System_Field`, and the verify step fails.

## Expected behavior

Fresh install should deterministically succeed, and autonumber metadata should
only be applied and verified after target fields exist.

## Actual behavior

Fresh install can fail during autonumber verify on a clean database depending on
install ordering.

## Suggested fix direction

1. Add an explicit dependency or ordering guarantee so `autonumber_format` runs
   after target `object_spec` fields are materialized.
2. Or move autonumber write and verify to a later phase after object metadata is
   guaranteed stable.
3. Or make verify tolerate the first pass and retry after object metadata
   reconciliation.