docs: rewrite README as portfolio-facing project overview #244
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-api!244
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "243-polish-readme-md-for-portfolio-facing-pr"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Replaces the internal-facing README (which referenced outdated SQLite architecture and operational details) with a polished, recruiter-ready document that leads with what the platform does and highlights engineering scope.
Changes
README.md— Full rewrite. New structure: title/one-liner, tech stack table, key features (block model, kanban, Forgejo sync, hybrid search, MCP integration, note graph), API surface summary (47 endpoints / 8 modules), data model diagram, project structure tree, development commands, related repos.Test Plan
pytest --co), 47 endpoints (confirmed via route decorator count), 22 migrations (confirmed viaalembic/versions/), 12 models (confirmed viamodels.py), 8 route modules (confirmed viaroutes/)Review Checklist
Related Notes
None — documentation-only change.
Related
Closes #243
QA Review — PR #244
Findings
Fixed (pushed in
3d0dc27):ls tests/test_*.py | wc -lreturns 29. Corrected to 29.database.pyuses synchronous sessions exclusively. Changed to "declarative mapped columns."Verified accurate:
Note: Related Repositories links point to internal Forgejo URLs. A recruiter without Tailscale access cannot follow them. This is acceptable if the repo itself is accessed via Forgejo (same network), but worth noting if the repo is ever mirrored to a public host.
VERDICT: APPROVED