@harness-forge/cli 0.1.0 → 1.0.1

package/LICENSE.md

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is 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.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  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.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  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 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. Use with the GNU Affero General Public License.
+
+  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 Affero 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 special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU 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 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 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 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.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU 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 General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  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 GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

package/README.md

@@ -1,27 +1,35 @@
-# Harness Forge
+# 🚀 Harness Forge
 
 <p align="center">
   <strong>Deterministic AI workspace bootstrapping for Codex, Claude Code, and adjacent agentic runtimes.</strong>
   <br />
-  Install skills, knowledge packs, workflows, validation gates, and repo intelligence into a real repository — without mixing package content with workspace state.
+  Install skills, knowledge packs, workflows, validation gates, and repo intelligence into a real repository - without mixing package content with workspace state.
 </p>
 
 <p align="center">
-  <!-- Replace <OWNER>, <REPO>, and workflow filenames to activate repository badges -->
-  <a href="https://github.com/<OWNER>/<REPO>/actions/workflows/ci.yml">
-    <img alt="Build" src="https://img.shields.io/github/actions/workflow/status/<OWNER>/<REPO>/ci.yml?branch=main&style=for-the-badge&logo=githubactions&label=build" />
+  <a href="https://github.com/ldilov/harness-forge/actions/workflows/ci.yml">
+    <img alt="Build" src="https://img.shields.io/github/actions/workflow/status/ldilov/harness-forge/ci.yml?branch=main&style=for-the-badge&logo=githubactions&label=build" />
   </a>
   <a href="https://www.npmjs.com/package/@harness-forge/cli">
     <img alt="npm version" src="https://img.shields.io/npm/v/@harness-forge/cli?style=for-the-badge&logo=npm" />
   </a>
-  <a href="./LICENSE.md">
-    <img alt="License: GPL-3.0" src="https://img.shields.io/badge/license-GPL--3.0-red?style=for-the-badge" />
+  <a href="https://www.npmjs.com/package/@harness-forge/cli">
+    <img alt="npm downloads per month" src="https://img.shields.io/npm/dm/@harness-forge/cli?style=for-the-badge&logo=npm&label=downloads%2Fmonth" />
+  </a>
+  <a href="https://www.npmjs.com/package/@harness-forge/cli">
+    <img alt="npm downloads 18 months" src="https://img.shields.io/npm/d18m/@harness-forge/cli?style=for-the-badge&logo=npm&label=downloads%2F18m" />
   </a>
-  <a href="https://github.com/<OWNER>/<REPO>/stargazers">
-    <img alt="GitHub stars" src="https://img.shields.io/github/stars/<OWNER>/<REPO>?style=for-the-badge&logo=github" />
+  <a href="https://github.com/ldilov/harness-forge/stargazers">
+    <img alt="GitHub stars" src="https://img.shields.io/github/stars/ldilov/harness-forge?style=for-the-badge&logo=github" />
   </a>
-  <a href="https://github.com/<OWNER>/<REPO>/issues">
-    <img alt="GitHub issues" src="https://img.shields.io/github/issues/<OWNER>/<REPO>?style=for-the-badge&logo=github" />
+  <a href="https://github.com/ldilov/harness-forge/network/members">
+    <img alt="GitHub forks" src="https://img.shields.io/github/forks/ldilov/harness-forge?style=for-the-badge&logo=github" />
+  </a>
+  <a href="https://github.com/ldilov/harness-forge/issues">
+    <img alt="GitHub issues" src="https://img.shields.io/github/issues/ldilov/harness-forge?style=for-the-badge&logo=github" />
+  </a>
+  <a href="./LICENSE.md">
+    <img alt="License: GPL-3.0" src="https://img.shields.io/badge/license-GPL--3.0-red?style=for-the-badge" />
   </a>
   <img alt="Node.js 22+" src="https://img.shields.io/badge/node-22%2B-339933?style=for-the-badge&logo=nodedotjs&logoColor=white" />
 </p>
@@ -29,8 +37,12 @@
 <p align="center">
   <a href="#-quick-start">Quick Start</a>
   ·
+  <a href="#-project-activity">Project Activity</a>
+  ·
   <a href="#-why-harness-forge">Why Harness Forge</a>
   ·
+  <a href="#-how-it-works">How It Works</a>
+  ·
   <a href="#-supported-targets">Supported Targets</a>
   ·
   <a href="#-operator-cheat-sheet">Commands</a>
@@ -39,31 +51,61 @@
 </p>
 
 > [!TIP]
-> First time here? Run `npx @harness-forge/cli` from the repository you want to equip. The CLI now acts like a guided front door for onboarding and setup.
+> First time here? Run `npx @harness-forge/cli` from the repository you want to equip. Harness Forge acts like a guided front door for onboarding on first run and a lightweight project hub after initialization.
+
+---
+
+## 📈 Project Activity
+
+<p align="center">
+  <a href="https://star-history.com/#ldilov/harness-forge&Date">
+    <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=ldilov/harness-forge&type=Date" />
+  </a>
+</p>
+
+<p align="center">
+  <strong>Point-in-time signals:</strong> live stars, forks, issues, and npm download badges above, plus a historical star timeline chart here.
+</p>
 
 ---
 
 ## ✨ Why Harness Forge?
 
-Harness Forge is a packaging-friendly agentic workspace kit built for teams that want **repeatable AI runtime setup** instead of ad hoc prompting.
+Harness Forge is a packaging-friendly agentic workspace kit for teams that want a **repeatable, inspectable, and maintenance-safe AI runtime** inside real repositories.
 
-It helps you:
+Instead of relying on one-off prompts or tribal setup knowledge, it gives you a deterministic way to:
 
-- **bootstrap a real repository** with agent-ready runtime surfaces
-- **compose language packs, framework packs, profiles, and capability bundles** through one CLI
-- **keep workspace state clean** by separating visible bridges from the hidden canonical AI layer
-- **generate repo-aware guidance** with evidence instead of guessing
-- **ship with validation gates** so install quality and support claims stay honest
+- **bootstrap agent-ready runtime surfaces** into a real repo
+- **compose targets, profiles, language packs, framework packs, and capability bundles** through one CLI
+- **keep product code and workspace state cleanly separated**
+- **generate repo-aware guidance with evidence** instead of generic assumptions
+- **validate what ships** before release, handoff, or adoption across teams
 
 ### What makes it different?
 
-| Area | What Harness Forge does |
+| Area | What Harness Forge does | Why it matters |
+| --- | --- | --- |
+| 🧠 Runtime surfaces | Materializes `AGENTS.md`, `.agents/skills/`, target runtimes, and a canonical hidden `.hforge/` layer | Agents get a predictable operating contract instead of improvising from prose |
+| 🔎 Repo intelligence | Scans, recommends, cartographs, classifies boundaries, and synthesizes instructions | Setup becomes evidence-backed rather than guess-based |
+| 🧩 Composition | Combines targets, profiles, languages, frameworks, and capability bundles | Teams can standardize without hard-coding one stack |
+| 🛡️ Validation | Ships doctor, audit, diff-install, review, and release gates | Support claims stay honest and installs stay measurable |
+| 🔁 Lifecycle | Supports bootstrap, refresh, sync, prune, upgrade, export, backup, repair, and restore flows | The workspace can evolve without becoming a black box |
+| 📊 Observability | Keeps local-first effectiveness summaries and signal files under `.hforge/observability/` | Operators can inspect what is working without sending telemetry to a backend |
+
+---
+
+## 🧬 Capability Snapshot
+
+| Domain | Coverage |
 | --- | --- |
