Skip to content

feat(agentic-engineering): add a machine-readable spend-stewardship enablement flag #93

Description

@devantler

🤖 Generated by the Agentic Engineer

Why

Spend stewardship is enabled by prose: the entrypoint performs a cost pass when the consumer's Spend contract section resolves, and spec.consumer.requiredWhenSpendStewardshipEnabled only lists required sections — it carries no enablement state. A reader of the manifest alone cannot tell whether the cost path is on, and a runtime reconciling the desired state has nothing to key off.

Raised as a 🟠 Major on monorepo#2455: with that deployment's private decision channel unresolved, nothing machine-readable stopped the decision-producing path from being active.

That consumer fixed the risk by gating the decision-producing half default-off on its private channel and pinning it with a test. What it cannot fix is the manifest shape: .spec.roles[*] is only_keys(["enabled", "mode"]) and .spec.consumer an exact six-key set, so a consumer-side flag key fails validate-manifests.sh, and the copied resource must stay byte-identical. This is the generic half.

Acceptance criteria

  • A machine-readable enablement field with an explicit default-off state, in the existing provider-neutral vocabulary.
  • validate-manifests.sh accepts the new shape and rejects a missing/malformed one; validate-manifests.test.sh covers both enabled and disabled states, per feature-flag-first.
  • onboarding.steps and the schedule prompts consume the field rather than restating the rule.
  • Plugin README documents it.
  • Consumer follow-up: bump the gitlink and mirror the copied desired state.

Size

Small–medium: schema + validator + self-test + README.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions