docs: record PR #187 and close the changelog gap; correct README - #192
Merged
Conversation
CHANGELOG.md - New [2026-09-11] section recording PR #187 (the `deliverables/product-crud/` full-stack CRUD reference: Express + Prisma + Zod backend, React + TanStack Query frontend, docker-compose, 30-row seed, production Dockerfile). - Added three entries to [2026-09-10] that had never been recorded: PR #184, PR #185 (fastapi-obsidian-backend deliverable) and commit de284dc, which merged that day after the last entry (#183). README.md - `frontend/` was missing from the layout table despite being its own package with its own Dockerfile and tsconfig. - Deliverables examples now name `product-crud` and `fastapi-obsidian-backend`. - Quick start said nothing about the frontend or the deliverable suites, both of which are runnable separately; now they are pointed at. - Repository health gained two honest entries: root Node tooling is declared but unusable (no lockfile, no eslint.config.* so `npm run lint` fails under ESLint 10, `scripts.vite` holds a version range where a command belongs, and no lockfile means the root tree has never been scanned for advisories); and ~800 unreviewed files now sit at the repo root from de284dc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documentation catch-up on
main.CHANGELOG.md[2026-09-11]section recording PR feat(deliverables): add product-crud full-stack CRUD deliverable #187 — thedeliverables/product-crud/full-stack CRUD reference (Express + Prisma + Zod backend, React + TanStack Query frontend, docker-compose, 30-row seed, production Dockerfile).[2026-09-10]. Three things merged that day after the last recorded entry (#183) and were never logged: PR docs: record PR #183 in the changelog #184, PR feat: add FastAPI + Obsidian backend deliverable #185 (deliverables/fastapi-obsidian-backend/— six routers, opt-in encryption at rest, bundled skill markdown), and commitde284dc, which landed directly onmainrather than through a PR.README.mdfrontend/was absent from the layout table despite being its own package with its ownpackage.json,Dockerfileandtsconfig.json.product-crudandfastapi-obsidian-backend.deliverables/suites are self-contained and several are one command from a running stack.eslint.config.*(sonpm run lintfails under ESLint 10, which requires the flat config), andscripts.viteholds a version range where a command belongs. With no lockfile the root dependency tree has also never been scanned for advisories.de284dc— dashboard exports, notebook HTML dumps, loose scripts and archives mixed into the source tree. Unpruned and unclassified.Notes
workflowsrestriction and the SHA-pin policy are not involved.main(440845e). Independent of open PRs feat(product-crud): add production Docker image for the backend #188, fix(product-crud): patch critical vitest advisory + clear npm audit #189, chore: switch root test runner to vitest and scope it to the root project #191.PROBLEMS.mdentries yet, since this PR was scoped to the two files named. Worth a follow-up if you want them tracked with owners like P-001/P-002 are.