Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/blocks/src/deepnote-file/deepnote-file-schema.ts`:
- Line 396: You added agentBlockSchema to the deepnote schema but did not update
the Deepnote skill docs and generated schema; regenerate the Deepnote skill
schema and add documentation: run the generator command `pnpm --filter
`@deepnote/cli` generate:skill-schema` to regenerate
skills/deepnote/references/schema.ts, then create or update the appropriate
skills/deepnote/references/blocks-*.md file to document the new agentBlockSchema
block (include its fields, usage, and examples) so the .deepnote format and
block docs remain in sync.

In `@packages/mcp/src/tools/writing.ts`:
- Around line 413-417: Replace the inline executable-type check that sets the
candidate variable with a call to the shared helper: import and use
isExecutableBlockType from `@deepnote/blocks/executable-blocks.ts` to evaluate
spec.type (i.e., candidate = isExecutableBlockType(spec.type)); if 'button' and
'big-number' are not covered by isExecutableBlockType keep those special cases
by OR-ing them (e.g., candidate = isExecutableBlockType(spec.type) || spec.type
=== 'button' || spec.type === 'big-number'), and remove the hardcoded array and
startsWith logic to avoid drift.

---

Outside diff comments:
In `@packages/reactivity/src/ast-analyzer.ts`:
- Around line 16-33: AST_ANALYZER_SUPPORTED_CELL_TYPES_LIST includes 'agent'
even though agent blocks only produce comments and cannot yield variable
definitions; remove the 'agent' entry from the
AST_ANALYZER_SUPPORTED_CELL_TYPES_LIST tuple in ast-analyzer.ts and verify any
code that references this list (e.g., functions that iterate over
AST_ANALYZER_SUPPORTED_CELL_TYPES_LIST) still behaves correctly—adjust callers
if they special-case 'agent' or rely on its presence and run relevant tests to
ensure no regressions.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/blocks/src/blocks/executable-blocks.test.ts`:
- Around line 6-35: The test silently allows invalid block types because the
arrays (executableTypes and nonExecutableTypes) are plain strings and the inline
cast on block uses as DeepnoteBlock; change the arrays to be typed with "as
const satisfies readonly DeepnoteBlock['type'][]" so TypeScript will catch typos
(e.g., replace 'divider' with the correct 'separator'), and stop using a broad
"as DeepnoteBlock" on the constructed block—use the strongly-typed array element
to build the block or cast a narrower type to ensure isExecutableBlock and
DeepnoteBlock types are validated at compile time.

In `@packages/cli/src/utils/block-label.test.ts`:
- Around line 116-201: Add a new test case to the agent blocks suite that
verifies getBlockLabel correctly handles prompts with special characters: create
a DeepnoteBlock with content containing quotes, backticks, and Unicode (e.g.,
`He said "hello" — 🧪 \`code\``), then assert getBlockLabel returns the first
non-empty line with those characters preserved and truncated behavior still
applies (if you provide a long special-character string, assert length is 50 and
endsWith('…')). Locate tests near other agent cases and add it alongside
existing getBlockLabel usages.

In `@packages/convert/package.json`:
- Line 3: Update the package.json "version" field from "3.2.1" to "3.3.0" to
reflect the new feature (agent block support); locate the "version" key in the
package.json for the convert package and change its value to 3.3.0, then run
your usual release/packaging checks (e.g., npm/yarn version or CI) to ensure
consistency.

In `@packages/mcp/src/tools/writing.test.ts`:
- Around line 69-87: Replace the plain property-existence checks in the test
with Jest's more idiomatic assertions: when asserting on the created Deepnote
notebook block (variable block retrieved after loadDeepnoteFile), use
expect(block).toHaveProperty('executionCount') and
expect(block).toHaveProperty('outputs') instead of expect('executionCount' in
block).toBe(true) and expect('outputs' in block).toBe(true); keep the rest of
the test (handleWritingTool call and checks for block.type and block.content)
unchanged.

In `@packages/reactivity/src/ast-analyzer.test.ts`:
- Around line 77-91: Replace the benign agent block content in the test for
getBlockDependencies with a code-like, parseable payload (e.g., containing
variable assignments, function defs or import statements) that would produce
dependencies if it were analyzed as code; keep the block type 'agent' and the
existing expectation that only the code block (id '1') defines variable 'a' so
the agent is ignored. Update the mockBlocks variable in ast-analyzer.test.ts
(the agent block with id '2') to use the parseable content and leave the
expect(result).toEqual assertion unchanged to ensure regressions where agent
content is incorrectly parsed are caught.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/blocks/src/python-code.test.ts`:
- Around line 24-98: Add a new exact-output test in the "Agent blocks" describe
for createPythonCode that supplies an agent block whose content contains special
characters (quotes, backticks, and Unicode, and e.g. embedded # or triple
quotes) to ensure the comment renderer doesn't alter formatting; call
createPythonCode with that block and assert the result equals the exact expected
string (including leading "# [agent block] System prompt:\n" and per-line "# "
prefixes or the "(empty system prompt)" form as appropriate) so the test fails
if quoting/backtick/Unicode handling changes.

---

Duplicate comments:
In `@packages/cli/src/utils/block-label.test.ts`:
- Around line 116-201: Add a test case to the agent blocks suite to cover
special characters: create a DeepnoteBlock with type 'agent' whose content's
first non-empty line includes quotes, backticks, and Unicode (e.g., `“Quote”
'single' `backtick` π`) and assert getBlockLabel(block) returns "prompt: " plus
that exact first non-empty line (respecting trimming and truncation rules); this
ensures getBlockLabel correctly extracts and preserves special characters—update
packages/cli/src/utils/block-label.test.ts near the other agent tests and
reference getBlockLabel in the assertion.