-| 🧠 Agent runtime | Creates predictable runtime surfaces like `AGENTS.md`, `.agents/skills/`, `.codex/`, `.claude/`, and the hidden canonical `.hforge/` layer |
-| 🧩 Composition | Lets you combine targets, profiles, languages, frameworks, and capability bundles through a single install flow |
-| 🔎 Repo intelligence | Recommends packs and guidance based on the actual repo rather than generic setup assumptions |
-| 🛡️ Validation | Ships doctor, audit, review, diff-install, and release-grade checks so handoff quality stays measurable |
-| 🔁 Lifecycle | Supports bootstrap, refresh, upgrade, sync, prune, export, and flow recovery workflows over time |
+| 🎯 Runtime targets | 4 target surfaces: Codex, Claude Code, Cursor, OpenCode |
+| 🧠 Knowledge system | 14 language packs total: 5 seeded + 9 structured |
+| 🧩 Framework coverage | 12 framework packs including React, Next.js, Vite, Express, FastAPI, Django, ASP.NET Core, Spring Boot, Laravel, Symfony, Gin, and Ktor |
+| 🛠 Skills | 43 packaged skills across language engineering, workflow orchestration, operational helpers, and workload-specialized flows |
+| 🔁 Flow support | `.specify/` spec → plan → tasks → implement flow plus flow-state recovery |
+| 🔬 Intelligence | `scan`, `recommend`, `cartograph`, `classify-boundaries`, and `synthesize-instructions` |
+| 📊 Local observability | Effectiveness summaries, recommendation acceptance, hook runs, maintenance traces, and runtime summaries |
+| 🧱 Hard-task support | Recursive runtime sessions, parallel planning, merge-checks, and decision recording |
 
 ---
 
@@ -78,7 +120,7 @@ npx @harness-forge/cli
 Best for first-time operators who want:
 
 - target selection
-- setup depth selection (`quick`, `recommended`, `advanced`)
+- setup depth selection: `quick`, `recommended`, or `advanced`
 - optional module selection
 - a review step before files are written
 
@@ -88,14 +130,20 @@ Best for first-time operators who want:
 npx @harness-forge/cli bootstrap --root . --yes
 ```
 
-This path is ideal when you want Harness Forge to:
+Ideal when you want Harness Forge to:
 
-- detect supported agent runtimes already present
+- detect supported runtimes already present in the repo
 - choose a sane first-class fallback target when none are present
 - recommend repo-aware packs and bundles
 - install runtime files, discovery bridges, and workspace state in one pass
 
-### 3) Validate the install
+### 3) Enable bare `hforge` on your PATH
+
+```bash
+npx @harness-forge/cli shell setup --yes
+```
+
+### 4) Validate the install
 
 ```bash
 hforge status --root . --json
@@ -105,46 +153,207 @@ hforge audit --root . --json
 
 ---
 
-## 🧭 Onboarding Flow
+## 🧠 CLI Mental Model
+
+Harness Forge works across four layers:
+
+| Layer | Responsibility | Examples |
+| --- | --- | --- |
+| 🔍 Understand | Inspect the repo and infer what matters | `scan`, `recommend`, `cartograph`, `classify-boundaries` |
+| 🧩 Compose | Decide what should be installed | targets, profiles, language packs, framework packs, bundles |
+| 🚀 Install | Materialize runtime surfaces into the workspace | `init`, `install`, `bootstrap`, `catalog add` |
+| 🛡 Operate | Verify, maintain, and evolve the runtime | `status`, `doctor`, `audit`, `refresh`, `review`, `export`, `diff-install` |
+
+> Think: **analyze → compose → install → validate → evolve**
+
+---
+
+## ⚙️ How It Works
 
 ```mermaid
 flowchart LR
-    A[Repository] --> B[npx @harness-forge/cli]
-    B --> C[Guided onboarding or bootstrap]
-    C --> D[Visible runtime bridges]
-    C --> E[Hidden canonical .hforge layer]
-    D --> F[.agents/skills and target runtimes]
-    E --> G[Rules, knowledge, templates, runtime state]
-    G --> H[status / doctor / audit / review]
+    A[Repository] --> B[hforge recommend / scan / cartograph]
+    B --> C[Select target + profile + packs + bundles]
+    C --> D[Install visible bridges]
+    C --> E[Install hidden canonical AI layer]
+    D --> F[AGENTS.md + .agents/skills + target runtimes]
+    E --> G[.hforge/library + .hforge/templates + .hforge/runtime]
+    G --> H[status / doctor / audit / review / export]
+    H --> I[long-term maintenance, observability, and flow recovery]
 ```
 
-### Your first 10 minutes
+### The architecture in one sentence
 
