Repository navigation
fix(license): align README and package.json with proprietary LICENSE - #7
Merged
Merged
Conversation
Co-authored-by: The Gaffer <drferdiiskandar@sentrahai.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
drferdi
marked this pull request as ready for review
October 16, 2026 11:00
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This branch was successfully deployed
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
2 participants
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.
Summary
Makes the license declarations consistent with the binding proprietary
LICENSEfile (© 2025–2026 Sentra Healthcare Solutions). Two lines changed, nothing else.Type:
fixScope:
licenseChanges
package.json:"license": "ISC"→"UNLICENSED"README.md§25:ISC © 2026 Sentra Healthcare Solutions→Proprietary — © 2025–2026 Sentra Healthcare Solutions. See LICENSE.Deploy-target evidence (inspected, not edited)
Inspected
docs/deployment.md,.agents/HANDOFF.md,.agents/DECISIONS.md,.github/workflows/ci.yml,.github/workflows/security.yml,project.contract.json; no edits to any of them.Railway evidence (
docs/deployment.md):https://sentrahai.comas "Deployed via Railway".npm run build… andnpm run start".railway.tomlin the project (confirmed: file absent); L59: push tomainauto-deploys; L100–L104: rollback viarailway rollbackor dashboard redeploy.sentra-mainnaming andnpmcommands throughout and carries no post-migration note (comparedocs/testing.md, which explicitly flags its pre-migration sections).Vercel evidence (newer):
.agents/HANDOFF.mdL23–L24 (dated 2026-09-26): next action is "Re-point the Vercel project for sentrahai.com to the root directoryprojects/healthcare/sentraverse(Chief)"..github/workflows/ci.ymlL2 (current standalone CI header): "Deploy ditangani Vercel.".agents/DECISIONS.mdL13: legacy.vercel/directory was excluded from the 2026-09-26 capsule migration (Vercel was in use in the legacy setup).vercel.jsonin the repo (confirmed absent); neither CI workflow deploys (CI = lint+build only,security.yml= audit/license-guard only).Conclusion: repo evidence shows Vercel as the intended current target (newest dated source plus current CI header), but the re-point is recorded as a pending next action, so what actually serves production today — and the authoritative rollback procedure — stays unknown (
belum dikonfirmasi). This matches thebelum dikonfirmasi / not yet confirmedstance recorded in the SPS docs (OPERATIONS.md/RELEASES.md, PR #8).