[finding] The skill-reference Exports: fallback ranks by source order, so DEPRECATED_/NON_AUTHORABLE_/LEGACY_ constants headline customer-facing rows

Filed unassigned while converging build-skill-references.ts on the shared module-docblock selector (#12094). Out of that card's scope — that one fixes which doc block is published; this is about what the fallback publishes when there is no module doc block at all. #12094 explicitly left the fallback chain in place and named the follow-up question, so this records the measurement rather than pre-judging it.

What

When a .zod.ts has no module doc block, extractDescription() in packages/spec/scripts/build-skill-references.ts falls through to an export list:

const re = /export\s+const\s+(\w+Schema|\w+)\s*(?:[:=])/g;
// …
if (exports.length > 0) return `Exports: ${exports.slice(0, 5).join(', ')}`;

Two properties combine badly on a customer-facing surface:

Rank is source order, not importance — slice(0, 5) keeps whichever five happen to be declared first.
The regex has no notion of public authorable surface — any export const qualifies, including constants whose own names say they are not for authoring.

Measured

After #12094 lands, these rows are what skills/** publishes (measured on main at 22c42c9 plus that change):

skills/objectstack-automation/references/_index.md

- `…/src/automation/approval.zod.ts` — Exports: ApproverType, DEPRECATED_APPROVER_TYPES, NON_AUTHORABLE_APPROVER_TYPES, ORG_MEMBERSHIP_LEVELS, APPROVER_EXPRESSION_ROOTS

Two of the five named constants are explicitly deprecated or explicitly non-authorable.

skills/objectstack-i18n/references/_index.md

- `…/src/system/translation.zod.ts` — Exports: LocaleSchema, FieldTranslationSchema, ActionResultDialogTranslationSchema, ObjectTranslationDataSchema, LEGACY_OBJECT_FIRST_KEYS

Why it is worth a card

The line is true — it is an accurate list of what the module exports, which is why #12094 kept it (an honest export list beats a confidently wrong prose sentence). It is the ranking that is the hazard, and only on this surface: skills/** is loaded whole into a customer agent's context window, and its job is to teach that agent what it may author. A row that headlines DEPRECATED_APPROVER_TYPES and NON_AUTHORABLE_APPROVER_TYPES is pointing an authoring agent at exactly the vocabulary it must not use, with nothing on the line marking them as such.

This is the "make AI-written metadata hard to get wrong" axis rather than a correctness bug — nothing is broken, and no gate is wrong today.

Options (not pre-judging)

Rank or filter the fallback list — prefer *Schema exports, or skip SCREAMING_SNAKE constants, which are machine constants rather than authorable metadata.
Require a module doc block on any .zod.ts reachable from SKILL_MAP and drop the fallback (the loud-refusal answer build-skill-references.ts still picks the first JSDoc block anywhere in the file — the defect build-docs.ts fixed, publishing a private constant's comment to customers #12094 declined to take for that card, since it would make "write a module docblock" an implicit prerequisite and red the gate on ~9 files).
Leave it — the export list is honest, and the real repair is authoring module doc blocks on the files that lack them.

The middle option interacts with the third: the population that reaches the fallback at all is the same ~9 files, so authoring their module doc blocks removes the symptom without any generator change.

Skills-lane self-triage: finding → promoted with the middle option, narrowed: in extractDescription()'s fallback, prefer *Schema exports and skip SCREAMING_SNAKE constants (machine vocabulary, never authorable); keep the honest Exports: form for what remains; regenerate. ⛔ The loud-refusal alternative (require module doc blocks, drop the fallback) is NOT taken — #12094 already declined it for the same population and the reasoning stands. Authoring the ~9 missing module doc blocks stays a separate editorial question and is not this card. Routing note: the file is packages/spec/scripts/build-skill-references.ts (spec toolchain) but central triage routed the card here and the affected surface is the published skills catalog — accepted as skills-lane work; the serial check found no open PR on the file (#12094's change is merged).

Claim: skills seat, session session_01RMTpSRF5CjMmQBFfPtPCwJ. Single-card dispatch. Branch: claude/issue-12201-exports-fallback-ranking. Regenerated skills/** artifacts ride under the #11705-A ruling's class (generator-owned outputs), but until that exemption LANDS in the checker, this PR still takes the governed path: draft, human merge.

Generated by Claude Code

{
  "issue": 12201,
  "status": "blocked",
  "branch": "claude/issue-12201-exports-fallback-ranking",
  "pr": null,
  "premise_still_valid": false,
  "summary": "Stopped before the first edit: the card's premise is false on origin/main, and the fix collides with in-flight work. (1) PR #12202 (OPEN, draft, session_01NDGG54XF5gbTLdQzCtnaVV, branch claude/issue-12094-skill-refs-module-docblock) is in flight on packages/spec/scripts/build-skill-references.ts and rewrites extractDescription() itself, plus 7 of the same skills/**/_index.md artifacts. #12094 is OPEN, not merged. The dispatch's two load-bearing assumptions -- '#12094's change is merged' and 'the serial check found no open PR on the file' -- are both incorrect. (2) Consequently the card's two quoted rows DO NOT EXIST on origin/main at eeec62a98: automation reads '-- Approval Step Approver Type' and i18n reads '-- Shared history sentence for every shape in this file.' Both quoted 'Exports:' rows are produced by #12202, not by main. (3) On main only THREE 'Exports:' rows exist in the whole catalog (shared/enums.zod.ts x2, shared/metadata-types.zod.ts) and NONE names a SCREAMING_SNAKE constant -- so the acceptance scan the card demands is already vacuously green, and the requested positive control has no live subject. Implementing here would ship a filter with zero observable effect on the published catalog, unverifiable by the card's own acceptance evidence, while guaranteeing a text conflict with #12202 on generator-owned artifacts that do not text-merge (AGENTS.md Multi-agent SS11). Recommendation: re-dispatch this card rebased on #12202 AFTER it lands. No edits were made. The branch claude/issue-12201-exports-fallback-ranking exists on origin but is EMPTY -- it points at eeec62a98, identical to origin/main, and carries no commits and no PR; it was pushed as the first-minute write-route probe before the premise was checked. Deleting it was attempted and REFUSED: `git push origin --delete` fails at the transport and the REST ref delete returns HTTP 403 'Write access to this GitHub API path is not permitted through this proxy.' Left in place rather than routed around; the local worktree and branch were removed.",
  "tests": "No build/test run -- stopped at premise verification before the first edit, so there was nothing to verify. Evidence is read-only measurement at BASE=eeec62a98d1ffafd0fadf2b6e9d34a6d48e381c7 (origin/main), the base the dispatch named. (a) Checked-in artifacts, verbatim: `grep -n approval.zod.ts skills/objectstack-automation/references/_index.md` -> '12:- `node_modules/@objectstack/spec/src/automation/approval.zod.ts` - Approval Step Approver Type'; `grep -n translation.zod.ts skills/objectstack-i18n/references/_index.md` -> '12:- `node_modules/@objectstack/spec/src/system/translation.zod.ts` - Shared history sentence for every shape in this file.' Neither matches the card's quoted row. (b) `grep -rn '— Exports:' skills/` returns exactly 3 rows (objectstack-ui/_index.md:34 and objectstack-data/_index.md:40, both shared/enums.zod.ts -> 'SortDirectionEnum, SortItemSchema, MutationEventEnum, IsolationLevelEnum'; objectstack-platform/_index.md:43, shared/metadata-types.zod.ts -> 'MetadataFormatSchema, BaseMetadataRecordSchema'). Zero SCREAMING_SNAKE among them: the card's acceptance scan is already green on main with no fix applied. (c) Ran the generator's own fallback regex (/export\\s+const\\s+(\\w+Schema|\\w+)\\s*(?:[:=])/g, build-skill-references.ts:213) over every source #12202's census routes into the fallback. Three files would publish a SCREAMING_SNAKE in their top-5 row, but only AFTER #12202 lands: automation/approval.zod.ts (DEPRECATED_APPROVER_TYPES, NON_AUTHORABLE_APPROVER_TYPES, ORG_MEMBERSHIP_LEVELS, APPROVER_EXPRESSION_ROOTS), system/translation.zod.ts (LEGACY_OBJECT_FIRST_KEYS), kernel/plugin.zod.ts (CORE_PLUGIN_TYPES, CONSUMER_INSTALLABLE_TYPES). The third is a scope gap: the card names only automation and i18n. (d) No filtered export list goes empty, so the 'fall through to the next fallback' arm the dispatch specifies has no live subject either: approval 17 exports -> 6 kept, translation 13 -> 12, plugin 4 -> 2, enums 4 -> 4.",
  "open_questions": [
    {
      "question": "The two sub-rules ('prefer *Schema first' AND 'skip SCREAMING_SNAKE') disagree on automation/approval.zod.ts, the card's headline row. Skip-only yields 'ApproverType, ApprovalDecision, ApprovalNodeApproverSchema, DecisionOutputDefSchema, ApprovalEscalationSchema'; adding Schema-first yields 'ApprovalNodeApproverSchema, DecisionOutputDefSchema, ApprovalEscalationSchema, ApprovalNodeConfigSchema, ApproverType' -- which demotes ApproverType, the approver-type enum an author actually writes, out of the headline. Which ranking is intended?",
      "options": [
        "A. Skip SCREAMING_SNAKE only, keep source order for what remains -- removes the hazard the card is about, changes nothing else, and keeps the most authorable name first on the one row the card quotes.",
        "B. Skip SCREAMING_SNAKE and sort *Schema first, as dispatched -- more uniform across rows, but demotes plain-named authorable enums (ApproverType, ApprovalDecision, HookBodyCapability, TransportProtocol) below schema objects on every row."
      ],
      "recommendation": "A. The measured hazard is machine vocabulary appearing at all, not schemas appearing late; skip-only fixes exactly that and is the smaller, more reviewable change on a governed surface. Schema-first is an additional ranking opinion that, on the card's own headline row, makes the result worse by the card's own 'teach the authoring agent what it may author' standard."
    },
    {
      "question": "Sequencing: how should this card be landed relative to #12202?",
      "options": [
        "A. Hold this card until #12202 merges, then re-dispatch on the new main -- all three hazard rows exist, before/after is measurable, the positive control has a real subject.",
        "B. Fold the filter into #12202 itself (same function, same artifacts, same author session).",
        "C. Branch this card off claude/issue-12094-skill-refs-module-docblock now."
      ],
      "recommendation": "A. It is the only option that produces a reviewable diff against main and a non-vacuous acceptance measurement. B re-opens a PR already through its census review and mixes two decisions on a governed surface. C yields a PR that cannot merge until #12202 does and whose diff is unreadable against main."
    }
  ],
  "out_of_scope_findings": []
}