-1. **Run the CLI** in the target repository.
-2. **Choose one or more targets** such as Codex or Claude Code.
-3. **Pick a setup depth**: `quick`, `recommended`, or `advanced`.
-4. **Enable optional modules** like recursive runtime, decision templates, or export support.
-5. **Review planned writes** before applying anything.
-6. **Confirm health** with `status`, `doctor`, and `audit`.
+Harness Forge keeps **agent-discoverable bridge files visible** while the **canonical runtime, knowledge, rules, templates, and generated state live under `.hforge/`**.
 
----
-
-## 📦 What gets installed?
+### What gets installed?
 
 | Surface | Purpose |
 | --- | --- |
-| `.agents/skills/` | Thin, discoverable wrappers for agent runtimes |
-| `.hforge/library/` | Hidden canonical skills, rules, templates, and knowledge packs |
+| `AGENTS.md` | Human and agent-visible root contract |
+| `.agents/skills/` | Thin, discoverable wrappers for supported runtimes |
+| `.hforge/library/skills/` | Canonical installed skill library |
+| `.hforge/library/rules/` | Canonical installed rules |
+| `.hforge/library/knowledge/` | Canonical installed knowledge packs |
+| `.hforge/templates/` | Canonical installed templates and workflow artifacts |
 | `.hforge/runtime/` | Shared runtime state, repo intelligence, findings, and decision indexes |
-| `.specify/` | Structured `spec -> plan -> tasks -> implement` workflow helpers |
+| `.hforge/generated/agent-command-catalog.json` | Machine-readable command catalog for agents |
+| `.hforge/agent-manifest.json` | Stable custom-agent contract |
+| `.hforge/generated/bin/` | Workspace-local launchers for PowerShell, CMD, and POSIX |
+| `.specify/` | Structured spec-driven delivery flow |
 | `.codex/` / `.claude/` | Target-specific runtime payloads and bridge files |
-| `.hforge/generated/` | Launchers, generated catalogs, and machine-readable runtime artifacts |
 
-### Core value proposition
+### Why this architecture helps
+
+- **Visible where runtimes need discovery**
+- **Hidden where canonical AI content should stay authoritative**
+- **Structured for upgrade, audit, and long-term maintenance**
+- **Safe to re-run through refresh, doctor, and audit workflows**
+
+---
+
+## 🎁 Benefits for teams
+
+### Reliability impact summary
+
+| Dimension | Expected impact |
+|---|---|
+| Task consistency | High improvement |
+| Install reproducibility | High improvement |
+| Runtime correctness | Medium to high improvement |
+| Cross-agent consistency | High improvement |
+| Failure recovery | Medium to high improvement |
+
+### Will it improve “memory”?
+
+Yes - but as **externalized operational memory**, not model memory
+Harness Forge does **not** make the model itself smarter or increase intrinsic memory.
+What it does is create a **persistent repo memory system and "runtime env"** around the project.
+
+### What that means
+Instead of the agent re-deriving everything on every task, the workspace can retain:
+
+- install state
+- runtime summaries
+- repo maps
+- findings
+- decision indexes
+- optional recursive session state
+- structured plans/tasks/spec artifacts
+
+### Why this matters
+This helps with:
+
+- continuity across sessions
+- less re-discovery of architecture
+- more durable reasoning traces
+- lower chance of repeating earlier mistakes
+- cleaner handoff between humans and agents
 
