/**
 * Initiative Record — public exports (Phase A0 kernel).
 *
 * Task I-1: types, schemas, errors, and the repository interface. Task I-2
 * adds `InitiativeRecordStore` (the SQLite-backed store) and
 * `runInitiativeMigrations` (the backup-before-upgrade migration runner) now
 * that `sqlite-store.ts` and `migrations.ts` exist.
 *
 * SPEC-003 Phase B (Task I-1) extends this surface with `Task.claimed_by`,
 * the `initiative_task_claim` / `initiative_task_release` /
 * `initiative_task_complete` / `initiative_task_execution` operations, their
 * `task_not_claimable` / `task_claim_conflict` / `invalid_task_transition`
 * typed errors, and the additive `initiatives.db` schema version 3 migration
 * — all re-exported through the wildcard exports below, no new export list
 * required.
 *
 * SPEC-004 Lifecycle Engine (Task I-1) extends this surface with the
 * `Phase` / `PhaseRecordState` / `Satisfier` / `Establishment` / `PhaseRecord`
 * / `LifecycleContract` / `GateEstablishmentResult` / `GateStatus` /
 * `LifecycleResumeBlock` domain types, `Initiative.focus_phase` /
 * `Initiative.lifecycle_contract`, the `initiative_phase_enter` /
 * `_satisfy` / `_reopen` / `_skip` / `initiative_focus_set` /
 * `initiative_set_lifecycle_contract` mutations and read-only
 * `initiative_gate_status`, their `invalid_phase_transition` /
 * `unknown_lifecycle_contract` typed errors, and the additive
 * `initiatives.db` schema version 4 migration (seeded immutable
 * `default-sdl@1`) — all re-exported through the wildcard exports below, no
 * new export list required. Store BEHAVIOR (transitions, live gate
 * evaluation) is Task I-2/I-3; this task is the data contract only.
 *
 * SPEC-005 Method Registry (Task I-1) extends this surface with `Task.method`,
 * the `MethodDeclaration` domain type, the `method_get` / `method_list` /
 * `initiative_task_set_method` operations, the `unknown_method` typed error,
 * and the additive `initiatives.db` schema version 5 migration (seeded
 * immutable nine-Method built-in catalog) — all re-exported through the
 * wildcard exports below, no new export list required. Store BEHAVIOR
 * (Method lookup, guidance resolution, Task Method persistence) is Task
 * I-2/I-3; this task is the data contract only.
 *
 * SPEC-005 Method Registry (Task I-2) adds `InitiativeRecordStore.getMethod()`
 * / `.listMethods()` (declared on the class itself, not re-exported
 * separately here) and `loadMethodGuidance(id)`, the committed
 * `packages/core/src/methods/<name>/guidance.md` resolver, exported below.
 * Its internal test seam `resolveGuidanceFromRootForTest` is DELIBERATELY
 * NOT re-exported here — it is reachable only from
 * `./method-guidance.js` directly, never from this public barrel.
 *
 * SPEC-006 Business intake (Task I-1) extends the built-in Method catalog with the tenth
 * declaration, `intent-to-initiative@1`, its committed guidance asset, and the additive
 * `initiatives.db` schema version 6 migration. No new export — the same `MethodDeclaration`
 * type, `method_get` / `method_list` operations, and `loadMethodGuidance` resolver already
 * exported above cover it.
 *
 * SPEC-007 Delivery Layer (Task I-2) extends this surface with the generic `TargetAdapter`
 * interface (`types.ts`, alongside `Deliverable` / `DeliverableArtifactMember` /
 * `DeliveryHistoryEntry` — declared now so `TargetAdapter.validate` type-checks, though their
 * store methods and operations are Task I-3/I-4), the `duplicate_target_adapter` typed error
 * (`DuplicateTargetAdapterError`), and the public process-local registry
 * `registerTargetAdapter` / `resolveTargetAdapter` (`target-adapters.ts`, exported below — the
 * only names from that module re-exported here; it registers no adapter of its own).
 *
 * SPEC-007 Delivery Layer (Task I-1) extends this surface with the `DeliveryContract` domain
 * type, `deliveryContractDeclarationSchema` / `deliveryContractGetInputSchema` /
 * `deliveryContractListInputSchema`, the `unknown_delivery_contract` typed error
 * (`UnknownDeliveryContractError`), the additive `initiatives.db` schema version 7 migration
 * (seeded immutable two-Delivery-Contract built-in catalog, plus the schema-only
 * `deliverables` / `deliverable_artifacts` / `deliverable_delivery_history` DDL a later task
 * populates), and `InitiativeRecordStore.getDeliveryContract()` / `.listDeliveryContracts()`
 * (declared on the class and the `InitiativeRepository` interface) — all re-exported through
 * the wildcard exports below, no new export list required. This task does not add the
 * `delivery_contract_get` / `delivery_contract_list` operations to the shared operation union,
 * the generic adapter interface/registry, or any Deliverable entity or operation — those are
 * later, independently checkable tasks.
 *
 * SPEC-007 Delivery Layer (Task I-9) adds `loadDeliveryPackager(id)`, the committed
 * `packages/core/src/delivery-packagers/<name>/packager.md` resolver, exported below — the same
 * declaration/guidance split and dev-vs-installed dual-path resolution `loadMethodGuidance`
 * already gives Method Procedure guidance.
 */
export * from './types.js';
export * from './schemas.js';
export * from './errors.js';
export { evaluateLifecycleGate } from './lifecycle-gates.js';
export type { EvaluateLifecycleGateInput } from './lifecycle-gates.js';
export type { InitiativeRepository, InitiativeWorkspaceLinkRead, RelatedInitiativeRead, RequirementWithCriteriaRead, LatestVerificationRead, } from './repository.js';
export { InitiativeRecordStore } from './sqlite-store.js';
export type { InitiativeRecordStorePragmas } from './sqlite-store.js';
export { runInitiativeMigrations, INITIATIVE_SCHEMA_VERSION } from './migrations.js';
export type { RunInitiativeMigrationsOptions, RunInitiativeMigrationsResult } from './migrations.js';
export { loadMethodGuidance } from './method-guidance.js';
export { registerTargetAdapter, resolveTargetAdapter } from './target-adapters.js';
export { loadDeliveryPackager } from './delivery-packagers.js';
//# sourceMappingURL=index.d.ts.map