Scribe v1.1.1

Scribe v1.1.1

Skill-layer hardening for the markdown table defect on the populate_from_markdown path, plus contributor doc updates. The workspace-mcp pin is unchanged at 1.21.2.

Why

GFM tables in markdown pushed through manage_doc_tab populate_from_markdown flatten to a single paragraph of raw pipe text while the tool reports success. The root cause is in the upstream converter (tables are not enabled in its parser) and a fix is submitted upstream as taylorwilsdon/google_workspace_mcp#929. Until that ships in a PyPI release and the pin bumps, the failure is silent, so the skills now make verification mandatory.

Changes

• docs skill - the Gotchas now carry a mandatory post-populate table verification (detailed inspect_doc_structure, table count matches source, zero pipe-text paragraphs) and the proven repair pass (modify_doc_text wipe plus create_table_with_data per table, bottom-up). Also corrects an inverted claim - import_to_google_doc renders tables natively and always has.
• push skill - new mandatory "Table integrity check" section; a push is not complete until the check passes.
• workspace skill - router hint updated to point at the verification pass.
• CLAUDE.md - contribution pattern rewritten around the standing fork (sync to mirror upstream, feature branch off upstream main, single focused PR); PR #929 recorded in the contribution history.

The skill wording is verification-driven rather than version-driven, so it remains correct after the upstream fix lands - the check simply passes on first inspect. A follow-up release will bump the workspace-mcp pin once the table fix ships upstream, at which point populate_from_markdown renders native Docs tables directly.