fix(spec): check:skill-examples refuses instead of degrading when a marked example does not parse (#12308)

* fix(spec): refuse instead of degrading when a marked example does not parse

check:skill-examples derives each block's build-file extension from its fence
language, so a marked block whose body is JSX under a ```ts / ```typescript
fence lands in a .ts file where JSX is a syntax error. TypeScript reports
syntactic diagnostics and then stops, so the semantic pass never runs -- for any
file in the program. The run did go red (measured), but in the vocabulary of a
semantic result, over a surface whose semantic pass had not run, and nothing in
the output said so.

Two guards separate those states. Marked blocks that do not parse now produce a
REFUSE verdict naming the surface and the number of blocks left unchecked, with
a tsx-retag prescription when the body really is JSX; the unmarked
JSX-under-a-ts-fence population is swept before anyone arms it. The green line
is printed only when every surface reached tsc, and says so.

Sweep repairs: five unmarked JSX blocks fenced ```typescript across
content/docs/** retagged ```tsx. skills/** carries none.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NDGG54XF5gbTLdQzCtnaVV

* refactor(spec): give REFUSE its own verdict token, distinct from a failed check

`✗ ⛔ REFUSE` stacked two prefixes and read as one emphatic failure rather than
as a different KIND of failure. A refusal ("this gate produced no result") and a
failure ("this gate produced a result and it is bad") now print two tokens a
reader can tell apart and grep for. Same exit code: a refusal is still red.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NDGG54XF5gbTLdQzCtnaVV

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: os-litant

content/docs/api/error-handling-client.mdx

@@ -130,7 +130,7 @@ async function parseApiError(response: Response): Promise<ObjectStackError> {
 
 Map field-level errors from the API response directly to form fields:
 
-```typescript
+```tsx
 import { useState } from 'react';
 
 interface FormErrors {
@@ -302,7 +302,7 @@ function sleep(ms: number): Promise<void> {
 
 Catch unexpected errors at the component tree level:
 
-```typescript
+```tsx
 import { Component, type ReactNode } from 'react';
 
 interface ErrorBoundaryState {

content/docs/protocol/objectui/concept.mdx

@@ -345,7 +345,7 @@ Authorization: Bearer <token>
 ```
 
 **Renderer Logic (Simplified):**
-```typescript
+```tsx
 function FormRenderer({ layout }) {
   return (
     <Form title={layout.title}>
@@ -644,7 +644,7 @@ A conformant ObjectUI renderer must:
 
 Renderers maintain a mapping from JSON types to components:
 
-```typescript
+```tsx
 const componentRegistry = {
   text: TextFieldComponent,
   email: EmailFieldComponent,

content/docs/protocol/objectui/index.mdx

@@ -315,7 +315,7 @@ Dashboard.create({
 
 ### 1. Declarative Over Imperative
 
-```typescript
+```tsx
 // ❌ Imperative (React)
 function TaskList() {
   const [tasks, setTasks] = useState([]);