fix(i18n): use lang_customer_title for Customer heading in transaction modal

CODE_OF_CONDUCT.md → .github/CODE_OF_CONDUCT.md

@@ -77,7 +77,7 @@ Roughly in order, starting at the lowest step that fits:
    severe act — harassment, threats, or deliberately putting shops' data at risk.
 
 Decisions are made by the maintainers, currently as described in
-[GOVERNANCE.md](GOVERNANCE.md#where-the-project-is-today). If you believe one
+[GOVERNANCE.md](../docs/GOVERNANCE.md#where-the-project-is-today). If you believe one
 was wrong, say so at the same address; where a second maintainer exists, they
 review it.
 

CONTRIBUTING.md → .github/CONTRIBUTING.md

@@ -6,6 +6,11 @@ hardware quirks from real shops.
 
 ## Getting started
 
+If this is your first Posnic contribution, start with the
+[contributor quickstart](../docs/CONTRIBUTOR_QUICKSTART.md). It has the local
+setup commands, common test commands, and task map for translations, GST,
+e-invoicing, AI helper work, integrations and hardware evidence.
+
 ```bash
 git clone https://github.com/Posnic/POS.git
 cd POS
@@ -18,20 +23,28 @@ You do **not** need to install MongoDB. Posnic bundles its own and picks a port
 derived from the application name, so it never collides with a database you
 already run. The first launch takes a few minutes while it unpacks.
 
-- [docs/DEVELOPMENT.md](docs/DEVELOPMENT.md) — full developer guide: tests,
+- [Contributor quickstart](../docs/CONTRIBUTOR_QUICKSTART.md) — first setup,
+  task map and test matrix
+- [docs/DEVELOPMENT.md](../docs/DEVELOPMENT.md) — full developer guide: tests,
   linting, conventions, and what not to rename
-- [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) — how the pieces fit together
-- [docs/API.md](docs/API.md) — REST reference, 478 endpoints
-- [docs/BUILD_INSTRUCTIONS.md](docs/BUILD_INSTRUCTIONS.md) — installer builds
+- [docs/ARCHITECTURE.md](../docs/ARCHITECTURE.md) — how the pieces fit together
+- [docs/API.md](../docs/API.md) — REST reference
+- [docs/BUILD_INSTRUCTIONS.md](../docs/BUILD_INSTRUCTIONS.md) — installer builds
 
 ## How to contribute
 
 1. **Open an issue first** for anything non-trivial — a bug report or a short
    proposal for a feature. It avoids wasted work on both sides.
-2. Fork, create a branch (`fix/receipt-rounding`, `feat/tamil-translation`).
-3. Keep pull requests focused — one change per PR.
-4. Match the style of the surrounding code; avoid drive-by reformatting.
-5. Run the tests: `cd api && npm test` (7,744 unit tests, about a minute), plus
+2. Pick a task from the
+   [contributor roadmap](https://github.com/Posnic/POS/issues/35) or the
+   [`good first issue`](https://github.com/Posnic/POS/labels/good%20first%20issue)
+   label.
+3. Read the issue acceptance criteria and choose one small checkbox or PR slice.
+   If the issue does not yet define "done", start by proposing that checklist.
+4. Fork, create a branch (`fix/receipt-rounding`, `feat/tamil-translation`).
+5. Keep pull requests focused — one change per PR.
+6. Match the style of the surrounding code; avoid drive-by reformatting.
+7. Run the tests: `cd api && npm test` (7,744 unit tests, about a minute), plus
    `npm test` at the repo root for the desktop side (294 more). Both should pass on a
    clean checkout — if they do not, that is worth an issue on its own.
 
@@ -46,7 +59,7 @@ that one is yours.
 **Do not rename a persisted field or collection in a pull request.** Those names
 travel over the sync wire to desktop installations that cannot be force-updated,
 so renaming them needs a versioned migration. See
-[docs/DEVELOPMENT.md](docs/DEVELOPMENT.md#what-not-to-rename).
+[docs/DEVELOPMENT.md](../docs/DEVELOPMENT.md#what-not-to-rename).
 
 ## What happens to your pull request
 
@@ -55,7 +68,7 @@ So you know what you are waiting for.
 1. **CI runs** — unit tests, the desktop tests, lint, the packaging check and
    the API docs check. All of them gate: if CI is red, the pull request waits.
 2. **A maintainer reads it.** Usually within a week. The project is small; see
-   [GOVERNANCE.md](GOVERNANCE.md).
+   [GOVERNANCE.md](../docs/GOVERNANCE.md).
 3. **You may get comments.** Comments are not rejection. A pull request with
    twenty comments is one someone is taking seriously.
 4. **It merges**, or it does not — and if it does not, the reason is written in
@@ -99,6 +112,38 @@ Two things worth repeating here:
   are trying to do tells us more than the button you imagined, and often has a
   better answer.
 
+## Contribute evidence without changing code
+
+Reproducible observations are useful contributions. They help turn a broad
+feature statement into a versioned result with an exact input, environment and
+limitation.
+
+- If you are reviewing Posnic independently, start with the public
+  [review brief](https://posnic.com/assets/posnic-independent-review-brief.txt)
+  and [24-control protocol](https://posnic.com/assets/posnic-independent-review-protocol.csv).
+  Review access does not require payment, positive coverage, a backlink or
+  advance approval. Publish failures, conflicts and untested areas as well as
+  successful results.
+- Run the public
+  [vendor-neutral POS acceptance fixture](https://posnic.com/open-source-pos-benchmark#vendor-neutral-pos-acceptance-fixture)
+  and submit the structured
+  [acceptance result form](https://github.com/Posnic/POS/issues/new?template=pos_acceptance_run.yml).
+- Test an exact printer, scanner, cash drawer, scale or display against the
+  [hardware matrix](../docs/HARDWARE_MATRIX.md), then submit the structured
+  [hardware evidence form](https://github.com/Posnic/POS/issues/new?template=hardware_evidence.yml).
+- If you operate, piloted, installed, evaluated or stopped using Posnic, read
+  the [adoption evidence policy](../docs/ADOPTION_EVIDENCE.md) and submit a
+  structured
+  [deployment evidence report](https://github.com/Posnic/POS/issues/new?template=deployment_evidence.yml).
+  Failures, workarounds and reasons not to adopt are useful evidence.
+- Read [ROADMAP.md](../docs/ROADMAP.md) for the current evidence gaps and the boundary
+  between released, reproduced, in-validation and planned work.
+
+An evidence issue is public and is not a certification or testimonial. Use
+fictional transactions and remove customer data, payment data, credentials,
+tokens, production logs and database files before attaching anything. Security
+problems still go through [SECURITY.md](SECURITY.md), never a public issue.
+
 ## Sign your commits (DCO)
 
 We use the [Developer Certificate of Origin](https://developercertificate.org/).

.github/ISSUE_TEMPLATE/config.yml

@@ -6,6 +6,10 @@
 blank_issues_enabled: false
 
 contact_links:
+  - name: Start contributing
+    url: https://github.com/Posnic/POS/blob/main/docs/CONTRIBUTOR_QUICKSTART.md
+    about: Local setup, test commands, good first issues, PR flow and safety rules.
+
   - name: Question or help using Posnic
     url: https://github.com/Posnic/POS/discussions/categories/q-a
     about: How do I do X, is this normal, hardware advice. Faster than an issue.

.github/ISSUE_TEMPLATE/deployment_evidence.yml

@@ -0,0 +1,154 @@
+name: Real deployment evidence report
+description: Report bounded, versioned experience from operating or evaluating Posnic
+title: "[Deployment evidence]: "
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this form for honest experience from a real deployment, pilot, installation, or sustained evaluation. Failures, workarounds, stopped trials, and reasons Posnic was not selected are as useful as successful use.
+
+        GitHub issues are public. Do not include customer records, card or bank data, credentials, tokens, tax identifiers, staff identities, production database files, private logs, an exact shop address, or anything you are not authorised to publish.
+
+        A submitted report is not automatically a testimonial, case study, certification, endorsement, uptime claim, or proof that another business will obtain the same result.
+
+  - type: dropdown
+    id: reporter_relationship
+    attributes:
+      label: Your relationship to this deployment
+      options:
+        - Business owner or operator
+        - Employee using Posnic at work
+        - Installer, consultant, or implementation partner
+        - Independent evaluator or researcher
+        - Posnic employee, contractor, affiliate, or investor
+        - Former user or stopped pilot
+        - Other relationship explained below
+    validations:
+      required: true
+
+  - type: textarea
+    id: relationship_details
+    attributes:
+      label: Relationship and financial disclosure
+      description: State who selected, configured, paid for, supplied, or reviewed the software and disclose any payment, free service, discount, employment, referral, or other material connection to Posnic.
+      placeholder: I operate the shop and used the free local edition; no payment or incentive was received for this report.
+    validations:
+      required: true
+
+  - type: input
+    id: product_identity
+    attributes:
+      label: Exact Posnic version or source commit
+      description: Include the release tag, About-screen version, or full source commit. Add the package filename and SHA-256 when available.
+      placeholder: v1.3.0, Posnic-1.3.0-windows-x64-installer.exe, SHA-256 ...
+    validations:
+      required: true
+
+  - type: dropdown
+    id: deployment_status
+    attributes:
+      label: Deployment status
+      options:
+        - Currently used for live business operations
+        - Time-bounded live pilot
+        - Production-like evaluation with synthetic data
+        - Installation or migration attempt that stopped
+        - Previously used and no longer in use
+    validations:
+      required: true
+
+  - type: input
+    id: observation_window
+    attributes:
+      label: Observation window
+      description: Give calendar dates or a bounded duration. Do not say "for a while".
+      placeholder: 1 June 2026 to 31 July 2026, or 12 operating days
+    validations:
+      required: true
+
+  - type: input
+    id: market_scope
+    attributes:
+      label: Country, business type, and deployment size
+      description: Country and state or region are enough. Do not publish an exact address. Use a range for staff or transaction volume if the exact value is sensitive.
+      placeholder: India, Tamil Nadu; one bakery; one till; 1-5 staff
+    validations:
+      required: true
+
+  - type: input
+    id: environment
+    attributes:
+      label: Operating system and relevant hardware
+      description: Include OS version, architecture, installation type, and only the exact device models relevant to your observations.
+      placeholder: Windows 11 23H2 x64; local edition; printer model and connection if discussed
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: workflows_observed
+    attributes:
+      label: Workflows actually observed
+      description: Select only paths used during the stated window. Explain depth and exceptions below.
+      options:
+        - label: Installation, setup, or migration
+        - label: Catalog, stock, or purchasing
+        - label: Sale, tender recording, receipt, or return
+        - label: Restaurant, table, kitchen, or kiosk workflow
+        - label: Register, close, report, or export
+        - label: Backup, restore, restart, or outage recovery
+        - label: Printer, scanner, drawer, scale, or display
+        - label: Multi-till, branch, sync, or Posnic Cloud
+        - label: Support, issue reporting, or update process
+    validations:
+      required: true
+
+  - type: textarea
+    id: observed_results
+    attributes:
+      label: What happened
+      description: Describe expected and observed behavior with counts or dates where you can support them. Include failures, retries, workarounds, abandoned paths, and unresolved issues.
+      placeholder: What was attempted; what worked; what failed; what changed; links to related public issues.
+    validations:
+      required: true
+
+  - type: textarea
+    id: evidence_and_method
+    attributes:
+      label: Evidence and method
+      description: Explain how the observations were recorded. Link public issues or attach only synthetic, aggregated, or fully redacted material.
+      placeholder: Version screen, synthetic test receipt, issue links, redacted setup notes, or measured aggregate with its calculation.
+    validations:
+      required: true
+
+  - type: textarea
+    id: limitations
+    attributes:
+      label: Limitations and untested paths
+      description: State what this report does not establish, including workflows, platforms, hardware, providers, countries, loads, recovery conditions, or time periods not observed.
+    validations:
+      required: true
+
+  - type: dropdown
+    id: citation_permission
+    attributes:
+      label: Permission to cite this report
+      description: This choice can be changed later by commenting on the issue. Separate written approval is still required before publishing a named business case study, logo, quotation, or private evidence.
+      options:
+        - Do not use this as marketing; keep it as a public issue only
+        - Posnic may link to this public issue with my GitHub username only
+        - Posnic may summarise this public report after I approve the exact wording
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: public_data_confirmation
+    attributes:
+      label: Public report confirmation
+      options:
+        - label: I am authorised to publish this report and removed private customer, payment, staff, credential, tax, address, log, and database data.
+          required: true
+        - label: I disclosed my relationship and any payment, free service, discount, referral, employment, or other material connection.
+          required: true
+        - label: I understand that maintainers may ask for correction, label the result unverified, or close it without turning it into a marketing claim.
+          required: true

.github/ISSUE_TEMPLATE/feature_request.md

@@ -33,6 +33,19 @@ the one you had in mind.
 <!-- Optional. If you have a shape in mind, describe it - but the problem above
      matters more. -->
 
+## Acceptance criteria
+
+<!--
+What must be true before this issue can be closed? Keep these specific and
+testable. A maintainer may edit this into smaller PR-sized steps before code
+starts.
+-->
+
+- [ ] The user can...
+- [ ] The app still...
+- [ ] Tests or evidence prove...
+- [ ] Documentation or operator wording explains...
+
 ## Does it need an internet connection?
 
 <!-- The local edition must work fully offline. Anything that needs a

.github/ISSUE_TEMPLATE/hardware_evidence.yml

@@ -0,0 +1,83 @@
+name: POS hardware evidence report
+description: Report a reproducible observation for an exact printer, scanner, drawer, scale, or display
+title: "[Hardware evidence]: "
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        A source path or protocol test is not the same as a physical-device result. Name the exact device and environment so another person can reproduce the observation.
+
+        GitHub issues are public. Use fictional transactions and remove customer data, payment data, credentials, tokens, production logs, serial numbers that identify an owner, and database files.
+
+  - type: dropdown
+    id: device_type
+    attributes:
+      label: Device type
+      options:
+        - Receipt printer
+        - Barcode scanner
+        - Cash drawer
+        - Weighing scale
+        - Customer or second display
+        - Other POS peripheral
+    validations:
+      required: true
+
+  - type: input
+    id: device_identity
+    attributes:
+      label: Manufacturer and exact model
+      placeholder: Manufacturer, model, hardware revision if visible
+    validations:
+      required: true
+
+  - type: input
+    id: connection
+    attributes:
+      label: Connection, cable, driver, and protocol
+      placeholder: USB, driver version, ESC/POS mode, serial settings, or network path
+    validations:
+      required: true
+
+  - type: input
+    id: software_environment
+    attributes:
+      label: Posnic version, operating system, and architecture
+      placeholder: Posnic v1.3.0, Windows 11 23H2 x64
+    validations:
+      required: true
+
+  - type: textarea
+    id: test_method
+    attributes:
+      label: Test method
+      description: Describe setup and the exact normal, disconnect, retry, restart, malformed-input, or recovery paths tested.
+    validations:
+      required: true
+
+  - type: textarea
+    id: observed_results
+    attributes:
+      label: Expected and observed results
+      description: Record each pass, failure, partial result, and error message. Attach fully redacted evidence where useful.
+    validations:
+      required: true
+
+  - type: textarea
+    id: limitations
+    attributes:
+      label: Limitations and untested paths
+      description: State what this observation does not prove, including other firmware, drivers, cables, platforms, receipt widths, loads, or recovery conditions.
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: public_data_confirmation
+    attributes:
+      label: Public evidence confirmation
+      options:
+        - label: I used fictional or fully redacted records and included no secrets, customer data, payment data, or production database content.
+          required: true
+        - label: I understand that one report is not an automatic hardware certification or universal compatibility claim.
+          required: true