2026-09-20 - 2026-09-21
Overview
140 Issues created by 1 user
Opened
#1 The accessibility check never sees a page state the demo data does not produce
Opened
#2 A budget of zero turns the abandonment ledger off in one layer and on in another
Opened
#3 An add-on a member is meant to hold several times can only be bought once
Opened
#5 Nothing says when the certificate endpoint stops deferring to the old answerer
Opened
#6 A site outside the console cannot tell whether its visitor is signed in
Opened
#4 Everything behind the operator pages is one audience, and deployment-wide settings need a second
Opened
#7 A session ended at the identity provider stays valid in the console for up to five minutes
Opened
#8 Who takes a database backup before migrations run, and what it has to cover
Opened
#9 A member cannot restore their own site from a backup
Opened
#10 Some operator lists read the database once per row
Opened
#11 The billing lists can only be narrowed to one organization by searching for its name
Opened
#12 A transient error reading the billing sweep schedule is read as the schedule being absent
Opened
#13 Members reach a payment page headed by a name the console never showed them
Opened
#14 Nothing runs the project's checks except the person who remembers to
Opened
#15 Two rules the domains registry depends on hold only in Go, while the schema looks like it holds them
Opened
#16 There is no commercial licence to send when someone asks to buy one
Opened
#17 An operator cannot put a minimum term on a subscription
Opened
#18 The member catalog does not say a plan change will wait for the end of a committed term
Opened
#19 The organization page uses four words a reader is expected to already know
Opened
#20 The product and organization pages were assembled part by part and never arranged
Opened
#21 Configuration has grown into a domain of its own with no page that describes it
Opened
#22 A preview of what a change will do is dressed as a warning
Opened
#23 The console connects to its database as a superuser, so the privilege revokes bind nothing
Opened
#24 The console keeps a person signed in for days after the sign-in behind it has expired
Opened
#25 An operator cannot offer a discount code
Opened
#26 Where a record is created, and what the control that opens the form should look like
Opened
#27 A member cannot hold prepaid credit and have it applied to their invoices
Opened
#28 A deployment cannot change the console's colors or add its own styles without forking
Opened
#29 Membership roles carry permissions that nothing checks
Opened
#30 Two generated domain queries have no caller outside their own tests
Opened
#31 Every row of the demo activity feed says the actor is unavailable
Opened
#32 The demo data covers whichever states someone noticed were missing
Opened
#33 The forum mapping tests pass only when another package has run first
Opened
#34 Choosing a domain for a site is a poor experience because the two capabilities are presented as one
Opened
#35 The Domains page hides two sections behind toggles chosen for convenience, not for a reason
Opened
#36 The Domains page lists every served domain and every history row without paging
Opened
#37 The domains registry calls a domain a name and a served domain a placement, and neither word says what it is
Opened
#38 A subscription with a minimum term and a fee policy refuses mid-term changes instead of charging the fee
Opened
#39 When a rule belongs in the database and when in the application
Opened
#40 What a member sees and can do when the entitlement behind their sites lapses
Opened
#41 An entitlement set cannot be taken out of service, only hidden from the operator's pickers
Opened
#42 The check for records left behind by a key change skips customers
Opened
#43 Should someone who proves control of a delegated subdomain be allowed to claim it under a domain another member holds
Opened
#44 The wiki integration reaches into the domains registry directly instead of through the integration contract
Opened
#45 Wiki state and quota enforcement wait for the next poll instead of reacting to the change
Opened
#46 The core database seeds a resource key that belongs to the wiki integration
Opened
#47 The operator's list of wiki sites never shows the limit those sites count against
Opened
#48 Only one test stack at a time can serve browser sign-in to the wiki farm
Opened
#49 What the fourth number on the operator's landing page should be
Opened
#50 A warning about superseding a paid plan is a single symbol with no words
Opened
#51 Capabilities can be recorded as given to a person, and nothing can deliver them
Opened
#52 A deployment without its own website has no front door
Opened
#53 The console has not decided which of the newer front-end library features to use
Opened
#54 Five identity tables store a status the database does not constrain
Opened
#55 A deployment's own settings can only be changed by redeploying it
Opened
#56 A deployment cannot turn off an integration it does not offer
Opened
#57 An integration cannot supply the words that explain it on the pages it owns
Opened
#58 Starting an integration means copying the same mechanical files by hand
Opened
#59 The page that says what an integration needs is not the page where it is set
Opened
#60 Invoice numbers tell any member roughly how much business the deployment does
Opened
#61 Nothing stops a plan ladder from ending up with gaps in its order
Opened
#62 A plan ladder cannot be taken out of service
Opened
#63 The project lint never checks routes an integration registers
Opened
#64 The operator search does not say what it can find, and finds less than it promises
Opened
#65 Nothing stops a text colour that fails the contrast floor from being used again
Opened
#66 A member cannot tell which plan their benefits come from
Opened
#67 A member cannot download an invoice to pass on to whoever does their books
Opened
#68 A metered limit can cover one provider or all of them, with nothing in between
Opened
#69 Five of the HTTP middlewares have no tests of their own
Opened
#70 The model pages do not name the smaller models their rules imply
Opened
#71 Nothing in the console edits the rules that decide which subdomains may be carved
Opened
#72 An operator cannot archive, purge or reassign a wiki site from the console
Opened
#73 An operator cannot change a record's key from its page
Opened
#74 There is no way to see who holds the operator role
Opened
#75 An organization cannot invite another person to work on its sites
Opened
#76 A refusal aimed at a field the form does not have shows nothing at all
Opened
#77 An external system cannot be told when something changes in the console
Opened
#78 The operator has no single place showing what needs attention
Opened
#79 How the operator overview should total money when a deployment bills in several currencies
Opened
#80 What a payments provider port looks like, and which billing code belongs behind it
Opened
#81 A count of pools still waiting to be recomputed never says how long they have waited
Opened
#82 A plan change affecting many organizations applies one outcome to all of them
Opened
#83 Should buying two of something give twice the allowance, and where is that decided
Opened
#84 The person page shows its memberships table without the box every other record page uses
Opened
#85 A member cannot give a script access to their own account
Opened
#86 Should a personal organization's name follow the name of the person who owns it
Opened
#87 A domain that serves something other than a wiki site cannot be recorded as served
Opened
#88 A product cannot be sold as a bundle covering several plan ladders at once
Opened
#89 The plan ladders page and a ladder's own page hold their parts in no considered order
Opened
#90 Should the two operator pages for plans be one page
Opened
#91 On the organization page an allowance, its unit and the control that extends it do not read as one thing
Opened
#92 Nothing defines what a suspended or archived resource pool means
Opened
#93 A person who signs up from another site is not returned to it
Opened
#94 A price can be stored with an amount no page is prepared to show
Opened
#95 Every product carries a category that changes nothing
Opened
#96 A product's page does not say how many organizations hold it
Opened
#97 An operator cannot retire a product; the only way out of the catalog is deleting it
Opened
#98 Creating a product means creating something else first, and the product never shows what it delivers
Opened
#99 A product can point at a set of capabilities that does not exist
Opened
#100 The operator cannot see which payment-provider product a catalog product is mapped to
Opened
#101 Nothing checks that an integration can carry out the work it says it can
Opened
#102 The readiness section calls a product unpurchasable when it was never meant to be sold
Opened
#103 Two plan pages disagree about which end of the list the lowest tier goes
Opened
#104 Which endpoints need a rate limit, and where the limit lives
Opened
#105 The rule form always opens the reduction policy on Clamp, even where the provider can take usage back
Opened
#106 A refund or a dispute at the payment provider is invisible in the console
Opened
#107 When the proxy asks whether a domain may get a certificate, a refusal is logged without the domain
Opened
#108 Account registration still depends on a Keycloak-only endpoint
Opened
#109 A hosted subdomain a member gives up can be claimed by anyone the same minute
Opened
#110 An operator cannot ask which domains and sites an organization holds
Opened
#111 Nothing fails when a new source file ships with no licence header
Opened
#112 The operator role is found in the identity provider's token only at hard-coded claim locations
Opened
#113 There is no way to review which organizations a rule change recomputed
Opened
#114 A rule in a capability set can be added and deleted but never edited
Opened
#115 Two of the four kinds of rule an operator can write deliver nothing
Opened
#116 A rule can be written against a capability no configured provider delivers
Opened
#117 A grant cannot be queued to start when the current one ends
Opened
#118 The screenshot harness cannot reach a page's interaction states
Opened
#119 Taking screenshots resets the database and signs out whoever is using the console
Opened
#120 Screenshots change every day because some cells count from today
Opened
#121 Nothing says which file a new HTTP handler belongs in
Opened
#122 A returning member lands in whichever organization comes first and cannot reach the others
Opened
#123 Should capabilities be grantable without inventing a product to carry them
Opened
#124 Which migration stream owns the trigger function every schema uses
Opened
#125 Creating or deleting a wiki site holds the request open until the work finishes or a timer runs out
Opened
#126 A member cannot host a mirror of a wiki site that lives elsewhere
Opened
#127 What a stacking policy is for, and where an operator would choose one
Opened
#128 Workflow schedules from an earlier configuration keep running after a redeploy
Opened
#129 Nothing measures the storage a member uses, so no storage limit can be offered or enforced
Opened
#130 Should the holder of a domain be able to hand a subdomain to someone else's workspace
Opened
#131 A column named for a payment provider's event holds words that are not events
Opened
#132 Should a date in a table be the same size as the rest of the row
Opened
#133 Tabs, filter pills and navigation pills look alike and do three different things
Opened
#134 The banner calls every figure test data when the console only knows today's connection
Opened
#135 Should the plan overview grid list ladders down the side instead of across the top
Opened
#136 The rule tying a plan change to its direction is written down and not enforced
Opened
#137 A price stores a number of trial days that nothing honors
Opened
#138 Nothing records which members hold voting rights
Opened
#139 Whether a member may create a workspace has never been decided
Opened
#140 Nothing defines what a suspended or archived workspace means