-- **Visible where it needs to be** for runtimes and operators
-- **Hidden where it should be** for the canonical AI layer
-- **Structured for maintenance** instead of prompt drift
+### Will it improve decision-making?
+
+Yes - mostly by constraining bad choices and improving context quality
+AI agents make worse decisions when they have:
+
+- weak architecture visibility
+- no explicit workflow
+- no capability boundaries
+- no durable task state
+- no validation feedback loop
+
+### Why it can reduce token usage
+Harness Forge can lower token burn because it gives the agent:
+
+- focused runtime summaries
+- machine-readable manifests
+- curated skills
+- reusable task/state artifacts
+- repo-aware recommendations
+- structured entrypoints instead of blind exploration
+
+---
+
+### For senior engineers
+
+- bootstrap a repo quickly without hand-assembling prompts and docs
+- get repo-aware recommendations before choosing packs
+- inspect runtime state instead of reverse-engineering what happened
+- keep advanced workflows like recursive planning and parallel execution available when work gets messy
+
+### For custom-agent builders
+
+- rely on `.hforge/agent-manifest.json` instead of scraping prose
+- consume a command catalog and runtime indexes that are machine-readable
+- route discovery via `.agents/skills/` while execution points to canonical packaged surfaces
+
+### For platform and enablement teams
+
+- standardize AI-assisted workflows across repositories
+- keep support claims explicit with a canonical capability matrix
+- hand teams a consistent install and maintenance surface
+- preserve auditability through generated runtime state and validation outputs
+
+---
+
+## Advantages
+### A. Better repo perception
+Features like scan/cartograph/classify/recommend help the agent answer:
+
+- what kind of repo is this?
+- what frameworks are present?
+- where are the service boundaries?
+- what target/runtime setup makes sense?
+
+### B. Better workflow structure
+The spec/plan/tasks flow pushes the agent toward:
+
+- decomposition before implementation
+- explicit planning
+- clearer validation expectations
+- less one-shot improvisation
+
+### C. Better decision persistence
+Indexes and runtime artifacts allow the workspace to retain:
+
+- findings
+- decisions
+- task context
+- recovery state
+
+That makes later decisions less myopic.
+
+### D. Better target-awareness
+The agent can act differently for Codex vs Claude Code vs partial runtimes instead of pretending all environments are equal.
+
+### Decision-making impact summary
+
+| Decision area | Expected impact |
+|---|---|
+| Choosing the right workflow | High improvement |
+| Choosing packs/bundles | High improvement |
+| Architectural consistency | Medium to high improvement |
+| Recovery from failed work | Medium improvement |
+| Avoiding unsupported behavior | High improvement |
+
+### Main benefits
+
+#### 1. More predictable AI behavior
+Agents get a structured runtime instead of improvising from the root folder.
+
+#### 2. Lower context reconstruction cost
+The workspace retains maps, state, and machine-readable guidance.
+
+#### 3. Better handoff quality
+Humans can inspect what was installed, what decisions were made, and what state exists.
+
+#### 4. Safer scaling across teams
+Multiple engineers and multiple agents can operate against the same contract.
+
+#### 5. Better release confidence
+Validation and maintenance commands make AI-assisted changes easier to verify.
+
+#### 6. Better target-specific execution
+Codex, Claude Code, and partial runtimes can be treated differently instead of flattened into one mental model.
 
 ---
 
@@ -152,24 +361,98 @@ flowchart LR
 
 Harness Forge is strongest with **Codex** and **Claude Code** today.
 
-| Target | Runtime support | Hooks | Flow recovery | Best fit |
+| Target | Runtime support | Hooks | Flow recovery | Recommended use |
 | --- | --- | --- | --- | --- |
-| Codex | First-class | Partial, documentation-driven | First-class | Default choice for full install, recommendation, maintenance, and flow support |
+| Codex | First-class | Partial, documentation-driven | First-class | Default choice when you want full install, recommendation, maintenance, and flow support |
 | Claude Code | First-class | First-class | First-class | Best choice when native hook support matters |
-| Cursor | Partial | Partial | Partial | Best for consuming docs, manifests, and recommendation output |
-| OpenCode | Partial | Partial | Partial | Best for docs, manifests, and recommendation output |
+| Cursor | Partial | Partial | Partial | Use for docs, manifests, and recommendation output |
+| OpenCode | Partial | Partial | Partial | Use for docs, manifests, and recommendation output |
 
 > [!NOTE]
-> Canonical support truth should live in `manifests/catalog/harness-capability-matrix.json`. Use `docs/target-support-matrix.md` as the operator-facing summary.
+> Canonical support truth lives in `manifests/catalog/harness-capability-matrix.json`. The broader compatibility view is derived into `manifests/catalog/compatibility-matrix.json`, and `docs/target-support-matrix.md` is the operator-facing summary.
+
+---
+
+## 📚 Content Coverage
+
+### Language packs
+
+**Seeded packs**
+
+- TypeScript
+- Java
+- .NET
+- Lua
+- PowerShell
+
+**Structured packs**
+
+- Python
+- Go
+- Kotlin
+- Rust
+- C++
+- PHP
+- Perl
+- Swift
+- Shell
+
+### Framework packs
+
+- React
+- Next.js
+- Vite
+- Express
+- FastAPI
+- Django
+- ASP.NET Core
+- Spring Boot
+- Laravel
+- Symfony
+- Gin
+- Ktor
+
+### Skill families
+
+- seeded language engineering skills
+- structured language engineering skills
+- Speckit workflow orchestration skills
+- operational helper skills
+- workload-specialized skills such as incident triage, dependency upgrade safety, profiling, API contract review, database migration review, release readiness, repo modernization, observability setup, and cloud architecture
+
+---
+
+## 🧭 Onboarding Flow
+
+```mermaid
+flowchart TD
+    A[Run npx @harness-forge/cli] --> B[Choose folder]
+    B --> C[Choose one or more targets]
+    C --> D[Select setup depth]
+    D --> E[Add optional modules]
+    E --> F[Review planned writes]
+    F --> G[Apply install]
+    G --> H[Run status / doctor / audit]
+```
+
+### Your first 10 minutes
+
+1. Run the CLI in the target repository.
+2. Choose one or more targets such as Codex or Claude Code.
+3. Pick a setup depth: `quick`, `recommended`, or `advanced`.
+4. Enable optional modules like recursive runtime, decision templates, or export support.
+5. Review planned writes before applying anything.
+6. Confirm health with `status`, `doctor`, and `audit`.
 
 ---
 
-## 🛠️ Install Modes
+## 🛠 Install Modes
 
 | Mode | Entry point | When to use it |
 | --- | --- | --- |
 | Guided onboarding | `npx @harness-forge/cli` | First-time setup, interactive review, and a polished onboarding experience |
-| Direct setup | `hforge init --root <repo> --agent codex --yes` | CI, scripts, automation, or operators who already know the desired target |
+| Direct setup | `hforge init --root . --agent codex --setup-profile recommended --yes` | CI, scripts, automation, or operators who already know the target choices |
+| Dry-run planning | `hforge init --root . --agent codex --dry-run` | Preview writes before modifying a repo |
 | Bootstrap | `npx @harness-forge/cli bootstrap --root . --yes` | Auto-detect runtimes and install a sensible target stack in one pass |
 | Catalog expansion | `hforge catalog add ...` | Add languages, frameworks, or bundles as the repository evolves |
 
@@ -203,28 +486,84 @@ node dist/cli/index.js install \
 
 ---
 
-## 🧠 Why teams adopt it
+## 🔬 Repo Intelligence & Guidance Synthesis
+
+Harness Forge can inspect a repository and recommend packs, profiles, skills, and missing validation surfaces with evidence.
+
+```bash
+hforge recommend tests/fixtures/benchmarks/typescript-web-app --json
+hforge cartograph tests/fixtures/benchmarks/monorepo --json
+hforge classify-boundaries tests/fixtures/benchmarks/monorepo --json
+hforge synthesize-instructions tests/fixtures/benchmarks/monorepo --target codex --json
+```
 
-- **Deterministic installs** instead of relying on ad hoc prompts
-- **Repo-aware recommendations** instead of hand-tuned tribal knowledge
-- **Target support that stays explicit** instead of vague compatibility claims
-- **Operational tooling built in** for validation, review, diffing, and maintenance
-- **A machine-readable contract** for custom agents via `.hforge/agent-manifest.json`
+This is one of the strongest parts of the project:
+
+- it helps choose the right runtime and pack mix
+- it keeps support claims tied to real repo evidence
+- it turns repo exploration into a reusable operator workflow instead of a one-off setup task
 
 ---
 
-## ⚙️ Prerequisites
+## 🧱 Advanced Runtime Features
 
