anigram-mcp 0.1.0 → 0.2.0

package/README.md

@@ -10,18 +10,28 @@ draw them.
 
 ## Tools
 
-| Tool             | What it does                                                                                         |
-| ---------------- | ---------------------------------------------------------------------------------------------------- |
-| `anigram_guide`  | The scene format, every part that has a drawing, the signal functions. Read first.                   |
-| `list_scenes`    | The built-in sheets.                                                                                 |
-| `get_scene`      | A built-in sheet as JSON — the best example to copy.                                                 |
-| `validate_scene` | Errors (won't load) and warnings (will run, probably not what you meant).                            |
-| `write_scene`    | Validate and save a `.json` scene file.                                                              |
-| `edit_scene`     | Add, move, update or remove parts and links in place.                                                |
-| `check_scene`    | Is it done? Validate, run the day, and check every line of the scene's `expect` list.                |
-| `simulate_scene` | Run a day headless: an hour-by-hour table, every alert, unmet demand. Knobs and switches can be set. |
-| `render_scene`   | The sheet at any hour, every flow labelled: a PNG the assistant can look at (default) or an SVG.     |
-| `share_link`     | A URL that opens the scene live in the browser. The scene travels in the link; nothing is uploaded.  |
+| Tool             | What it does                                                                                                                                                                                                                               |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `anigram_guide`  | The scene format, every part that has a drawing, the signal functions. Read first.                                                                                                                                                         |
+| `list_scenes`    | The built-in sheets.                                                                                                                                                                                                                       |
+| `get_scene`      | A built-in sheet as JSON — the best example to copy.                                                                                                                                                                                       |
+| `new_scene`      | A working starter for a practice (pictorial, P&ID, single-line, PFD) and that practice's house rules. Optionally saves it.                                                                                                                 |
+| `validate_scene` | Errors (won't load) and warnings (will run, probably not what you meant).                                                                                                                                                                  |
+| `write_scene`    | Validate and save a `.json` scene file.                                                                                                                                                                                                    |
+| `edit_scene`     | Add, move, update or remove parts and links in place.                                                                                                                                                                                      |
+| `check_scene`    | Is it done? Validate, run the day, and check every line of the scene's `expect` list.                                                                                                                                                      |
+| `check_drawing`  | For a P&ID, single-line or PFD: what an engineer would mark up (tags in the practice's scheme, numbered lines, closed control loops, protected feeders, a filled title block), each with its fix. Advisory; `strict` fails on any finding. |
+| `lint_layout`    | Does the sheet read cleanly? Crossing or overlapping lines, a line through a part, slanted runs, labels on top of things or off the sheet.                                                                                                 |
+| `auto_layout`    | Lay the sheet out by its flow: single-lines top to bottom, everything else left to right, instruments above what they serve. Rewrites only the geometry.                                                                                   |
+| `export_dexpi`   | A P&ID as DEXPI 1.3 Proteus XML: equipment and nozzles, numbered lines with their valves, off-page connectors, instrument loops.                                                                                                           |
+| `simulate_scene` | Run a day headless: an hour-by-hour table, every alert, unmet demand. Knobs and switches can be set.                                                                                                                                       |
+| `render_scene`   | The sheet at any hour, every flow labelled: a PNG the assistant can look at (default), an SVG, or a one-page PDF on A4–A1 paper.                                                                                                           |
+| `share_link`     | A URL that opens the scene live in the browser, or in the editor with `view: "editor"`. The scene travels in the link; nothing is uploaded.                                                                                                |
+
+Prompts `draw-pid`, `draw-single-line`, `draw-pfd` and `draw-sheet` take a
+one-line brief and hand the assistant the practice's conventions and the way
+to work: start from `new_scene`, keep `check_scene` and `check_drawing` green,
+look at the render.
 
 Every tool except `anigram_guide` declares an output schema and returns its
 result as structured content too, so a client can read fields instead of

package/dist/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Vaibhav Patel
+
+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/dist/OFL.txt

@@ -0,0 +1,92 @@
+Copyright (c) 2016 The Inter Project Authors (https://github.com/rsms/inter)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+http://scripts.sil.org/OFL
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION AND CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.