@oscharko-dev/test-intelligence 0.0.1-beta.0 → 0.1.0-beta.2

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,22 @@
+# Code of Conduct
+
+## Purpose
+
+This project supports respectful, inclusive, and professional collaboration.
+
+## Expected behavior
+
+- Use clear, concise, and professional language.
+- Keep reviews and discussions focused on technical quality and evidence.
+- Respect branch, release, and governance rules for all contributions.
+- Share concerns directly and provide actionable alternatives.
+
+## Unacceptable behavior
+
+- Harassment, intimidation, or demeaning language.
+- Removing governance controls for convenience.
+- Misrepresenting project status or scope in public documentation.
+
+## Enforcement
+
+Project owners may remove, pause, or close contributions that materially violate this standard.

package/CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing to Test Intelligence
+
+## Scope and readiness
+
+This repository is the public, standalone implementation surface for Test Intelligence.
+Work is expected to be production-oriented and aligned with the enterprise charter.
+
+## Workflow
+
+1. Create work on topic branches from `dev`.
+2. Open PRs against `dev`; changes reach `main` only through the release governance flow.
+3. Use issue templates for new work and keep acceptance criteria explicit.
+4. Resolve review comments and update issue-linked evidence before merge.
+5. Merge to `main` only through the release governance flow.
+
+## Standards
+
+- Use professional English in all GitHub artifacts.
+- No claims that position the repository as demo/prototype/sample/POC.
+- Include references to the product charter when introducing scope or constraints.
+- Keep PR changes minimal, deterministic, and auditable.
+
+## Required artifacts
+
+Before merge, ensure:
+
+- issue scope is complete.
+- root documentation remains aligned with current behavior.
+- release-impacting changes reference package metadata updates and `NOTICE` requirements.
+- branch/merge expectations in this repository are respected.
+
+## Attribution and licensing
+
+Test Intelligence is distributed under the Apache License 2.0. Any redistribution or derivative work — including redistribution of any source portion — must include a copy of the Apache License 2.0 and preserve the attribution notices from [`NOTICE`](NOTICE), retaining attribution to the product name "Test Intelligence" and the originator "oscharko-dev" in derivative documentation and notices. [`NOTICE`](NOTICE) is the defining source for this requirement.
+
+## Questions and support
+
+Open an issue for governance and architecture questions.

package/GOVERNANCE.md

@@ -0,0 +1,36 @@
+# Test Intelligence Governance
+
+## Product status
+
+Test Intelligence is a standalone product initiative for enterprise quality and testing intelligence in regulated banking and insurance environments.
+
+The repository is not a prototype, demo, sample, or proof of concept.
+
+## Operating model
+
+- Development baseline branch: `dev`
+- Release and package publication baseline: `main`
+- Merges to `main` are restricted to reviewed pull requests originating from `dev`.
+- Release artifacts must remain deterministic and auditable.
+
+## Scope
+
+Governance work in this repository defines:
+
+- product scope and trust posture
+- communication and evidence standards for all work
+- delivery constraints across release preparation, security, and quality.
+
+## Communication standard
+
+All issue text, pull requests, comments, commit messages, commit metadata,
+repository documentation, code comments, configuration, and release notes must
+use professional English and avoid prototype framing.
+
+## Attribution and reuse
+
+For any redistribution or derivative work:
+
+- preserve license and notice files.
+- preserve the required attribution to `Test Intelligence` and `oscharko-dev`.
+- avoid weakening these requirements in downstream package metadata.

package/LICENSE

@@ -0,0 +1,199 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation source,
+      and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this definition, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution infringes a patent, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and this License
+          must be attached to the Work or Derivative Works with a
+          copy of the License. You may not offer or impose any
+          terms on the Work or Derivative Works that alter or
+          restrict the terms of this License.
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+          If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear.
+
+          The contents of the NOTICE file are for informational purposes only
+          and do not modify the License. You may add your own attribution
+          notices within Derivative Works that you distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed as
+          modifying the License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions
+      of this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or
+      modify the terms of any separate license agreement you may have
+      executed with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or
+      conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or
+      FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for
+      determining the appropriateness of using or redistributing the Work
+      and assume any risks associated with Your exercise of permissions under
+      this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,12 @@
+Test Intelligence
+Copyright 2026 oscharko-dev
+
+This product includes work authored by oscharko-dev.
+
+Attribution requirements:
+- You must retain this NOTICE file in redistributions and derivative works.
+- You must preserve and reference the product name "Test Intelligence" and
+  the originator "oscharko-dev" in derivative documentation, notices,
+  and where practical in downstream communication.
+
+This product is provided under the Apache License 2.0.

package/README.md

@@ -1,19 +1,81 @@
-I am Test-Intelligence...
+# Test Intelligence
 
-## Package
+Test Intelligence turns design and requirement evidence into traceable test
+intelligence for regulated banking and insurance delivery.
 
-Dieses Repository wird als extrem frühes Pre-Beta-Paket veröffentlicht.
+The current user-facing surface is the **Workbench** in `apps/workbench`. It is
+a local Next.js operator UI for configuring runs, launching the runtime, and
+inspecting generated artifacts.
 
-**Name:** `@oscharko-dev/test-intelligence`  
-**Version:** `0.0.1-beta.0`
+## Local Workbench
 
