Skip to content

website/functions: CONTROL vocabulary gains code-only/unregistered - #1044

Open
gHashTag wants to merge 1 commit into
mainfrom
fn-control-unregistered
Open

gHashTag wants to merge 1 commit into
mainfrom
fn-control-unregistered

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Companion of gHashTag/t27#4038 (spec of record) and gHashTag/999-multibots-telegraf#2502 (registry + manifest).

  • FN_CONTROLS += 'code-only/unregistered' with a comment saying what it means.
  • Test: a spec with that CONTROL and a manifest entry with the same control builds ok with no distance; a value outside the vocabulary is still a build problem.

Not in this PR: public/functions/manifest.json is still the 28-function vendored copy (no crm-proactive-sweep, five withdrawn still spec+code). Refresh it after #2502 merges, otherwise the five cards would show a CONTROL distance (warn) -- which would be the honest state until then.

Witness: node --test scripts/agents-from-specs.test.mjs 46 pass / 1 fail; the failing test 31 (tri tool spec card) fails on main before this change too.

t27 specs/functions/README.md (gHashTag/t27#4038) added the value for the
five functions withdrawn from the bot's registerFunctions.ts on 2026-09-17
(999-multibots-telegraf#2502). The generator accepts it and the card shows no
distance when spec and manifest agree; a value outside the vocabulary is
still a build problem (test added). The vendored manifest is refreshed
separately once the bot PR lands.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant