Squashed 'vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/' content from commit 7454bad

git-subtree-dir: vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline git-subtree-split: 7454badfb02566a9d74a8a70c687daa4a8488850
2024-12-10 17:11:26 -06:00 · 2024-12-10 17:11:26 -06:00 · 0fc507c735
commit 0fc507c735
109 changed files with 6259 additions and 0 deletions
--- a/.gitignore
+++ b/.gitignore
@ -0,0 +1,9 @@
 build-output/client-submission/*.md
 build-output/client-submission/*.pdf
 build-output/client-submission/*.doc
 build-output/CandidateInfoSheet*
 build-output/job-board/*.md
 build-output/job-board/*.pdf
 build-output/job-board/*.doc
 build-temp/*.yml
 build-temp/*.md
--- a/235
+++ b/235
@ -0,0 +1,235 @@
 GNU AFFERO GENERAL PUBLIC LICENSE
 Version 3, 19 November 2007
 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
                            Preamble
 The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
 The licenses for most software and other practical works are designed to take away your freedom to share and change the works.  By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
 When we speak of free software, we are referring to freedom, not price.  Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
 Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
 A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate.  Many developers of free software are heartened and encouraged by the resulting cooperation.  However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
 The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community.  It requires the operator of a network server to provide the source code of the modified version running there to the users of that server.  Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
 An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals.  This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
 The precise terms and conditions for copying, distribution and modification follow.
                       TERMS AND CONDITIONS
 0. Definitions.
 "This License" refers to version 3 of the GNU Affero General Public License.
 "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
 "The Program" refers to any copyrightable work licensed under this License.  Each licensee is addressed as "you".  "Licensees" and "recipients" may be individuals or organizations.
 To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy.  The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
 A "covered work" means either the unmodified Program or a work based on the Program.
 To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy.  Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
 To "convey" a work means any kind of propagation that enables other parties to make or receive copies.  Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
 An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License.  If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
 1. Source Code.
 The "source code" for a work means the preferred form of the work for making modifications to it.  "Object code" means any non-source form of a work.
 A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
 The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form.  A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
 The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.  However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work.  For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those
 subprograms and other parts of the work.
 The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
 The Corresponding Source for a work in source code form is that same work.
 2. Basic Permissions.
 All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met.  This License explicitly affirms your unlimited permission to run the unmodified Program.  The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work.  This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
 You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.  You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright.  Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
 Conveying under any other circumstances is permitted solely under the conditions stated below.  Sublicensing is not allowed; section 10 makes it unnecessary.
 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
 No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
 When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
 4. Conveying Verbatim Copies.
 You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
 You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
 5. Conveying Modified Source Versions.
 You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
    a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
    b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7.  This requirement modifies the requirement in section 4 to "keep intact all notices".
    c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy.  This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.  This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
    d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
 A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit.  Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
 6. Conveying Non-Source Forms.
 You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
    a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
    c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source.  This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
    d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge.  You need not require recipients to copy the Corresponding Source along with the object code.  If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source.  Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
    e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
 A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
 A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.  In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage.  For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product.  A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
 "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source.  The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
 If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information.  But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
 The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed.  Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
 Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
 7. Additional Terms.
 "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law.  If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
 When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it.  (Additional permissions may be written to require their own removal in certain cases when you modify the work.)  You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
 Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
    a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
    b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
    c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
    d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
    e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
    f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
 All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10.  If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.  If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
 If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
 Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
 8. Termination.
 You may not propagate or modify a covered work except as expressly provided under this License.  Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
 However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
 Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
 Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License.  If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
 9. Acceptance Not Required for Having Copies.
 You are not required to accept this License in order to receive or run a copy of the Program.  Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance.  However, nothing other than this License grants you permission to propagate or modify any covered work.  These actions infringe copyright if you do not accept this License.  Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
 10. Automatic Licensing of Downstream Recipients.
 Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.  You are not responsible for enforcing compliance by third parties with this License.
 An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations.  If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
 You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.  For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
 11. Patents.
 A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based.  The work thus licensed is called the contributor's "contributor version".
 A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version.  For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
 Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
 In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement).  To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
 If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent
 license to downstream recipients.  "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
 If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
 A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License.  You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
 Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
 12. No Surrender of Others' Freedom.
 If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.  If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
 not convey it at all.  For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
 13. Remote Network Interaction; Use with the GNU General Public License.
 Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software.  This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
 Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work.  The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
 14. Revised Versions of this License.
 The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time.  Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
 Each version is given a distinguishing version number.  If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation.  If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
 If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
 Later license versions may give you additional or different permissions.  However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
 15. Disclaimer of Warranty.
 THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
 16. Limitation of Liability.
 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
 17. Interpretation of Sections 15 and 16.
 If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
 END OF TERMS AND CONDITIONS
            How to Apply These Terms to Your New Programs
 If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
 To do so, attach the following notices to the program.  It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
     MarkdownResume-Pipeline
     Copyright (C) 2024  reachableceo
     This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero General Public License for more details.
     You should have received a copy of the GNU Affero General Public License along with this program.  If not, see <http://www.gnu.org/licenses/>.
 Also add information on how to contact you by electronic and paper mail.
 If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source.  For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code.  There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.
 You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.
--- a/README.md
+++ b/README.md
@ -0,0 +1,53 @@
 # MarkdownResume-Pipeline
 - [MarkdownResume-Pipeline](#markdownresume-pipeline)
  - [Introduction](#introduction)
  - [Directory Overview](#directory-overview)
  - [Build pipeline](#build-pipeline)
    - [Outputs](#outputs)
  - [Production Use](#production-use)
 ## Introduction
 Resume formatting/publication/management is difficult, tedious, annoying etc. The @ReachableCEO has hacked the process and made it easy! This repository is the core build scripts, templates etc used for resume management. It's meant as one half of a complete solution.
 Please see [MarkdownResum-Pipeline-ClientExample repository](https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline-ClientExample) for the other half. You would clone that repository and follow the instructions. That repository has this repository vendored into it.
 ## Directory Overview
 - build: build script and associated support files.
 - build-output: markdown file for pandoc gets placed here. If you want to make formatting changes before conversion to PDF/Word, you can do so.
 - build-temp: working directory for the build process. In case you need to debug an intermediate step.
 - Templates
  - CandidateInfoSheet: contains the markdown/yaml template files for a candidate information sheet. This allows you to produce a standardized reply to recruiters to eliminate an average of 6 emails/phone calls per inbound lead. It has a rate sheet and all the standard "matrix" tables they need to fill out for submission to an end client (or, in reality, to the US based recruiting team who interfaces with the client).
  - ContactInfo: contact info (one version for the recruiter facing resume, one version for client facing).
  - JobHistoryDetails: details for each position listed in WorkHistory/WorkHistory.csv.
  - SkillsAndProjects: This contains what the name says. Holds a skills.csv file that gets turned into a skills table and a projects file that gets placed at beginning of resume as a career highlights section.
  - WorkHistory: contains the WorkHistory.csv file used by the build script to generate Employment History section.
 ## Build pipeline
 In the build directory:
 - build-demo.sh - End to end self contained build example for testing the repository after changes to templates.
 - build-pipeline-server.sh - Used by client repository to builds three assets:
  - PDF/Word for submitting to job portals
  - PDF/Word for submitting to end clients (strips cover sheet/contact info)
  - PDF of the candidate information sheet.
 - BuildTemplate-* : Templatized YAML metadata files that get rendered during the build process to be used by Pandoc.
 - resume-docx-reference.docx: Template "style" file for Word output.
 ### Outputs
 - Word format output is a best effort . The style file was sourced from : <https://sdsawtelle.github.io/blog/output/simple-markdown-resume-with-pandoc-and-wkhtmltopdf.html> (vendored in vendor/git.knownelement.com/ExternalVendorCode/markdown-resume just in case)
 - PDF output considered production. Please see: <https://github.com/Wandmalfarbe/pandoc-latex-template> (vendored in vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template ) and <https://github.com/ReachableCEO/rcdoc-pipeline> if you want to re-create/modify the build pipeline for your own markdown project.
 ## Production Use
 This system is in production use by the @ReachableCEO:
 - [MarkdownResume-ClientExample-ReachableCEO](https://git.knownelement.com/reachableceo/MarkdownResume-ReachableCEO)
 - [ReachableCEO Career Site](https://resume.reachableceo.com)
 - uploaded to all major job portals
 This was a labor of love by the @ReachableCEO in the hopes others can massively optimize the job hunt process.
--- a/Templates/CandidateInfoSheet/CandidateInfoSheet.md
+++ b/Templates/CandidateInfoSheet/CandidateInfoSheet.md
@ -0,0 +1,121 @@
 # {{CandidateName}} Candidate Information Sheet
 ## Introduction
 Hello,
 I apologize for the form letter response.
 I receive a high volume of recruiter emails every day and I've found this letter to be the most efficient way to
 handle the high volume of emails and reduce back and forth emails/texts/calls.
 If you have any questions/comments/concerns not covered by this document, please let me know via e-mail and I'm happy to address them!
 If you ask me something answered in this document, I will not respond and will not move forward with the opportunity, so please read it in detail!
 ## Re: share my ID over email
 I WILL NOT share my (full or redacted) photo ID over email or any other electronic written  
 communication. If that is "required" then I have no interest in moving forward with this opportunity.
 I am happy to get on a teams/zoom/google meet etc call and show my ID.
 ## Re: professional references
 I am happy to provide professional references once an interview with the end client/customer/hiring manager/team has been scheduled. I will NOT provide references up front. If that is "required" then I have no interest in moving forward with this opportunity.
 ## Re: relocation
 if the role is not based in **{{CandidateLocation}}** or **Other Location** I will need to re-locate
 | Question                                  | Answer |
 |-------------------------------------------|--------|
 | Am I open to relocation?                  | Yes    |
 | Am I willing to re-locate at own expense? | No     |
 | Am I open to up to 100% travel            | Yes    |
 Please be aware that:
 - I will **only re-locate at the employer expense**.
 - I will need **two weeks of time** to re-locate.
 - The net amount of the re-location benefit **MUST be at least {{CandidateRelocationNetMinimumAmount}}** to fully compensate me for the time/effort to re-locate.
 - The full re-location benefit **must be provided prior to the confirmed start date**.
 - I **will NOT** accept a reimbursement based re-location package.
 - I am happy to come onsite (at client expense (paid up front)) for training/orientation etc.
 \pagebreak
 ## Rate Schedule (compensation expectations)
 ### Fully remote roles
 I have a **very strong** preference for fully remote roles.
 I am open to (at the absolute bottom of my range):
 - **{{CandidateRateSheetRemoteW2HourlyMinimum}}** per hour(w2)
 - **{{CandidateRateSheetRemoteW2AnnualMinimum}}** annually
 - **{{CandidateRateSheetRemote1099HourlyMinimum}}** per hour (1099/corp to corp)
 I have a strong preference for roles that are :
 - **{{CandidateRateSheetRemoteW2HourlyPrefer}}** per hour(w2) or more
 - **{{CandidateRateSheetRemoteW2AnnualPrefer}}** annually or more
 - **{{CandidateRateSheetRemote1099HourlyPrefer}}** per hour (1099/corp to corp) or more
 ### On-site/hybrid roles
 - **{{CandidateRateSheetRemoteW2HourlyPrefer}}** per hour(w2) or more
 - **{{CandidateRateSheetRemoteW2AnnualPrefer}}** annually or more
 - **{{CandidateRateSheetRemote1099HourlyPrefer}}** per hour (1099/corp to corp) or more
 In regards to compensation type, I am open to:
 - w2
 - corp to corp (I have my own LLC)
 - 1099  
 If you have a rate for any of the compensation options above, send them all. I will pick which one works best for my situation and the opportunity.
 If it's a different rate with/without benefits, send both.
 If the above is in alignment with this opportunity, please feel free to send me an RTR with the best rate you can offer.
 \pagebreak
 ## Details needed for submission
 ### My resume
 [Download Candidate resume(format)](https://some.resume.somewhere/some-Resume.pdf)
 I am happy to discuss and make edits to the resume content specific to the opportunity if you feel they are needed.
 ### Candidate details  
 Here are my complete candidate details for submission to the role.
 | Question                              | Answer                              |
 |---------------------------------------|-------------------------------------|
 | Full name                             | {{CandidateName}}                   |
 | E-mail address                        | {{CandiateEmail}}                   |
 | Phone number                          | {{CandidatePhone}}                  |
 | Preferred form of contact             | {{CandidatePreferredContactMethod}} |
 | Work authorization                    | {{CandidateWorkAuthorization}}      |
 | Are you employed presently?           | {{CandidateEmploymentStatus}}       |
 | Current location                      | {{CandidateCurrentLocation}}        |
 | Current timezone                      | {{CandidateCurrentTimezone}}        |
 | Timezones I can work in               | {{CandidateWorkableTimezones}}      |
 | Availability to interview             | {{CandidateInterviewAvailability}}  |
 | Availability to start                 | {{CandidateStartAvailability}}      |
 | Highest Education                     | {{CandidateHighestEducation}}       |
 | Graduated Year                        | {{CandidateGraduationYear}}         |
 | Name of school                        | {{CandidateSchoolName}}             |
 | Location of school                    | {{CandidateSchoolLocation}}         |
 | Linkedin Profile                      | ({{CandidateLinkedin}})             |
 | Github Profile                        | ({{CandidateGithub}})               |
 | Last project                          | {{CandidateLastProject}}            |
 | DOB                                   | {{CandidateDOB}}                    |
 | Total IT/career experience            | {{CandidateTotalExperience}}        |
 | Open to in-office/hybrid/remote       | Yes                                 |
 | Any trips planned in next six months? | No                                  |
--- a/Templates/ContactInfo/ContactInfo-ClientSubmit.md
+++ b/Templates/ContactInfo/ContactInfo-ClientSubmit.md
@ -0,0 +1,4 @@
 {{CandidateName}}
 =====
 {{CandidateOneLinerSummary}}
--- a/Templates/ContactInfo/ContactInfo-JobBoard.md
+++ b/Templates/ContactInfo/ContactInfo-JobBoard.md
@ -0,0 +1,6 @@
 {{CandidateName}}
 =====
 {{CandidateOneLinerSummary}}
 [ [Github Profile]({{CandidateGithub}}) ] .  [ [Linkedin Profile]({{CandidateLinkedin}}) ] . [ {{CandidateEmail}} ] . [ {{CandidatePhone}} ] . [ {{CandidateLocation}} ]
--- a/Templates/JobHistoryDetails/job1.md
+++ b/Templates/JobHistoryDetails/job1.md
@ -0,0 +1,3 @@
 - Stuff
 - Things
 - Amazing project!
--- a/Templates/JobHistoryDetails/job2.md
+++ b/Templates/JobHistoryDetails/job2.md
@ -0,0 +1,3 @@
 - Stuff
 - Things
 - Amazing project!
--- a/Templates/SkillsAndProjects/Projects.md
+++ b/Templates/SkillsAndProjects/Projects.md
@ -0,0 +1,2 @@
 - Cool project 1.
 - cool project 2.
--- a/Templates/SkillsAndProjects/Skills.csv
+++ b/Templates/SkillsAndProjects/Skills.csv
@ -0,0 +1,2 @@
 skill1|1 years|skill,1,details,and,stuff
 skill2|2 years|skill2,2,details,and,stuff,and,things
--- a/Templates/WorkHistory/WorkHistory.csv
+++ b/Templates/WorkHistory/WorkHistory.csv
@ -0,0 +1,2 @@
 job1,Title of job 1,January 1 1970 - January 6 1980
 job2,Title of Job 2,January 1 1970 - January 6 1980
--- a/build-output/CandidateInfoSheet.md
+++ b/build-output/CandidateInfoSheet.md
@ -0,0 +1,121 @@
 # First Middle Last Candidate Information Sheet
 ## Introduction
 Hello,
 I apologize for the form letter response.
 I receive a high volume of recruiter emails every day and I've found this letter to be the most efficient way to
 handle the high volume of emails and reduce back and forth emails/texts/calls.
 If you have any questions/comments/concerns not covered by this document, please let me know via e-mail and I'm happy to address them!
 If you ask me something answered in this document, I will not respond and will not move forward with the opportunity, so please read it in detail!
 ## Re: share my ID over email
 I WILL NOT share my (full or redacted) photo ID over email or any other electronic written  
 communication. If that is "required" then I have no interest in moving forward with this opportunity.
 I am happy to get on a teams/zoom/google meet etc call and show my ID.
 ## Re: professional references
 I am happy to provide professional references once an interview with the end client/customer/hiring manager/team has been scheduled. I will NOT provide references up front. If that is "required" then I have no interest in moving forward with this opportunity.
 ## Re: relocation
 if the role is not based in **Place 1/Place 2** or **Other Location** I will need to re-locate
 | Question                                  | Answer |
 |-------------------------------------------|--------|
 | Am I open to relocation?                  | Yes    |
 | Am I willing to re-locate at own expense? | No     |
 | Am I open to up to 100% travel            | Yes    |
 Please be aware that:
 - I will **only re-locate at the employer expense**.
 - I will need **two weeks of time** to re-locate.
 - The net amount of the re-location benefit **MUST be at least 1,987.11** to fully compensate me for the time/effort to re-locate.
 - The full re-location benefit **must be provided prior to the confirmed start date**.
 - I **will NOT** accept a reimbursement based re-location package.
 - I am happy to come onsite (at client expense (paid up front)) for training/orientation etc.
 \pagebreak
 ## Rate Schedule (compensation expectations)
 ### Fully remote roles
 I have a **very strong** preference for fully remote roles.
 I am open to (at the absolute bottom of my range):
 - **$12.34** per hour(w2)
 - **$123,456.00** annually
 - **$56.78** per hour (1099/corp to corp)
 I have a strong preference for roles that are :
 - **$34.56** per hour(w2) or more
 - **$321,987.00** annually or more
 - **$78.90** per hour (1099/corp to corp) or more
 ### On-site/hybrid roles
 - **$34.56** per hour(w2) or more
 - **$321,987.00** annually or more
 - **$78.90** per hour (1099/corp to corp) or more
 In regards to compensation type, I am open to:
 - w2
 - corp to corp (I have my own LLC)
 - 1099  
 If you have a rate for any of the compensation options above, send them all. I will pick which one works best for my situation and the opportunity.
 If it's a different rate with/without benefits, send both.
 If the above is in alignment with this opportunity, please feel free to send me an RTR with the best rate you can offer.
 \pagebreak
 ## Details needed for submission
 ### My resume
 [Download Candidate resume(format)](https://some.resume.somewhere/some-Resume.pdf)
 I am happy to discuss and make edits to the resume content specific to the opportunity if you feel they are needed.
 ### Candidate details  
 Here are my complete candidate details for submission to the role.
 | Question                              | Answer                              |
 |---------------------------------------|-------------------------------------|
 | Full name                             | First Middle Last                   |
 | E-mail address                        |                    |
 | Phone number                          | 1 123 456 7890                  |
 | Preferred form of contact             | Email will get the fastest response. |
 | Work authorization                    | US Citizen      |
 | Are you employed presently?           | Not currently employed       |
 | Current location                      | City,State,Country etc        |
 | Current timezone                      | Timezone        |
 | Timezones I can work in               | Timezones      |
 | Availability to interview             | Sometime  |
 | Availability to start                 | Sometime      |
 | Highest Education                     | Some education level       |
 | Graduated Year                        | Graduation year         |
 | Name of school                        | School name             |
 | Location of school                    | School location         |
 | Linkedin Profile                      | (https://www.linkedin.com/)             |
 | Github Profile                        | (https://www.github.com/)               |
 | Last project                          | Last project            |
 | DOB                                   | MM/DD                    |
 | Total IT/career experience            | epoch        |
 | Open to in-office/hybrid/remote       | Yes                                 |
 | Any trips planned in next six months? | No                                  |
--- a/build-output/client-submission/ignore-this-dir
+++ b/build-output/client-submission/ignore-this-dir
@ -0,0 +1 @@
 This directory is used by the build process. Ignore it.
--- a/build-output/ignore-this-dir
+++ b/build-output/ignore-this-dir
@ -0,0 +1 @@
 Working directory for the pipeline. Don't use.
--- a/build-output/job-board/ignore-this-dir
+++ b/build-output/job-board/ignore-this-dir
@ -0,0 +1 @@
 This directory is used by the build process. Ignore it.
--- a/build-temp/ignore-this-dir
+++ b/build-temp/ignore-this-dir
@ -0,0 +1 @@
 Working directory for the pipeline. Don't use.
--- a/build/BuildTemplate-CandidateInfoSheet.yml
+++ b/build/BuildTemplate-CandidateInfoSheet.yml
@ -0,0 +1,14 @@
 title: "{{CandidateName}} Candidate Information Sheet"
 titlepage: true
 titlepage-logo: "{{CandidateLogo}}"
 toc: true
 toc-own-page: true
 date: \today
 header-left: "\\hspace{1cm}"
 header-center: "\\leftmark"
 header-right: "Page \\thepage"
 footer-left: "{{CandidateName}}"
 footer-center: "{{CandidateTagline}}"
 footer-right: "[Source code]({{SourceCode}})"
 urlcolor: {{URLCOLOR}}
 page-background: "{{PAGEBACKGROUND}}"
--- a/build/BuildTemplate-ClientSubmission.yml
+++ b/build/BuildTemplate-ClientSubmission.yml
@ -0,0 +1,7 @@
 title: "{{CandidateName}} Resume"
 header-left: "\\hspace{1cm}"
 header-center: "\\leftmark"
 header-right: "Page \\thepage"
 footer-left: "{{CandidateName}}"
 urlcolor: {{URLCOLOR}}
 page-background: "{{PAGEBACKGROUND}}"
--- a/build/BuildTemplate-JobBoard.yml
+++ b/build/BuildTemplate-JobBoard.yml
@ -0,0 +1,12 @@
 title: "{{CandidateName}} Resume"
 titlepage: true
 titlepage-logo: "{{CandidateLogo}}"
 date: \today
 header-left: "\\hspace{1cm}"
 header-center: "\\leftmark"
 header-right: "Page \\thepage"
 footer-left: "{{CandidateName}}"
 footer-center: "{{CandidateTagline}}"
 footer-right: "[Source code]({{SourceCode}})"
 urlcolor: {{URLCOLOR}}
 page-background: "{{PAGEBACKGROUND}}"
--- a/build/background3.pdf
+++ b/build/background3.pdf
--- a/build/build-demo.sh
+++ b/build/build-demo.sh
@ -0,0 +1,268 @@
 #!/usr/bin/env bash
 # This is a demo used for testing the build pipeline end to end  in a self contained way.
 # It's only used by developers of this repository for testing/validating changes.
 # Your client repository has a build-pipeline-client.sh script and it uses
 # build-pipeline-server.sh, not this script.
 ###################################################
 # Modify these values to suit
 ###################################################
 ########################
 # Contact info
 ########################
 export CandidateName="First Middle Last"
 export CandidatePhone="1 123 456 7890"
 export CandidateLocation="Place 1/Place 2"
 export CandidateEmail="candidate@domain.com"
 ########################
 # Profile information
 ########################
 export CandidateOneLineSummary="Super awesome and stuff."
 export CandidateLinkedin="https://www.linkedin.com/"
 export CandidateGithub="https://www.github.com/"
 export CandidateTagline="Your.Tagline.Here."
 ########################
 # Formatting options
 ########################
 export CandidateLogo=""
 export SourceCode="https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline"
 export URLCOLOR="blue"
 export PAGEBACKGROUND="./background3.pdf"
 ##########################
 # Candidate info sheet
 ##########################
 export CandidatePreferredContactMethod="Email will get the fastest response."
 export CandidateWorkAuthorization="US Citizen"
 export CandidateEmploymentStatus="Not currently employed"
 export CandidateCurrentLocation="City,State,Country etc"
 export CandidateCurrentTimezone="Timezone"
 export CandidateWorkableTimezones="Timezones"
 export CandidateInterviewAvailability="Sometime"
 export CandidateStartAvailability="Sometime"
 export CandidateHighestEducation="Some education level"
 export CandidateGraduationYear="Graduation year"
 export CandidateSchoolName="School name"
 export CandidateSchoolLocation="School location"
 export CandidateLastProject="Last project"
 export CandidateDOB="MM/DD"
 export CandidateTotalExperience="epoch"
 ########################
 #Compensation targets
 ########################
 export CandidateRelocationNetMinimumAmount="1,987.11"
 export CandidateRateSheetRemoteW2HourlyMinimum="\$12.34"
 export CandidateRateSheetRemoteW2AnnualMinimum="\$123,456.00"
 export CandidateRateSheetRemote1099HourlyMinimum="\$56.78"
 export CandidateRateSheetRemoteW2HourlyPrefer="\$34.56"
 export CandidateRateSheetRemoteW2AnnualPrefer="\$321,987.00"
 export CandidateRateSheetRemote1099HourlyPrefer="\$78.90"
 ####################################################
 #DO NOT CHANGE ANYTHING BELOW THIS LINE
 ####################################################
 ############################################################
 # Setup globals
 ############################################################
 readonly MO_PATH="bash ../vendor/git.knownelement.com/ExternalVendorCode/mo/mo"
 readonly BUILD_OUTPUT_DIR="../build-output"
 readonly BUILD_TEMP_DIR="../build-temp"
 readonly BUILDYAML_JOBBOARD="$BUILD_TEMP_DIR/JobBoard.yml"
 readonly BUILDYAML_CLIENTSUBMISSION="$BUILD_TEMP_DIR/ClientSubmission.yml"
 readonly BUILDYAML_CANDIDATEINFOSHEET="$BUILD_TEMP_DIR/CandidateInfoSheet.yml"
 CandidateInfoSheetMarkdownOutputFile="$BUILD_OUTPUT_DIR/CandidateInfoSheet.md"
 CandidateInfoSheetPDFOutputFIle="$BUILD_OUTPUT_DIR/CandidateInfoSheet.pdf"
 JobBoardMarkdownOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.md"
 JobBoardPDFOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.pdf"
 JobBoardMSWordOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.doc"
 ClientSubmissionMarkdownOutputFile="$BUILD_OUTPUT_DIR/client-submission/Resume.md"
 ClientSubmissionPDFOutputFile="$BUILD_OUTPUT_DIR/client-submission//Resume.pdf"
 ClientSubmissionMSWordOutputFile="$BUILD_OUTPUT_DIR/client-submission/Resume.doc"
 echo "Cleaning up from previous runs..."
 rm $BUILDYAML_CANDIDATEINFOSHEET
 rm $CandidateInfoSheetMarkdownOutputFile
 rm $CandidateInfoSheetPDFOutputFIle
 rm $BUILDYAML_JOBBOARD
 rm $JobBoardMarkdownOutputFile
 rm $JobBoardPDFOutputFile
 rm $JobBoardMSWordOutputFile
 rm $BUILDYAML_CLIENTSUBMISSION
 rm $ClientSubmissionMarkdownOutputFile
 rm $ClientSubmissionPDFOutputFile
 rm $ClientSubmissionMSWordOutputFile
 # Expand variables into rendered YAML files. These will be used by pandoc to create the output artifacts
 $MO_PATH ./BuildTemplate-CandidateInfoSheet.yml > $BUILDYAML_CANDIDATEINFOSHEET
 $MO_PATH ./BuildTemplate-JobBoard.yml > $BUILDYAML_JOBBOARD
 $MO_PATH ./BuildTemplate-ClientSubmission.yml > $BUILDYAML_CLIENTSUBMISSION
 echo "Creating candidate info sheet..."
 $MO_PATH ../Templates/CandidateInfoSheet/CandidateInfoSheet.md > $CandidateInfoSheetMarkdownOutputFile
 pandoc \
 "$CandidateInfoSheetMarkdownOutputFile" \
 --template eisvogel \
 --metadata-file="../build-temp/CandidateInfoSheet.yml" \
 --from markdown \
 --to=pdf \
 --output $CandidateInfoSheetPDFOutputFIle
 echo "Combining markdown files into single input file for pandoc..."
 # Create contact info md file
 $MO_PATH ../Templates/ContactInfo/ContactInfo-JobBoard.md > $BUILD_TEMP_DIR/ContactInfo-JobBoard.md
 $MO_PATH ../Templates/ContactInfo/ContactInfo-ClientSubmit.md > $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md
 #Pull in contact info
 cat $BUILD_TEMP_DIR/ContactInfo-JobBoard.md >> $JobBoardMarkdownOutputFile
 echo " " >> $JobBoardMarkdownOutputFile
 cat $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md >> $ClientSubmissionMarkdownOutputFile
 echo " " >> $ClientSubmissionMarkdownOutputFile
 echo "## Career Highlights" >> $JobBoardMarkdownOutputFile
 echo "## Career Highlights" >> $ClientSubmissionMarkdownOutputFile
 cat ../Templates/SkillsAndProjects/Projects.md >> $JobBoardMarkdownOutputFile
 echo "\pagebreak" >> $JobBoardMarkdownOutputFile
 cat ../Templates/SkillsAndProjects/Projects.md >> $ClientSubmissionMarkdownOutputFile
 echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
 echo " " >> $JobBoardMarkdownOutputFile
 echo "## Employment History" >> $JobBoardMarkdownOutputFile
 echo " " >> $JobBoardMarkdownOutputFile
 echo " " >> $ClientSubmissionMarkdownOutputFile
 echo "## Employment History" >> $ClientSubmissionMarkdownOutputFile
 echo " " >> $ClientSubmissionMarkdownOutputFile
 #And here we do some magic...
 #Pull in :
 # employer
 # title
 # start/end dates of employment 
 # long form position summary data from each position
 IFS=$'\n\t'
 for position in \
 $(cat ../Templates/WorkHistory/WorkHistory.csv); do
 COMPANY="$(echo $position|awk -F ',' '{print $1}')"
 TITLE="$(echo $position|awk -F ',' '{print $2}')"
 DATEOFEMPLOY="$(echo $position|awk -F ',' '{print $3}')"
 echo " " >> "$JobBoardMarkdownOutputFile"
 echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $JobBoardMarkdownOutputFile
 echo " " >> "$JobBoardMarkdownOutputFile"
 echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $ClientSubmissionMarkdownOutputFile
 echo " " >> "$ClientSubmissionMarkdownOutputFile"
 echo " " >> "$JobBoardMarkdownOutputFile"
 cat ../Templates/JobHistoryDetails/$COMPANY.md >> "$JobBoardMarkdownOutputFile"
 echo " " >> "$JobBoardMarkdownOutputFile"
 cat ../Templates/JobHistoryDetails/$COMPANY.md >> "$ClientSubmissionMarkdownOutputFile"
 echo " " >> "$ClientSubmissionMarkdownOutputFile"
 done
 #Pull in my skills and generate a beautiful table.
 echo "\pagebreak" >> $JobBoardMarkdownOutputFile
 echo " " >> "$JobBoardMarkdownOutputFile"
 echo "## Skills" >> "$JobBoardMarkdownOutputFile"
 echo " " >> "$JobBoardMarkdownOutputFile"
 echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
 echo " " >> "$ClientSubmissionMarkdownOutputFile"
 echo "## Skills" >> "$ClientSubmissionMarkdownOutputFile"
 echo " " >> "$ClientSubmissionMarkdownOutputFile"
 #Table heading
 echo "|Skill|Experience|Skill Details|" >> $JobBoardMarkdownOutputFile
 echo "|---|---|---|" >> $JobBoardMarkdownOutputFile
 echo "|Skill|Experience|Skill Details|" >> $ClientSubmissionMarkdownOutputFile
 echo "|---|---|---|" >> $ClientSubmissionMarkdownOutputFile
 #Table rows
 IFS=$'\n\t'
 for skill in \
 $(cat ../Templates/SkillsAndProjects/Skills.csv); do
 SKILL_NAME="$(echo $skill|awk -F '|' '{print $1}')"
 SKILL_YEARS="$(echo $skill|awk -F '|' '{print $2}')"
 SKILL_DETAIL="$(echo $skill|awk -F '|' '{print $3}')"
 echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $JobBoardMarkdownOutputFile
 echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $ClientSubmissionMarkdownOutputFile
 done
 unset IFS
 echo "Generating PDF output for job board version..."
 pandoc \
 "$JobBoardMarkdownOutputFile" \
 --template eisvogel \
 --metadata-file="../build-temp/JobBoard.yml" \
 --from markdown \
 --to=pdf \
 --output $JobBoardPDFOutputFile
 echo "Generating MSWord output for job board version..."
 pandoc \
 "$JobBoardMarkdownOutputFile" \
 --metadata-file="../build-temp/JobBoard.yml" \
 --from markdown \
 --to=docx \
 --reference-doc=resume-docx-reference.docx \
 --output $JobBoardMSWordOutputFile
 echo "Generating PDF output for client submission version..."
 pandoc \
 "$ClientSubmissionMarkdownOutputFile" \
 --template eisvogel \
 --metadata-file="../build-temp/ClientSubmission.yml" \
 --from markdown \
 --to=pdf \
 --output $ClientSubmissionPDFOutputFile
 echo "Generating MSWord output for client submission version..."
 pandoc \
 "$ClientSubmissionMarkdownOutputFile" \
 --metadata-file="../build-temp/ClientSubmission.yml" \
 --from markdown \
 --to=docx \
 --reference-doc=resume-docx-reference.docx \
 --output $ClientSubmissionMSWordOutputFile
--- a/build/build-pipeline-server.sh
+++ b/build/build-pipeline-server.sh
@ -0,0 +1,168 @@
 #!/usr/bin/env bash
 echo "Cleaning up from previous runs..."
 rm $BUILDYAML_CANDIDATEINFOSHEET
 rm $CandidateInfoSheetMarkdownOutputFile
 rm $CandidateInfoSheetPDFOutputFIle
 rm $BUILDYAML_JOBBOARD
 rm $JobBoardMarkdownOutputFile
 rm $JobBoardPDFOutputFile
 rm $JobBoardMSWordOutputFile
 rm $BUILDYAML_CLIENTSUBMISSION
 rm $ClientSubmissionMarkdownOutputFile
 rm $ClientSubmissionPDFOutputFile
 rm $ClientSubmissionMSWordOutputFile
 # Expand variables into rendered YAML files. These will be used by pandoc to create the output artifacts
 $MO_PATH $PipelineClientWorkingDir/build/BuildTemplate-CandidateInfoSheet.yml > $BUILDYAML_CANDIDATEINFOSHEET
 $MO_PATH $PipelineClientWorkingDir/build/BuildTemplate-JobBoard.yml > $BUILDYAML_JOBBOARD
 $MO_PATH $PipelineClientWorkingDir/build/BuildTemplate-ClientSubmission.yml > $BUILDYAML_CLIENTSUBMISSION
 echo "Creating candidate info sheet..."
 $MO_PATH $PipelineClientWorkingDir/Templates/CandidateInfoSheet/CandidateInfoSheet.md > $CandidateInfoSheetMarkdownOutputFile
 pandoc \
 "$CandidateInfoSheetMarkdownOutputFile" \
 --template eisvogel \
 --metadata-file="$PipelineClientWorkingDir/build-temp/CandidateInfoSheet.yml" \
 --from markdown \
 --to=pdf \
 --output $CandidateInfoSheetPDFOutputFIle
 echo "Combining markdown files into single input file for pandoc..."
 # Create contact info md file
 $MO_PATH $PipelineClientWorkingDir/Templates/ContactInfo/ContactInfo-JobBoard.md > $BUILD_TEMP_DIR/ContactInfo-JobBoard.md
 $MO_PATH $PipelineClientWorkingDir/Templates/ContactInfo/ContactInfo-ClientSubmit.md > $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md
 #Pull in contact info
 cat $BUILD_TEMP_DIR/ContactInfo-JobBoard.md >> $JobBoardMarkdownOutputFile
 echo " " >> $JobBoardMarkdownOutputFile
 cat $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md >> $ClientSubmissionMarkdownOutputFile
 echo " " >> $ClientSubmissionMarkdownOutputFile
 echo "## Career Highlights" >> $JobBoardMarkdownOutputFile
 echo "## Career Highlights" >> $ClientSubmissionMarkdownOutputFile
 cat $PipelineClientWorkingDir/Templates/SkillsAndProjects/Projects.md >> $JobBoardMarkdownOutputFile
 echo "\pagebreak" >> $JobBoardMarkdownOutputFile
 cat  $PipelineClientWorkingDir/Templates/SkillsAndProjects/Projects.md >> $ClientSubmissionMarkdownOutputFile
 echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
 echo " " >> $JobBoardMarkdownOutputFile
 echo "## Employment History" >> $JobBoardMarkdownOutputFile
 echo " " >> $JobBoardMarkdownOutputFile
 echo " " >> $ClientSubmissionMarkdownOutputFile
 echo "## Employment History" >> $ClientSubmissionMarkdownOutputFile
 echo " " >> $ClientSubmissionMarkdownOutputFile
 #And here we do some magic...
 #Pull in :
 # employer
 # title
 # start/end dates of employment 
 # long form position summary data from each position
 IFS=$'\n\t'
 for position in \
 $(cat $PipelineClientWorkingDir/Templates/WorkHistory/WorkHistory.csv); do
 COMPANY="$(echo $position|awk -F ',' '{print $1}')"
 TITLE="$(echo $position|awk -F ',' '{print $2}')"
 DATEOFEMPLOY="$(echo $position|awk -F ',' '{print $3}')"
 echo " " >> "$JobBoardMarkdownOutputFile"
 echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $JobBoardMarkdownOutputFile
 echo " " >> "$JobBoardMarkdownOutputFile"
 echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $ClientSubmissionMarkdownOutputFile
 echo " " >> "$ClientSubmissionMarkdownOutputFile"
 echo " " >> "$JobBoardMarkdownOutputFile"
 cat $PipelineClientWorkingDir/Templates/JobHistoryDetails/$COMPANY.md >> "$JobBoardMarkdownOutputFile"
 echo " " >> "$JobBoardMarkdownOutputFile"
 cat $PipelineClientWorkingDir/Templates/JobHistoryDetails/$COMPANY.md >> "$ClientSubmissionMarkdownOutputFile"
 echo " " >> "$ClientSubmissionMarkdownOutputFile"
 done
 #Pull in my skills and generate a beautiful table.
 echo "\pagebreak" >> $JobBoardMarkdownOutputFile
 echo " " >> "$JobBoardMarkdownOutputFile"
 echo "## Skills" >> "$JobBoardMarkdownOutputFile"
 echo " " >> "$JobBoardMarkdownOutputFile"
 echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
 echo " " >> "$ClientSubmissionMarkdownOutputFile"
 echo "## Skills" >> "$ClientSubmissionMarkdownOutputFile"
 echo " " >> "$ClientSubmissionMarkdownOutputFile"
 #Table heading
 echo "|Skill|Experience|Skill Details|" >> $JobBoardMarkdownOutputFile
 echo "|---|---|---|" >> $JobBoardMarkdownOutputFile
 echo "|Skill|Experience|Skill Details|" >> $ClientSubmissionMarkdownOutputFile
 echo "|---|---|---|" >> $ClientSubmissionMarkdownOutputFile
 #Table rows
 IFS=$'\n\t'
 for skill in \
 $(cat $PipelineClientWorkingDir/Templates/SkillsAndProjects/Skills.csv); do
 SKILL_NAME="$(echo $skill|awk -F '|' '{print $1}')"
 SKILL_YEARS="$(echo $skill|awk -F '|' '{print $2}')"
 SKILL_DETAIL="$(echo $skill|awk -F '|' '{print $3}')"
 echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $JobBoardMarkdownOutputFile
 echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $ClientSubmissionMarkdownOutputFile
 done
 unset IFS
 echo "Generating PDF output for job board version..."
 pandoc \
 "$JobBoardMarkdownOutputFile" \
 --template eisvogel \
 --metadata-file="$PipelineClientWorkingDir/build-temp/JobBoard.yml" \
 --from markdown \
 --to=pdf \
 --output $JobBoardPDFOutputFile
 echo "Generating MSWord output for job board version..."
 pandoc \
 "$JobBoardMarkdownOutputFile" \
 --metadata-file="$PipelineClientWorkingDir/build-temp/JobBoard.yml" \
 --from markdown \
 --to=docx \
 --reference-doc="$PipelineClientWorkingDir/build/resume-docx-reference.docx" \
 --output $JobBoardMSWordOutputFile
 echo "Generating PDF output for client submission version..."
 pandoc \
 "$ClientSubmissionMarkdownOutputFile" \
 --template eisvogel \
 --metadata-file="$PipelineClientWorkingDir/build-temp/ClientSubmission.yml" \
 --from markdown \
 --to=pdf \
 --output $ClientSubmissionPDFOutputFile
 echo "Generating MSWord output for client submission version..."
 pandoc \
 "$ClientSubmissionMarkdownOutputFile" \
 --metadata-file="$PipelineClientWorkingDir/build-temp/ClientSubmission.yml" \
 --from markdown \
 --to=docx \
 --reference-doc="$PipelineClientWorkingDir/build/resume-docx-reference.docx" \
 --output $ClientSubmissionMSWordOutputFile
--- a/build/resume-docx-reference.docx
+++ b/build/resume-docx-reference.docx
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/.eslintrc.yaml
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/.eslintrc.yaml
@ -0,0 +1,168 @@
 parserOptions:
    ecmaVersion: latest
    sourceType: module
 env:
    es6: true
    jasmine: true
    node: true
 extends: eslint:recommended
 rules:
    accessor-pairs: error
    array-bracket-spacing:
        - error
        - never
    array-callback-return: error
    block-spacing:
        - error
        - never
    brace-style: error
    comma-dangle: error
    comma-spacing: error
    comma-style: error
    complexity:
        - error
        - 10
    computed-property-spacing: error
    consistent-return: error
    consistent-this: error
    constructor-super: error
    curly: error
    default-case: error
    dot-notation: error
    eol-last: error
    eqeqeq: error
    generator-star-spacing: error
    global-require: off
    guard-for-in: error
    jsx-quotes: error
    key-spacing: error
    keyword-spacing: error
    linebreak-style: error
    lines-around-comment:
        - error
        -
            allowBlockStart: true
            allowObjectStart: true
            allowArrayStart: true
    max-statements-per-line: error
    new-cap: error
    new-parens: error
    no-array-constructor: error
    no-bitwise: error
    no-caller: error
    no-case-declarations: error
    no-catch-shadow: error
    no-class-assign: error
    no-cond-assign: error
    no-confusing-arrow: error
    no-console: off
    no-const-assign: error
    no-constant-condition: error
    no-continue: error
    no-delete-var: error
    no-dupe-args: error
    no-dupe-class-members: error
    no-dupe-keys: error
    no-duplicate-case: error
    no-duplicate-imports: error
    no-empty: off
    no-empty-character-class: error
    no-empty-pattern: error
    no-eq-null: error
    no-eval: error
    no-extend-native: error
    no-extra-bind: error
    no-extra-boolean-cast: error
    no-extra-label: error
    no-extra-semi: error
    no-fallthrough: error
    no-func-assign: error
    no-implied-eval: error
    no-inner-declarations: error
    no-invalid-this: error
    no-invalid-regexp: error
    no-irregular-whitespace: error
    no-iterator: error
    no-label-var: error
    no-labels: error
    no-lone-blocks: error
    no-lonely-if: error
    no-loop-func: error
    no-mixed-spaces-and-tabs: error
    no-multi-spaces: error
    no-multi-str: error
    no-multiple-empty-lines:
        - error
        -
            max: 2
    no-native-reassign: error
    no-negated-condition: error
    no-nested-ternary: error
    no-new: error
    no-new-func: error
    no-new-object: error
    no-new-symbol: error
    no-new-wrappers: error
    no-obj-calls: error
    no-octal: error
    no-octal-escape: error
    no-path-concat: error
    no-plusplus: error
    no-proto: error
    no-redeclare: error
    no-regex-spaces: error
    no-restricted-globals: error
    no-return-assign: error
    no-script-url: error
    no-self-assign: error
    no-self-compare: error
    no-sequences: error
    no-shadow: error
    no-shadow-restricted-names: error
    no-spaced-func: error
    no-sparse-arrays: error
    no-this-before-super: error
    no-throw-literal: error
    no-trailing-spaces: error
    no-undef: error
    no-undef-init: error
    no-unexpected-multiline: error
    no-unmodified-loop-condition: error
    no-unneeded-ternary: error
    no-unreachable: error
    no-unsafe-finally: error
    no-unused-expressions: error
    no-unused-labels: error
    no-unused-vars: error
    no-useless-call: error
    no-useless-computed-key: error
    no-useless-concat: error
    no-useless-constructor: error
    no-useless-escape: error
    no-void: error
    no-warning-comments: warn
    no-whitespace-before-property: error
    no-with: error
    operator-assignment: error
    padded-blocks:
        - error
        - never
    prefer-const: error
    quote-props:
        - error
        - as-needed
    radix: error
    require-yield: error
    semi: error
    semi-spacing: error
    space-before-blocks: error
    space-in-parens: error
    space-infix-ops:
        - error
        -
            int32Hint: false
    space-unary-ops: error
    spaced-comment: error
    use-isnan: error
    valid-typeof: error
    yield-star-spacing: error
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/.github/workflows/ci.yaml
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/.github/workflows/ci.yaml
@ -0,0 +1,13 @@
 name: CI
 on: [push]
 jobs:
  test:
    name: Test
    runs-on: ubuntu-latest
    steps:
      - name: Check out code
        uses: actions/checkout@v1
      - name: Run tests
        run: ./run-tests
      - name: Run against spec
        run: ./run-spec
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/.github/workflows/release.yaml
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/.github/workflows/release.yaml
@ -0,0 +1,45 @@
 name: docker push
 on: [push]
 jobs:
  push_to_registry:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@master
      - name: Docker meta
        if: startsWith(github.ref, 'refs/tags/')
        id: docker_meta
        uses: crazy-max/ghaction-docker-meta@v1
        with:
          images: ghcr.io/${{ github.repository }}
          tag-match: v(.*)
      - name: Set up QEMU
        if: startsWith(github.ref, 'refs/tags/')
        uses: docker/setup-qemu-action@v1
      - name: Set up Docker Buildx
        id: buildx
        uses: docker/setup-buildx-action@v1
      - name: Cache Docker layers
        if: startsWith(github.ref, 'refs/tags/')
        uses: actions/cache@v2
        with:
          path: /tmp/.buildx-cache
          key: ${{ runner.os }}-buildx-${{ github.sha }}
          restore-keys: |
            ${{ runner.os }}-buildx-
      - name: Login to GitHub Container Registry
        if: startsWith(github.ref, 'refs/tags/')
        uses: docker/login-action@v1
        with:
          registry: ghcr.io
          username: ${{ github.repository_owner }}
          password: ${{ secrets.GITHUB_TOKEN }}
      - name:  Build and push
        uses: docker/build-push-action@v2
        if: startsWith(github.ref, 'refs/tags/')
        with:
          builder: ${{ steps.buildx.outputs.name }}
          platforms: linux/amd64,linux/arm64
          tags: ${{ steps.docker_meta.outputs.tags }}
          cache-from: type=local,src=/tmp/.buildx-cache
          cache-to: type=local,dest=/tmp/.buildx-cache
          push: true
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/.gitignore
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/.gitignore
@ -0,0 +1,9 @@
 *.swp
 diagnostic.partial
 diagnostic.test
 tests/*.diff
 spec/
 spec-runner/
 node_modules/
 package.json
 package-lock.json
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/API.md
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/API.md
@ -0,0 +1,616 @@
 API / Function Documentation
 ============================
 This documentation is generated automatically from the source of [mo] thanks to [tomdoc.sh].
 `mo()`
 ------
 Public: Template parser function.  Writes templates to stdout.
 * $0 - Name of the mo file, used for getting the help message.
 * $@ - Filenames to parse.
 Returns nothing.
 `mo::debug()`
 -------------
 Internal: Show a debug message
 * $1 - The debug message to show
 Returns nothing.
 `mo::debugShowState()`
 ----------------------
 Internal: Show a debug message and internal state information
 No arguments
 Returns nothing.
 `mo::error()`
 -------------
 Internal: Show an error message and exit
 * $1 - The error message to show
 * $2 - Error code
 Returns nothing. Exits the program.
 `mo::errorNear()`
 -----------------
 Internal: Show an error message with a snippet of context and exit
 * $1 - The error message to show
 * $2 - The starting point
 * $3 - Error code
 Returns nothing. Exits the program.
 `mo::usage()`
 -------------
 Internal: Displays the usage for mo.  Pulls this from the file that contained the `mo` function.  Can only work when the right filename comes is the one argument, and that only happens when `mo` is called with `$0` set to this file.
 * $1 - Filename that has the help message
 Returns nothing.
 `mo::content()`
 ---------------
 Internal: Fetches the content to parse into MO_UNPARSED.  Can be a list of partials for files or the content from stdin.
 * $1 - Destination variable name
 * $2-@ - File names (optional), read from stdin otherwise
 Returns nothing.
 `mo::contentFile()`
 -------------------
 Internal: Read a file into MO_UNPARSED.
 * $1 - Destination variable name.
 * $2 - Filename to load - if empty, defaults to /dev/stdin
 Returns nothing.
 `mo::indirect()`
 ----------------
 Internal: Send a variable up to the parent of the caller of this function.
 * $1 - Variable name
 * $2 - Value
 Examples
    callFunc () {
        local "$1" && mo::indirect "$1" "the value"
    }
    callFunc dest
    echo "$dest"  # writes "the value"
 Returns nothing.
 `mo::indirectArray()`
 ---------------------
 Internal: Send an array as a variable up to caller of a function
 * $1 - Variable name
 * $2-@ - Array elements
 Examples
    callFunc () {
        local myArray=(one two three)
        local "$1" && mo::indirectArray "$1" "${myArray[@]}"
    }
    callFunc dest
    echo "${dest[@]}" # writes "one two three"
 Returns nothing.
 `mo::trimUnparsed()`
 --------------------
 Internal: Trim leading characters from MO_UNPARSED
 Returns nothing.
 `mo::chomp()`
 -------------
 Internal: Remove whitespace and content after whitespace
 * $1 - Name of the destination variable
 * $2 - The string to chomp
 Returns nothing.
 `mo::parse()`
 -------------
 Public: Parses text, interpolates mustache tags. Utilizes the current value of MO_OPEN_DELIMITER, MO_CLOSE_DELIMITER, and MO_STANDALONE_CONTENT. Those three variables shouldn't be changed by user-defined functions.
 * $1 - Destination variable name - where to store the finished content
 * $2 - Content to parse
 * $3 - Preserve standalone status/content - truthy if not empty. When set to a value, that becomes the standalone content value
 Returns nothing.
 `mo::parseInternal()`
 ---------------------
 Internal: Parse MO_UNPARSED, writing content to MO_PARSED. Interpolates mustache tags.
 No arguments
 Returns nothing.
 `mo::parseBlock()`
 ------------------
 Internal: Handle parsing a block
 * $1 - Invert condition ("true" or "false")
 Returns nothing
 `mo::parseBlockFunction()`
 --------------------------
 Internal: Handle parsing a block whose first argument is a function
 * $1 - Invert condition ("true" or "false")
 * $2-@ - The parsed tokens from inside the block tags
 Returns nothing
 `mo::parseBlockArray()`
 -----------------------
 Internal: Handle parsing a block whose first argument is an array
 * $1 - Invert condition ("true" or "false")
 * $2-@ - The parsed tokens from inside the block tags
 Returns nothing
 `mo::parseBlockValue()`
 -----------------------
 Internal: Handle parsing a block whose first argument is a value
 * $1 - Invert condition ("true" or "false")
 * $2-@ - The parsed tokens from inside the block tags
 Returns nothing
 `mo::parsePartial()`
 --------------------
 Internal: Handle parsing a partial
 No arguments.
 Indentation will be applied to the entire partial's contents before parsing. This indentation is based on the whitespace that ends the previously parsed content.
 Returns nothing
 `mo::parseComment()`
 --------------------
 Internal: Handle parsing a comment
 No arguments.
 Returns nothing
 `mo::parseDelimiter()`
 ----------------------
 Internal: Handle parsing the change of delimiters
 No arguments.
 Returns nothing
 `mo::parseValue()`
 ------------------
 Internal: Handle parsing value or function call
 No arguments.
 Returns nothing
 `mo::isFunction()`
 ------------------
 Internal: Determine if the given name is a defined function.
 * $1 - Function name to check
 Be extremely careful.  Even if strict mode is enabled, it is not honored in newer versions of Bash.  Any errors that crop up here will not be caught automatically.
 Examples
    moo () {
        echo "This is a function"
    }
    if mo::isFunction moo; then
        echo "moo is a defined function"
    fi
 Returns 0 if the name is a function, 1 otherwise.
 `mo::isArray()`
 ---------------
 Internal: Determine if a given environment variable exists and if it is an array.
 * $1 - Name of environment variable
 Be extremely careful.  Even if strict mode is enabled, it is not honored in newer versions of Bash.  Any errors that crop up here will not be caught automatically.
 Examples
    var=(abc)
    if moIsArray var; then
       echo "This is an array"
       echo "Make sure you don't accidentally use \$var"
    fi
 Returns 0 if the name is not empty, 1 otherwise.
 `mo::isArrayIndexValid()`
 -------------------------
 Internal: Determine if an array index exists.
 * $1 - Variable name to check
 * $2 - The index to check
 Has to check if the variable is an array and if the index is valid for that type of array.
 Returns true (0) if everything was ok, 1 if there's any condition that fails.
 `mo::isVarSet()`
 ----------------
 Internal: Determine if a variable is assigned, even if it is assigned an empty value.
 * $1 - Variable name to check.
 Can not use logic like this in case invalid variable names are passed.      [[ "${!1-a}" == "${!1-b}" ]]
 Returns true (0) if the variable is set, 1 if the variable is unset.
 `mo::isTruthy()`
 ----------------
 Internal: Determine if a value is considered truthy.
 * $1 - The value to test
 * $2 - Invert the value, either "true" or "false"
 Returns true (0) if truthy, 1 otherwise.
 `mo::evaluate()`
 ----------------
 Internal: Convert token list to values
 * $1 - Destination variable name
 * $2-@ - Tokens to convert
 Sample call:
      mo::evaluate dest NAME username VALUE abc123 PAREN 2
 Returns nothing.
 `mo::evaluateListOfSingles()`
 -----------------------------
 Internal: Convert an argument list to individual values.
 * $1 - Destination variable name
 * $2-@ - A list of argument types and argument name/value.
 This assumes each value is separate from the rest. In contrast, mo::evaluate will pass all arguments to a function if the first value is a function.
 Sample call:
      mo::evaluateListOfSingles dest NAME username VALUE abc123
 Returns nothing.
 `mo::evaluateSingle()`
 ----------------------
 Internal: Evaluate a single argument
 * $1 - Name of variable for result
 * $2 - Type of argument, either NAME or VALUE
 * $3 - Argument
 Returns nothing
 `mo::evaluateKey()`
 -------------------
 Internal: Return the value for @key based on current's name
 * $1 - Name of variable for result
 Returns nothing
 `mo::evaluateVariable()`
 ------------------------
 Internal: Handle a variable name
 * $1 - Destination variable name
 * $2 - Variable name
 Returns nothing.
 `mo::findVariableName()`
 ------------------------
 Internal: Find the name of a variable to use
 * $1 - Destination variable name, receives an array
 * $2 - Variable name from the template
 The array contains the following values
    * [0] - Variable name
    * [1] - Array index, or empty string
 Example variables      a="a"
      b="b"
      c=("c.0" "c.1")
      d=([b]="d.b" [d]="d.d")
 Given these inputs (function input, current value), produce these outputs      a c => a
      a c.0 => a
      b d => d.b
      b d.d => d.b
      a d => d.a
      a d.d => d.a
      c.0 d => c.0
      d.b d => d.b
      '' c => c
      '' c.0 => c.0
 Returns nothing.
 `mo::join()`
 ------------
 Internal: Join / implode an array
 * $1    - Variable name to receive the joined content
 * $2    - Joiner
 * $3-@ - Elements to join
 Returns nothing.
 `mo::evaluateFunction()`
 ------------------------
 Internal: Call a function.
 * $1 - Variable for output
 * $2 - Content to pass
 * $3 - Function to call
 * $4-@ - Additional arguments as list of type, value/name
 Returns nothing.
 `mo::standaloneCheck()`
 -----------------------
 Internal: Check if a tag appears to have only whitespace before it and after it on a line. There must be a new line before and there must be a newline after or the end of a string
 No arguments.
 Returns 0 if this is a standalone tag, 1 otherwise.
 `mo::standaloneProcess()`
 -------------------------
 Internal: Process content before and after a tag. Remove prior whitespace up to the previous newline. Remove following whitespace up to and including the next newline.
 No arguments.
 Returns nothing.
 `mo::indentLines()`
 -------------------
 Internal: Apply indentation before any line that has content in MO_UNPARSED.
 * $1 - Destination variable name.
 * $2 - The indentation string.
 * $3 - The content that needs the indentation string prepended on each line.
 Returns nothing.
 `mo::escape()`
 --------------
 Internal: Escape a value
 * $1 - Destination variable name
 * $2 - Value to escape
 Returns nothing
 `mo::getContentUntilClose()`
 ----------------------------
 Internal: Get the content up to the end of the block by minimally parsing and balancing blocks. Returns the content before the end tag to the caller and removes the content + the end tag from MO_UNPARSED. This can change the delimiters, adjusting MO_OPEN_DELIMITER and MO_CLOSE_DELIMITER.
 * $1 - Destination variable name
 * $2 - Token string to match for a closing tag
 Returns nothing.
 `mo::tokensToString()`
 ----------------------
 Internal: Convert a list of tokens to a string
 * $1 - Destination variable for the string
 * $2-$@ - Token list
 Returns nothing.
 `mo::getContentTrim()`
 ----------------------
 Internal: Trims content from MO_UNPARSED, returns trimmed content.
 * $1 - Destination variable
 Returns nothing.
 `mo::getContentComment()`
 -------------------------
 Get the content up to and including a close tag
 * $1 - Destination variable
 Returns nothing.
 `mo::getContentDelimiter()`
 ---------------------------
 Get the content up to and including a close tag. First two non-whitespace tokens become the new open and close tag.
 * $1 - Destination variable
 Returns nothing.
 `mo::getContentWithinTag()`
 ---------------------------
 Get the content up to and including a close tag. First two non-whitespace tokens become the new open and close tag.
 * $1 - Destination variable, an array
 * $2 - Terminator string
 The array contents:      [0] The raw content within the tag
      [1] The parsed tokens as a single string
 Returns nothing.
 `mo::tokenizeTagContents()`
 ---------------------------
 Internal: Parse MO_UNPARSED and retrieve the content within the tag delimiters. Converts everything into an array of string values.
 * $1 - Destination variable for the array of contents.
 * $2 - Stop processing when this content is found.
 The list of tokens are in RPN form. The first item in the resulting array is the number of actual tokens (after combining command tokens) in the list.
 Given: a 'bc' "de\"\n" (f {g 'h'}) Result: ([0]=4 [1]=NAME [2]=a [3]=VALUE [4]=bc [5]=VALUE [6]=$'de\"\n' [7]=NAME [8]=f [9]=NAME [10]=g [11]=VALUE [12]=h [13]=BRACE [14]=2 [15]=PAREN [16]=2
 Returns nothing
 `mo::tokenizeTagContentsName()`
 -------------------------------
 Internal: Get the contents of a variable name.
 * $1 - Destination variable name for the token list (array of strings)
 Returns nothing
 `mo::tokenizeTagContentsDoubleQuote()`
 --------------------------------------
 Internal: Get the contents of a tag in double quotes. Parses the backslash sequences.
 * $1 - Destination variable name for the token list (array of strings)
 Returns nothing.
 `mo::tokenizeTagContentsSingleQuote()`
 --------------------------------------
 Internal: Get the contents of a tag in single quotes. Only gets the raw value.
 * $1 - Destination variable name for the token list (array of strings)
 Returns nothing.
 `MO_ORIGINAL_COMMAND`
 ---------------------
 Save the original command's path for usage later
 [mo]: ./mo
 [tomdoc.sh]: https://github.com/tests-always-included/tomdoc.sh
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/Dockerfile
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/Dockerfile
@ -0,0 +1,7 @@
 FROM alpine
 RUN apk add --no-cache bash
 ADD mo /usr/local/bin/mo
 RUN chmod +x /usr/local/bin/mo
 ENTRYPOINT /usr/local/bin/mo
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/LICENSE.md
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/LICENSE.md
@ -0,0 +1,7 @@
 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 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.
 Except as contained in this notice, the name(s) of the above copyright holders shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization.
 The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed  by contributors", in the same place and form as other third-party acknowledgments. Alternately, this acknowledgment may appear in the software itself, in the same form and location as other such third-party acknowledgments.
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/README.md
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/README.md
@ -0,0 +1,340 @@
 Mo - Mustache Templates in Bash
 ===============================
 [Mustache] templates are simple, logic-less templates.  Because of their simplicity, they are able to be ported to many languages.  The syntax is quite simple.
    Hello, {{NAME}}.
    I hope your {{TIME_PERIOD}} was fun.
 The above file is [`demo/fun-trip.mo`](demo/fun-trip.mo).  Let's try using this template some data from bash's environment.  Go to your checked out copy of the project and run a command like this:
    NAME=Tyler TIME_PERIOD=weekend ./mo demo/fun-trip.mo
 Your result?
    Hello, Tyler.
    I hope your weekend was fun.
 This bash version supports conditionals, functions (both as filters and as values), as well as indexed arrays (for iteration).  You are able to leverage these additional features by adding more information into the environment.  It is easiest to do this when you source `mo`.  See the [demo scripts](demo/) for further examples.
 Requirements
 ------------
 * Bash 3.x (the aim is to make it work on Macs)
 * The "coreutils" package (`basename` and `cat`)
 * ... that's it.  Why?  Because bash **can**!
 If you intend to develop this and run the official specs, you also need node.js.
 Installation
 ------------
 There are a few ways you can install this tool.  How you install it depends on how you want to use it.
 ### Globally; For Everyone
 You can install this file in `/usr/local/bin/` or `/usr/bin/` by simply downloading it, changing the permissions, then moving it to the right location.  Double check that your system's PATH includes the destination folder, otherwise users may have a hard time starting the command.
    # Download
    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
    # Make executable
    chmod +x mo
    # Move to the right folder
    sudo mv mo /usr/local/bin/
    # Test
    echo "works" | mo
 ### Locally; For Yourself
 This is very similar to installing it globally but it does not require root privileges.  It is very important that your PATH includes the destination folder otherwise it won't work.  Some local folders that are typically used are `~/bin/` and `~/.local/bin/`.
    # Download
    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
    # Make executable
    chmod +x mo
    # Ensure destination folder exists
    mkdir -p ~/.local/bin/
    # Move to the right folder
    mv mo ~/.local/bin/
    # Test
    echo "works" | mo
 ### As A Library; For A Tool
 Bash scripts can source `mo` to include the functionality in their own routines.  This usage typically would have `mo` saved to a `lib/` folder in an application and your other scripts would use `. lib/mo` to bring it into your project.
    # Download
    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
    # Move into your project folder
    mv mo ~/projects/amazing-things/lib/
 To allow it to work this way, you either should source the file (`. "lib/mo"`) or make it executable (`chmod +x lib/mo`) and run it from your scripts.
 How to Use
 ----------
 If you only plan using strings and numbers, nothing could be simpler.  In your shell script you can choose to export the variables.  The below script is [`demo/using-strings`](demo/using-strings).
    #!/usr/bin/env bash
    cd "$(dirname "$0")" # Go to the script's directory
    export TEST="This is a test"
    echo "Your message:  {{TEST}}" | ../mo
 The result?  "Your message:  This is a test".
 Using arrays adds a slight level of complexity.  *You must source `mo`.*  Look at [`demo/using-arrays`](demo/using-arrays).
    #!/usr/bin/env bash
    cd "$(dirname "$0")" # Go to the script's directory
    export ARRAY=( one two "three three three" four five )
    . ../mo # This loads the "mo" function
    cat << EOF | mo
    Here are the items in the array:
    {{#ARRAY}}
        * {{.}}
    {{/ARRAY}}
    EOF
 The result?  You get a list of the five elements in the array.  It is vital that you source `mo` and run the function when you want arrays to work because you can not execute a command and have arrays passed to that command's environment.  Instead, we first source the file to load the function and then run the function directly.
 There are more scripts available in the [demos directory](demo/) that could help illustrate how you would use this program.
 There are additional features that the program supports. Try using `mo --help` to see what is available.
 Please note that this command is written in Bash and pulls data from either the environment or (when using `--source`) from a text file that will be sourced and loaded into the environment, which means you will need to have Bash-style variables defined. Please see the examples in `demo/` for different ways you can use `mo`.
 Enhancements
 ------------
 In addition to many of the features built-in to Mustache, `mo` includes a number of unique features that make it a bit more powerful.
 ### Loop @key
 `mo` implements Handlebar's `@key` references for outputting the key inside of a loop:
 Env:
 ```bash
 myarr=( foo bar )
 # Bash v4+
 declare -A myassoc
 myassoc[hello]="mo"
 myassoc[world]="is great"
 ```
 Template:
 ```handlebars
 {{#myarr}}
 - {{@key}} {{.}}
 {{/myarr}}
 {{#myassoc}}
 * {{@key}} {{.}}
 {{/myassoc}}
 ```
 Output:
 ```markdown
 - 0 foo
 - 1 bar
 * hello mo
 * world is great
 ```
 ### Helpers / Function Arguments
 Function Arguments are not a part of the official Mustache implementation, and are more often associated with Handlebar's Helper functionality.
 `mo` allows for passing strings to functions.
 ```handlebars
 {{myfunc foo bar}}
 ```
 For security reasons, these arguments are not immediately available to function calls without a flag.
 #### with `--allow-function-arguments`
 ```bash
 myfunc() {
    # Outputs "foo, bar"
    echo "$1, $2";
 }
 ```
 #### Using `$MO_FUNCTION_ARGS`
 ```bash
 myfunc() {
    # Outputs "foo, bar"
    echo "${MO_FUNCTION_ARGS[0]}, ${MO_FUNCTION_ARGS[1]}";
 }
 ```
 ### Triple Mustache, Parenthesis, and Quotes
 Normally, triple mustache syntax, such as `{{{var}}}` will avoid HTML escaping of the variable. Because HTML escaping is not supported in `mo`, this is now used differently. Anything within braces will be looked up and the values will be concatenated together and the result will be treated as a value. Anything in parenthesis will be looked up, concatenated, and treated as a name. Also, anything in single quotes is passed as a value; double quoted things first are unescaped and then passed as a value.
 ```
 # Example input
 var=abc
 user=admin
 admin=Administrator
 u=user
 abc=([0]=zero [1]=one [2]=two)
 ```
 | Mustache syntax | Resulting output | Notes |
 |-----------------|------------------|-------|
 | `{{var}}` | `abc` | Normal behavior |
 | `{{var us}}` | `abcus` | Concatenation |
 | `{{'var'}}` | `var` | Passing as a value |
 | `{{"a\tb"}}` | `a       b` | There was an escaped tab in the value |
 | `{{u}}` | `user` | Normal behavior |
 | `{{{u}}}` | `user` | Look up "$u", treat as the value `{{'user'}}` |
 | `{{(u)}}` | `admin` | Look up "$u", treat as the name `{{user}}` |
 | `{{var user}}` | `abcuser` | Concatenation |
 | `{{(var '.1')}}` | `one` | Look up "$var", treat as "abc", then concatenate ".1" and look up `{{abc.1}}` |
 In double-quoted strings, the following escape sequences are defined.
 * `\"` - Quote
 * `\b` - Bell
 * `\e` - Escape (note that Bash typically uses $'\E' for the same thing)
 * `\f` - Form feed
 * `\n` - Newline
 * `\r` - Carriage return
 * `\t` - Tab
 * `\v` - Vertical tab
 * Anything else will skip the `\` and place the next character. However, this implementation is allowed to change in the future if a different escape character mapping becomes commonplace.
 Environment Variables and Functions
 -----------------------------------
 There are several functions and variables used to process templates. `mo` reserves variables that start with `MO_` for variables exposing data or configuration, functions starting with `mo::`, and local variables starting with `mo[A-Z]`. You are welcome to use internal functions, though only ones that are marked as "Public" should not change their interface. Scripts may also read any of the variables.
 Functions are all executed in a subshell, with another subshell for lambdas. Thus, your lambda can't affect the parsing of a template. There's more information about lambdas when talking about tests that fail.
 * `MO_ALLOW_FUNCTION_ARGUMENTS` - When set to a non-empty value, this allows functions referenced in templates to receive additional options and arguments.
 * `MO_CLOSE_DELIMITER` - The string used when closing a tag. Defaults to "}}". Used internally.
 * `MO_CLOSE_DELIMITER_DEFAULT` - The default value of `MO_CLOSE_DELIMITER`. Used when resetting the close delimiter, such as when parsing a partial.
 * `MO_CURRENT` - Variable name to use for ".".
 * `MO_DEBUG` - When set to a non-empty value, additional debug information is written to stderr.
 * `MO_FUNCTION_ARGS` - Arguments passed to the function.
 * `MO_FAIL_ON_FILE` - If a filename from the command-line is missing or a partial does not exist, abort with an error.
 * `MO_FAIL_ON_FUNCTION` - If a function returns a non-zero status code, abort with an error.
 * `MO_FAIL_ON_UNSET` - When set to a non-empty value, expansion of an unset env variable will be aborted with an error.
 * `MO_FALSE_IS_EMPTY` - When set to a non-empty value, the string "false" will be treated as an empty value for the purposes of conditionals.
 * `MO_OPEN_DELIMITER` - The string used when opening a tag. Defaults to "{{". Used internally.
 * `MO_OPEN_DELIMITER_DEFAULT` - The default value of MO_OPEN_DELIMITER. Used when resetting the open delimiter, such as when parsing a partial.
 * `MO_ORIGINAL_COMMAND` - Used to find the `mo` program in order to generate a help message.
 * `MO_PARSED` - Content that has made it through the template engine.
 * `MO_STANDALONE_CONTENT` - The unparsed content that preceeded the current tag. When a standalone tag is encountered, this is checked to see if it only contains whitespace. If this and the whitespace condition after a tag is met, then this will be reset to $'\n'.
 * `MO_UNPARSED` - Template content yet to make it through the parser.
 Concessions
 -----------
 I admit that implementing everything in bash just doesn't make a lot of sense.  For example, the following things just don't work because they don't really mesh with the "bash way".
 Pull requests to solve the following issues would be helpful.
 ### Mustache Syntax
 * Dotted names are supported but only for associative arrays (Bash 4).  See [`demo/associative-arrays`](demo/associative-arrays) for an example.
 * There's no "top level" object, so `echo '{{.}}' | ./mo` does not do anything useful.  In other languages you can say the data for the template is a string and in `mo` the data is always the environment.  Luckily this type of usage is rare and `{{.}}` works great when iterating over an array.
 * [Parents](https://mustache.github.io/mustache.5.html#Parents), where a template can override chunks of a partial, are not supported.
 * HTML encoding is not built into `mo`.  `{{{var}}}`, `{{&var}}` and `{{var}}` all do the same thing.  `echo '{{TEST}}' | TEST='<b>' mo` will give you "`<b>`" instead of "`&gt;b&lt;`".
 ### General Scripting Issues
 * Using binary files as templates is simply not allowed.
 * Bash does not support anything more complex than strings/numbers inside of associative arrays.  I'm not able to add objects nor nested arrays to bash - it's just a shell after all!
 * You must make sure the data is in the environment when `mo` runs.  The easiest way to do that is to source `mo` in your shell script after setting up lots of other environment variables / functions.
 Developing
 ----------
 Check out the code and hack away.  Please add tests to show off bugs before fixing them.  New functionality should also be covered by a test.
 First, make sure you install Node.js. After that, run `npm run install-tests` to get the dependencies and the repository of YAML tests. Run `npm run test` to run the JavaScript tests. There's over 100 of them, which is great. Not all of them will pass, but that's discussed later.
 When submitting patches, make sure to run them past [ShellCheck] and ensure no problems are found.  Also please use Bash 3 syntax if you are manipulating arrays.
 ### Porting and Backporting
 In case of problems, setting MO_DEBUG to a non-empty value will give you LOTS of output.
    MO_DEBUG=1 ./mo my-template
 ### Failed Specs
 It is acceptable for some of the official spec tests to fail. The spec runner has specific exclusions and overrides to test similar functionality that avoid the following issues.
 * Using `{{.}}` outside of a loop - In order to access any variable, you must use its name. In a loop, `{{.}}` will refer to the current value, but outside the loop you are unable to use this dot notation because there is no current value.
 * Deeply nested data - Bash doesn't support complex data structure. Basically, just strings and arrays of strings.
 * Interpolation; Multiple Calls:  This fails because lambdas execute in a subshell so their output can be captured. If you want state to be preserved, you will need to write it outside of the current environment and load it again later.
 * HTML Escaping - Since bash is not often executed in a web server context, it makes no sense to have the output escaped as HTML.  Performing shell escaping of variables may be an option in the future if there's a demand.
 * Lambdas - Function results are *not* automatically interpreted again. If you want to parse the results as Mustache content, use `mo::parse`. When they use `mo::parse`, it will use the current delimiters.
 For lambdas, these examples may help.
 ```bash
 # Retrieve content into a variable.
 content=$(cat)
 # Retrieve all content and do not trim newlines at the end.
 content=$(cat; echo -n '.')
 content=${content%.}
 # Parse content using the current delimiters
 mo::parse results "This is my content. Hello, {{username}}"
 echo -n "$results"
 # Parse content using the default delimiters
 MO_OPEN_DELIMITER=$MO_OPEN_DELIMITER_DEFAULT
 MO_CLOSE_DELIMITER=$MO_CLOSE_DELIMITER_DEFAULT
 mo::parse results "This is my content. Hello, {{username}}"
 echo -n "$results"
 ```
 ### Future Enhancements
 There's a few places in the code marked with `TODO` to signify areas that could use improvement.  Care to help?  Keep in mind that this uses bash exclusively, so it might not look the prettiest.
 License
 -------
 This program is licensed under an MIT license with an additional non-advertising clause.  See [LICENSE.md](LICENSE.md) for the full text.
 [Mustache]: https://mustache.github.io/
 [ShellCheck]: https://github.com/koalaman/shellcheck
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/associative-arrays
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/associative-arrays
@ -0,0 +1,19 @@
 #!/usr/bin/env bash
 cd "$(dirname "$0")" # Go to the script's directory
 declare -A DATA
 export DATA=([one]=111 [two]=222)
 . ../mo
 cat <<EOF | mo
 Accessing data directly:
    DATA: {{DATA}}
    One: {{DATA.one}}
    Two: {{DATA.two}}
 Things in DATA:
 {{#DATA}}
    Item: {{.}}
 {{/DATA}}
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/embedded-template
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/embedded-template
@ -0,0 +1,28 @@
 #!/usr/bin/env bash
 #
 # This embeds a template in the script without using strange `cat` syntax.
 # shellcheck disable=SC1083 disable=SC1010 disable=SC1054 disable=SC1073 disable=SC1072 disable=SC1056 disable=SC1009
 cd "$(dirname "$0")" # Go to the script's directory
 export NAME="Tyler"
 export VEHICLE="Ford Explorer"
 export OVERDUE_LENGTH="2 months"
 export OPTIONS=(
    "Call a service representative at 1-800-000-0000 to discuss payment options"
    "Return the vehicle immediately and pay a fine of 1 million dollars"
 )
 . ../mo
 sed '0,/^# END/ d' "$(basename "$0")" | mo
 exit
 # END
 Attention {{NAME}},
 You need to pay for the {{VEHICLE}} you are leasing from us.
 It has been {{OVERDUE_LENGTH}} since your last payment.
 At this point you must do one of the following:
 {{#OPTIONS}}
 * {{.}}
 {{/OPTIONS}}
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/fun-trip.mo
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/fun-trip.mo
@ -0,0 +1,3 @@
 Hello, {{NAME}}
 I hope your {{TIME_PERIOD}} was fun.
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args
@ -0,0 +1,31 @@
 #!/usr/bin/env bash
 #
 # This sources a simple script with the env. variables needed for the template.
 cd "$(dirname "$0")" # Go to the script's directory
 source ../mo
 export NAME="Alex"
 export ARRAY=( AAA BBB CCC )
 # Include an external template
 INCLUDE() {
    # shellcheck disable=SC2031
    cat "${MO_FUNCTION_ARGS[0]}"
 }
 # Print section title
 TITLE() {
    echo "+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+"
    # shellcheck disable=SC2031
    echo "${MO_FUNCTION_ARGS[0]}"
    echo "+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+"
 }
 cat <<EOF | mo -u
 {{TITLE 'Part 1'}}
 {{INCLUDE 'function-args-part1'}}
 {{TITLE 'Part 2'}}
 {{INCLUDE 'function-args-part2'}}
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args-part1
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args-part1
@ -0,0 +1 @@
 Hello, my name is {{NAME}}.
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args-part2
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args-part2
@ -0,0 +1,3 @@
 {{#ARRAY}}
    * {{.}}
 {{/ARRAY}}
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-advanced-looping
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-advanced-looping
@ -0,0 +1,42 @@
 #!/usr/bin/env bash
 cd "$(dirname "$0")" # Go to the script's directory
 EVERY_REPO() {
    # The block contents come in through standard input. Capture it here.
    content=$(cat)
    echo "# Starting EVERY_REPO"
    # Get list of repos
    for REPO in "${REPOS[@]}"; do
        echo "## Looping one time for repo: $REPO"
        # String replace REPO_ with the name
        # This changes everything in the content block of the template.
        # It rewrites {{__REPO__.name}} into {{resque.name}}, for instance.
        # You can prefix your environment variables and do other things as well.
        echo "$content" | sed "s/__REPO__/${REPO}/"
        echo "## Looped one time for repo: $REPO"
    done
    echo "# Finished EVERY_REPO"
 }
 REPOS=(resque hub rip)
 declare -A resque hub rip
 resque=([name]=Resque [url]=http://example.com/resque)
 hub=([name]=Hub [url]=http://example.com/hub)
 rip=([name]=Rip [url]=http://example.com/rip)
 . ../mo
 cat <<EOF | mo
 {{#EVERY_REPO}}
 The repo is __REPO__
    Name:  {{__REPO__.name}}
    URL:  {{__REPO__.url}}
 {{/EVERY_REPO}}
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-building-json
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-building-json
@ -0,0 +1,39 @@
 #!/usr/bin/env bash
 cd "$(dirname "$0")" # Go to the script's directory
 # Detect if this is the first item and write a comma if it is.
 # Normally, I would track this using a variable, like so:
 #
 # COMMA_IF_NOT_FIRST_FLAG=false
 # COMMA_IF_NOT_FIRST() {
 #     $COMMA_IF_NOT_FIRST || echo ","
 #     COMMA_IF_NOT_FIRST_FLAG=true
 # }
 #
 # Since this function executes in a subshell, that approach will not work.
 # Instead, we peek inside mo and see what is being processed. If the variable
 # name in moParse() changes, this will need to get updated as well. An
 # alternate variable that is usable is context, but that is in moLoop() and is
 # two levels levels deep instead of just one.
 COMMA_IF_NOT_FIRST() {
    [[ "${moCurrent#*.}" != "0" ]] && echo ","
 }
 # Create an array that will be embedded into the JSON. If you are manipulating
 # JSON, might I suggest you look at using jq? It's really good at processing
 # JSON.
 items=(
    '{"position":"one","url":"1"}'
    '{"position":"two","url":"2"}'
    '{"position":"three","url":"3"}'
 )
 . ../mo
 cat <<EOF | mo
 {
    {{#items}}
    {{COMMA_IF_NOT_FIRST}}
    {{.}}
    {{/items}}
 }
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-foreach
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-foreach
@ -0,0 +1,50 @@
 #!/usr/bin/env bash
 # Example for how #29 can get implemented.
 cd "$(dirname "$0")" # Go to the script's directory
 foreach() {
    # Trying to use unique names
    local foreachSourceName foreachIterator foreachEvalString foreachContent
    foreachContent=$(cat)
    local x
    x=("${@}")
    if [[ "$2" != "as" && "$2" != "in" ]]; then
        echo "Invalid foreach - bad format."
    elif [[ "$(declare -p "$1")" != "declare -"[aA]* ]]; then
        echo "$1 is not an array"
    else
        foreachSourceName="${1}[@]"
        for foreachIterator in "${!foreachSourceName}"; do
            foreachEvalString=$(declare -p "$foreachIterator")
            foreachEvalString="declare -A $3=${foreachEvalString#*=}"
            eval "$foreachEvalString"
            echo "$foreachContent" | mo
        done
    fi
 }
 # The links are associative arrays
 declare -A resque hub rip
 resque=([name]=Resque [url]=http://example.com/resque)
 hub=([name]=Hub [url]=http://example.com/hub)
 rip=([name]=Rip [url]=http://example.com/rip)
 # This is a list of the link arrays
 links=(resque hub rip)
 # Source mo in order to work with arrays
 . ../mo
 # Process the template
 cat <<EOF | mo --allow-function-arguments
 Here are your links:
 {{#foreach 'links' 'as' 'link'}}
 * [{{link.name}}]({{link.url}})
 {{/foreach 'links' 'as' 'link'}}
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/important-file
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/important-file
@ -0,0 +1,28 @@
 #!/usr/bin/env bash
 cd "$(dirname "$0")"/..
 date-string() {
    date
 }
 wrapper() {
    echo -n "*** $(cat) ***"
 }
 export IP=127.0.0.1
 export ALLOWED_HOSTS=( 192.168.0.1 192.168.0.2 192.168.0.3 )
 . ./mo  # Keep in mind this script is executing in the parent directory
 cat <<EOF | mo
 # {{#wrapper}}OH SO IMPORTANT{{/wrapper}}
 # This file automatically generated at {{date-string}}
 home_ip={{IP}}
 # ALLOWED HOSTS
 {{#ALLOWED_HOSTS}}allowed_host={{.}}
 {{/ALLOWED_HOSTS}}{{^ALLOWED_HOSTS}}# No allowed hosts{{/ALLOWED_HOSTS}}
 # DENIED HOSTS
 {{#DENIED_HOSTS}}denied_host={{.}}
 {{/DENIED_HOSTS}}{{^DENIED_HOSTS}}# No denied hosts{{/DENIED_HOSTS}}
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/indented-partial
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/indented-partial
@ -0,0 +1,15 @@
 #!/usr/bin/env bash
 export data=$'line 1\nline 2'
 cat <<EOF | ../mo
 Here is a partial without an indent:
 {{> partial}}
 And here's the same partial with a 4-space indent:
    {{> partial}}
 :-)
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/partial
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/partial
@ -0,0 +1 @@
 {{data}}
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/sourcing
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/sourcing
@ -0,0 +1,13 @@
 #!/usr/bin/env bash
 #
 # This sources a simple script with the env. variables needed for the template.
 cd "$(dirname "$0")" # Go to the script's directory
 cat <<EOF | ../mo --source=sourcing.vars
 Hello, my name is {{NAME}}.
 And this is ARRAY's conntents:
 {{#ARRAY}}
    * {{.}}
 {{/ARRAY}}
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/sourcing.vars
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/sourcing.vars
@ -0,0 +1,2 @@
 export NAME="Alex"
 export ARRAY=( AAA BBB CCC )
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/using-arrays
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/using-arrays
@ -0,0 +1,10 @@
 #!/usr/bin/env bash
 cd "$(dirname "$0")" # Go to the script's directory
 export ARRAY=( one two "three three three" four five )
 . ../mo
 cat << EOF | mo
 Here are the items in the array:
 {{#ARRAY}}
    * {{.}}
 {{/ARRAY}}
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/using-strings
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/using-strings
@ -0,0 +1,7 @@
 #!/usr/bin/env bash
 #
 # This example does not source `mo` and is intentionally restricted to
 # variables that are not arrays.
 cd "$(dirname "$0")" # Go to the script's directory
 export TEST="This is a test"
 echo "Your message:  {{TEST}}" | ../mo
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/writing-out-braces
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/demo/writing-out-braces
@ -0,0 +1,12 @@
 #!/usr/bin/env bash
 cd "$(dirname "$0")" # Go to the script's directory
 export OPEN="{{"
 export CLOSE="}}"
 cat <<'EOF' | mo
 You can use environment variables to write output that has double braces.
    {{OPEN}}sampleTag{{CLOSE}}
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/make-api-doc
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/make-api-doc
@ -0,0 +1,20 @@
 #!/usr/bin/env bash
 #
 # This requires tomdoc.sh to be in your PATH.
 # https://github.com/tests-always-included/tomdoc.sh
 cd "${0%/*}" || exit 1
 cat <<'EOF'
 API / Function Documentation
 ============================
 This documentation is generated automatically from the source of [mo] thanks to [tomdoc.sh].
 EOF
 sed 's/# shellcheck.*//' mo | tomdoc.sh -m
 cat <<'EOF'
 [mo]: ./mo
 [tomdoc.sh]: https://github.com/tests-always-included/tomdoc.sh
 EOF
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/mo
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/mo
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/run-spec
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/run-spec
@ -0,0 +1,22 @@
 #!/usr/bin/env bash
 # Install or update the specs
 if [[ ! -d spec ]]; then
    git clone https://github.com/mustache/spec.git spec
 else
    (
        cd spec
        git pull
    )
 fi
 if [[ "$BASH_VERSION" == 3.* ]]; then
    echo "WARNING! Specs assume you are using a version of Bash with associative arrays!"
 fi
 # Actually run the specs
 node run-spec.js spec/specs/*.json
 if [[ "$BASH_VERSION" == 3.* ]]; then
    echo "Some tests may have failed because they assume Bash supports associative arays"
 fi
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/run-spec.js
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/run-spec.js
@ -0,0 +1,512 @@
 #!/usr/bin/env node
 const exec = require("child_process").exec;
 const fsPromises = require("fs").promises;
 // Skip or override portions of tests. The goal is to still have as much
 // coverage as possible, but skip things that Bash does not support.
 //
 // To skip a test, define a "skip" property and explain why the test is
 // skipped.
 //
 // To override any test property, just define that property. It replaces the
 // original property, not augmenting it.
 const testOverrides = {
    "Comments -> Variable Name Collision": {
        // Can't use variables with exclamation points easily
        data: {
            comment: 4
        }
    },
    "Interpolation -> Dotted Names - Arbitrary Depth": {
        skip: "Not able to use more than one level of depth"
    },
    "Interpolation -> Dotted Names - Broken Chain Resolution": {
        data: {
            a: {
                b: "wrong"
            },
            name: "Jim"
        },
        template: '"{{a.name}}" == ""'
    },
    "Interpolation -> Dotted Names - Initial Resolution": {
        data: {
            a: {
                name: "Phil"
            },
            name: "Wrong"
        },
        template: "\"{{#a}}{{name}}{{/a}}\" == \"Phil\""
    },
    "Interpolation -> Implicit Iterators - Ampersand": {
        skip: "HTML escaping is not supported"
    },
    "Interpolation -> Implicit Iterators - Basic Interpolation": {
        skip: "Can not use {{.}} outside of a loop. Need to use a variable name."
    },
    "Interpolation -> Implicit Iterators - Basic Integer Interpolation": {
        skip: "Can not use {{.}} outside of a loop. Need to use a variable name."
    },
    "Interpolation -> Implicit Iterators - Triple Mustache": {
        skip: "Can not use {{.}} outside of a loop. Need to use a variable name."
    },
    "Interpolation -> HTML Escaping": {
        skip: "HTML escaping is not supported"
    },
    "Interpolation -> Implicit Iterators - HTML Escaping": {
        skip: "HTML escaping is not supported"
    },
    "Inverted -> Dotted Names - Falsey": {
        data: {
            a: {
                b: ""
            }
        },
        template: '"{{^a.b}}Not Here{{/a.b}}" == "Not Here"'
    },
    "Inverted -> Dotted Names - Truthy": {
        data: {
            a: {
                b: "1"
            }
        },
        template: '"{{^a.b}}Not Here{{/a.b}}" == ""'
    },
    "Lambdas -> Escaping": {
        skip: "HTML escaping is not supported"
    },
    "Lambdas -> Interpolation - Alternate Delimiters": {
        skip: "There is no difference between a lamba used as a value and a lambda used as a block. Both will parse using the current delimiters."
    },
    "Lambdas -> Inverted Section": {
        // This one passed mostly by accident. Correcting so the test still
        // tests what is was designed to illustrate.
        data: {
            static: "static",
            lambda: {
                __tag__: 'code',
                bash: 'false'
            }
        }
    },
    "Lambdas -> Interpolation": {
        data: {
            lambda: {
                __tag__: 'code',
                bash: 'echo -n "world"'
            }
        }
    },
    "Lambdas -> Interpolation - Expansion": {
        data: {
            lambda: {
                __tag__: 'code',
                bash: 'mo::parse result "{{planet}}"; echo -n "$result"'
            },
            planet: 'world'
        }
    },
    "Lambdas -> Interpolation - Multiple Calls": {
        skip: "Calls are not cached, but they run in isolated environments, so saving a global variable does not work."
    },
    "Lambdas -> Section": {
        data: {
            lambda: {
                __tag__: 'code',
                bash: 'if [[ "$(cat)" == "{{x}}" ]]; then echo -n yes; else echo -n no; fi'
            },
            x: "Error!"
        }
    },
    "Lambdas -> Section - Alternate Delimiters": {
        data: {
            lambda: {
                __tag__: 'code',
                bash: 'local content=$(cat); mo::parse content "$content{{planet}} => |planet|$content"; echo -n "$content"'
            },
            planet: 'Earth'
        }
    },
    "Lambdas -> Section - Expansion": {
        data: {
            lambda: {
                __tag__: 'code',
                bash: 'local content=$(cat); mo::parse content "$content{{planet}}$content"; echo -n "$content"'
            },
            planet: "Earth"
        }
    },
    "Lambdas -> Section - Multiple Calls": {
        data: {
            lambda: {
                __tag__: 'code',
                bash: 'echo -n "__$(cat)__"'
            }
        }
    },
    "Partials -> Recursion": {
        skip: "Complex objects are not supported and context is reset to the global level, so the recursion will loop forever"
    },
    "Sections -> Deeply Nested Contexts": {
        skip: "Nested objects are not supported"
    },
    "Sections -> Dotted Names - Broken Chains": {
        // Complex objects are not supported
        template: `"{{#a.b}}Here{{/a.b}}" == ""`
    },
    "Sections -> Dotted Names - Falsey": {
        // Complex objects are not supported
        data: { a: { b: false } },
        template: `"{{#a.b}}Here{{/a.b}}" == ""`
    },
    "Sections -> Dotted Names - Truthy": {
        // Complex objects are not supported
        data: { a: { b: true } },
        template: `"{{#a.b}}Here{{/a.b}}" == "Here"`
    },
    "Sections -> Implicit Iterator - Array": {
        skip: "Nested arrays are not supported"
    },
    "Sections -> List": {
        // Arrays of objects are not supported
        data: { list: [1, 2, 3] },
        template: `"{{#list}}{{.}}{{/list}}"`
    },
    "Sections -> List Context": {
        skip: "Deeply nested objects are not supported"
    },
    "Sections -> List Contexts": {
        skip: "Deeply nested objects are not supported"
    }
 };
 function specFileToName(file) {
    return file
        .replace(/.*\//, "")
        .replace(".json", "")
        .replace("~", "")
        .replace(/(^|-)[a-z]/g, function (match) {
            return match.toUpperCase();
        });
 }
 function processArraySequentially(array, callback) {
    function processCopy() {
        if (arrayCopy.length) {
            const item = arrayCopy.shift();
            return Promise.resolve(item)
                .then(callback)
                .then((singleResult) => {
                    result.push(singleResult);
                    return processCopy();
                });
        } else {
            return Promise.resolve(result);
        }
    }
    const result = [];
    const arrayCopy = array.slice();
    return processCopy();
 }
 function debug(...args) {
    if (process.env.DEBUG) {
        console.debug(...args);
    }
 }
 function makeShellString(value) {
    if (typeof value === "boolean") {
        return value ? '"true"' : '""';
    }
    if (typeof value === "string") {
        // Newlines are tricky
        return value
            .split(/\n/)
            .map(function (chunk) {
                return JSON.stringify(chunk);
            })
            .join('"\n"');
    }
    if (typeof value === "number") {
        return value;
    }
    return "ERR_CONVERTING";
 }
 function addToEnvironmentArray(name, value) {
    const result = ["("];
    value.forEach(function (subValue) {
        result.push(makeShellString(subValue));
    });
    result.push(")");
    return name + "=" + result.join(" ");
 }
 function addToEnvironmentObjectConvertedToAssociativeArray(name, value) {
    const values = [];
    for (const [k, v] of Object.entries(value)) {
        if (typeof v === "object") {
            if (v) {
                // An object - abort
                return `# ${name}.${k} is an object that can not be converted to an associative array`;
            }
            // null
            values.push(`[${k}]=`);
        } else {
            values.push(`[${k}]=${makeShellString(v)}`);
        }
    }
    return `declare -A ${name}\n${name}=(${values.join(" ")})`;
 }
 function addToEnvironmentObject(name, value) {
    if (!value) {
        // null
        return `#${name} is null`;
    }
    if (value.__tag__ === "code") {
        return `${name}() { ${value.bash || 'echo "NO BASH VERSION OF CODE"'}; }`;
    }
    return addToEnvironmentObjectConvertedToAssociativeArray(name, value);
 }
 function addToEnvironment(name, value) {
    if (Array.isArray(value)) {
        return addToEnvironmentArray(name, value);
    }
    if (typeof value === "object") {
        return addToEnvironmentObject(name, value);
    }
    return `${name}=${makeShellString(value)}`;
 }
 function buildScript(test) {
    const script = ["#!/usr/bin/env bash"];
    Object.keys(test.data).forEach(function (name) {
        script.push(addToEnvironment(name, test.data[name]));
    });
    script.push(". ./mo");
    script.push("mo spec-runner/spec-template");
    script.push("");
    return script.join("\n");
 }
 function writePartials(test) {
    return processArraySequentially(
        Object.keys(test.partials),
        (partialName) => {
            debug("Writing partial:", partialName);
            return fsPromises.writeFile(
                "spec-runner/" + partialName,
                test.partials[partialName]
            );
        }
    );
 }
 function setupEnvironment(test) {
    return cleanup()
        .then(() => fsPromises.mkdir("spec-runner/"))
        .then(() =>
            fsPromises.writeFile("spec-runner/spec-script", test.script)
        )
        .then(() =>
            fsPromises.writeFile("spec-runner/spec-template", test.template)
        )
        .then(() => writePartials(test));
 }
 function executeScript(test) {
    return new Promise((resolve) => {
        exec(
            "bash spec-runner/spec-script 2>&1",
            {
                timeout: 2000
            },
            (err, stdout) => {
                if (err) {
                    test.scriptError = err.toString();
                }
                test.output = stdout;
                resolve();
            }
        );
    });
 }
 function cleanup() {
    return fsPromises.rm("spec-runner/", { force: true, recursive: true });
 }
 function detectFailure(test) {
    if (test.scriptError) {
        return true;
    }
    if (test.output !== test.expected) {
        return true;
    }
    return false;
 }
 function showFailureDetails(test) {
    console.log(`FAILURE: ${test.fullName}`);
    console.log("");
    console.log(test.desc);
    console.log("");
    console.log(JSON.stringify(test, null, 4));
 }
 function applyTestOverrides(test) {
    const overrides = testOverrides[test.fullName];
    const originals = {};
    if (!overrides) {
        return;
    }
    for (const [key, value] of Object.entries(overrides)) {
        originals[key] = test[key];
        test[key] = value;
    }
    test.overridesApplied = true;
    test.valuesBeforeOverride = originals;
 }
 function runTest(testSet, test) {
    test.partials = test.partials || {};
    test.fullName = `${testSet.name} -> ${test.name}`;
    applyTestOverrides(test);
    test.script = buildScript(test);
    if (test.skip) {
        debug("Skipping test:", test.fullName, `(${test.skip})`);
        return Promise.resolve();
    }
    debug("Running test:", test.fullName);
    return setupEnvironment(test)
        .then(() => executeScript(test))
        .then(cleanup)
        .then(() => {
            test.isFailure = detectFailure(test);
            if (test.isFailure) {
                showFailureDetails(test);
            } else {
                debug('Test pass:', test.fullName);
            }
        });
 }
 function processSpecFile(filename) {
    debug("Read spec file:", filename);
    return fsPromises.readFile(filename, "utf8").then((fileContents) => {
        const testSet = JSON.parse(fileContents);
        testSet.name = specFileToName(filename);
        return processArraySequentially(testSet.tests, (test) =>
            runTest(testSet, test)
        ).then(() => {
            testSet.pass = 0;
            testSet.fail = 0;
            testSet.skip = 0;
            testSet.passOverride = 0;
            for (const test of testSet.tests) {
                if (test.isFailure) {
                    testSet.fail += 1;
                } else if (test.skip) {
                    testSet.skip += 1;
                } else {
                    testSet.pass += 1;
                    if (test.overridesApplied) {
                        testSet.passOverride += 1;
                    }
                }
            }
            console.log(
                `### ${testSet.name} Results = ${testSet.pass} passed (with ${testSet.passOverride} overridden), ${testSet.fail} failed, ${testSet.skip} skipped`
            );
            return testSet;
        });
    });
 }
 // 0 = node, 1 = script, 2 = file
 if (process.argv.length < 3) {
    console.log("Specify one or more JSON spec files on the command line");
    process.exit();
 }
 processArraySequentially(process.argv.slice(2), processSpecFile).then(
    (result) => {
        console.log("=========================================");
        console.log("");
        console.log("Failed Test Summary");
        console.log("");
        let pass = 0,
            fail = 0,
            skip = 0,
            total = 0,
            passOverride = 0;
        for (const testSet of result) {
            pass += testSet.pass;
            fail += testSet.fail;
            skip += testSet.skip;
            total += testSet.tests.length;
            passOverride += testSet.passOverride;
            console.log(
                `* ${testSet.name}: ${testSet.tests.length} total, ${testSet.pass} pass (with ${passOverride} overridden), ${testSet.fail} fail, ${testSet.skip} skip`
            );
            for (const test of testSet.tests) {
                if (test.isFailure) {
                    console.log(`    * Failure: ${test.name}`);
                }
            }
        }
        console.log("");
        console.log(
            `Final result: ${total} total, ${pass} pass (with ${passOverride} overridden), ${fail} fail, ${skip} skip`
        );
        if (fail) {
            process.exit(1);
        }
    },
    (err) => {
        console.error(err);
        console.error("FAILURE RUNNING SCRIPT");
        console.error("Testing artifacts are left in script-runner/ folder");
    }
 );
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/run-tests
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/run-tests
@ -0,0 +1,162 @@
 #!/usr/bin/env bash
 #
 # Run one or more tests.
 #
 # Command-line usage to run all tests.
 #
 #     ./run-tests
 #
 # To run only one test, run "tests/test-name".
 #
 # Usage within a test as a template. Source run-tests to get functions, export
 # any necessary variables, then call runTest.
 #
 #     #!/usr/bin/env bash
 #     cd "${0%/*}" || exit 1
 #     . ../run-tests
 #
 #     export template="This is a template"
 #     export expected="This is a template"
 #     runTest
 #
 # When used within the test, you control various aspects with environment
 # variables or functions.
 #
 # - The content passed into mo is either the variable "$template" or the output
 #   of the function called template.
 # - The expected result is either "$expected" or the function called expected.
 # - The expected return code is "$returnCode" and defaults to 0.
 # - The arguments to pass to mo is the array "${arguments[@]}" and defaults to ().
 #
 # When $MO_DEBUG is set to a non-empty value, the test does not run, but mo is
 # simply executed directly. This allows for calling mo in the same manner as
 # the test but does not buffer output nor expect the output to match the
 # expected.
 #
 # When $MO_DEBUG_TEST is set to a non-empty value, the expected and actual
 # results are shown using "declare -p" to provide an easier time seeing the
 # differences, especially with whitespace.
 testCase() {
    echo "Input: $1"
    echo "Expected: $2"
 }
 indirect() {
    unset -v "$1"
    printf -v "$1" '%s' "$2"
 }
 getValue() {
    local name temp len hardSpace
    name=$2
    hardSpace=" "
    if declare -f "$name" &> /dev/null; then
        temp=$("$name"; echo -n "$hardSpace")
        len=$((${#temp} - 1))
        if [[ "${temp:$len}" == "$hardSpace" ]]; then
            temp=${temp:0:$len}
        fi
    else
        temp=${!name}
    fi
    local "$1" && indirect "$1" "$temp"
 }
 runTest() (
    local testTemplate testExpected testActual hardSpace len testReturnCode testFail
    hardSpace=" "
    . ../mo
    getValue testTemplate template
    getValue testExpected expected
    if [[ -n "${MO_DEBUG:-}" ]]; then
        echo -n "$testTemplate" | mo ${arguments[@]+"${arguments[@]}"} 2>&1
        return $?
    fi
    testActual=$(echo -n "$testTemplate" | mo ${arguments[@]+"${arguments[@]}"} 2>&1; echo -n "$hardSpace$?")
    testReturnCode=${testActual##*$hardSpace}
    testActual=${testActual%$hardSpace*}
    testFail=false
    if [[ "$testActual" != "$testExpected" ]]; then
        echo "Failure"
        echo "Expected:"
        echo "$testExpected"
        echo "Actual:"
        echo "$testActual"
        if [[ -n "${MO_DEBUG_TEST-}" ]]; then
            declare -p testExpected
            # Align the two declare outputs
            echo -n "  "
            declare -p testActual
        fi
        testFail=true
    fi
    if [[ "$testReturnCode" != "$returnCode" ]]; then
        echo "Expected return code $returnCode, but got $testReturnCode"
        testFail=true
    fi
    if [[ "$testFail" == "true" ]]; then
        return 1
    fi
    return 0
 )
 runTestFile() (
    local file=$1
    echo "Test: $file"
    "$file"
 )
 runTests() (
    PASS=0
    FAIL=0
    if [[ $# -gt 0 ]]; then
        for TEST in "$@"; do
            runTestFile "$TEST" && PASS=$((PASS + 1)) || FAIL=$((FAIL + 1))
        done
    else
        cd "${0%/*}"
        for TEST in tests/*; do
            if [[ -f "$TEST" ]]; then
                runTestFile "$TEST" && PASS=$((PASS + 1)) || FAIL=$((FAIL + 1))
            fi
        done
    fi
    echo ""
    echo "Pass: $PASS"
    echo "Fail: $FAIL"
    if [[ $FAIL -gt 0 ]]; then
        exit 1
    fi
 )
 # Clear test related variables
 template="Template not defined"
 expected="Expected not defined"
 returnCode=0
 arguments=()
 # If sourced, load functions.
 # If executed, perform the actions as expected.
 if [[ "$0" == "${BASH_SOURCE[0]}" ]] || [[ -z "${BASH_SOURCE[0]}" ]]; then
    runTests ${@+"${@}"}
 fi
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/ampersand
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/ampersand
@ -0,0 +1,9 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export thing="Works"
 export template="{{&thing}}"
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/array
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/array
@ -0,0 +1,21 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export repo=( "resque" "hub" "rip" )
 template() {
    cat <<EOF
 {{#repo}}
  <b>{{@key}} - {{.}}</b>
 {{/repo}}
 EOF
 }
 expected() {
    cat <<EOF
  <b>0 - resque</b>
  <b>1 - hub</b>
  <b>2 - rip</b>
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/assoc-array
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/assoc-array
@ -0,0 +1,25 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 declare -A repo
 # The order of the array elements can be shuffled depending on the version of
 # Bash. Keeping this to a minimal set and alphabetized seems to help.
 repo[hub]="Hub"
 repo[rip]="Rip"
 export repo
 template() {
    cat <<EOF
 {{#repo}}
  <b>{{@key}} - {{.}}</b>
 {{/repo}}
 EOF
 }
 expected() {
    cat <<EOF
  <b>hub - Hub</b>
  <b>rip - Rip</b>
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment
@ -0,0 +1,8 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export template="Wor{{!comment}}ks"
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment-newline
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment-newline
@ -0,0 +1,15 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 template() {
    cat <<EOF
 <h1>Today{{! ignore me
 and this can
 run through multiple
 lines}}.</h1>
 EOF
 }
 export expected=$'<h1>Today.</h1>\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment-with-spaces
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment-with-spaces
@ -0,0 +1,8 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export template="Wor{{! comment }}ks"
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/concatenated-variables
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/concatenated-variables
@ -0,0 +1,10 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export thing="Wor"
 export thing2="ks"
 export template="{{thing thing2}}"
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/delimiters
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/delimiters
@ -0,0 +1,9 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export thing="Works"
 export template="{{=| |=}}|thing|"
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/double-hyphen
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/double-hyphen
@ -0,0 +1,10 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export arguments=(--fail-on-file -- --help)
 export returnCode=1
 export template=""
 export expected=$'ERROR: No such file: --help\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/double-quote
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/double-quote
@ -0,0 +1,8 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export template='{{"Works"}}'
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fail-not-set
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fail-not-set
@ -0,0 +1,20 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 unset __NO_SUCH_VAR
 export POPULATED="words"
 export EMPTY=""
 export arguments=(--fail-not-set)
 export returnCode=1
 template() {
    cat <<EOF
 Populated: {{POPULATED}};
 Empty: {{EMPTY}};
 Unset: {{__NO_SUCH_VAR}};
 EOF
 }
 export expected=$'ERROR: Environment variable not set: __NO_SUCH_VAR\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fail-on-function
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fail-on-function
@ -0,0 +1,13 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 failFunction() {
    false
 }
 export arguments=(--fail-on-function)
 export returnCode=1
 export template="Fail on function? {{failFunction}}"
 export expected=$'ERROR: Function failed with status code 1: "failFunction"\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-is-empty-arg
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-is-empty-arg
@ -0,0 +1,18 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export USER=j.doe
 export ADMIN=false
 export arguments=(--false)
 template() {
    cat <<EOF
 The user {{USER}} exists.
 {{#ADMIN}}
 WRONG - should not be an admin.
 {{/ADMIN}}
 EOF
 }
 export expected=$'The user j.doe exists.\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-is-empty-env
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-is-empty-env
@ -0,0 +1,18 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export USER=j.doe
 export ADMIN=false
 MO_FALSE_IS_EMPTY=yeppers
 template() {
    cat <<EOF
 The user {{USER}} exists.
 {{#ADMIN}}
 WRONG - should not be an admin.
 {{/ADMIN}}
 EOF
 }
 export expected=$'The user j.doe exists.\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-list
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-list
@ -0,0 +1,16 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export person=""
 template() {
    cat <<EOF
 Shown.
 {{#person}}
  Never shown!
 {{/person}}
 EOF
 }
 export expected=$'Shown.\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/indented-partials.partial
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/indented-partials.partial
@ -0,0 +1,2 @@
 first line
 second line
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/inline-indentation
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/inline-indentation
@ -0,0 +1,2 @@
 >
 >
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/multi-line-partial.partial
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/multi-line-partial.partial
@ -0,0 +1 @@
 {{multilineData}}
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/partial.partial
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/partial.partial
@ -0,0 +1 @@
 <strong>{{.}}</strong>
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source-multiple-1.vars
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source-multiple-1.vars
@ -0,0 +1,2 @@
 export A=from1
 export B=from1
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source-multiple-2.vars
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source-multiple-2.vars
@ -0,0 +1,2 @@
 export B=from2
 export C=from2
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source.vars
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source.vars
@ -0,0 +1,5 @@
 export VAR=value
 export ARR=(1 2 3)
 declare -A ASSOC_ARR
 # Can not export associative arrays, otherwise they turn into indexed arrays
 ASSOC_ARR=([a]=AAA [b]=BBB)
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/standalone-indentation.partial
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/standalone-indentation.partial
@ -0,0 +1,3 @@
 |
 {{content}}
 |
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function
@ -0,0 +1,25 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export name=Willy
 wrapped() {
    # Wrapping 'cat' in a subshell eats the trailing whitespace
    # The echo adds a newline, which is preserved.
    echo "<b>$(cat)</b>"
 }
 template() {
    cat <<EOF
 {{#wrapped}}
  {{name}} is awesome.
 {{/wrapped}}
 ... this is the last line.
 EOF
 }
 # We don't expect {{name}} to be changed. The function returns whatever content
 # that should be the result. There is a separate test where the function handles
 # parsing mustache tags.
 export expected=$'<b>  {{name}} is awesome.</b>\n... this is the last line.\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function-alternate-delimiters
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function-alternate-delimiters
@ -0,0 +1,16 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export planet=Earth
 lambda() {
    local content
    content=$(cat)
    mo::parse content "$content{{planet}} => |planet|$content"
    echo -n "$content"
 }
 export template="{{= | | =}}<|#lambda|-|/lambda|>"
 export expected="<-{{planet}} => Earth->"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function-args
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function-args
@ -0,0 +1,35 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export name=Willy
 MO_ALLOW_FUNCTION_ARGUMENTS=true
 pipeTo() {
    cat | "$1"
 }
 testArgs() {
    printf "%d" "$#"
    # Display all arguments
    printf " %q" ${@+"$@"}
 }
 template() {
    cat <<EOF
 No args: {{testArgs}} - done
 One arg: {{testArgs 'one'}} - done
 Getting name in a string: {{testArgs {"The name is " name}}} - done
 Reverse this: {{#pipeTo "rev"}}abcde{{/pipeTo "rev"}}
 EOF
 }
 expected() {
    cat <<EOF
 No args: 0 '' - done
 One arg: 1 one - done
 Getting name in a string: 1 The\ name\ is\ Willy - done
 Reverse this: edcba
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function-args-read
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function-args-read
@ -0,0 +1,42 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 testArgs() {
    local args
    # shellcheck disable=SC2031
    args=$(declare -p MO_FUNCTION_ARGS)
    # The output from declare -p could look like these
    #     declare -a MO_FUNCTION_ARGS=([0]="one")
    #     declare -ax MO_FUNCTION_ARGS='([0]="one")'
    # Trim leading declare statement and variable name
    args="${args#*=}"
    # If there are any quotes, remove them. The function arguments will always
    # be an array.
    if [[ "${args:0:1}" == "'" ]]; then
        args=${args#\'}
        args=${args%\'}
    fi
    echo -n "$args"
 }
 template() {
    cat <<EOF
 No args: {{testArgs}} - done
 One arg: {{testArgs 'one'}} - done
 Multiple arguments: {{testArgs 'aa' 'bb' 'cc' 'x' "" '!' '{[_.|' }} - done
 Evil: {{testArgs bla; cat /etc/issue}} - done
 EOF
 }
 expected() {
    cat <<EOF
 No args: () - done
 One arg: ([0]="one") - done
 Multiple arguments: ([0]="aa" [1]="bb" [2]="cc" [3]="x" [4]="" [5]="!" [6]="{[_.|") - done
 Evil: ([0]="" [1]="" [2]="") - done
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function-with-more-parsing
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/function-with-more-parsing
@ -0,0 +1,28 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export name=Willy
 wrapped() {
    local content
    # Wrapping 'cat' in a subshell eats the trailing whitespace
    content="<b>$(cat)</b>"
    # Parse the content using mustache
    mo::parse content "$content"
    # The echo adds a newline, which is preserved.
    echo "$content"
 }
 template() {
    cat <<EOF
 {{#wrapped}}
  {{name}} is awesome.
 {{/wrapped}}
 ... this is the last line.
 EOF
 }
 export expected=$'<b>  Willy is awesome.</b>\n... this is the last line.\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/globals-in-loop
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/globals-in-loop
@ -0,0 +1,28 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export STR=abc
 export DATA=(111 222)
 template() {
    cat <<EOF
 Issue #7
 {{STR}}
 {{#DATA}}
    Item: {{.}}
    String: {{STR}}
 {{/DATA}}
 EOF
 }
 expected() {
    cat <<EOF
 Issue #7
 abc
    Item: 111
    String: abc
    Item: 222
    String: abc
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/help
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/help
@ -0,0 +1,101 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export arguments=(--help)
 expected() {
    cat <<'EOF'
 Mo is a mustache template rendering software written in bash.  It inserts
 environment variables into templates.
 Simply put, mo will change {{VARIABLE}} into the value of that
 environment variable.  You can use {{#VARIABLE}}content{{/VARIABLE}} to
 conditionally display content or iterate over the values of an array.
 Learn more about mustache templates at https://mustache.github.io/
 Simple usage:
   mo [OPTIONS] filenames...
 Options:
   --allow-function-arguments
         Permit functions to be called with additional arguments. Otherwise,
         the only way to get access to the arguments is to use the
         MO_FUNCTION_ARGS environment variable.
   -d, --debug
         Enable debug logging to stderr.
   -u, --fail-not-set
         Fail upon expansion of an unset variable. Will silently ignore by
         default. Alternately, set MO_FAIL_ON_UNSET to a non-empty value.
   -x, --fail-on-function
         Fail when a function returns a non-zero status code instead of
         silently ignoring it. Alternately, set MO_FAIL_ON_FUNCTION to a
         non-empty value.
   -f, --fail-on-file
         Fail when a file (from command-line or partial) does not exist.
         Alternately, set MO_FAIL_ON_FILE to a non-empty value.
   -e, --false
         Treat the string "false" as empty for conditionals. Alternately,
         set MO_FALSE_IS_EMPTY to a non-empty value.
   -h, --help
         This message.
   -s=FILE, --source=FILE
         Load FILE into the environment before processing templates.
         Can be used multiple times. The file must be a valid shell script
         and should only contain variable assignments.
   -o=DELIM, --open=DELIM
         Set the opening delimiter. Default is "{{".
   -c=DELIM, --close=DELIM
         Set the closing delimiter. Default is "}}".
   --    Indicate the end of options. All arguments after this will be
         treated as filenames only. Use when filenames may start with
         hyphens.
 Mo uses the following environment variables:
 MO_ALLOW_FUNCTION_ARGUMENTS - When set to a non-empty value, this allows
    functions referenced in templates to receive additional options and
    arguments.
 MO_CLOSE_DELIMITER - The string used when closing a tag. Defaults to "}}".
    Used internally.
 MO_CLOSE_DELIMITER_DEFAULT - The default value of MO_CLOSE_DELIMITER. Used
    when resetting the close delimiter, such as when parsing a partial.
 MO_CURRENT - Variable name to use for ".".
 MO_DEBUG - When set to a non-empty value, additional debug information is
    written to stderr.
 MO_FUNCTION_ARGS - Arguments passed to the function.
 MO_FAIL_ON_FILE - If a filename from the command-line is missing or a
    partial does not exist, abort with an error.
 MO_FAIL_ON_FUNCTION - If a function returns a non-zero status code, abort
    with an error.
 MO_FAIL_ON_UNSET - When set to a non-empty value, expansion of an unset env
    variable will be aborted with an error.
 MO_FALSE_IS_EMPTY - When set to a non-empty value, the string "false" will
    be treated as an empty value for the purposes of conditionals.
 MO_OPEN_DELIMITER - The string used when opening a tag. Defaults to "{{".
    Used internally.
 MO_OPEN_DELIMITER_DEFAULT - The default value of MO_OPEN_DELIMITER. Used
    when resetting the open delimiter, such as when parsing a partial.
 MO_ORIGINAL_COMMAND - Used to find the `mo` program in order to generate a
    help message.
 MO_PARSED - Content that has made it through the template engine.
 MO_STANDALONE_CONTENT - The unparsed content that preceeded the current tag.
    When a standalone tag is encountered, this is checked to see if it only
    contains whitespace. If this and the whitespace condition after a tag is
    met, then this will be reset to $'\n'.
 MO_UNPARSED - Template content yet to make it through the parser.
 Mo is under a MIT style licence with an additional non-advertising clause.
 See LICENSE.md for the full text.
 This is open source!  Please feel free to contribute.
 https://github.com/tests-always-included/mo
 MO_VERSION=3.0.7
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/indented-partials
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/indented-partials
@ -0,0 +1,56 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export thisIsTrue=true
 template() {
    cat <<EOF
 With spacing
    {{> fixtures/indented-partials.partial}}
    {{> fixtures/indented-partials.partial}}
 Without spacing
    {{> fixtures/indented-partials.partial}}
    {{> fixtures/indented-partials.partial}}
 With text
    {{> fixtures/indented-partials.partial}}
    text
    {{> fixtures/indented-partials.partial}}
 In a conditional
 {{#thisIsTrue}}
    {{> fixtures/indented-partials.partial}}
 {{/thisIsTrue}}
 EOF
 }
 expected() {
    cat <<EOF
 With spacing
    first line
    second line
    first line
    second line
 Without spacing
    first line
    second line
    first line
    second line
 With text
    first line
    second line
    text
    first line
    second line
 In a conditional
    first line
    second line
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/inline-indentation
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/inline-indentation
@ -0,0 +1,19 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export data="|"
 template() {
    cat <<EOF
  {{data}}  {{> fixtures/inline-indentation}}
 EOF
 }
 expected() {
    cat <<EOF
  |  >
 >
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/internal-whitespace
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/internal-whitespace
@ -0,0 +1,9 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export boolean=true
 export template=$' | {{#boolean}} {{! Important Whitespace }}\n {{/boolean}} | \n'
 export expected=$' |  \n  | \n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/invalid-option
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/invalid-option
@ -0,0 +1,11 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export person=""
 export template=""
 export returnCode=1
 export arguments=(--something)
 export expected=$'ERROR: Unknown option: --something (See --help for options)\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/inverted
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/inverted
@ -0,0 +1,18 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export repo=()
 template() {
    cat <<EOF
 {{#repo}}
  <b>{{.}}</b>
 {{/repo}}
 {{^repo}}
  No repos :(
 {{/repo}}
 EOF
 }
 export expected=$'  No repos :(\n'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/issue-75
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/issue-75
@ -0,0 +1,9 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export uv
 export template='{{^uv}}OK{{/uv}}{{#uv}}FAIL{{/uv}}'
 export expected='OK'
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/list-contexts
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/list-contexts
@ -0,0 +1,16 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export a=foo
 export b=wrong
 declare -A sec
 sec=([b]="bar")
 export sec
 declare -A c
 c=([d]="baz")
 export c
 export template="{{#sec}}{{a}} {{b}} {{c.d}}{{/sec}}"
 export expected="foo bar baz"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/miss
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/miss
@ -0,0 +1,24 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export name="Chris"
 export company="<b>GitHub</b>"
 template() {
    cat <<EOF
 * .{{name}}.
 * .{{age}}.
 * .{{company}}.
 * .{{{company}}}.
 EOF
 }
 expected() {
    cat <<EOF
 * .Chris.
 * ..
 * .<b>GitHub</b>.
 * .<b>GitHub</b>.
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/multi-line-partial
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/multi-line-partial
@ -0,0 +1,35 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export multilineData=$'line 1\nline 2'
 template() {
    cat <<EOF
 Partial:
 {{> fixtures/multi-line-partial.partial}}
 Indented:
    {{> fixtures/multi-line-partial.partial}}
 EOF
 }
 expected() {
    cat <<EOF
 Partial:
 line 1
 line 2
 Indented:
    line 1
 line 2
 EOF
    # This one looks odd, but if you check the spec spec/specs/partials.yaml,
    # name "Standalone Indentation" (mirrors "standalone-indentation" in
    # tests/), then the spec clearly shows that the indentation is applied
    # before rendering.
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/mush
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/mush
@ -0,0 +1,33 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export USER=jwerle
 export GENDER=male
 export THING=apple
 export COLOR=red
 export PERSON=tobi
 export ADJECTIVE=cool
 template() {
    cat <<EOF
 {{! this is a comment }}
 {{USER}} is {{GENDER}}
 {{THING}} is {{COLOR}}
 {{PERSON}} is {{ADJECTIVE}}
 {{USER}} is friends with {{PERSON}}
 {{var}} {{value}}
 EOF
 }
 expected() {
    cat <<EOF
 jwerle is male
 apple is red
 tobi is cool
 jwerle is friends with tobi
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/no-content
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/no-content
@ -0,0 +1,8 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export template="Works"
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/partial
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/partial
@ -0,0 +1,22 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export names=( "Tyler" "Abc" )
 template() {
    cat <<EOF
 <h2>Names</h2>
 {{#names}}
  {{> fixtures/partial.partial}}
 {{/names}}
 EOF
 }
 expected() {
    cat <<EOF
 <h2>Names</h2>
  <strong>Tyler</strong>
  <strong>Abc</strong>
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/partial-bad-file
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/partial-bad-file
@ -0,0 +1,9 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 # This file intentionally does not exist
 export template="{{>fixtures/partial-bad-file.partial}}"
 export expected=""
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/partial-missing
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/partial-missing
@ -0,0 +1,19 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export returnCode=1
 export arguments=(--fail-on-file)
 export person=""
 template() {
    cat <<EOF
 Won't be there: {{> fixtures/partial-missing.partial}}
 EOF
 }
 expected() {
    cat <<EOF
 ERROR: No such file: partial-missing.partial
 EOF
 }
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/single-quote
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/single-quote
@ -0,0 +1,8 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export template="{{'Works'}}"
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/single-variable-replacement
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/single-variable-replacement
@ -0,0 +1,9 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export thing="Works"
 export template="{{thing}}"
 export expected="Works"
 runTest
--- a/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/source
+++ b/vendor/git.knownelement.com/ExternalVendorCode/mo/tests/source
@ -0,0 +1,25 @@
 #!/usr/bin/env bash
 cd "${0%/*}" || exit 1
 . ../run-tests
 export arguments=(--source=fixtures/source.vars)
 template() {
    cat <<EOF
 {{VAR}}
 {{#ARR}}
 * {{.}}
 {{/ARR}}
 {{ASSOC_ARR.a}} {{ASSOC_ARR.b}}
 EOF
 }
 expected() {
    cat <<EOF
 value
 * 1
 * 2
 * 3
 AAA BBB
 EOF
 }
 runTest
--- a/Show More
+++ b/Show More
		`@ -0,0 +1,2 @@`
							`skill1\|1 years\|skill,1,details,and,stuff`
							`skill2\|2 years\|skill2,2,details,and,stuff,and,things`
		`@ -0,0 +1,2 @@`
							`job1,Title of job 1,January 1 1970 - January 6 1980`
							`job2,Title of Job 2,January 1 1970 - January 6 1980`
		`@ -0,0 +1 @@`
							`This directory is used by the build process. Ignore it.`
		`@ -0,0 +1 @@`
							`Working directory for the pipeline. Don't use.`
		`@ -0,0 +1,3 @@`
							`Hello, {{NAME}}`

							`I hope your {{TIME_PERIOD}} was fun.`
		`@ -0,0 +1,2 @@`
							`export NAME="Alex"`
							`export ARRAY=( AAA BBB CCC )`