Release v0.1.8

.gitignore

@@ -0,0 +1,348 @@
+# ---> Node
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+.pnpm-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional stylelint cache
+.stylelintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variable files
+.env
+.env.development.local
+.env.test.local
+.env.production.local
+.env.local
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# Next.js build output
+.next
+out
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# vuepress v2.x temp and cache directory
+.temp
+.cache
+
+# vitepress build output
+**/.vitepress/dist
+
+# vitepress cache directory
+**/.vitepress/cache
+
+# Docusaurus cache and generated files
+.docusaurus
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+# yarn v2
+.yarn/cache
+.yarn/unplugged
+.yarn/build-state.yml
+.yarn/install-state.gz
+.pnp.*
+
+# Local WebUI test/build scratch directories
+.component-test-build/
+.module-test-build/
+.policy-test-build/
+.template-preview-test-build/
+.import-test-build/
+webui/.component-test-build/
+webui/.module-test-build/
+webui/.policy-test-build/
+webui/.template-preview-test-build/
+webui/.import-test-build/
+
+# ---> Python
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# ---> VisualStudioCode
+.vscode/*
+!.vscode/settings.json
+!.vscode/tasks.json
+!.vscode/launch.json
+!.vscode/extensions.json
+!.vscode/*.code-snippets
+
+# Local History for Visual Studio Code
+.history/
+
+# Built Visual Studio Code Extensions
+*.vsix
+
+*.db
+
+# GovOPlaN local runtime state
+runtime/
+
+# GovOPlaN WebUI test output
+webui/.module-test-build/
+webui/.component-test-build/

README.md

@@ -0,0 +1,16 @@
+# GovOPlaN Templates
+
+<!-- govoplan-repository-type:start -->
+**Repository type:** module (domain).
+<!-- govoplan-repository-type:end -->
+
+`govoplan-templates` owns reusable renderable template definitions and render
+contracts for GovOPlaN. It is intentionally separate from reporting, DMS/files,
+mail delivery, forms runtime, and workflow state.
+
+This repository is currently a tag-only scaffold. It should gain package
+metadata and module manifests only after the first backend or WebUI slice is
+designed.
+
+See [docs/TEMPLATE_BOUNDARY.md](docs/TEMPLATE_BOUNDARY.md) for the boundary
+decision.

docs/TEMPLATE_BOUNDARY.md

@@ -0,0 +1,113 @@
+# Template Module Boundary
+
+`govoplan-templates` owns reusable renderable templates, not the data selection
+or persistence semantics around the generated output.
+
+The core boundary decision register is in
+`/mnt/DATA/git/govoplan-core/docs/MODULE_ARCHITECTURE.md`.
+
+## Ownership
+
+Templates owns:
+
+- template definitions for letters, decisions, permits, emails, forms, reports,
+  certificates, notices, and workflow messages
+- template versions, draft/published lifecycle, localization, and merge-field
+  declarations
+- render profiles such as output format, page/layout hints, fallback language,
+  and safe preview mode
+- render-context schema declarations so callers know which fields are required
+- reusable template fragments inside configuration packages
+- rendering capability contracts exposed to mail, campaign, reporting, forms,
+  workflow, cases, DMS, and files
+
+## Boundaries
+
+Templates does not own:
+
+- report data selection, aggregation, dashboards, scheduled exports, or BI
+  semantics; those belong to `govoplan-reporting`
+- document lifecycle, collaborative editing, locks, approvals, legal hold, or
+  records management; those belong to `govoplan-dms` and `govoplan-records`
+- file/blob storage and file permissions; those belong to `govoplan-files`
+- mail sending, mailbox behavior, and mail profile policy; those belong to
+  `govoplan-mail`
+- form submissions, drafts, receipts, and public submission state; those belong
+  to `govoplan-forms-runtime` when implemented
+- workflow transitions, tasks, and case lifecycle
+
+## Initial Template Types
+
+- `letter`
+- `decision_document`
+- `permit`
+- `email`
+- `form`
+- `report`
+- `certificate`
+- `notice`
+- `workflow_message`
+
+Template types can share a render engine but should keep type-specific metadata
+explicit, especially when retention, signature, accessibility, or delivery
+rules differ.
+
+## Render Context Contract
+
+Candidate render request:
+
+```json
+{
+  "template_id": "permit-decision",
+  "template_version_id": "v1",
+  "template_type": "permit",
+  "locale": "de-DE",
+  "output_format": "pdf",
+  "context": {
+    "case_id": "case-1",
+    "recipient": {"display_name": "Example Person"},
+    "decision": {"approved": true}
+  },
+  "trace": {"correlation_id": "request-1"}
+}
+```
+
+Candidate render response:
+
+```json
+{
+  "render_id": "render-1",
+  "template_id": "permit-decision",
+  "template_version_id": "v1",
+  "output_format": "pdf",
+  "artifact": {
+    "content_type": "application/pdf",
+    "storage_ref": "files://generated/render-1.pdf",
+    "checksum": "sha256:..."
+  },
+  "warnings": []
+}
+```
+
+Generated artifact storage can be delegated to files/DMS through capabilities.
+Templates should not import those modules directly.
+
+## Candidate Capabilities
+
+- `templates.catalog`
+- `templates.renderer`
+- `templates.preview`
+- `templates.schema`
+- `templates.packageFragments`
+
+Consumers should request these through core-mediated capability lookup. The
+template module should not import consumer modules.
+
+## First Implementation Slice
+
+1. Define manifest metadata, permissions, and capability names.
+2. Add template definition/version DTOs.
+3. Add render-context schema validation for one safe text/PDF preview path.
+4. Add package fragment format for reusable templates.
+5. Add tests that mail/campaign/reporting/forms can detect template capability
+   presence without importing template internals.