-Install:
+Start from a fresh checkout:
 
 ```bash
-npm install @oscharko-dev/test-intelligence@pre-beta
+pnpm run local:start
 ```
 
-```js
-const testIntelligence = require("@oscharko-dev/test-intelligence");
-console.log(testIntelligence.ping());
+Open `http://localhost:1983`.
+
+`local:start` checks for missing `node_modules`, runs `pnpm install` when
+needed, builds `apps/workbench` when the build output is missing, and starts the
+Workbench on port `1983`. If that port is already occupied, the script exits and
+asks the operator to free the port locally; it does not switch ports.
+
+Stop the managed Workbench process:
+
+```bash
+pnpm run local:stop
+```
+
+Useful variants are:
+
+```bash
+pnpm run local:start:mock       # UI-only mock runner, no live Figma/LLM calls
+pnpm run local:start:prod       # production Next.js mode
+pnpm run local:start -- --env-file=.env.local
+```
+
+Runtime state, PID files, and logs are written under
+`.test-intelligence/local-runtime/` and are intentionally ignored by Git.
+
+The Workbench currently provides Runs and Model Settings for local operator
+workflows. Run History is read-only sample data until persisted history loading
+is implemented.
+
+## Final Local E2E
+
+Run the local final end-to-end suite after the Workbench is running and local
+case fixtures have been provided:
+
+```bash
+pnpm run test:final-e2e
 ```
+
+The command runs the Workbench Playwright flow against operator-provided local
+fixtures in the untracked `test-case/` directory and writes fresh results to
+`.test-intelligence/final-e2e/`. The test clears that result directory at the
+start of each run so stale artifacts are not reused as successful evidence.
+
+## Maintainer Checks
+
+For Workbench changes:
+
+```bash
+pnpm --dir apps/workbench lint
+pnpm --dir apps/workbench test
+pnpm --dir apps/workbench typecheck
+pnpm --dir apps/workbench build
+```
+
+For visual or final local E2E coverage:
+
+```bash
+pnpm --dir apps/workbench exec playwright install chromium
+pnpm --dir apps/workbench test:visual
+pnpm run test:final-e2e
+```
+
+Update visual snapshots with `pnpm --dir apps/workbench test:visual:update`
+only after reviewing the UI diff. For repository-wide runtime changes, use the
+CI scripts in `package.json`.

package/SECURITY.md

@@ -0,0 +1,64 @@
+# Security Policy
+
+Test Intelligence is published as a standalone enterprise package for
+regulated banking and insurance modernization workflows. This policy documents
+how vulnerabilities are reported and which security controls are maintained for
+the public package.
+
+## Supported Versions
+
+| Version line | Supported |
+| --- | --- |
+| `0.0.x` | Supported during the current pre-1.0 line |
+| Older unpublished snapshots | Not supported |
+
+## Reporting a Vulnerability
+
+Do not open public issues for security vulnerabilities.
+
+Report privately via GitHub private vulnerability reporting on this repository.
+If that is unavailable, contact
+[security@oscharko.dev](mailto:security@oscharko.dev).
+
+Include the impact summary, reproduction steps, affected versions, suggested
+remediation, and any relevant operator configuration.
+
+## Response Targets
+
+| Severity | Acknowledge | Fix target |
+| --- | --- | --- |
+| Critical | 4 hours | 24 hours |
+| High | 8 hours | 72 hours |
+| Medium | 24 hours | 7 calendar days |
+| Low | 48 hours | Next scheduled release |
+
+## Security-Sensitive Surfaces
+
+- The HTTP runtime binds to loopback by default and requires explicit operator
+  configuration for broader exposure.
+- Write routes require bearer-token authentication and fail closed when
+  authentication is unavailable.
+- Feature gates fail closed when disabled or unset.
+- The model gateway reads operator-provided endpoints, deployment names, and
+  keys from environment variables; secrets are not committed to the repository.
+- Evidence, audit-dossier, region-attestation, and reviewer signing keys are
+  operator-owned.
+- Runtime artifacts are written only under operator-selected output roots.
+
+## Supply-Chain Controls
+
+- Dependencies are installed from the committed lockfile.
+- Lockfile hosts are checked against an allowlist.
+- Dependency review runs on package metadata changes.
+- GitHub Actions use pinned actions and `persist-credentials: false` on
+  checkout.
+- SBOM and package-shape checks are part of the release posture.
+- Private runtime state, generated caches, secrets, and internal documentation
+  are excluded from the public package.
+
+## Remediation Policy
+
+Released versions are not unpublished. Affected releases are deprecated when
+needed and fixed by publishing a patched forward release. Public release notes
+must not disclose unpublished vulnerability details before coordinated
+disclosure is complete.

package/SUPPORT.md

@@ -0,0 +1,18 @@
+# Support
+
+## Scope
+
+Test Intelligence is provided as a pre-1.0 open-source package for regulated
+test-intelligence workflows.
+
+## Channels
+
+- GitHub Issues: feature requests, operational questions, and reproducible bugs.
+- Security matters: use the private security reporting path on GitHub.
+- Enterprise onboarding and licensing questions: open an issue without secrets,
+  customer data, or private runtime logs.
+
+## Response Expectations
+
+Response times depend on issue severity and maintainer availability.
+Security disclosures follow the Security Policy process.