active-svelte

Commit Graph

Author	SHA1	Message	Date
dev	38462f3282	Cleanup: remove stale orca v0/v0.1+ markers across docs and types After v1 closed, the public surface still carried `@v0.0 Accepted, ignored`, `@v0.1+ never produced`, `@v1+ never invoked` notes that no longer match the engine. They lied to readers about what the runtime does. Code: - `types.ts` — rewrite docstrings for `OrcaTimeout`, `OrcaFatal`, `ctx.tokens`, `after`, `unless`, `abortOn`, `provides`, `actionTimeoutMs`, `onError`, `compensate` to describe current behaviour. - `consts.ts` — `ORCA_RESULT_TIMEOUT` / `_FATAL` and the error policy block lose their "never produced" / "v0.0" hedges. - `result.ts` — `orcaTimeout` / `orcaFatal` get real docstrings instead of `@v0.1+` markers. Docs: - `orca/README.md` "Estado Del Documento" — summarise v1 surface (engine + active wrapper, queue policies, transactions, fan-in, bus interception, tokens with payload). Drop the legacy `## Roadmap` section that listed v0/v0.1/v1 line items already delivered or already covered by the lower "Roadmap v1" / "v2" sections. - `active-app/README.md` — drop the dangling "orca v0.0" link. - `docs/orca_minds.txt` — prepend an ARCHIVED banner. - `docs/active-app-refactorizacion.md` — replace the "Working document, abierto a evaluación" header with an ARCHIVED notice (refactor completed 2026-05-04). No behavioural change. Tests still 1471/1471. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	feacd46c62	Promote orca v0 from callback runner to orchestration kernel Implements the v0-kernel design captured in docs/orca_minds.txt: the engine now carries every event through an internal envelope, exposes trace identity to actions, and bounds derived-event chains through configurable reentry guards. The previous engine was effectively a callback runner with stages; this commit turns it into a runtime that can answer "where does this event come from, how deep is it, and when should I stop?" without polluting user-defined payloads with runtime metadata. New public surface: - OrcaEnvelope<TPayload> + OrcaEventMeta (eventId, traceId, parentEventId, parentRunId, emittedByAction, depth, stack, publishedAt, dedupeKey) - OrcaActionContext gains eventId / traceId / parentEventId / depth plus emit(event, payload, options?) -> OrcaEventId \| null - OrcaResult adds OrcaInterrupted (with orcaInterrupted() helper) - OrcaActionRun.status and OrcaRunResult.status add 'interrupted' - OrcaRunResult exposes eventId / traceId / parentEventId / depth - OrcaReentryOptions on EngineOrcaOptions: maxDepth (16), maxEventsPerTrace (128), repeatedEventLimit (2), repeatedEventPolicy (skip / abort-trace / error) - Constants for reentry policies and reasons; OrcaReentryError class Engine semantics: - Bus publishes are roots: fresh traceId, depth=0, no parent. They never enter the reentry counters. - ctx.emit() builds a child envelope inheriting the parent's traceId and incrementing depth. The child is enqueued, never executed inline. - Reentry guards apply only to derived envelopes. Crossing maxDepth, maxEventsPerTrace, repeatedEventLimit, or matching a previous dedupeKey triggers the configured policy. Skip blocks just that envelope; abort-trace marks the trace and skips every queued event that belongs to it; error throws OrcaReentryError synchronously. - dispose() marks every live trace aborted with reason 'disposed' so late ctx.emit() calls (e.g. from compensating cleanup) get a clean rejection instead of an exception. Diagnostics gain four new event types (action.interrupted, event.emitted, reentry.blocked, trace.aborted) and every existing one carries the envelope identifiers (runId, eventId, traceId, parentEventId, depth) where applicable, so a log sink can correlate runs without parsing variant tags. Tests: 10 new tests covering envelope identity (root depth=0, child depth+1), ctx.emit() trace inheritance, run-trace correlation, orphan emit, all four reentry guards (maxDepth with disjoint event names so the same-name limit doesn't interfere, repeatedEventLimit, error policy throwing OrcaReentryError, abort-trace, dedupeKey), and the invariant that bus publishes start fresh traces. Active-app presets keep working unchanged (they don't call ctx.emit yet); the API extension is additive on the OrcaActionContext side (presets still type-check against the wider context shape). Total: 1357/1357 vitest tests pass (47 in orca, +10 from this commit). Roadmap v1 documented at the foot of the orca README and parked under @v1+ in the source: actionTimeoutMs runtime, compensate invocation, after/unless/abortOn gating, OrcaFatal distinction, queue policies (commit/replace/parallel), transaction/atomic groups, payload-bearing tokens, fan-in, validate()/commit() static graph validation, createActiveOrca() reactive wrapper, and the bus.publish interception (Option B) that would let modules' direct publishes attach emittedByAction perfectly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago

Author

SHA1

Message

Date

dev

38462f3282

Cleanup: remove stale orca v0/v0.1+ markers across docs and types

After v1 closed, the public surface still carried `@v0.0 Accepted,
ignored`, `@v0.1+ never produced`, `@v1+ never invoked` notes that
no longer match the engine. They lied to readers about what the
runtime does.

Code:
- `types.ts` — rewrite docstrings for `OrcaTimeout`, `OrcaFatal`,
  `ctx.tokens`, `after`, `unless`, `abortOn`, `provides`,
  `actionTimeoutMs`, `onError`, `compensate` to describe current
  behaviour.
- `consts.ts` — `ORCA_RESULT_TIMEOUT` / `_FATAL` and the error
  policy block lose their "never produced" / "v0.0" hedges.
- `result.ts` — `orcaTimeout` / `orcaFatal` get real docstrings
  instead of `@v0.1+` markers.

Docs:
- `orca/README.md` "Estado Del Documento" — summarise v1 surface
  (engine + active wrapper, queue policies, transactions, fan-in,
  bus interception, tokens with payload). Drop the legacy
  `## Roadmap` section that listed v0/v0.1/v1 line items already
  delivered or already covered by the lower "Roadmap v1" / "v2"
  sections.
- `active-app/README.md` — drop the dangling "orca v0.0" link.
- `docs/orca_minds.txt` — prepend an ARCHIVED banner.
- `docs/active-app-refactorizacion.md` — replace the
  "Working document, abierto a evaluación" header with an
  ARCHIVED notice (refactor completed 2026-05-04).

No behavioural change. Tests still 1471/1471.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

dev

feacd46c62

Promote orca v0 from callback runner to orchestration kernel

Implements the v0-kernel design captured in docs/orca_minds.txt: the
engine now carries every event through an internal envelope, exposes
trace identity to actions, and bounds derived-event chains through
configurable reentry guards. The previous engine was effectively a
callback runner with stages; this commit turns it into a runtime that
can answer "where does this event come from, how deep is it, and when
should I stop?" without polluting user-defined payloads with runtime
metadata.

New public surface:
  - OrcaEnvelope<TPayload> + OrcaEventMeta (eventId, traceId,
    parentEventId, parentRunId, emittedByAction, depth, stack,
    publishedAt, dedupeKey)
  - OrcaActionContext gains eventId / traceId / parentEventId / depth
    plus emit(event, payload, options?) -> OrcaEventId | null
  - OrcaResult adds OrcaInterrupted (with orcaInterrupted() helper)
  - OrcaActionRun.status and OrcaRunResult.status add 'interrupted'
  - OrcaRunResult exposes eventId / traceId / parentEventId / depth
  - OrcaReentryOptions on EngineOrcaOptions: maxDepth (16),
    maxEventsPerTrace (128), repeatedEventLimit (2),
    repeatedEventPolicy (skip / abort-trace / error)
  - Constants for reentry policies and reasons; OrcaReentryError class

Engine semantics:
  - Bus publishes are roots: fresh traceId, depth=0, no parent. They
    never enter the reentry counters.
  - ctx.emit() builds a child envelope inheriting the parent's traceId
    and incrementing depth. The child is enqueued, never executed
    inline.
  - Reentry guards apply only to derived envelopes. Crossing maxDepth,
    maxEventsPerTrace, repeatedEventLimit, or matching a previous
    dedupeKey triggers the configured policy. Skip blocks just that
    envelope; abort-trace marks the trace and skips every queued event
    that belongs to it; error throws OrcaReentryError synchronously.
  - dispose() marks every live trace aborted with reason 'disposed' so
    late ctx.emit() calls (e.g. from compensating cleanup) get a clean
    rejection instead of an exception.

Diagnostics gain four new event types
  (action.interrupted, event.emitted, reentry.blocked, trace.aborted)
and every existing one carries the envelope identifiers
(runId, eventId, traceId, parentEventId, depth) where applicable, so a
log sink can correlate runs without parsing variant tags.

Tests: 10 new tests covering envelope identity (root depth=0, child
depth+1), ctx.emit() trace inheritance, run-trace correlation, orphan
emit, all four reentry guards (maxDepth with disjoint event names so
the same-name limit doesn't interfere, repeatedEventLimit, error
policy throwing OrcaReentryError, abort-trace, dedupeKey), and the
invariant that bus publishes start fresh traces.

Active-app presets keep working unchanged (they don't call ctx.emit
yet); the API extension is additive on the OrcaActionContext side
(presets still type-check against the wider context shape).

Total: 1357/1357 vitest tests pass (47 in orca, +10 from this commit).

Roadmap v1 documented at the foot of the orca README and parked under
@v1+ in the source: actionTimeoutMs runtime, compensate invocation,
after/unless/abortOn gating, OrcaFatal distinction, queue policies
(commit/replace/parallel), transaction/atomic groups, payload-bearing
tokens, fan-in, validate()/commit() static graph validation,
createActiveOrca() reactive wrapper, and the bus.publish interception
(Option B) that would let modules' direct publishes attach
emittedByAction perfectly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2 Commits (a001bc3b2d1be5dd5ff38a45f94ab081ee4122fd)