# @tagma/core

Runtime-independent orchestration core for Tagma pipelines.

This package owns pipeline DAG execution, plugin registries, approval gateways, lifecycle events, logging abstractions, dataflow helpers, prompt document helpers, and the `TagmaRuntime` interface. It does not provide a concrete process runner or file watcher; hosts must pass a runtime implementation to `runPipeline()`.

```ts
import { PluginRegistry, runPipeline } from '@tagma/core';
import { bunRuntime } from '@tagma/runtime-bun';

const registry = new PluginRegistry();
const result = await runPipeline(config, process.cwd(), {
  registry,
  runtime: bunRuntime(),
});
```

Use `@tagma/sdk` for the Bun-first convenience API with built-ins registered by default.

## Runtime Contract

`@tagma/core` intentionally does not declare an `engines.bun` requirement. The
published package is runtime-agnostic orchestration code; concrete Bun-only
process execution, file watching, and CLI convenience behavior live in
`@tagma/runtime-bun` and `@tagma/sdk`.

## Retry Host Context

Low-level hosts can pass `taskPromptContexts` and `taskContinuations` in
`RunPipelineOptions`, keyed by fully qualified task ID (`track.task`). Prompt
contexts are appended after middleware enrichment. Continuation seeds carry a
prior same-task session ID, driver, and normalized output so drivers can resume
the session when supported and fall back to text context otherwise.
An authored task `continue_from` remains authoritative; hosts do not replace its
current upstream handoff with same-task retry state.

The SDK workflow runner uses these options for finite self-repair lifecycles;
ordinary single-pipeline runs are unchanged when the options are omitted.

## Publishing

`@tagma/core` is a public npm dependency of `@tagma/runtime-bun` and `@tagma/sdk`. Publish it after `@tagma/types` and before runtime or SDK packages.