API 1.7.0
Troubleshooting
| Symptom | Next step |
|---|---|
| npm cannot find SDK/CLI | They are unpublished; install the supplied local release tarballs. |
| Missing .tabs-extension | Run npm run build before validation/loading. |
| Invalid publisher/name | Use 2–63 lowercase letters/numbers/hyphens, beginning with a letter. |
| Unsupported engines.api or Tabs version | Check target version and SDK compatibility; never bypass validation. |
| Capability denied | Review the current project's grants and profile assignment in Settings. |
| No host bridge in a browser preview | The bridge exists only in a real active desktop extension view. |
| 401 from private registry | Reconnect with a current read token and confirm the GitHub allowlist. |
| CLI publishing denied | Check publish-token scope, namespace membership, and whether submissions are enabled. |
| Duplicate version | Increase semantic version; existing archive bytes are immutable. |
| Approved but absent from Explore | Operator must publish current signed target metadata. |
| Signed metadata expired/invalid | Operator must repair signing/freshness; this is not offline permission to bypass trust. |
| Rejected package | Inspect scan/reviewer reasons, correct the package, publish a new version, or use the appeal flow. |
When reporting a bug include CLI/SDK/Tabs versions, safe reproduction steps, and the non-secret digest. Never attach tokens, credentials, private packages, or workspace data without permission.