@alisio/plugin-thesis 0.1.0

package/typst-packages/preview/merman/0.3.0/LICENSE

@@ -0,0 +1,231 @@
+This package is dual-licensed under either of:
+
+- Apache License, Version 2.0
+- MIT License
+
+Full license texts follow.
+
+MIT License
+
+Copyright (c) 2026 merman contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/typst-packages/preview/merman/0.3.0/README.md

@@ -0,0 +1,388 @@
+# merman
+
+Render Mermaid diagrams in Typst with the `merman` Rust renderer.
+
+`merman` embeds a WebAssembly plugin so Typst documents can render Mermaid diagrams directly during compilation while reusing the parser, layout, and SVG renderer from the broader `merman` project. This README documents the `0.3.0` package and requires Typst `0.15.0` or newer.
+
+## Quick Start
+
+Import `mermaid` and pass a Mermaid source string:
+
+```typst
+#import "@preview/merman:0.3.0": mermaid
+
+#mermaid("
+flowchart TD
+  A[Write Mermaid] --> B[Render with merman]
+  B --> C[Embed SVG in Typst]
+")
+```
+
+## Version Mapping
+
+| Typst package | merman source version | Typst plugin ABI | Notes |
+| --- | --- | --- | --- |
+| `0.3.0` | `0.8.0-alpha.6` | `2` | Size-optimized WASM package; requires Typst `0.15.0` or newer. |
+| `0.2.0` | `0.8.0-alpha.6` | `2` | Requires Typst `0.15.0` or newer. |
+| `0.1.0` | `0.8.0-alpha.1` | `1` | Previous package API. |
+
+The Typst package version tracks the `@preview/merman` wrapper API. The merman source version is the Rust workspace version used to build the package. The Typst plugin ABI tracks the WebAssembly export names and byte payload contracts; wrapper-only API breaks do not require an ABI bump when that plugin surface stays stable. Render option JSON follows shared binding options schema `2`, including `presentation` for first-party profiles and host themes, `layout` for geometry, and `environment` for text measurement and math rendering. This options schema is independent from Typst plugin ABI 2 and native ABI 3.
+
+The API and example sections below describe the `0.3.0` package.
+
+Version `0.3.0` rebuilds the plugin after removing ICU4X collation data and generated font-metric tables from the production WebAssembly closure. Layout still uses the deterministic Unicode-aware measurement provider, and the host text-measurement callback seam remains available to transports that can provide one. The Typst plugin ABI remains `2`; this release changes the packaged implementation closure, not the exported protocol.
+
+## Examples
+
+- [basic.typ](examples/basic.typ): minimal `#mermaid(...)` usage.
+- [document-context.typ](examples/document-context.typ): opt-in document typography and width bridging.
+- [elk.typ](examples/elk.typ): Mermaid's `layout: elk` frontmatter and the bundled ELK backend.
+- [profile.typ](examples/profile.typ): reusable renderer settings shared by direct calls and raw blocks.
+- [figure.typ](examples/figure.typ): Mermaid diagrams wrapped as Typst figures with reusable layout defaults.
+- [raw-block.typ](examples/raw-block.typ): document-wide Mermaid fences with `show-mermaid-blocks`.
+- [options.typ](examples/options.typ): themes, stable IDs, `mermaid-result`, SVG export, and placeholder errors.
+- [print.typ](examples/print.typ): print-friendly white-background output.
+- [presentation.typ](examples/presentation.typ): dark slide-sized output.
+- [svg-export.typ](examples/svg-export.typ): raw SVG and structured render payloads.
+
+Package fixtures are grouped by behavior family under `distribution/typst/merman/tests` in the Merman source repository. They cover API, render environments, context, errors, figures, raw blocks, README examples, historical issues, and visual smoke coverage; test fixtures are not included in the published Typst package.
+
+## ELK Layout
+
+The `0.3.0` publish profile includes Mermaid's ELK layout backend. Select it in Mermaid source with frontmatter:
+
+```typst
+#mermaid("---\nconfig:\n  layout: elk\n---\nflowchart LR\n  Source --> Layout\n  Layout --> SVG\n")
+```
+
+ELK is an embedded, modified Rust translation of Eclipse ELK. The wrapper and Merman-authored code remain under `MIT OR Apache-2.0`; the ELK-derived portion is under `EPL-2.0`. This is a component-level license boundary, not a relicensing of the whole package. When redistributing the package or a derivative artifact, preserve `THIRD_PARTY_NOTICES.md` and the matching files under `THIRD_PARTY_LICENSES/`.
+
+## Document Fonts
+
+`mermaid(...)` is explicit-only by default. It does not automatically inherit the surrounding Typst font, text size, or container width.
+
+Pass `document-context: true` to content-rendering APIs when you want opt-in document context bridging. This forwards the current Typst text font, text size, and available width as renderer options unless you override them directly.
+
+```typst
+#mermaid(source, document-context: true, width: 100%)
+
+#show raw.where(lang: "mermaid"): show-mermaid-blocks(
+  document-context: true,
+  width: 100%,
+)
+```
+
+You can also pass typography intent explicitly:
+
+```typst
+#mermaid(
+  source,
+  typography: (
+    font: ("Source Sans 3", "Arial", "sans-serif"),
+    size: "16px",
+  ),
+)
+```
+
+The typography size accepts CSS `px` strings, absolute Typst lengths, or numeric CSS pixels. Typst lengths are converted through the SVG 96-DPI coordinate system (`72pt == 96px`) so layout measurement and CSS presentation use the same pixel value. Typst font descriptors are projected to their ordered family names; descriptor `covers` constraints have no CSS or deterministic-measurer equivalent and are therefore not preserved.
+
+This changes the SVG style intent sent to the headless renderer. It does not mean the Typst plugin measured the exact Typst font file. The plugin has no synchronous font-measurement host import and therefore advertises and uses only the built-in `deterministic` provider. Browser-style host callbacks and Typst font-asset measurement are not available through this transport.
+
+Check the compiled plugin capability surface with:
+
+```typst
+#let capabilities = merman-capabilities()
+#capabilities.capabilities.text_measurement
+```
+
+## Profiles
+
+Use `mermaid-profile(...)` for reusable diagram settings:
+
+```typst
+#let diagrams = mermaid-profile(
+  typography: (
+    font: ("Source Sans 3", "Arial", "sans-serif"),
+    size: "16px",
+  ),
+  background: "#ffffff",
+  theme-name: "base",
+  figure: (
+    placement: bottom,
+    scope: "parent",
+    caption-position: top,
+    gap: 1em,
+    outlined: false,
+  ),
+)
+
+#mermaid(source, profile: diagrams, width: 100%)
+#mermaid-figure(source, profile: diagrams, caption: [System flow], width: 100%)
+```
+
+Profiles work with `mermaid(...)`, `mermaid-figure(...)`, `mermaid-svg(...)`, `mermaid-result(...)`, `analyze-mermaid(...)`, and raw-block show rules. The optional `figure` section is consumed only by `mermaid-figure(...)`; it does not change raw SVG rendering or non-figure image calls.
+
+For normal documents, start with `width`, `theme-name`, `theme`, `background`, `typography`, `document-context`, and reusable `profile` values. Lower-level renderer fields remain available when you need parity debugging or deterministic fixture control, but they are not the main authoring path.
+
+`base-theme` is a lower-priority compatibility alias for `theme-name`; prefer `theme-name` in new documents. When both are supplied, `theme-name` wins.
+
+Raw `options` always wins. Without it, precedence is field-specific and deterministic:
+
+- site config: profile full object, profile theme shorthands, direct full object, direct theme shorthands;
+- environment: profile full object, profile measurement/math shorthands, direct full object, direct measurement/math shorthands;
+- host theme: document context, profile typography, profile host theme, direct typography, direct host theme;
+- layout: profile layout followed by container shorthands, unless a direct full `layout` object is present, in which case that object replaces the layout shorthands;
+- scalar fields: direct value, profile value, package or renderer default.
+
+Theme shorthands replace the `theme` or `themeVariables` field at their layer; they do not deep-merge individual theme-variable keys.
+
+A direct `site-config` object replaces the profile `site-config` object; use the direct `theme-name` and `theme` shorthands when you want the documented theme-layer precedence instead of replacing the full object.
+
+A profile that contains raw `options` is an opaque binding-options bundle: it bypasses the profile and call-site shorthands. Pass a direct raw `options` dictionary to replace that bundle, or use the structured profile fields when you want field-level overrides.
+
+## Raw Blocks
+
+Use `show-mermaid-blocks` with Typst's `raw.where` selector:
+
+````typst
+#import "@preview/merman:0.3.0": show-mermaid-blocks
+
+#show raw.where(lang: "mermaid"): show-mermaid-blocks(width: 100%)
+
+```mermaid
+flowchart LR
+  Source --> Typst
+  Typst --> SVG
+```
+````
+
+Raw-block show rules default to `error-mode: "placeholder"`, so one invalid fence stays visible as a marked block instead of aborting the whole document. Pass `error-mode: "panic"` when a document-wide rule must fail the compile on the first render error.
+
+Avoid setting a fixed `id` in a document-wide raw-block show rule unless the document has only one Mermaid block; otherwise multiple diagrams will share the same SVG id.
+
+For document-context-aware rendering, pass `document-context: true`. This reads the current Typst text font, text size, and container width inside `context`, then forwards them to the renderer.
+
+```typst
+#import "@preview/merman:0.3.0": show-mermaid-blocks
+
+#show raw.where(lang: "mermaid"): show-mermaid-blocks(
+  document-context: true,
+  width: 100%,
+)
+```
+
+## API Migration
+
+This refactor intentionally removes compatibility-only context wrappers:
+
+```typst
+// Old:
+#mermaid-context(source, width: 100%)
+#show raw.where(lang: "mermaid"): show-mermaid-blocks-context(width: 100%)
+
+// New:
+#mermaid(source, document-context: true, width: 100%)
+#show raw.where(lang: "mermaid"): show-mermaid-blocks(
+  document-context: true,
+  width: 100%,
+)
+```
+
+`context` is a Typst keyword, so the public parameter is named `document-context`.
+
+The current development package also moves measurement and math selection to the binding options schema `2` render environment:
+
+```typst
+#mermaid(source, text-measurement: "deterministic", math-renderer: "none")
+#mermaid(
+  source,
+  environment: (
+    text_measurement: "deterministic",
+    math_renderer: "none",
+  ),
+)
+```
+
+The removed layout fields are rejected; they are not translated through a compatibility path.
+
+## API
+
+### `mermaid(source, ..)`
+
+Renders a Mermaid string or raw block as an SVG image.
+
+Common parameters:
+
+- `width`, `height`, `fit`, `alt`: forwarded to Typst's `image`.
+- `scale`: wraps the rendered image with Typst `scale`; accepts ratios such as `120%` or numbers such as `1.2`.
+- `document-context`: `false` by default. Set to `true` to inherit Typst text font, text size, and finite available width for image rendering. An auto-width page reports an infinite outer width, so Merman keeps its renderer default instead of serializing infinity.
+- `profile`: reusable options produced by `mermaid-profile(...)`.
+- `typography`: high-level font and size intent, merged into the Typst host theme and projected to `presentation.theme`.
+- `presentation-profile`: first-party Merman presentation profile ID, such as `"merman-modern"`. This is independent from Mermaid themes and SVG output policy.
+- `id`: stable SVG root id. `diagram-id` is the lower-level binding name; direct values override profile values, and `diagram-id` overrides `id` at the same call layer.
+- `background`: SVG root background color, mapped to `svg.root_background_color`.
+- `theme-name`: Mermaid theme name, such as `"base"` or `"dark"`.
+- `theme`: Mermaid `themeVariables`.
+- `error-mode`: `"panic"` by default. Use `"placeholder"` or `"text"` to show diagram errors in the document instead of failing the Typst compile. These modes handle structured errors returned by `merman`; missing wasm files, Typst plugin loading failures, invalid `error-mode` values, and SVG image decoding failures still fail the Typst compile.
+
+This entry point is explicit-only unless `document-context: true` is set.
+
+Advanced renderer parameters:
+
+- `pipeline`: `"resvg-safe"` by default for embedded Typst images. Use `"parity"` when you need Mermaid-like SVG DOM output, or `"readable"` for inline SVG inspection.
+- `site-config`: full Mermaid site config object.
+- `host-theme`: lower-level, already-normalized values projected to `presentation.theme`. Use stable semantic role IDs such as `"actor-background"`; this is independent from `theme-name`/`theme`, which configure Mermaid itself.
+- `layout`: full binding layout object for container geometry. This overrides the container shorthands.
+- `container-width`, `container-height`: shorthands for `layout.container_width` and `layout.container_height`.
+- `environment`: full binding render-environment object. Use `text_measurement` and `math_renderer` fields when composing options directly.
+- `text-measurement`, `math-renderer`: shorthands for `environment.text_measurement` and `environment.math_renderer`. Direct values override `environment`, which overrides profile environment values.
+- `scoped-css`, `css-override-policy`, `drop-native-duplicate-fallbacks`: SVG post-processing shorthands.
+  The package keeps `scoped-css` unopinionated by default: Merman resolves fallback typography
+  from the original SVG/XHTML context before removing `foreignObject`, so ClassDiagram labels do
+  not need a hidden global 16px override. If a document deliberately wants a host-specific paint
+  policy, pass an explicit `scoped-css` string. Selectors matching the original SVG/XHTML context
+  can affect fallback measurement; selectors matching the generated
+  `.merman-foreignobject-fallback-text` marker are post-fallback paint hooks and cannot recompute
+  wrapping or placement. CSS injected after fallback can therefore change painted font metrics but
+  must not be treated as a new measurement pass.
+- `fixed-today`, `fixed-local-offset-minutes`: deterministic date controls for date-sensitive diagrams.
+- `options`: escape hatch; when present, it supplies the Rust binding options and overrides shorthand parameters. The plugin reserves the constrained `resources` ceiling; documents may provide stricter limits, while looser profiles or overrides return a structured options error.
+
+Use `typography` for Typst-facing font intent: it accepts Typst font descriptors, absolute Typst lengths, and numeric or string CSS pixels. `host-theme` is the lower-level binding-shaped escape hatch; pass normalized `font_family`, `font_size`, and semantic role values there instead of raw Typst font descriptors or lengths.
+
+### `mermaid-profile(..)`
+
+Returns a reusable Typst settings dictionary. `profile` refers to this wrapper-level bundle, while `presentation-profile` selects a first-party Merman presentation profile. Profiles normalize into the same binding options used by direct parameters, so they do not create a second rendering path.
+
+### `mermaid-figure(source, ..)`
+
+Renders a Mermaid diagram and wraps it in a Typst `figure`.
+
+Use `document-context: true` when the figure should opt into the same document-context bridge as `mermaid(...)`.
+
+Figure layout parameters are forwarded to Typst's native `figure`: `placement`, `scope`, `supplement`, `numbering`, `gap`, and `outlined`. Use `caption-position` and `caption-separator` when you need a top caption or document-specific caption separator. Direct figure parameters override `profile.figure` defaults.
+
+### `mermaid-svg(source, ..)`
+
+Returns the rendered SVG as a string instead of embedding it as an image.
+
+This value-returning API does not enter Typst `context`; pass `typography`, `host-theme`, `layout`, or `container-width` explicitly when exporting SVG text. Rendering failures panic; use `mermaid-result(...)` when the document needs programmatic error handling.
+
+### `mermaid-result(source, ..)`
+
+Returns a structured render payload:
+
+```typst
+#let result = mermaid-result("flowchart TD\nA --> B")
+#if result.ok {
+  result.svg
+} else {
+  result.message
+}
+```
+
+The result also includes `operation`, `kind`, and `capability_id`. On failure, these fields let callers distinguish a missing compiled capability from invalid input or a general render error without parsing `message`.
+Resource-limit failures additionally expose `details.resource` with the stable limit id, profile, and actual/max values.
+
+### `analyze-mermaid(source, ..)`
+
+Returns the canonical analysis schema 1 payload produced by the Rust bindings:
+
+```typst
+#let analysis = analyze-mermaid("flowchart TD\nA --> B")
+#analysis.version
+#analysis.valid
+#analysis.summary.errors
+#analysis.diagnostics
+```
+
+Invalid Mermaid source remains a schema-1 analysis payload with `valid: false`; transport, options, and missing-capability failures use the structured operation envelope instead.
+
+### `merman-capabilities()`
+
+Returns the compiled plugin capability payload, including the current text measurement boundary:
+
+```typst
+#let capabilities = merman-capabilities()
+#capabilities.capabilities.text_measurement.provider_ids
+```
+
+The flat catalog reports the artifact's current capability, output, operation, registry, and resource sets. The plugin independently applies a fixed constrained resource ceiling to every render and analysis operation. Raw binding options may tighten individual resource limits but cannot loosen or silently replace that transport-owned policy. The options root and any `analysis` or `merman` wrapper must be JSON objects; malformed wrapper values return a structured options error before rendering or analysis begins.
+
+### `show-mermaid-blocks(..)`
+
+Returns a raw block show handler. This is the shortest way to enable Mermaid fences across a Typst document:
+
+```typst
+#show raw.where(lang: "mermaid"): show-mermaid-blocks(width: 100%)
+```
+
+## Development
+
+The Typst package uses its own version track and is not locked to the Rust crate version. The embedded WebAssembly plugin also has a separate ABI version, documented in the Version Mapping table, for exported function and payload compatibility.
+
+Build the publish Typst package locally:
+
+```sh
+cargo run --locked -p xtask -- build-typst-package --profile publish
+```
+
+The release build requires `wasm-tools` and Binaryen `wasm-opt version 131`. The package builder applies a pinned `wasm-opt -Oz` pass before stripping custom sections and records both tool versions in the artifact manifest.
+
+The package is written to:
+
+```sh
+dist/typst/merman/0.3.0
+```
+
+The source package carries the examples shown above so they remain readable in the package review. `typst.toml` excludes `examples/**` from the runtime download; tests stay in the Merman source repository and are not bundled.
+
+For a manual local install, copy that directory to `<package-root>/preview/merman/0.3.0` and pass the parent directory to Typst:
+
+```text
+<package-root>/preview/merman/0.3.0/typst.toml
+<package-root>/preview/merman/0.3.0/lib.typ
+<package-root>/preview/merman/0.3.0/merman_typst_plugin.wasm
+```
+
+```sh
+typst compile --package-path <package-root> document.typ
+```
+
+The `typst-package-smoke` command creates this preview layout automatically in a temporary directory.
+
+For local `@preview` smoke tests, copy the built package under a preview namespace package path and compile with `--package-path`:
+
+```sh
+cargo run --locked -p xtask -- typst-package-smoke --profile publish --skip-wasm-build
+```
+
+Use an explicit Typst binary when the CLI is downloaded outside `PATH`:
+
+```sh
+cargo run --locked -p xtask -- typst-package-smoke --profile publish --skip-wasm-build --typst /path/to/typst
+```
+
+Each smoke run owns an independent temporary directory under `target/typst-package-smoke/`. Positive fixtures preserve their nested output paths, and `tests/compile-fail/` fixtures must fail with the diagnostic declared by their adjacent `.error.txt` file. Successful runs remove their artifacts by default; pass `--keep-artifacts` to retain the run directory for inspection.
+
+The build verifies artifact-recipe provenance from its private build directory, then stages only the
+runtime wrapper, WASM, examples, and legal materials. The transaction snapshots source bytes,
+verifies the complete file shape and contents, and rechecks live source identity immediately before
+atomically replacing the version directory; build receipts are not included in the published package.
+
+The sole package profile, `publish`, enables SVG rendering, analysis, the complete Mermaid language catalog, and the Cytoscape and ELK layout backends. There are no alternate bridge-only or SVG-only package profiles. ASCII, PNG, JPEG, and PDF are not compiled because this wrapper exposes no operation for those outputs. Maintainer experiments use direct Cargo features and do not create another package identity or release recipe.
+
+## Current Limits
+
+- Output is SVG embedded through Typst `image`; diagrams are not Typst-native vector elements.
+- Font family and size can be forwarded as style intent, but exact Typst font glyph measurement is not automatic.
+- RaTeX math rendering is not available in the Typst plugin. Its current upstream closure depends on browser system-font discovery; the capability will remain closed until a zero-browser-import implementation passes admission.
+- Browser-only Mermaid interactions such as script callbacks and popup behavior are not expected to work in static Typst output.
+- The package is smoke-tested with Typst 0.15.0. Typst 0.15 HTML export remains experimental and is not a package promise here.
+- The `readable` and `parity` pipelines can embed SVG structures that Typst warns about; `resvg-safe` is the intended embedded-image path for package output.
+
+## License
+
+The wrapper and Merman-authored code are available under either MIT or Apache-2.0. The embedded ELK-derived implementation is a separate component under EPL-2.0; it does not relicense the rest of the package. `THIRD_PARTY_NOTICES.md` records the exact source revision, relationship, and scope for ELK and the other embedded or translated components, while `THIRD_PARTY_LICENSES/` contains their applicable legal files. Preserve these materials when redistributing the package or a derivative artifact.
+
+The machine-readable Cargo dependency report remains in the source repository's release evidence instead of being duplicated in the downloaded Typst package.

package/typst-packages/preview/merman/0.3.0/THIRD_PARTY_LICENSES/cose-base-v1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 - present, iVis@Bilkent.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/typst-packages/preview/merman/0.3.0/THIRD_PARTY_LICENSES/cose-base-v2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 - present, iVis@Bilkent.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.