Question:

When importing cap table data from external sources (e.g., public filings, legacy systems), we often have current state but not full transaction history.

For example, a UK Companies House confirmation statement tells us:

"Shareholder A holds 85,000,000 shares as of 2024-12-01"

But we don't know when these shares were originally issued, what transfers occurred, or the issuance price.

Current workaround: Create a TX_STOCK_ISSUANCE with date set to the filing date.

Problem: This is misleading - it appears shares were issued on that date, when we're really just recording a point-in-time snapshot.

Is there a recommended pattern for this? Some ideas:

1. Add quantity_source to StockIssuance (as WarrantIssuance has) with a value like SNAPSHOT?
2. A new transaction type like TX_BALANCE_FORWARD for opening balances?
3. A manifest-level flag indicating the package represents a snapshot, not full history?

Anything else we need to know?

Related to #440 (handling mapping conflicts/gaps on import).

Our use case is importing UK Companies House public filings into OCF while being transparent that we lack the underlying transaction log.