chore: community surface — issue templates, CONTRIBUTING, package name

[zelinewang]

What

• Set package.json name from the Vite scaffold default to postprism
  (kept private: true — this is an app, not a published package)
• Add GitHub issue forms: .github/ISSUE_TEMPLATE/bug_report.yml + feature_request.yml
• Add CONTRIBUTING.md (front-end Bun setup, backend note, PR expectations, MIT)

The bug form's first field splits the two surfaces (credential-free front-end
demo vs. the credentialed computer-use backend) plus browser/OS.

Why

The project still carried the generic scaffold identity in package.json, and
had no issue template or contributing guide — the signals a reviewer scans in
the first ten seconds.

How verified

Front-end setup from CONTRIBUTING run against this clone:

$ bun install
135 packages installed
$ bun run build
✓ built in 1.55s

Dev server port (http://localhost:8080) confirmed against vite.config.ts.
Repo has no lockfile, so the rename needs no lockfile regeneration.

Docs + identity metadata only — no runtime/default-behavior changes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8dcf3f8db9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update the npm lockfile name as well

Because this repo still tracks package-lock.json, changing only package.json leaves the lockfile root package named vite_react_shadcn_ts at both name and packages[""] .name. In npm-based workflows, the next npm install --package-lock-only rewrites those fields to postprism, so this commit leaves dependency metadata inconsistent and causes avoidable lockfile churn for contributors using the tracked npm lockfile.

Useful? React with 👍 / 👎.