Harden quality checks and documentation

Author: nripankadas07

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,31 @@
+---
+name: Bug report
+about: Report reproducible incorrect behavior in csvtable
+title: "[bug] "
+labels: bug
+assignees: ""
+---
+
+## What happened?
+
+Describe the behavior and why it is incorrect.
+
+## Minimal reproduction
+
+```text
+Paste the smallest input, command, or code sample that reproduces the issue.
+```
+
+## Expected behavior
+
+What should happen instead?
+
+## Environment
+
+- OS:
+- Python/Node version:
+- Repository commit or version:
+
+## Notes
+
+Include edge cases, security impact, or related standards references if useful.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Propose a focused improvement to csvtable
+title: "[feature] "
+labels: enhancement
+assignees: ""
+---
+
+## Problem
+
+What concrete user or developer problem should this solve?
+
+## Proposed shape
+
+Describe the smallest API, CLI, example, or documentation change that would
+solve it.
+
+## Alternatives
+
+What can users do today? What existing library or standard should this be
+compared against?
+
+## Fit with the lab
+
+Explain why this belongs in a small, readable, auditable project.

.github/pull_request_template.md

@@ -0,0 +1,14 @@
+## Summary
+
+Describe what changed in `csvtable` and why.
+
+## Verification
+
+- [ ] Tests pass locally.
+- [ ] Type/lint/build checks pass where applicable.
+- [ ] README, examples, roadmap, or changelog updated if behavior changed.
+- [ ] No fake package, benchmark, badge, download, or adoption claims added.
+
+## Risk
+
+Call out compatibility, security, parsing, performance, or migration risks.

CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+All notable changes to `csvtable` will be tracked here.
+
+This project follows an honest-source rule: no package publication, benchmark,
+download, or adoption claim is added unless it has been verified.
+
+## Unreleased
+
+- Added the shared lab maintainer surface: code of conduct, changelog, roadmap,
+  issue templates, and pull request template.
+- Clarified source-checkout installation guidance where package-registry
+  publication has not been verified.
+- Removed static or unverifiable status badges.

CODE_OF_CONDUCT.md

@@ -0,0 +1,24 @@
+# Code of Conduct
+
+This repository is part of the No-Dependency AI + Systems Lab. The goal is to
+make small engineering artifacts easier to read, run, audit, and improve.
+
+## Expected Behavior
+
+- Be precise, kind, and technical.
+- Critique code, documentation, tests, and assumptions rather than people.
+- Prefer reproducible examples over vague claims.
+- Disclose security-sensitive issues responsibly through `SECURITY.md`.
+
+## Unacceptable Behavior
+
+- Harassment, personal attacks, discriminatory language, or intimidation.
+- Publishing secrets, private data, or exploit details before maintainers have a
+  chance to respond.
+- Spam, star-bait, or promotional noise unrelated to `csvtable`.
+
+## Enforcement
+
+Maintainers may edit, hide, or remove issues, discussions, comments, or pull
+requests that violate this code. Repeated or severe violations may lead to a
+block from the project.

ROADMAP.md

@@ -0,0 +1,25 @@
+# Roadmap
+
+`csvtable`: Pretty-print CSV/TSV (or any rows) as aligned ASCII / Unicode / Markdown / plain tables — column-width inference, per-column align, 3-mode truncation, wide-char width..
+
+## Near Term
+
+- Keep the README specific: audience, thesis, quick demo, limitations, and
+  source-checkout install instructions.
+- Keep edge-case tests near the code they protect.
+- Keep CI aligned with the local commands: `pytest` and `python -m build` where
+  applicable.
+
+## Release Readiness
+
+- Verify package metadata before publishing anywhere.
+- Add a release tag only after tests, type checks, build/pack checks, and docs
+  are all current.
+- Do not add download, usage, benchmark, or adoption claims without evidence.
+
+## Later
+
+- Add small examples for the most common workflow.
+- Add benchmark or conformance scripts only where performance or standards
+  compliance is part of the value proposition.
+- Consolidate with a sibling repo if the audience and API overlap too much.