If a track is unregistered in Charmhub, it will not be exposed by the `status` command. This is because the StatusCommand shows only the tracks that exist in the `package` part of the response. See this excerpt of a real server response where something is released to `test1/candidate` but then `test1` was unregistered: ``` {'channel-map': [{'base': {'architecture': 'amd64', 'channel': '18.04', 'name': 'ubuntu'}, 'channel': 'test1/candidate', 'expiration-date': None, 'progressive': {'paused': None, 'percentage': None}, 'resources': [], 'revision': 13, 'when': '2022-06-15T16:14:09Z'}, ... ], 'package': {'channels': [{'branch': None, 'fallback': None, 'name': 'latest/stable', 'risk': 'stable', 'track': 'latest'}, {'branch': None, 'fallback': 'latest/stable', 'name': 'latest/candidate', 'risk': 'candidate', 'track': 'latest'}, {'branch': None, 'fallback': 'latest/candidate', 'name': 'latest/beta', 'risk': 'beta', 'track': 'latest'}, {'branch': None, 'fallback': 'latest/beta', 'name': 'latest/edge', 'risk': 'edge', 'track': 'latest'}, {'branch': None, 'fallback': None, 'name': 'test-track/stable', 'risk': 'stable', 'track': 'test-track'}, {'branch': None, 'fallback': 'test-track/stable', 'name': 'test-track/candidate', 'risk': 'candidate', 'track': 'test-track'}, {'branch': None, 'fallback': 'test-track/candidate', 'name': 'test-track/beta', 'risk': 'beta', 'track': 'test-track'}, {'branch': None, 'fallback': 'test-track/beta', 'name': 'test-track/edge', 'risk': 'edge', 'track': 'test-track'}]}, 'revisions': [{'bases': [{'architecture': 'all', 'channel': '18.04', 'name': 'ubuntu'}], 'created-at': '2021-03-05T16:19:34.877239', 'errors': None, 'revision': 13, 'sha3-384': '309439e730c451277b32e03739101621d0d64f89a7fa93852bd140a5af022d2e6f41e4861ee27be980bcf2773e6e87a7', 'size': 810689, 'status': 'released', 'version': '7.4a'}, ... ]} ``` The status report should show the unregesitered track, but flagging it properly. For example, adding `(unregistered)` to its name.