-| Requirement | Notes |
-| --- | --- |
-| Node.js 22+ | Required to build and run the CLI |
-| npm | Used for install, build, validation, and bootstrap flows |
-| A target repository | The workspace that should receive the installed agent surfaces |
-| PowerShell | Needed for the shipped PowerShell validation bundle on Windows and cross-platform PowerShell setups |
+### Recursive runtime
+
+For difficult work, Harness Forge can escalate into a durable recursive session under:
+
+```text
+.hforge/runtime/recursive/sessions/RS-XXX/
+```
+
+That gives you:
+
+- a durable session identity
+- budget and promotion state
+- compact working memory
+- append-only trace output
+- resumable investigation flow
+
+### Parallel planning and merge safety
+
+Harness Forge also supports shard planning and merge-readiness checks:
+
+```bash
+hforge parallel plan specs/<feature>/tasks.md --json
+hforge parallel status --json
+hforge parallel merge-check --json
+```
+
+### Local-first observability
+
+Observability is designed to remain local, inspectable, and diagnostic:
+
+- `.hforge/observability/effectiveness-signals.json`
+- `.hforge/observability/summary.json`
+- `hforge observability summarize --json`
+- `hforge observability report . --json`
 
 ---
 
-## ✅ Verify everything is healthy
+## 🔐 Trust, Safety, and Inspectability
+
+Harness Forge is designed to be **inspectable, deterministic, and operator-friendly**.
+
+- no external observability backend is required
+- generated runtime state stays inside the repository under `.hforge/`
+- dry-run setup is supported before writes
+- lifecycle commands are diagnostic first and destructive second
+- support claims are grounded in capability matrices rather than vague marketing
+- generated runtime artifacts remain traceable back to canonical authored surfaces
+
+In practice, that means teams can understand:
+
+1. what was installed
+2. what drifted
+3. what is safe to refresh, repair, prune, or upgrade
+
+---
+
+## ✅ Verify Everything Is Healthy
 
 Run these after installation:
 
@@ -246,8 +585,9 @@ hforge review --root /path/to/your/workspace --json
 | Custom-agent manifest | `.hforge/agent-manifest.json` exists |
 | Skill discovery layer | `.agents/skills/` is present |
 | Canonical AI layer | `.hforge/library/skills/`, `rules/`, and `knowledge/` are populated |
-| Runtime state | `.hforge/runtime/index.json` and related findings/decision files exist |
+| Runtime state | `.hforge/runtime/index.json` and related findings and decision files exist |
 | Target runtime | `.codex/` or `.claude/` exists in the workspace |
+| Local launchers | `.hforge/generated/bin/hforge`, `.ps1`, or `.cmd` exists |
 
 ---
 
@@ -269,19 +609,8 @@ hforge review --root /path/to/your/workspace --json
 | Inspect target capabilities | `hforge target inspect codex --json` |
 | Validate templates | `hforge template validate --json` |
 | Compare install state vs workspace | `hforge diff-install --root /path/to/your/workspace --json` |
-
----
-
-## 🔬 Repo Intelligence & Guidance Synthesis
-
-Harness Forge can inspect a repository and recommend packs, profiles, skills, and missing validation surfaces with evidence.
-
-```bash
-hforge recommend tests/fixtures/benchmarks/typescript-web-app --json
-hforge cartograph tests/fixtures/benchmarks/monorepo --json
-hforge classify-boundaries tests/fixtures/benchmarks/monorepo --json
-hforge synthesize-instructions tests/fixtures/benchmarks/monorepo --target codex --json
-```
+| Inspect flow recovery state | `hforge flow status --json` |
+| Review observability effectiveness | `hforge observability summarize --json` |
 
 ---
 
@@ -325,11 +654,11 @@ npm run knowledge:drift
 ```
 
 > [!IMPORTANT]
-> `npm run validate:release` should be treated as the front-door release gate for shipped changes.
+> `npm run validate:release` is the front-door release gate for shipped changes.
 
 ---
 
-## 🗂️ Repository Structure
+## 🗂 Repository Structure
 
 <details>
 <summary><strong>Expand repository layout</strong></summary>

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@harness-forge/cli",
-  "version": "0.1.0",
+  "version": "1.0.1",
   "description": "Harness Forge: modular agentic AI workspace installer, catalog, and workflow runtime.",
   "type": "module",
   "bin": {
     "hforge": "./dist/cli/index.js"
   },
-   "repository": {
+  "repository": {
     "type": "git",
     "url": "git+https://github.com/ldilov/harness-forge.git"
   },