Convert barant.com JET 1.4 marketing pages to jetc/.jtc (local, non-production)

Pulls .page files and shared template infrastructure (mainpagetemplate.temp,
menu.bar, barant.tag, opensource.menu, cart.menu, login.menu) read-only from
barant.com via SFTP into jetc/barant-site/src, then convert.py mechanically
flattens them into self-contained .jet files: linkbutton becomes a plain
anchor link (the old SESSIONCTL PAGE/PROCESS form-postback model has no
equivalent here - each page is its own real #api route now, not a shared
single-form state machine), sectionframe is expanded per its barant.tag
definition, /images/* references are fetched and inlined as data URIs
(APIServer has no static-file serving), and session-gated chrome (cart,
account/admin, login.menu) is resolved to its anonymous-visitor default
state, since no session/DB backend is wired into this conversion.

17 pages convert and serve cleanly end-to-end (verified via a local
apiserver-barant-site.json instance on :8081, kept separate from the
existing demo server on :8080 to avoid a /main route collision with the
earlier hand-cloned barant.jet). Two pages deliberately out of scope for
this pass: davidarant.page (whiledir filesystem iteration) and the
per-topic sub-pages of jet.page (dispatches on an ARGS query param this
conversion does not populate - only the default overview state converts).
vst.page/modular1.page/modular1_patches.page also deferred - they pull
live product rows via sql, a real backend dependency beyond "pages and
their template" scope.

Nothing was written back to barant.com - SFTP access was read-only
throughout, per explicit instruction to convert locally without touching
the original site.

jetc/barant-site/src/barantmail.page

@@ -0,0 +1,23 @@
+<page template="mainpagetemplate">
+<title>BARANTMAIL OPEN SOURCE PROJECT</title>
+<contents>
+<sectionframe title="BARANTMAIL OPEN SOURCE PROJECT">
+<p>In the year 2000 I was extremely frustrated with the state of e-amil
+systems available to Linux. Sendmail and q-mail were pretty much the two
+mainstays. sendmail was prohibitively complex for the newly emerging
+Internet method of using e-mail and q-mail was poorly maintained.</p>
+<p>As a result, I embarked on a mission to write my own e-mail system that used
+mysql as it's storage medium. I wanted to keep it simple and support
+multiple users and domains with the simplest of configurations imaginable.
+I also wanted a scalable multi-server capability.</p>
+<p>The result is BARANTMAIL.</p>
+<h2>Features</h2>
+<p>Features of BARANTMAIL are:</p>
+<ul>
+<li>Fully compliant e-mail system.</li>
+<li>Support for multiple domains.</li>
+</ul>
+<p></p>
+</sectionframe>
+</contents>
+</page>