Generated by Claude Code

ACCEPT (blocked) — premise-first stop was right, and the dispatch error was mine. My claim comment asserted "the serial check found no open PR on the file (#12094's change is merged)" — asserted, not measured. PR #12202 (draft, in flight) rewrites extractDescription() itself and carries 7 of the same artifacts; the card's two quoted rows exist only on that branch. Both load-bearing dispatch assumptions were false; the dev's read-only refutation (3 Exports: rows on main, zero SCREAMING_SNAKE, acceptance scan vacuously green) is complete. This is a #11936-family instance on my side: a serial-constraint claim written without the measurement that defines it.

Both open questions adjudicated per the dev's recommendations:

Ranking = A (skip-only): filter SCREAMING_SNAKE, keep source order for what remains. ⛔ Schema-first is NOT taken — on the card's own headline row it demotes ApproverType, the enum an author actually writes, which fails the card's own standard. This supersedes the Schema-first half of my grading comment.
Sequencing = A (hold until fix(spec): publish each skill reference's own module doc block, not the first block in the file #12202 lands, re-dispatch on the new main) — the only shape with a reviewable diff and a non-vacuous acceptance measurement. Scope note for the re-dispatch: the fallback census found a THIRD affected file the card missed — kernel/plugin.zod.ts (CORE_PLUGIN_TYPES, CONSUMER_INSTALLABLE_TYPES) — include it in the acceptance scan.

State: pm:dispatched → pm:blocked.
Blocked-by: #12094
Unlock-action: when PR #12202 merges, re-dispatch this card on the new main with ranking A and the three-file scope; the branch claude/issue-12201-exports-fallback-ranking exists on origin but is empty at old main (ref delete was refused by the write proxy — harmless; the re-dispatch may reuse or replace it).

Generated by Claude Code

Unlock-action fired: PR #12202 merged to main (18c432ed2). Re-dispatching per the recorded adjudication — ranking A (skip SCREAMING_SNAKE, keep source order; ⛔ no Schema-first reordering), acceptance scope = the THREE files the fallback census found (automation/approval.zod.ts, system/translation.zod.ts, kernel/plugin.zod.ts), measured on the post-#12202 main where the hazard rows now exist.

Claim (round 2): skills seat, session session_01RMTpSRF5CjMmQBFfPtPCwJ. Branch: claude/issue-12201-exports-fallback-ranking (reset onto current main; it exists empty on origin).

State: pm:blocked → pm:dispatched.

Generated by Claude Code

fix(spec): keep machine constants off the skill-reference `Exports:` …

{
  "issue": 12201,
  "status": "done",
  "branch": "claude/issue-12201-exports-fallback-ranking",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/12391",
  "premise_still_valid": true,
  "summary": "Premise re-verified on post-#12202 main (BASE=7986d973f): all three hazard rows now EXIST, so round 1's refutation is resolved. Implemented ranking A exactly as adjudicated — SCREAMING_SNAKE exports are dropped from the `Exports:` fallback and source order is kept for the rest; no Schema-first reordering, no module doc blocks authored, fallback not dropped. The rule is extracted to packages/spec/scripts/lib/export-list.ts (the generator runs main() on import, so it cannot be imported by a test — the same reason lib/file-description.ts exists), the cap of five is applied AFTER filtering so authorable names are promoted rather than the row merely shortened, and an all-machine-constant module returns null so the caller prints no description instead of a bare `Exports:`. Regenerated with gen:skill-refs; exactly the three predicted artifact rows changed, and `ApproverType` stays first on the headline row — the property the adjudication turned on. Two things the dispatch assumed that measurement corrected, both stated in the PR body: (1) PR #12202 carried NO test of its own — it inherited coverage by importing the shared selector whose pin is file-description.test.ts, so 'extend the coverage that pinned #12202's selector change' meant reproducing that extract-and-pin PATTERN, which is what was done; (2) the card named two constants on the approval row, but it actually carried FOUR (ORG_MEMBERSHIP_LEVELS and APPROVER_EXPRESSION_ROOTS too) — 7 offenders total across the 3 rows, not 5. Three input-declaration layers had to be repaired because the new corpus gate reads outside its package (see tests). PR #12274 has NOT merged, so the #11705 generated-artifact exemption does not apply; the governed regime was measured, not assumed, and the PR is draft.",
  "tests": "All runs via `bash scripts/pm/os-verify-lock.sh -c '…'`; exit codes captured before any pipe; gate verdicts quoted from each gate's own output. Final commit 74667b86d — the gate union below was run AFTER it.\n\nPOSITIVE CONTROL (pre-fix, unmodified generator + unmodified artifacts): the new corpus gate FIRES — `FAIL scripts/export-list.test.ts > published catalog — no Exports: row names a machine constant / AssertionError: expected [ …(7) ] to deeply equal []`, naming DEPRECATED_APPROVER_TYPES, NON_AUTHORABLE_APPROVER_TYPES, ORG_MEMBERSHIP_LEVELS, APPROVER_EXPRESSION_ROOTS (automation), LEGACY_OBJECT_FIRST_KEYS (i18n), CORE_PLUGIN_TYPES, CONSUMER_INSTALLABLE_TYPES (platform).\n\nAFTER: `pnpm --filter @objectstack/spec test scripts/export-list.test.ts` -> `Test Files 1 passed (1) · Tests 8 passed (8)`. Acceptance scan green: `grep -rn '— Exports:' skills/` = 14 rows, zero SCREAMING_SNAKE.\n\nABLATION (reverse verification), run from the COMMITTED state with `trap '<restore>' EXIT INT TERM`: dropped the MACHINE_CONSTANT test from exportListDescription. NO REBUILD WAS NEEDED OR DONE, and that is a property of the resolution path, not an omission: the test imports './lib/export-list' by RELATIVE specifier inside the same package's scripts/ dir, so vitest resolves the TypeScript source — no package `exports` map, no dist/, nothing between the edit and the reading (contrast the dist-resolved pairs in KNOWN_UNALIASED_TEST_IMPORTS, where the rebuild is mandatory). MUTATION CONFIRMED ON DISK before the reading, anchored on the text being changed rather than on a bare diffstat: guarded-push `grep -c` 1 -> 0 and unguarded-push 0 -> 1, plus `git diff --stat` `1 insertion(+), 1 deletion(-)`. OBSERVED DIRECTION, predicted first and then checked: 4 of the 6 unit cases red (the three about which names survive, PLUS the fall-through case — its `null` exists only because filtering can empty a list; I had predicted three), and the corpus gate stayed GREEN because it reads checked-in artifacts, which only move on regeneration. The test's docblock was corrected to state the observed direction before the commit was amended. RESTORE LEG confirmed byte-identical: `git diff --stat HEAD -- packages/spec/scripts/lib/export-list.ts` empty.\n\nGATES — derived with `node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack` (never a hand list, never a `git diff` fed to it), and RE-DERIVED after the edits: the second derivation added five families once the diff grew `scripts/**` (check:bash32-floor, check:cli-command-ids, check:entry-guard, check:parse-guard, check:pnpm-filter-targets) — all run. Note the dispatch's named set was a clue, not a spec: it predicted check:docs/check:generated, which the derivation does NOT name for these paths, and did not predict the five above.\n  · `pnpm --filter @objectstack/spec run check:skill-refs` -> `✅ 9 generated files in sync with packages/spec`\n  · `pnpm --filter @objectstack/spec typecheck` -> `check:test-typecheck: OK — @objectstack/spec's test layer compiles under packages/spec/tsconfig.test.json`\n  · `pnpm check:cross-package-test-inputs` -> `OK: 18 package(s) read outside themselves, all declared, and turbo.json hashes every declared glob.`\n  · `node scripts/check-ci-filter-parity.mjs` -> exit 0\n  · `node scripts/check-skills-token-ratchet.mjs` -> `✓ check-skills-token-ratchet: 11 published SKILL.md within their ceilings.`\n  · `pnpm check:nul-bytes` -> `✓ check-nul-bytes --self-test: 75 assertions over a temp git repo (real scan() path)` (plus a manual control-char scan of all 7 touched files: no hits)\n  · `pnpm check:doc-authoring` -> `✓ doc authoring guard: 48 published skill files clean — no internal issue-id references.`\n  · `pnpm check:where-matcher` -> `✓ where-matcher conformance holds: 302 matcher(s) discovered, 302 answer the combinator battery correctly or refuse it loudly (189 refuse).`\n  · ~30 more green (full list in the PR body), incl. check:pm-governed-merges, check:skill-frame-sync, check:engine-double-contract, check:type-check-coverage, check:empty-state/liveness/strictness-ledger/variant-docs, docs-audit x2, and check:doc-formula-expressions after building its @objectstack/formula + @objectstack/lint closure.\n\nTHREE GATE-FOUND REPAIRS (not in the dispatch, found by running the derivation rather than the named list): the new corpus gate reads `skills/` from inside @objectstack/spec, so check:cross-package-test-inputs reddened correctly. Repaired by DECLARING the input across all three layers the mechanism has — scripts/cross-package-test-inputs.mjs ('skills/**'), turbo.json ($TURBO_ROOT$/skills/**), and .github/workflows/ci.yml's `crosspkg:` filter (which check-ci-filter-parity then required separately; layer 3 is the scheduler and neither of the other two can see it). Subtree rather than skills/*/references/_index.md because the test reads the DIRECTORY too and a file-only glob does not cover a listing (coversDirectory); the narrower spelling was tried first and rejected by the gate.\n\nTOKEN DELTA — reported as TWO readings because the ratchet cannot see this change: its population is skills/<name>/SKILL.md only, so its bundle line reads 117851/117857 (-6) IDENTICALLY before and after this diff. Whole-tree skills/** measured directly on the same ceil(bytes/4) convention: 745007 -> 744946 bytes, 186252 -> 186237 tokens = -61 bytes / -15 tokens. Filtering SHRINKS the catalog, as expected. (That blind spot is now filed as #12392.)\n\nDECLARED NARROWING — two families not run, both refusing on an unbuilt workspace rather than reporting a finding: `node scripts/check-dev-prereqs.mjs` (exit 1: 67 of 67 workspace packages have no dist/ — the count being ALL packages is what shows it is an environment fact of a fresh worktree, not a consequence of this diff; its remedy is a whole-workspace `pnpm build`, which CI owns), and `pnpm check:type-check-debt` (the convention-triggered ratchet for adding a test file; refuses on an unbuilt closure by its own design, and its throw means NOT MEASURED). The half of that pair which does judge this diff's new test file, check:test-typecheck, ran green above. Repo-wide `pnpm lint` was likewise not run and no claim is made about it — CI owns it.",
  "open_questions": [],
  "out_of_scope_findings": [
    "filed as #12392: the published-skills TOKEN ratchet prices only SKILL.md — references/, rules/, evals/ and contracts/ (38 files, 68,390 tokens, 37% of the shipped bundle) carry no ceiling, so the 'whole-package before/after' expansion budget agents are held to is measured against 63% of what ships; skills/objectstack-data/references/data-hooks.md alone (12,611 tok) is larger than nine of the eleven ratcheted ceilings. Filed as an observation with the counter-arguments (some of it is generator-owned; #9923/#9962 settled the sibling case by documenting the boundary instead of extending coverage), unassigned, no pm:queue."
  ]
}

Extra context for the PM, outside the machine-read block:

Reviewer request refused, not worked around. POST /pulls/12391/requested_reviewers with os-zhuang returned HTTP 422 — "Review cannot be requested from pull request author.", the expected shared-identity refusal.
Merge regime measured, not assumed. PR Carve generator-owned skills/** outputs out of the governed-merge fork #12274 is still OPEN (merged: false), so the [finding] skills/*/references/_index.md is generator-owned (gen:skill-refs) yet sits inside the skills/** governed-merge fence — every spec PR touching an indexed headline is forced to carry a governed-surface file #11705 generated-artifact exemption has not landed. node scripts/pm/check-governed-merges.mjs --test <the 10 files> → EXIT=3, ⛔ GOVERNED — a human merge is the review record for this PR (#9495 regime), hit by skills/** ×3. The PR is draft and stays draft. Worth flagging for whenever Carve generator-owned skills/** outputs out of the governed-merge fork #12274 does land: this PR would remain governed even then, because Carve generator-owned skills/** outputs out of the governed-merge fork #12274's own table puts a diff editing the generator alongside its artifacts under the [finding] The provenance exception's recompute trusts the PR tree's own scripts/docs-audit/** — a PR editing the generator and the workflow artifact together can self-certify; cheap hardening: fail closed on that co-edit #11084 co-edit fence — which is exactly this diff's shape.
The empty round-1 branch was reused, not replaced — it was an ancestor of current main, so the push fast-forwarded with no force.
CI convergence is not awaited, per the standing contract; gate status at hand-off is local-green, CI in_progress.

Generated by Claude Code

ACCEPT — PR #12391 reviewed on its actual diff. Ranking A lands exactly as adjudicated: SCREAMING_SNAKE dropped, source order kept, cap applied AFTER filtering (promotion, not truncation), all-machine module → null (no bare Exports:), and the headline row now reads ApproverType, ApprovalDecision, …Schema… — the property the adjudication turned on, verbatim in the artifact. The rule is extracted to lib/export-list.ts with both taken and not-taken shapes documented at the decision site; positive control fired on all SEVEN offenders (including the two the card under-counted on the approval row); corpus gate + 8 unit pins with a committed-state ablation whose observed direction (4 red, not the predicted 3) was reported and the docblock corrected. The three gate-found input-declaration repairs (cross-package-test-inputs ×3 layers) are the derivation discipline working. Token −15 whole-tree; ratchet blind spot correctly filed as #12392 rather than patched in passing.

Landing under the maintainer's shift-close instruction, 2026-08-25: 「当前任务处理完，合并了就下班。」 — arming auto-merge on the measured-governed draft (co-edit fence case, correctly kept governed even post-#12274).

Generated by Claude Code

record #12201's skills/** root in the parity gate's rollback pin (13 …

Keep machine constants off the skill-reference `Exports:` fallback (o…

Navigation Menu

Repository navigation

[finding] The skill-reference `Exports:` fallback ranks by source order, so DEPRECATED_/NON_AUTHORABLE_/LEGACY_ constants headline customer-facing rows #12201

What

Measured

Why it is worth a card

Options (not pre-judging)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[finding] The skill-reference Exports: fallback ranks by source order, so DEPRECATED_/NON_AUTHORABLE_/LEGACY_ constants headline customer-facing rows #12201

Description

What

Measured

Why it is worth a card

Options (not pre-judging)

Activity

os-zhuang commented on Aug 25, 2026

claude commented on Aug 25, 2026

os-zhuang commented on Aug 25, 2026

os-zhuang commented on Aug 25, 2026

os-zhuang commented on Aug 26, 2026

os-zhuang commented on Aug 26, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

[finding] The skill-reference `Exports:` fallback ranks by source order, so DEPRECATED_/NON_AUTHORABLE_/LEGACY_ constants headline customer-facing rows #12201