Repository navigation
Fix web runtime status and document legacy login-service retirement (1.0.8) - #30
Merged
Merged
Conversation
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.
Summary
The Jobs page reported a responding production web server as inactive because Next.js renames its process to
next-server, which the process-name probe misses. The runtime route now uses its own execution as evidence that web is running, while preserving launchd management and restart restrictions.Release 1.0.8 also documents retiring legacy macOS login agents that fail before startup with
Operation not permitted. On the affected Mac, onlycom.media-studio.apiandcom.media-studio.webwere persistently disabled; their plist files and all installation/data files were retained. The Desktop launcher remains the normal startup path.Evidence
After: original HTTP assertion returns both running; Chrome Jobs shows both running with a healthy runner and no console errors. Persistent launchctl state shows both legacy agents disabled.
Merge Danger
Door: two-way
Code is revertable; legacy service configurations are retained. No database changes.
Blast Radius: diagnostics
Web runtime status and macOS troubleshooting documentation. API discovery and access controls are unchanged.